[JIRA] (JENKINS-38077) Silently Failing to Deploy Released Artifacts to Maven Repository

[email protected] (JIRA) Fri, 09 Sep 2016 08:40:12 -0700

Title: Message Title

This problem and solution are alluded to in Jenkins' own documentation for plugin authors.

The release process created a "SNAPSHOT" version / Using git version 1.8.5.2 or around
After cd-ing to your plugin git repo folder, run the maven release commands this way, forcing version 2.5 of maven-release-plugin; alternatively, proceed to the next work-around topic right after this one:
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform
git push (should your git status still be "dirty")

Further down on the same page is a potentially related problem and solution:

If a release only deploys snapshots consider upgrading the maven-scm-provider-gitexe to 1.9.1 or more (see more details.)
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-release-plugin</artifactId>
        <version>2.5.1</version>
        <dependencies>
          <dependency>
            <groupId>org.apache.maven.scm</groupId>
            <artifactId>maven-scm-provider-gitexe</artifactId>
            <version>1.9.2</version>
          </dependency>
        </dependencies>
      </plugin>
or running following command may make your maven-release-plugin work correct (this changes output format of git status).
git config --global --add status.displayCommentPrefix true

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38077) Silently Failing to Deploy Released Artifacts to Maven Repository

Reply via email to