-
Task
-
Resolution: Fixed
-
Minor
See details in attached links.
Currently the project uses a snapshot version of Jenkins to consume API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository master branch.
Thus, the Jenkins version used in the project will need to be updated once the changes have been merged into the upstream Jenkins main repository and released publicly for use.
[JENKINS-55489] Update Jenkins upstream version from snapshot
Epic Link |
New:
|
Remote Link | New: This issue links to "Jira discussion comment on upstream update (Web Link)" [ 22172 ] |
Remote Link | New: This issue links to "Pull Request containing required changes to be merged into Jenkins (Web Link)" [ 22173 ] |
Description |
Original:
See details in attached link. Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repo branch. Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repo and released publicly. |
New:
See details in attached links. Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository branch. Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repository and released publicly. |
Description |
Original:
See details in attached links. Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository branch. Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repository and released publicly. |
New:
See details in attached links. Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository branch. Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repository and released publicly for use. |
Description |
Original:
See details in attached links. Currently the project uses a snapshot version of Jenkins to consume the API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository branch. Thus, the Jenkins version used in the project will need to be updated once the upstream changes have been merged into the Jenkins main repository and released publicly for use. |
New:
See details in attached links. Currently the project uses a snapshot version of Jenkins to consume API changes, as the changes the snapshot contains have yet to be merged into the Jenkins main repository master branch. Thus, the Jenkins version used in the project will need to be updated once the changes have been merged into the upstream Jenkins main repository and released publicly for use. |
Rank | New: Ranked higher |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | New: David Olorundare [ mide ] |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |