[FOLIO-651] Capture snapshot version of Gradle projects by reading Jar file manifest Created: 07/Jun/17 Updated: 12/Nov/18 Resolved: 19/Jul/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 6 hours | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Jenkins Pipeline includes a function which will read the manifest of Jar file so we should be able to capture and tag artifacts with the the snapshot versions of Gradle-based projects, mod-inventory and mod-circulation like we currently do for Maven-based projects. Create pipeline jobs using this function for these two modules. |
| Comments |
| Comment by John Malconian [ 19/Jul/17 ] |
|
Jenkins pipeline scripts have been added to both gradle-based projects - mod-inventory and mod-circulation which parse the snapshot version information from build.gradle and create docker images for modules with the snapshot version appended by the Jenkins build number. |