[FOLIO-3063] Add full FOLIO ansible deployment to build-platform-complete-snapshot job Created: 06/Mar/21 Updated: 16/Apr/21 Resolved: 16/Apr/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 110, DevOps Sprint 111, DevOps Sprint 112 |
| Development Team: | FOLIO DevOps |
| Description |
|
Goal Catch build and deployment failures at the point where new modules are added/updated on the 'snapshot' branch so that regular nightly folio-snapshot builds are not affected. Process Add a full stack FOLIO deployment (folio-snaphot) to build-platform-complete-snapshot Jenkins job. Do not commit changes to platform-complete@snapshot repository unless build is successful. This should lower the number of "broken" daily folio-snapshot builds. Build failures should be reported to the #hosted-reference-env channel. David Crossley will add a note to the dev.folio.org on howto investigate Jenkins build logs. "folio-snapshot hourly buid failed, the log: <link-to-the-log>. Howto read logs: <link-to-David's-FAQ>" |
| Comments |
| Comment by Marc Johnson [ 16/Mar/21 ] |
|
We are going to build a full environment as part of the verification of potential changes to platform complete in order to stop module versions that fail tenant enablement from making it into the platform. Have I understood this correctly? |
| Comment by Jakub Skoczen [ 17/Mar/21 ] |
|
Marc Johnson Yes. |
| Comment by David Crossley [ 18/Mar/21 ] |
| Comment by John Malconian [ 16/Apr/21 ] |
|
Automation/build-platform-complete-snapshot and Automation/build-platform-core-snapshot Jenkins pipeline jobs are now configured to use a pipeline defined in platform-core and platform-complete called Jenkinsfile.build. The only way now for install json files to be updated are through this job which includes a minimal deployment of each platform. Failures are reported to the hosted-reference-envs Slack channel. |