[BUILD-773] New commits to Foundation Terraform projects should trigger a deploy Created: 03/May/22 Updated: 24/May/22 Resolved: 24/May/22 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Roberto Gomez |
| Resolution: | Done | Votes: | 0 |
| Labels: | foundation_team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Description |
|
Both the Renovate setup and the usage-metrics are Terraform projects that wouldn't get published if somebody pushed a commit but didn't involve the maintainer to manually deploy it. This should be achieved by a Jenkinsfile. In order to not duplicate the code, introduce a magnoliaTerraformPipeline in pipeline-templates and use it from both projects? |