Quantcast

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

JIRA noreply@jenkins-ci.org
Christian Lövsund created JENKINS-13593:
-------------------------------------------

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


ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162030#comment-162030 ]

Frédéric Camblor commented on JENKINS-13593:
--------------------------------------------

Hi Christian,

Can you confirm your JENKINS_HOME is /var/lib/jenkins (it should since this is what I get when I use Hudson.getInstance().getRootDir())

Do you know which plugin (or script) is generating this file ?
I need more context for your specific use, I could remove this exception check, but I could avoid it, I'd prefer :-)
               

> 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
>
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

    [ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162039#comment-162039 ]

Christian Lövsund commented on JENKINS-13593:
---------------------------------------------

HOME /var/lib/jenkins
JENKINS_HOME /var/lib/jenkins
LANG en_US.UTF-8
LANGUAGE en_US:en
LD_LIBRARY_PATH /usr/lib/jvm/jdk1.6.0_31/jre/lib/amd64/server:/usr/lib/jvm/jdk1.6.0_31/jre/lib/amd64:/usr/lib/jvm/jdk1.6.0_31/jre/../lib/amd64
LOGNAME jenkins
MAIL /var/mail/jenkins
NLSPATH /usr/dt/lib/nls/msg/%L/%N.cat
PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
PWD /var/lib/jenkins
SHELL /bin/bash
SHLVL 1
TERM screen
USER jenkins
XDG_SESSION_COOKIE 2a2862c8d59aff8cfea5a5f000000010-1335363605.122239-652733116
XFILESEARCHPATH /usr/dt/app-defaults/%L/Dt
               

> 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
>
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

    [ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162040#comment-162040 ]

Christian Lövsund commented on JENKINS-13593:
---------------------------------------------

I got this Exception when trying to build any job in jenkins.
So I needed to uninstall/disable plugin in order to make Jenkins build any job.
It worked before I updated from version 0.0.4
I have a setup where all the build data (artifacts and all) is put on a big slower disk, while jenkins itself and all build occur on a SSD.
See picture for more info.
               

> 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
>
> ERROR: Processing failed due to a bug in the code. Please report this to [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

     [ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Lövsund updated JENKINS-13593:
----------------------------------------

    Attachment: jenkins.png
   

> 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 [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

    [ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162048#comment-162048 ]

Frédéric Camblor commented on JENKINS-13593:
--------------------------------------------

Wow ok this is related to this workspace root directory / build record root directory configuration stuff !

I think you're the first person I encounter using these fields :-)

I'll try to see if I can find a workaround about this special case..
               

> 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 [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

    [ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162050#comment-162050 ]

Christian Lövsund commented on JENKINS-13593:
---------------------------------------------

great, thanks!
               

> 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 [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

    [ https://issues.jenkins-ci.org/browse/JENKINS-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162183#comment-162183 ]

Alexander Alexeev commented on JENKINS-13593:
---------------------------------------------

Hi! I've same issue with SCM Sync Configuration Plugin.
I use Windows 2008 R2.
Jenkins home and build data is placed on different drives.
This issue has appeared when I upgrade Jenkins from 1.459 to 1.461
               

> 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 [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

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

    [ 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 [hidden email]
> 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


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-13593) Seems to not handle having builds in seperate folder

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Change By: Frédéric Camblor (18/Sep/12 7:14 AM)
Priority: Major Blocker
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...