Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dumping of reprod directory happening after post_package_hook #4541

Open
damianam opened this issue May 23, 2024 · 0 comments
Open

Dumping of reprod directory happening after post_package_hook #4541

damianam opened this issue May 23, 2024 · 0 comments

Comments

@damianam
Copy link
Member

Currently the dump of the reprod directory is happening after the last hook that is package specific. All other hooks after that are not specific to any EB file (with the exception of the hook for testcases, but that does not get executed always, and that happens anyway also before the dump happens).

This is problematic in our case, which is admittedly a bit convoluted. Bear with me:

  • We install via CI once a MR is merged in our private repo
  • The installations via CI are done by a single user that has rights over most of the software stack
  • We want different team members to be responsible for their own packages and be able to do corrections or reinstallations on their own, without having rights over everything else
  • To implement that we rely on ACLs
  • The ACLs are adjusted with a script that is executed with post_package_hook

That script works as intended, but the fact that the reprod directory is dumped after it is executed, messes up that approach, since the owner of that directory is the one that has rights over the whole stack, and so the different team members can not overwrite those installations, because the ACLs are not applied to that directory.

I can think of 2 solutions:

  • Dump the reprod directory during the packaging step
  • Create a new hook for after the dump, but before the end of the build_and_install_loop

Opinions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant