-
Notifications
You must be signed in to change notification settings - Fork 22
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
[WIP][INFRA-1363] Add pkgServer promotion mechanism #88
Open
olblak
wants to merge
4
commits into
jenkins-infra:master
Choose a base branch
from
olblak:INFRA-1363
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+62
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It doesn't seem to be possible to cleanup duplicate package entry other than being sure that no packages could be present in both directories at the same time |
daniel-beck
reviewed
Aug 5, 2020
README.adoc
Outdated
@@ -345,6 +345,7 @@ The security release follows the same process as the stable one except that arti | |||
.. `JENKINS_VERSION` set to the final release version that will be packaged. If set to 'stable' or 'weekly' then the packaging job will try to guess the version based on what was pushed to the maven repository. cfr settings. | |||
.. `PACKAGING_GIT_BRANCH` set to the appropriated jenkinsci/packaging branch | |||
.. `MAVEN_REPOSITORY_NAME` set to the maven repository name where we are going to publish staging maven artifacts. This is also the source location used by the packaging job to build distribution packages | |||
<<<<<<< HEAD |
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.
Improperly resolved merge conflict.
Putting on hold as requested by @olblak |
olblak
commented
Nov 3, 2020
Signed-off-by: Olivier Vernin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is an untested attempt to have packages promotion mechanism.
In order to work we'll have to update the jenkinsci/packaging repository to be sure that be default we push packages to a staging directory instead that the production as defined here
Remark: In the current state, generating pkg.jenkins.io website data need to be refactored as it requires distribution to be in the production directory