[FOLIO-846] release UI modules through the CI Created: 19/Sep/17 Updated: 12/Nov/18 Resolved: 06/Sep/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | build-release, ci, montreal, sprint23, sprint43, sprint44, sprint45, sprint46 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 hour | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
During the plenary we decided that setting 'fixVersion' in Jira will be done during the sprint planning meeting (when we pull issues into the sprint). For UI modules the expectation is that the release happens at the end of the sprint cycle so that we are able to construct a working system at the end of the sprint. For library dependencies not all planning will happen in this way but even if it does we need to be able to detect unreleased dependencies (e.g stripes-*) during the build that effectively prevent us from constructing a stable system. |
| Comments |
| Comment by John Malconian [ 06/Sep/18 ] |
|
UI module artifacts can now be released via FOLIO Jenkins as long as the release has been tagged in Git first. Log into https://jenkins-aws.indexdata.com first with your folio-org Github credentials. Select the project you want to release under the GitHub 'folio-org' folder and select the 'Tags' tab. Select the Git tag you want to release, and, if you have the necessary permissions, run 'Build Now' to build the release artifacts. Release documentation updated. |