[
https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162221#comment-162221
]
Joe Mihalich commented on JENKINS-13593:
----------------------------------------
At minimum the builds directory field is completely non functional. It updates
the build-directory in the master config.xml but it does not even attempt to
create the jobs in that directory. The jobs are always created in the jenkins
home dir/jobs. It doesn't seem like this variable is meant to specify a jobs
directory. The field description in the help doesn't match the field title.
This field does not work for me in builds 459-461 (minimum). I don't know if
they worked before those builds.
Anyway, as a work around till you figure this out, I just left the defaults
alone, and deleted the jobs & workspace directory, and created them again as
symlinks to the drive i wanted them created on. This seems to work fine.
The functionality we need for my purposes is a way to specify the directory
where the workspaces go, and where the jobs go.
Thanks,
Joe
> Seems to not handle having builds in seperate folder
> -----------------------------------------------------
>
> Key: JENKINS-13593
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13593
> Project: Jenkins
> Issue Type: Bug
> Components: scm-sync-configuration
> Affects Versions: current
> Environment: Ubuntu 11.10
> Jenkins 1.461
> SCM Sync Configuration Plugin 0.0.5
> Reporter: Christian Lövsund
> Assignee: Frédéric Camblor
> Attachments: jenkins.png
>
>
> ERROR: Processing failed due to a bug in the code. Please report this to
> [email protected]
> java.lang.IllegalArgumentException: Err ! File
> [/mnt/store/jenkins/CodeGenerationMaven/builds/2012-04-25_15-39-35/build.xml]
> seems not to reside in [/var/lib/jenkins] !
> at
> hudson.plugins.scm_sync_configuration.JenkinsFilesHelper.buildPathRelativeToHudsonRoot(JenkinsFilesHelper.java:12)
> at
> hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:21)
> at
> hudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:22)
> at
> hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:172)
> at
> hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:19)
> at
> hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78)
> at hudson.model.Run.save(Run.java:1571)
> at
> hudson.maven.MavenModuleSetBuild.setMavenVersionUsed(MavenModuleSetBuild.java:388)
> at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:581)
> at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
> at hudson.model.Run.run(Run.java:1434)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
--
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
