public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/4] Fix ccache issues
Date: Sun, 2 Apr 2023 20:44:38 +0200	[thread overview]
Message-ID: <ZCnNFv8Q2HsEaglJ@ilbers.de> (raw)
In-Reply-To: <9c4580332e0520197ed589f26af61c89ca8bb955.camel@siemens.com>

On 2023-03-29 12:43, Moessbauer, Felix wrote:
> > You might have /ccache/a/ created earlier by 'root', and not it can't
> > create a 
> > subdir as sbuild user.
> 
> Hi, this could very well be the case. However, when running in a CI on
> a project with multiple branches (e.g. during feature integration),
> this situation cannot be avoided. The cache is shared across all builds
> of a single project, but these builds might use different ISAR
> versions.
> 
> This technically means, we need to update all branches of the project
> in a lockstep to be able to re-enable the ccache.
> 
> It would be good if we could find a way to avoid this situation.

What about sudo addgroup ccache; sudo adduser build ccache; sudo chgrp -R
ccache /ccache; sudo chmod -R g+w /ccache; find /ccache -type d |sudo xargs
chmod g+s? Maybe also sudo adduser root ccache.

With kind regards,
Baurzhan

  parent reply	other threads:[~2023-04-02 18:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  7:56 Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 1/4] ccache: fix dirs creation Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 2/4] ccache: fix CCACHE_DIR owner for sbuild Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 3/4] meta: unify cross selection Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 4/4] ccache: separate cache based on cross compile Anton Mikanovich
2023-02-13  8:01 ` [PATCH v2 0/4] Fix ccache issues Anton Mikanovich
2023-03-27  5:27 ` Uladzimir Bely
2023-03-28 15:51   ` Moessbauer, Felix
2023-03-28 15:56     ` Uladzimir Bely
2023-03-29 12:43       ` Moessbauer, Felix
2023-03-30  7:37         ` Uladzimir Bely
2023-04-02 18:44         ` Baurzhan Ismagulov [this message]
2023-04-05 11:56           ` Moessbauer, Felix
2023-04-05 13:28             ` Baurzhan Ismagulov
2023-04-10  5:44               ` Moessbauer, Felix

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=ZCnNFv8Q2HsEaglJ@ilbers.de \
    --to=ibr@radix50.net \
    --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