From: Ali Alnubani <alialnu@nvidia.com>
To: David Marchand <david.marchand@redhat.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Cc: "ci@dpdk.org" <ci@dpdk.org>, Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-ci] GitHub Actions status in patchwork
Date: Tue, 15 Dec 2020 14:24:11 +0000 [thread overview]
Message-ID: <DM6PR12MB4910BA13D2E65178C18BD353DAC60@DM6PR12MB4910.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zT2NAStXQhZW8RsVNt4KQ89GarE9OT4OXVnZVVdDaRAg@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, December 15, 2020 2:09 PM
> To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
> Cc: Ali Alnubani <alialnu@nvidia.com>; ci@dpdk.org; Aaron Conole
> <aconole@redhat.com>
> Subject: Re: GitHub Actions status in patchwork
>
> On Tue, Dec 15, 2020 at 11:14 AM Thomas Monjalon
> <thomas@monjalon.net> wrote:
> >
> > 15/12/2020 09:28, Ali Alnubani:
> > > From: David Marchand <david.marchand@redhat.com>
> > > > Now that GitHub actions have been added in the main branch, could
> > > > you add a link to the last run for the main branch in patchwork
> > > > like what we already have for Travis?
> > >
> > > Done. Thanks for working on this.
> >
> > Should we remove the badge for Travis?
>
> We don't have enough credits to run jobs on the main branch and we can
> end up with contradicting status from GHA and Travis CI.
> I disabled Travis CI build on push for the dpdk-replication: it's better to keep
> the credits for builds if we ever need them.
> Yes, let's remove the badge for the main branch.
>
Removed.
Regards,
Ali
next prev parent reply other threads:[~2020-12-15 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 16:33 David Marchand
2020-12-15 8:28 ` Ali Alnubani
2020-12-15 10:14 ` Thomas Monjalon
2020-12-15 12:08 ` David Marchand
2020-12-15 14:24 ` Ali Alnubani [this message]
2020-12-15 15:22 ` David Marchand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM6PR12MB4910BA13D2E65178C18BD353DAC60@DM6PR12MB4910.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).