[FOLIO-1742] build and deploy platform-core/master daily Created: 25/Jan/19 Updated: 03/Jun/20 Resolved: 04/Apr/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | Core: Platform - Sprint 60, Core: Platform - Sprint 57 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||
| Description |
|
Description: A scheduled job in Jenkins that builds the environment from the stable release branch (master) of platform-core using the artefacts that have been committed to that branch - namely yarn.lock for the stripes bundle, and okapi-install.json for the backend modules. Acceptance criteria:
|
| Comments |
| Comment by John Malconian [ 24/Mar/19 ] |
|
I don't think we need a "daily" build of platform-core/master. It would be sufficient to rebuild platform-core/master whenever the branch is updated. The trigger for this build would be in the repository's Jenkinsfile. Let's not call it 'folio-release-core' either. That is too confusing with builds based on quarterly releases. Instead, let's call it 'folio-platform-core'. This will be a relatively straight-forward task. However, I think we should earmark it for Sprint 61 - after the Q1 release is finalized. |
| Comment by John Malconian [ 03/Apr/19 ] |
|
An Ansible playbook called 'folio-release.yml' now exists which will build platform-complete and platform-core from tip of master of those repos. |
| Comment by John Malconian [ 04/Apr/19 ] |
|
This is complete. A system built from the master (ongoing release) branch of platform-core is available at https://folio-release-core.aws.indexdata.com |