public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/2] ci: add support for sstate cache
Date: Thu, 18 Dec 2025 11:57:17 +0000	[thread overview]
Message-ID: <4fc80c2806a1a4cc3b3019c437b76af83d59f4dd.camel@siemens.com> (raw)
In-Reply-To: <20251218073853.41121-3-felix.moessbauer@siemens.com>

On Thu, 2025-12-18 at 08:38 +0100, Felix Moessbauer wrote:
> The gitlab CI jobs should finish in a timely manner to give quick
> feedback to the developer. By running the tests with sstate cache,
> simple changes require far less CI time.
> 
> We prepare the gitlab ci job description to pick up the sstate cache
> configuration from the environment and enable the caching for all jobs
> (we always enable it, even if running without sstate cache, as then the
> cache is simply thrown away later on). We further introduce a (manual)
> info task to show the state of the cache, as well as a cleanup task to
> drain the cache.
> 
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  .gitlab-ci.yml | 34 ++++++++++++++++++++++++++++------
>  1 file changed, 28 insertions(+), 6 deletions(-)
> 
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 1a7abcb8..9bd8ff07 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -12,6 +12,14 @@ variables:
>      - export ftp_proxy=$FTP_PROXY
>      - export no_proxy=$NO_PROXY
>      - export DISTRO_APT_PREMIRRORS=$DISTRO_APT_PREMIRRORS
> +  after_script:
> +    - |
> +      if [[ -n "${SSTATE_LOCATION}" ]] && [[ -d "sstate-cache" ]]; then
> +        echo "=== Upload sstate artifacts to ${SSTATE_LOCATION} ==="
> +        ./scripts/isar-sstate upload "sstate-cache" "${SSTATE_LOCATION}"
> +        ./scripts/isar-sstate info -v "${SSTATE_LOCATION}"
> +      fi

We need to increase the timeout of the after_script, as otherwise not
all artifacts might be uploaded on larger runs like "-t fast". We need
to add [1]

variables:
  RUNNER_AFTER_SCRIPT_TIMEOUT: 15m

I'll add it in case a v2 is needed. Otherwise it can also be added
later one, when more evidence around resonable timeouts are gathered.

[1]
https://docs.gitlab.com/ci/runners/configure_runners/#set-script-and-after_script-timeouts

Felix

-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/4fc80c2806a1a4cc3b3019c437b76af83d59f4dd.camel%40siemens.com.

      reply	other threads:[~2025-12-18 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18  7:38 [PATCH 0/2] Enable SState cache in GitLab CI 'Felix Moessbauer' via isar-users
2025-12-18  7:38 ` [PATCH 1/2] testsuite: forward SSTATE_MIRRORS into CI env on sstate 'Felix Moessbauer' via isar-users
2025-12-18  7:38 ` [PATCH 2/2] ci: add support for sstate cache 'Felix Moessbauer' via isar-users
2025-12-18 11:57   ` 'MOESSBAUER, Felix' via isar-users [this message]

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=4fc80c2806a1a4cc3b3019c437b76af83d59f4dd.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.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