From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] gitlab-ci: Add full nightly build
Date: Tue, 1 Oct 2019 08:11:15 +0200 [thread overview]
Message-ID: <3625acaa-cfac-7f97-c088-d7f98dcb85ec@siemens.com> (raw)
In-Reply-To: <aa219f54-40e5-5054-841d-c2cf69e25e71@siemens.com>
On 30.09.19 14:20, [ext] Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Add a job that can be scheduled for nightly build. It performs a full CI
> run, but only if its commit SHA wasn't tried to build yet.
>
More precisely, only successful builds count. I was hoping that the cache would
be filled unconditionally, but that's only the case when the job succeeded.
Anyway, rerunning has a use case as well: failing network connections.
Jan
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> I've now set up our CI to perform this for jan/next.
>
> .gitlab-ci.yml | 27 ++++++++++++++++++++++++---
> 1 file changed, 24 insertions(+), 3 deletions(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 5c64adc..dd6e12b 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -3,17 +3,38 @@ image: kasproject/kas-isar:latest
> variables:
> GIT_STRATEGY: clone
>
> -all:
> +.common-build: &common-build
> stage: build
> - script:
> + before_script:
> - export http_proxy=$HTTP_PROXY
> - export https_proxy=$HTTPS_PROXY
> - export ftp_proxy=$FTP_PROXY
> - export no_proxy=$NO_PROXY
> - - scripts/ci_build.sh -q -f
> artifacts:
> name: "logs-$CI_JOB_ID"
> paths:
> - build/tmp/work/*/*/*/temp
> when: on_failure
> expire_in: 1 week
> +
> +fast-ci:
> + <<: *common-build
> + except:
> + - schedules
> + script:
> + - scripts/ci_build.sh -q -f
> +
> +full-ci:
> + <<: *common-build
> + only:
> + - schedules
> + script:
> + - PREVIOUS_SHA="$(cat .CI_COMMIT_SHA || true)"
> + - if [ "$CI_COMMIT_SHA" != "$PREVIOUS_SHA" ]; then
> + echo "$CI_COMMIT_SHA" > .CI_COMMIT_SHA;
> + scripts/ci_build.sh -q -c -r -s;
> + fi
> + cache:
> + key: "$CI_COMMIT_REF_SLUG"
> + paths:
> + - .CI_COMMIT_SHA
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-10-01 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 12:20 Jan Kiszka
2019-10-01 6:11 ` Jan Kiszka [this message]
2019-10-24 12:30 ` Baurzhan Ismagulov
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=3625acaa-cfac-7f97-c088-d7f98dcb85ec@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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