You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2019/02/20 10:57:00 UTC

[jira] [Created] (SLING-8286) Jenkins should not try and deploy release commits

Robert Munteanu created SLING-8286:
--------------------------------------

             Summary: 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


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)