[9.0] Update deployment workflow to reenable CVMFS deployment#8478
[9.0] Update deployment workflow to reenable CVMFS deployment#8478fstagni merged 2 commits intointegrationfrom
Conversation
|
Is this supposed to solve DIRACGrid/management#11? |
|
Have you pushed directly to |
Yes, it was a faster way to test. Now there's a whitespace to fix in the content of cvmfs.yml which is in integration |
|
Yes, I did testing by editing the action yaml in place in Github and then made the PR from there as well. Of course this bypasses the pre-commit hooks. Will fix it quickly. And yes, it solves once again the DIRACGrid/management#11 |
|
@aldbr : No, this was not pushed to the integration directly, it was done in the atsareg-patch- branch and then PR'ed from there. |
31442a8 to
2dfc293
Compare
|
Let's try to quickly finish this PR because all PRs currently have Also for my education: in DIRACGrid/management#11 (comment), we discussed about moving to another CVMFS repo. What's the status of that? |
That's something that needs some design. |
|
They, at RAL, made effort to improve their CVMFS environment. For the moment, it is working. They are still looking at monitoring that all the updates are guaranteed to be synchronized quickly. Let's see |
Co-authored-by: aldbr <aldbr@outlook.com>
BEGINRELEASENOTES
*Github actions
FIX: Reenable automatc release deployment in CVMFS
ENDRELEASENOTES