-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat: RPM & DEB package building #3677
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when would a package be published to nexus? or will that be another PR? we could for now cherry pick a 'LTS' by hand. However, if we want to do rapid deploys like we now do but then using this then we should publish an 'experimental' package at every release.
I just added the build process ( I'm still in the testing modus with circleci and ssh debug) We have then 2 repo's per OS (deb & rpm) :
|
Create a process |
Can you give a bit more context? Stable release of what? |
Sorry @EleanorHyde-UMCG i was supposed to type this in the internal issue's. But we need to put up an process (as stated in the roadmap day) to cherry pick an stable release. Let's discuss this later on face2face. |
$NEXUS_USER and $NEXUS_PASS are not available in the shell script anymore? |
Quality Gate passedIssues Measures |
Waiting on selecting a stable version before release. |
What are the main changes you did:
how to test:
todo: