[SLING-8286] Jenkins should not try and deploy release commits

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Build and Source Control
• Assignee: Robert Munteanu
• Reporter: Robert Munteanu
• Created: 20/Feb/19 10:56
• Updated: 21/Feb/19 13:28
• Resolved: 21/Feb/19 13:28

Description

With the Jenkins multi-branch pipeline all commits are built. However, at the moment commits which change the version to a release fail. The failures happen because the job tries to deploy the resulting artifact, which is a release version. We should make sure to never try and deploy release artifacts

See for instance:

• https://builds.apache.org/blue/organizations/jenkins/Sling%2Fsling-org-apache-sling-datasource/detail/master/9/pipeline
• https://github.com/apache/sling-org-apache-sling-datasource/commits/master ( commit status )