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
Migration of build.libelektra.org #3139
Comments
Currently we have a Jenkins server online. Pipeline needs to be created, so does the nodes. |
I personally have Jenkins as a Docker image, with the home being a volume I don't delete (-v jenkins_home:/var/jenkins_home). I can then simply remove outdated Jenkins Docker images by fetching new ones, with the home always persisted, thus having quite simple upgrade paths. I used this for >2 years with regular updates to everything. Maybe I have a too simplistic view but is it not possible to simply:
|
I would have also done it like @mpranj describes (I did step 1). But we can check if @Mistreated is able to recreate everything. The advantage of recreating would be that we get a more up-to-date docu and everything is clean afterwards (at the moment we have many outdated jobs). |
Status update:
Currently Im having this error:
Edit:
|
Thank you for the status report! According the system log the credentials for hooks are missing. I gave elektrabot more rights. |
Hooks should be fine now. Is there a possibility to close the #809 PR? |
done |
Same thing happens with #769.
Could it be that these PRs are outdated? Edit: I took the liberty to close #769. Now the repo is scanned completely. |
What happens?
Yes, they are. Good that you closed them. #323 might still be relevant, though. But it is possible to reopen, so it should not be a big deal.
Good hint, the rescan also helped on the old buildserver to function again. I hope this rescan of the old server did not make troubles on the new server?
Please write me always and immediately by email about all credentials you (might) need. But what are docker-hub-elektra-jenkins credentials? Do you mean the docker registry on a7? |
This:
#323 isnt closed. There was no null pointer there.
I wrote an email. |
@ingwinlu can you help us out with the docker-hub-elektra-jenkins credentials? @Mistreated is something else missing besides the docker-hub-elektra-jenkins credentials? |
Status update: Build fails on
Probalby some plugin error. Edit: fixed. |
Yes.
Which plugin was it? So the status now is that copying the artifacts fails? |
Pipeline Utility Steps
Jenkins publishes on 2 servers, |
Maybe we can publish everything on doc.libelektra.org? It would be good if we reduce what is running on a7 as it would make the setup easier. (maybe except of the docker registry, for performance reasons) As I see it, the Debian packages are the only thing to be published on a7, which does not work satisfactory anyway as it does not support multiple repositories, but we need this now: Debian and Ubuntu. |
Migration mostly done. |
This issue is about the migration of build.libelektra.org to the new server. #160 is only for the essential stuff (downtime), here we can discuss details.
From #2967:
I hope we can finally move to the new build server before we run into this problem again!
@Mistreated what is the status?
The text was updated successfully, but these errors were encountered: