Quantcast

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Components: cvs
Created: 19/Jun/12 8:33 AM
Description:

Since upgrading Jenkins to version 1.470, sources are checked out into folder <workspace>/<module name>. Before (v1.457), the folder <module name> was not created.

This broke all our jobs due to artifact archiving and build configuration. We already used CVS plugin 2.4 for at least one week without problems, before updating Jenkins from 1.457 to 1.470.

Since the update option Legacy Mode is enabled for all jobs by default and cannot be disabled. When trying to disable the selection box and saving the configuration, it jumps back to enabled. Tested in Firefox 12.0 and Internet Explorer 8. The option was not enabled before the update.

CVS configuration after the update:

<scm class="hudson.scm.CVSSCM">
<flatten>false</flatten>
<repositories>
<hudson.scm.CvsRepository>
<cvsRoot>:pserver:user@host:/path</cvsRoot>
<repositoryItems>
<hudson.scm.CvsRepositoryItem>
<modules>
<hudson.scm.CvsModule>
<localName></localName>
<remoteName>module_name</remoteName>
</hudson.scm.CvsModule>
</modules>
<location class="hudson.scm.CvsRepositoryLocation$HeadRepositoryLocation">
<locationType>HEAD</locationType>
<useHeadIfNotFound>false</useHeadIfNotFound>
</location>
</hudson.scm.CvsRepositoryItem>
</repositoryItems>
<compressionLevel>-1</compressionLevel>
<excludedRegions>
<hudson.scm.ExcludedRegion>
<pattern></pattern>
</hudson.scm.ExcludedRegion>
</excludedRegions>
<password>secret</password>
<passwordRequired>true</passwordRequired>
</hudson.scm.CvsRepository>
</repositories>
<canUseUpdate>false</canUseUpdate>
<skipChangeLog>false</skipChangeLog>
<pruneEmptyDirectories>true</pruneEmptyDirectories>
<disableCvsQuiet>false</disableCvsQuiet>
<cleanOnFailedUpdate>false</cleanOnFailedUpdate>
</scm>

Before:

<scm class="hudson.scm.CVSSCM">
<flatten>true</flatten>
<repositories>
<hudson.scm.CvsRepository>
<cvsRoot>:pserver:user@host:/path</cvsRoot>
<modules>
<hudson.scm.CvsModule>
<localName></localName>
<remoteName>module_name</remoteName>
<moduleLocation class="hudson.scm.CvsModuleLocation$HeadModuleLocation">
<locationType>HEAD</locationType>
<useHeadIfNotFound>false</useHeadIfNotFound>
</moduleLocation>
</hudson.scm.CvsModule>
</modules>
<compressionLevel>-1</compressionLevel>
<excludedRegions>
<hudson.scm.ExcludedRegion>
<pattern></pattern>
</hudson.scm.ExcludedRegion>
</excludedRegions>
<password>secret</password>
<passwordRequired>true</passwordRequired>
</hudson.scm.CvsRepository>
</repositories>
<canUseUpdate>false</canUseUpdate>
<skipChangeLog>false</skipChangeLog>
<pruneEmptyDirectories>true</pruneEmptyDirectories>
<disableCvsQuiet>false</disableCvsQuiet>
<cleanOnFailedUpdate>false</cleanOnFailedUpdate>
</scm>

I have not tried to set flatten back to true directly in config.xml. To solve the problem locally, I have updated all affected job configurations to include the <module_name> folder in paths where necessary.

Environment: Jenkins 1.470, Jenkins CVS Plug-in 2.4, Linux X86, SLES 10, Apache Tomcat 7.0.26
Project: Jenkins
Labels: cvs workspace
Priority: Major Major
Reporter: Bjoern Sonntag
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org

Manually editing the config.xml does work, however after doing so, you cannot configure anything about the job without the setting reverting.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Code changed in jenkins
User: mc1arke
Path:
src/main/java/hudson/scm/CVSSCM.java
http://jenkins-ci.org/commit/cvs-plugin/773d49911d9abe3eea4b7d9c57022f2cffad8b53
Log:
[FIXED JENKINS-14141] (regression) allow flattening of workspace on single module

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: SCM/JIRA link daemon (09/Jul/12 5:59 PM)
Status: Open Resolved
Resolution: Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Michael Clarke (09/Jul/12 6:23 PM)
Assignee: Michael Clarke
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
Jordan Grant edited a comment on Bug JENKINS-14141

Closing due to fix in CVS plugin 2.5

This was still an issue in CVS plugin 2.6-SNAPSHOT as of 27 AUG 2012

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Code changed in jenkins
User: mc1arke
Path:
src/main/java/hudson/scm/CVSSCM.java
src/test/java/hudson/scm/CVSSCMTest.java
http://jenkins-ci.org/commit/cvs-plugin/d7a1ee21db9fb641d504d6d180c900f064624042
Log:
[FIXED JENKINS-14141] Fix legacy mode disable and added unit test

Compare: https://github.com/jenkinsci/cvs-plugin/compare/bfc1a2dd6034...d7a1ee21db9f

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Sorry, my fault. Fixed now.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

Thank you! I have built and can verify that this is fixed in 2.6 SNAPSHOT.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...