Skip to content

[9.0] Update deployment workflow to reenable CVMFS deployment#8478

Open
atsareg wants to merge 1 commit intointegrationfrom
atsareg-patch-2
Open

[9.0] Update deployment workflow to reenable CVMFS deployment#8478
atsareg wants to merge 1 commit intointegrationfrom
atsareg-patch-2

Conversation

@atsareg
Copy link
Contributor

@atsareg atsareg commented Mar 9, 2026

BEGINRELEASENOTES

*Github actions
FIX: Reenable automatc release deployment in CVMFS

ENDRELEASENOTES

@atsareg atsareg requested a review from fstagni as a code owner March 9, 2026 14:48
@aldbr
Copy link
Contributor

aldbr commented Mar 9, 2026

Is this supposed to solve DIRACGrid/management#11?

@aldbr
Copy link
Contributor

aldbr commented Mar 10, 2026

Have you pushed directly to integration?

@fstagni
Copy link
Contributor

fstagni commented Mar 10, 2026

Have you pushed directly to integration?

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

@atsareg
Copy link
Contributor Author

atsareg commented Mar 10, 2026

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

@atsareg
Copy link
Contributor Author

atsareg commented Mar 10, 2026

@aldbr : No, this was not pushed to the integration directly, it was done in the atsareg-patch- branch and then PR'ed from there.

@aldbr aldbr linked an issue Mar 10, 2026 that may be closed by this pull request
run: |
eval "$(conda shell.bash hook)" && conda activate cvmfs-env
conda install ca-policy-lcg openssl==3.0.7 gct
#conda install ca-policy-lcg openssl==3.0.7 gct
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it's not needed since it's already installed in prepare environment

Suggested change
#conda install ca-policy-lcg openssl==3.0.7 gct

ssh-keyscan cvmfs-upload01.gridpp.rl.ac.uk >> ~/.ssh/known_hosts
gsissh -p 1975 -t cvmfs-upload01.gridpp.rl.ac.uk /home/diracsgm/admin/sync_packages.sh -v
ssh-keyscan cvmfs-uploader-egi.gridpp.rl.ac.uk >> ~/.ssh/known_hosts
gsissh -p 1975 -t cvmfs-uploader-egi.gridpp.rl.ac.uk /home/diracsgm/admin/sync_packages.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity: any reason for removing -v? Won't it be harder to debug without it?

@aldbr
Copy link
Contributor

aldbr commented Mar 10, 2026

Let's try to quickly finish this PR because all PRs currently have pre-commit failures due to the changes introduced in integration.

Also for my education: in DIRACGrid/management#11 (comment), we discussed about moving to another CVMFS repo. What's the status of that?

@fstagni
Copy link
Contributor

fstagni commented Mar 10, 2026

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.

@atsareg
Copy link
Contributor Author

atsareg commented Mar 10, 2026

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

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

Successfully merging this pull request may close these issues.

Always upload releases to CVMFS

3 participants