From: "Philippe Mathieu-Daudé" <firstname.lastname@example.org> To: "Thomas Huth" <email@example.com>, "Alex Bennée" <firstname.lastname@example.org>, "Daniel P . Berrangé" <email@example.com> Cc: Willian Rampazzo <firstname.lastname@example.org>, email@example.com, Stefan Hajnoczi <firstname.lastname@example.org>, Wainer dos Santos Moschetta <email@example.com> Subject: Re: [RFC PATCH 5/5] gitlab-ci.d/crossbuilds.yml: Enable compilation with ccache Date: Wed, 14 Apr 2021 12:35:41 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 4/14/21 12:29 PM, Philippe Mathieu-Daudé wrote: > On 4/14/21 10:19 AM, Thomas Huth wrote: >> Ccache can speed up the compilation in some cases, so enable it for >> our cross-compilation CI builds, too. >> >> Signed-off-by: Thomas Huth <firstname.lastname@example.org> >> --- >> .gitlab-ci.d/crossbuilds.yml | 28 ++++++++++++++++++++++++++++ >> 1 file changed, 28 insertions(+) >> >> diff --git a/.gitlab-ci.d/crossbuilds.yml b/.gitlab-ci.d/crossbuilds.yml >> index 017731a894..dee327a936 100644 >> --- a/.gitlab-ci.d/crossbuilds.yml >> +++ b/.gitlab-ci.d/crossbuilds.yml >> @@ -1,4 +1,26 @@ >> + >> +.ccache_cross_setup: >> + cache: >> + key: "$CI_JOB_NAME" >> + paths: >> + - ccache > > I discovered last month the cache/artifact passing feature is useful > when all runners are in the same premises, but when you used runner > in different locations it become slower (except if all your runners > are in very fast clouds probably). > > Not a short term problem, but can hit us long term. I haven't looked > if GitLab already figured how to manage this globally, like registering > runners with affinity, or assigning them to pools. > > If we decide to stick with the free-tier runners, then this is a great > improvement. > > For custom runners, a simple kludge is to assert they do *not* use > cache/artifacts (from free-tier runners). > > We could restrict this to free-tier runners but these runners tag aren't > standardized, and AFAIK we can not (yet?) use the "ANY" word to "select > runners with any of this tag list". So far I noticed gitlab uses these: > - shared docker > - gce docker > - gitlab-org > - gitlab-org-docker > > The last 2 are recent, and seem to help with the problem I reported > that some runners don't have Docker installed: > https://lists.gnu.org/archive/html/qemu-devel/2021-04/msg02213.html Actually found the doc for the last 2: https://docs.gitlab.com/ee/user/gitlab_com/#linux-shared-runners - gitlab-org-docker All your CI/CD jobs run on n1-standard-1 instances with 3.75GB of RAM, CoreOS and the latest Docker Engine installed. Instances provide 1 vCPU and 25GB of HDD disk space. The default region of the VMs is US East1. Each instance is used only for one job, this ensures any sensitive data left on the system can’t be accessed by other people their CI jobs. - gitlab-org The gitlab-shared-runners-manager-X.gitlab.com fleet of runners are dedicated for GitLab projects as well as community forks of them. They use a slightly larger machine type (n1-standard-2) and have a bigger SSD disk size. They don’t run untagged jobs and unlike the general fleet of shared runners, the instances are re-used up to 40 times.
next prev parent reply other threads:[~2021-04-14 10:37 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-14 8:19 [RFC PATCH 0/5] Use ccache in the gitlab-CI Thomas Huth 2021-04-14 8:19 ` [RFC PATCH 1/5] tests/docker/dockerfiles: Add ccache to containers where it was missing Thomas Huth 2021-04-14 8:19 ` [RFC PATCH 2/5] tests/docker/dockerfiles/ubuntu2004: Add missing symlink for cc Thomas Huth 2021-04-14 10:16 ` Philippe Mathieu-Daudé 2021-04-14 8:19 ` [RFC PATCH 3/5] gitlab-ci.d/crossbuilds: Limit the amount of targets in the cross-win64 build Thomas Huth 2021-04-14 8:19 ` [RFC PATCH 4/5] gitlab-ci.yml: Compile with ccache enabled Thomas Huth 2021-04-14 8:19 ` [RFC PATCH 5/5] gitlab-ci.d/crossbuilds.yml: Enable compilation with ccache Thomas Huth 2021-04-14 10:29 ` Philippe Mathieu-Daudé 2021-04-14 10:35 ` Philippe Mathieu-Daudé [this message] 2021-04-14 10:31 ` [RFC PATCH 0/5] Use ccache in the gitlab-CI Stefan Hajnoczi
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC PATCH 5/5] gitlab-ci.d/crossbuilds.yml: Enable compilation with ccache' \ /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
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).