From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Yonggang Luo <luoyonggang@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
"Philippe Mathieu-Daudиж" <f4bug@amsat.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"QEMU Devel" <qemu-devel@nongnu.org>,
"Alex Bennижe" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 1/2] ci: Add github workflow for getting cirrus working properly
Date: Wed, 23 Mar 2022 09:20:17 +0000 [thread overview]
Message-ID: <YjrmUStDoWnk/t4A@redhat.com> (raw)
In-Reply-To: <20220322191409.1330-2-luoyonggang@gmail.com>
On Wed, Mar 23, 2022 at 03:14:08AM +0800, Yonggang Luo wrote:
> Signed-off-by: Yonggang Luo <luoyonggang@gmail.com>
> ---
> .github/workflows/main.yml | 29 +++++++++++++++++++++++++++++
> MAINTAINERS | 4 +++-
> 2 files changed, 32 insertions(+), 1 deletion(-)
> 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..85a392b962
> --- /dev/null
> +++ b/.github/workflows/main.yml
> @@ -0,0 +1,29 @@
> +# 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: sudo apt install perl
> + - name: Checkpatch
> + run: |
> + git fetch https://git.qemu.org/git/qemu.git master
> + git tag base_tag_to_rebase FETCH_HEAD --force
> + ./scripts/checkpatch.pl --mailback base_tag_to_rebase..
I really don't think we want to start duplicating our CI efforts into
GitHub. We are using GitLab as our primary hosting platform for QEMU,
and have standardized on using GitLab for CI, only using Cirrus CI
and Travis for specific non-x86 or non-Linux tasks.
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 :|
next prev parent reply other threads:[~2022-03-23 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 19:14 [PATCH v2 0/2] CI fixes Yonggang Luo
2022-03-22 19:14 ` [PATCH v2 1/2] ci: Add github workflow for getting cirrus working properly Yonggang Luo
2022-03-23 7:44 ` Thomas Huth
2022-03-23 7:54 ` 罗勇刚(Yonggang Luo)
2022-03-23 9:20 ` Daniel P. Berrangé [this message]
2022-03-22 19:14 ` [PATCH v2 2/2] cirrus: upgrade mingw base packages Yonggang Luo
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=YjrmUStDoWnk/t4A@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=f4bug@amsat.org \
--cc=luoyonggang@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/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).