[BUILD-1037] Turn update_git_mirrors into a magnolia-mgmt task Created: 31/Mar/23 Updated: 04/May/23 Resolved: 02/May/23 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Federico Grilli |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Work Started: | |||||||||||||||||
| Description |
|
Ever since we have introduced the mirror between the hello-saas & hello-saas-tests repositories in the following Bash script: https://git.magnolia-cms.com/projects/SYS/repos/puppet/browse/code/environments/production/modules/git/files/update_git_mirrors We have become maintainers/owners of these mirrors, which we actually are. That being said, that script is not really easy to work with, especially with the use case that we have right now to introduce a GitHub <-> Bitbucket mirror. Since this is a cron job that reports via emails, the idea would be to use a magnolia-mgmt task instead. Then it would align with our stack and we'd have full debugging/implementation control over it. This task also involves tearing down the setup in Puppet and letting ITI know about it. |