qemu-trivial
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v3 2/3] ci: Add empty github workflow for reporting historica


From: Yonggang Luo
Subject: Re: [PATCH v3 2/3] ci: Add empty github workflow for reporting historical cirrus result at github
Date: Wed, 23 Mar 2022 19:35:35 +0800



On Wed, Mar 23, 2022 at 5:33 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> On Wed, Mar 23, 2022 at 04:07:54PM +0800, Yonggang Luo wrote:
> > Looks like https://github.com/lygstate/qemu/actions does
> >
> > Signed-off-by: Yonggang Luo <luoyonggang@gmail.com>
> > ---
> >  .github/workflows/main.yml | 24 ++++++++++++++++++++++++
> >  MAINTAINERS                |  1 +
> >  2 files changed, 25 insertions(+)
> >  create mode 100644 .github/workflows/main.yml
> >
> > diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> > new file mode 100644
> > index 0000000000..71f5fbd556
> > --- /dev/null
> > +++ b/.github/workflows/main.yml
> > @@ -0,0 +1,24 @@
> > +# This is a basic workflow to help you get started with Actions
> > +
> > +name: CI
> > +
> > +# Controls when the action will run. Triggers the workflow on push or pull request
> > +# events but only for the master branch
> > +on:
> > +  push:
> > +    branches: [ master ]
> > +  pull_request:
> > +    branches: [ master ]
> > +
> > +# A workflow run is made up of one or more jobs that can run sequentially or in parallel
> > +jobs:
> > +  check-patch:
> > +    name: Check Patch
> > +    runs-on: ubuntu-latest
> > +    steps:
> > +      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
> > +      - uses: actions/checkout@v2
> > +        with:
> > +          fetch-depth: 0
> > +      - name: Install dependent packages
> > +        run: echo "Empty action"
>
> I really rather we just integrated the Cirrus CI windows job into our GitLab
> pipeline using cirrus-run, as we did for the other Cirrus jobs.
>
> We've also already got some native msys jobs under GitLab that test some
> combinations, but not all since they're somewhat slow. So we still need
> to take advantage of Cirrus for some msys testing, but we can likely
> reduce the overlap.
>
> I definitely don't want to see us increasing our use of GitHub, as having
> multiple places to look at for CI results is a really bad thing. We want
> todo what is possible to make GitLab the single dashboard for all CI info.

Agreed a single dashboard is meaningfull, I'll try that. other than that, a empty
github actions can give better experience with qemu, there is 3.9k for at github,
and 5.9k star at github 

>
>
> With regards,
> Daniel
> --
> |: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-            https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
>


--
         此致

罗勇刚
Yours
    sincerely,
Yonggang Luo

reply via email to

[Prev in Thread] Current Thread [Next in Thread]