[BUILD-737] Find out how to trigger custom actions Created: 04/Apr/22 Updated: 19/Jul/22 Resolved: 19/Jul/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: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | Release automation | ||||||||||||||||
| Description |
|
With the former, homemade dependency bot, it was possible after a PR with a suggested update was created, to trigger for instance the following Jenkins job for validation purposes: https://git.magnolia-cms.com/projects/ARCHIVE/repos/dep-bot-validate-pr-job/browse Using postUpgradeTasks and maybe a curl call (to trigger custom Java code in release-webapp?) experiment with restoring the ability to trigger custom tasks. Draft impl
|