[
https://issues.apache.org/jira/browse/SLING-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-8286.
------------------------------------
Resolution: Fixed
Fixed with
* [sling-tooling-jenkins commit
36ffc4b|https://github.com/apache/sling-tooling-jenkins/commit/36ffc4b]
* [sling-tooling-jenkins commit
e4bb4ad|https://github.com/apache/sling-tooling-jenkins/commit/e4bb4ad]
> Jenkins should not try and deploy release commits
> -------------------------------------------------
>
> Key: SLING-8286
> URL: https://issues.apache.org/jira/browse/SLING-8286
> Project: Sling
> Issue Type: Bug
> Components: Build and Source Control
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
>
> 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 )
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
