[FOLIO-1116] Disable Jenkins release jobs for backend modules Created: 09/Mar/18 Updated: 12/Nov/18 Resolved: 16/May/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | David Crossley |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint34, sprint37, sprint38 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 4 hours, 15 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Description |
|
With an update to a Jenkins plugin, it is no longer necessary to have separate "release" jobs in Jenkins for java-based server-side modules. The existing pipeline job that builds snapshot releases for java-based server-side modules has been updated (
|
| Comments |
| Comment by John Malconian [ 09/Mar/18 ] |
|
Still need to update developer documentation and disable existing release jobs in Jenkins. |
| Comment by John Malconian [ 13/Mar/18 ] |
|
I've disabled all previous Jenkins release jobs in the "Release Jobs" folder with the exception of RMB and Okapi. Those two jobs are a bit different so release artifacts for those two projects should continue to use the jobs in the Release Jobs folder. All other backend module artifact releases can now be triggered manually from the Tags tab in the Github folio-org folder for each project. Just to be clear, nothing else has changed in the release process (for devs) except for the location of the job in Jenkins that needs to be triggered. |
| Comment by John Malconian [ 01/May/18 ] |
|
David Crossley - Can I assign this to you to complete? The Dev release documentation should be updated to reflect the change in the above comment. |
| Comment by David Crossley [ 16/May/18 ] |
|
Done. Also tidied and removed other old sections. See dev.folio.org/guidelines/release-procedures/#build-and-release-artifacts when the cache refreshes. |