[
https://issues.jenkins-ci.org/browse/JENKINS-13734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163677#comment-163677
]
SCM/JIRA link daemon commented on JENKINS-13734:
------------------------------------------------
Code changed in jenkins
User: mc1arke
Path:
src/main/java/hudson/scm/CVSSCM.java
http://jenkins-ci.org/commit/cvs-plugin/b0653878a7316dc676e25894b10235590e7fe327
Log:
[FIXED JENKINS-13734] Remove sticky date tag properly
Prevent CVS thinking we're on an old date and therefore aren't up-to-date
Compare: https://github.com/jenkinsci/cvs-plugin/compare/de148b3...b065387
> CVS plugin crashes Maven release builds with the error "Cannot prepare the
> release because you have local modifications"
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-13734
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13734
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Affects Versions: current
> Environment: CentOS, Jenkins 1.463, CVS plugin 2.3, Jenkins Maven
> Release Plugin 0.9.1
> Reporter: Sergey Skladchikov
> Labels: cvs, maven, plugin, release
> Attachments: config.xml, log
>
>
> 1. Install Jenkins Maven Release Plugin 0.9.1
> 2. Make a new project and add the pom.xml file containing the following
> settings:
> {code:xml}
> ...
> <scm>
>
> <developerConnection>scm:cvs:pserver:CVS-ACCOUNT:PASSWORD@CVS-SERVER:/REPOSITORY:MODULE</developerConnection>
> </scm>
> ...
> <build>
> <plugins>
> <plugin>
> <groupId>maven</groupId>
> <artifactId>maven-scm-plugin</artifactId>
> <version>1.6.1</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.2.2</version>
> <configuration>
> <useReleaseProfile>false</useReleaseProfile>
> </configuration>
> </plugin>
> </plugins>
> </build>
> ...
> <distributionManagement>
> <repository>
> <id>my-releases</id>
> <!-- specify any valid HTTP URL -->
> <url>ANY_RELEASES_REPOSITORY_URL</url>
> </repository>
> </distributionManagement>
> ...
> {code}
> 3. Import the project into your CVS server
> 4. Create a new maven job and specify all the necessary CVS connection
> settings
> 5. Open the job page and click the link "Perform Maven Release"
> Expected: the job compiles the project and publishes a newly created artefact
> Actual: the job is crushed with the error "Cannot prepare the release because
> you have local modifications" (see attachments for details)
> Important note: everything works properly if I use CVS plugin version 1.6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
