Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Currently for most (if not all) releases the Sling Committer CLI fails to validate the release because the CI check fails.
This is because our Jenkins jobs do not execute on tags and therefore the CI check doesn't see a success code for the tag commit's build status.
It seems not trivial to add builds on tags to Jenkins (though someone who knows Jenkins DSL may know better than I) but either way it would seem like a good idea to check the parent commit's build status if the tag commit does not have a build status.
Attachments
Issue Links
- links to