From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Simone Ballarin <simone.ballarin@bugseng.com>,
xen-devel@lists.xenproject.org, consulting@bugseng.com,
Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [XEN PATCH 3/4] automation/eclair: add scheduled pipelines
Date: Wed, 2 Aug 2023 02:05:17 +0200 [thread overview]
Message-ID: <ZMmdvllVvfDz3T92@mail-itl> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2308011545350.2127516@ubuntu-linux-20-04-desktop>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Tue, Aug 01, 2023 at 03:55:20PM -0700, Stefano Stabellini wrote:
> On Tue, 1 Aug 2023, Simone Ballarin wrote:
> > This patch introduces six new ECLAIR jobs that run only
> > when triggered by a GitLab scheduled pipeline.
> >
> > Signed-off-by: Simone Ballarin <simone.ballarin@bugseng.com>
> > ---
> > +.eclair-analysis:on-schedule:
> > + extends: .eclair-analysis
> > + rules:
> > + - if: $CI_PIPELINE_SOURCE == "schedule"
>
> If I understand this right, the idea is that someone would schedule a
> pipeline (Build -> "Pipeline Schedules") and as part of that, they would
> also define the variable "CI_PIPELINE_SOURCE" to schedule.
No, this is pre-defined variable in gitlab:
https://docs.gitlab.com/ee/ci/variables/predefined_variables.html
>
> Is that correct?
>
> If so, please add a good in-code comments here on top of
> .eclair-analysis:on-schedule to explain it. So that someone reading this
> might know how what to do with the Gitlab CI settings.
>
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-02 0:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 9:57 [XEN PATCH 0/4] automation/eclair: improvements to the ECLAIR integration Simone Ballarin
2023-08-01 9:57 ` [XEN PATCH 1/4] automation/eclair: add support for tag pipelines Simone Ballarin
2023-08-01 22:54 ` Stefano Stabellini
2023-08-02 7:43 ` Simone Ballarin
2023-08-01 9:57 ` [XEN PATCH 2/4] automation/eclair: add direct link to reports Simone Ballarin
2023-08-01 22:55 ` Stefano Stabellini
2023-08-01 9:57 ` [XEN PATCH 3/4] automation/eclair: add scheduled pipelines Simone Ballarin
2023-08-01 22:55 ` Stefano Stabellini
2023-08-02 0:05 ` Marek Marczykowski-Górecki [this message]
2023-08-02 0:08 ` Stefano Stabellini
2023-08-02 7:39 ` Simone Ballarin
2023-08-01 9:57 ` [XEN PATCH 4/4] automation/eclair: avoid failure in case of missing merge point Simone Ballarin
2023-08-01 22:55 ` Stefano Stabellini
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=ZMmdvllVvfDz3T92@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=simone.ballarin@bugseng.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.