Skip to content

Conversation

@olblak
Copy link
Member

@olblak olblak commented Jul 9, 2020

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

@olblak
Copy link
Member Author

olblak commented Jul 16, 2020

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

README.adoc Outdated
.. `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
Copy link
Contributor

Choose a reason for hiding this comment

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

Improperly resolved merge conflict.

@oleg-nenashev
Copy link
Contributor

Putting on hold as requested by @olblak

olblak and others added 2 commits November 3, 2020 11:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants