[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:
relation
is related to BUILD-853 Domain for the webapp/endpoints Closed
is related to BUILD-872 Make dep-bot-validate-pr-job compatib... Closed
is related to BUILD-827 Declined Renovate PRs Closed
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

  1. renovate runs
  2. triggers a custom action (bash script): curl }}{{https://magnolia-mgmt.aws.eu-central1.com/endpoints/trigger-validation
  3. some magnolia-mgmt command triggers (simply calls a method in JenkinsService, for instance runCveScan())
  4. jenkins job triggers, and automatically adds build status to the PR

Generated at Sun Feb 11 23:44:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.