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

Prerequisites for Artifactory & Jenkins migration/upgrade #5293

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

Cervator
Copy link
Member

@Cervator Cervator commented Dec 1, 2024

This fixes an apparent syntax issue in a newer Jenkinsfile and attempts to refresh the support to test a different Artifactory URL via alternativeResolutionRepo in a gradle.properties copied (manually due to something else that broke) from the templates directory to the project root

Tested over at https://jenkins.nanoware.us/job/repatriation/job/terasologyengine/job/mbdev/ (building Nanoware/Terasology/mbdev) as infra migration / upgrades are sort of tricky to test normally. Plus the Nanoware org job line in the current Jenkins is actually empty, partly because moving from the fancy Cloudbees Jenkins lost us a plugin that let you set easy properties at the folder level - which allowed all Nanoware jobs to automatically swap to a different set of Artifactory registries :-(

Or rather, lol, it would be tested there, but apparently I've run up against an SSD quota within GCP since I have two 200 GB Jenkins disks and some smaller stuff (including the build agent for the current test) and apparently the default limit is 500 GB? Who knew. Submitted a request to increase and will also decrease the Jenkins disk as we haven't needed that much space for a long time at this point.

Odds are this PR will fail testing here, and I may have to merge it on the spot when I get a chance to try swapping DNS over to the new stuff to start validating and rebuilding all the things. I count it a breaking change not to the game but logistics-wise - some stuff is likely to blow up till everything is trickled out to everywhere.

I've largely kept https://github.com/MovingBlocks/Logistics/tree/repatriation updated with new infra config and docs, but there's a bit more to come

@Cervator Cervator added Category: Build/CI Requests, Issues and Changes targeting gradle, groovy, Jenkins, etc. Breaking Change API breaking change requiring follow-up work in dependant areas labels Dec 1, 2024
@Cervator Cervator self-assigned this Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change API breaking change requiring follow-up work in dependant areas Category: Build/CI Requests, Issues and Changes targeting gradle, groovy, Jenkins, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant