qemu-devel
[Top][All Lists]
Advanced

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

Re: [PATCH 0/5] QEMU Gating CI


From: Cleber Rosa
Subject: Re: [PATCH 0/5] QEMU Gating CI
Date: Mon, 16 Mar 2020 08:04:13 -0400 (EDT)


----- Original Message -----
> From: "Peter Maydell" <address@hidden>
> To: "Cleber Rosa" <address@hidden>
> Cc: "Alex Bennée" <address@hidden>, "QEMU Developers" <address@hidden>, "Fam 
> Zheng" <address@hidden>,
> "Eduardo Habkost" <address@hidden>, "Beraldo Leal" <address@hidden>, 
> "Philippe Mathieu-Daudé"
> <address@hidden>, "Thomas Huth" <address@hidden>, "Wainer dos Santos 
> Moschetta" <address@hidden>, "Erik
> Skultety" <address@hidden>, "Willian Rampazzo" <address@hidden>, "Wainer 
> Moschetta" <address@hidden>
> Sent: Monday, March 16, 2020 7:57:33 AM
> Subject: Re: [PATCH 0/5] QEMU Gating CI
> 
> On Thu, 12 Mar 2020 at 22:16, Cleber Rosa <address@hidden> wrote:
> > The quick answer is:
> >
> >  $ git push address@hidden:qemu-project/qemu.git my-branch:staging
> 
> So I did this bit...
> 
> > Once that push happens, you could use:
> >
> >  $ contrib/ci/scripts/gitlab-pipeline-status --verbose --wait
> 
> ...but this script just says:
> 
> $ ./contrib/ci/scripts/gitlab-pipeline-status --verbose --wait
> ERROR: No pipeline found
> failure
> 

Hi Peter,

A few possible reasons come to my mind:

1) It usually takes a few seconds after the push for the pipeline to

2) If you've pushed to a repo different than gitlab.com/qemu-project/qemu,
   you'd have to tweak the project ID (-p|--project-id).

3) The local branch is not called "staging", so the script can not find the
   commit ID, in that case you can use -c|--commit.

> thanks
> -- PMM
> 
> 

Please let me know if any of these points helps.

Cheers,
- Cleber.




reply via email to

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