[JIRA] [junit] (JENKINS-22236) LinkageError when using Maven 3.1.1 and 3.2.1 with Jenkins 1.555
Julian Payne updated JENKINS-22236 LinkageError when using Maven 3.1.1 and 3.2.1 with Jenkins 1.555 Change By: Julian Payne (19/Mar/14 10:58 AM) Summary: LinkageErrorwhenusingMaven3. 1.1and3. 2.1withJenkins1.555 Description: WhenusingMaven3.2.1withJenkins1.555theunittestsblockwithaLinkageErrorlikethis:Runningasf.artifact.ArtifactHandlerManagerTestTestsrun:1,Failures:0,Errors:0,Skipped:0,Timeelapsed:0.149sec-inasf.artifact.ArtifactHandlerManagerTestExceptioninthreadThread-11java.lang.LinkageError:org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil atjava.lang.ClassLoader.defineClassImpl(NativeMethod) atjava.lang.ClassLoader.defineClass(ClassLoader.java:364) atjava.security.SecureClassLoader.defineClass(SecureClassLoader.java:154) atjava.net.URLClassLoader.defineClass(URLClassLoader.java:777) atjava.net.URLClassLoader.access$400(URLClassLoader.java:96) atjava.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1225) atjava.security.AccessController.doPrivileged(AccessController.java:366) atjava.net.URLClassLoader.findClass(URLClassLoader.java:660) atorg.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389) atorg.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) atorg.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) atorg.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) atorg.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) atorg.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:95)OncethiserroroccurstheJenkinsjobblocks.IdonotgettheseerrorsifIruntheunittestsdirectlywithMaven3.2.1IcouldnotfindanythingofinterestintheManageJenkins-Jenkinslog IamalsoseeingthiserroroccasionallywithMaven3.1.1 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-22236) LinkageError when using Maven 3.2.1 with Jenkins 1.555
Julian Payne created JENKINS-22236 LinkageError when using Maven 3.2.1 with Jenkins 1.555 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: junit, maven2 Created: 17/Mar/14 6:01 PM Description: When using Maven 3.2.1 with Jenkins 1.555 the unit tests block with a LinkageError like this: Running asf.artifact.ArtifactHandlerManagerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.149 sec - in asf.artifact.ArtifactHandlerManagerTest Exception in thread "Thread-11" java.lang.LinkageError: org.apache.maven.surefire.shade.org.apache.maven.shared.utils.io.IOUtil at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:364) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:154) at java.net.URLClassLoader.defineClass(URLClassLoader.java:777) at java.net.URLClassLoader.access$400(URLClassLoader.java:96) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1225) at java.security.AccessController.doPrivileged(AccessController.java:366) at java.net.URLClassLoader.findClass(URLClassLoader.java:660) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:389) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) at org.apache.maven.surefire.shade.org.apache.maven.shared.utils.cli.StreamPumper.run(StreamPumper.java:95) Once this error occurs the Jenkins job blocks. I do not get these errors if I run the unit tests directly with Maven 3.2.1 I could not find anything of interest in the Manage Jenkins - Jenkins log Environment: Maven 3.2.1, Jenkins 1.555 Project: Jenkins Labels: jenkins Priority: Critical Reporter: Julian Payne 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-19050) RTC plugin is not recognizing Jazz 4.0.3
Julian Payne created JENKINS-19050 RTC plugin is not recognizing Jazz 4.0.3 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: teamconcert Created: 02/Aug/13 2:08 PM Description: When trying to use Jazz 4.0.3 the plugin is not recognizing the toolkit. The same job works fine with Jazz 3.0.1.6 This is the message that I get from the plugin: Started by user julianpa...@fr.ibm.com Building remotely on ncedemeter01 in workspace /data/jenkins/workspace/BackupReleaseAssetRepository RTC : checkout... FATAL: RTC : checkout failure: Built toolkit directory not found at: /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit java.lang.IllegalArgumentException: Built toolkit directory not found at: /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory.newFacade(RTCFacadeFactory.java:149) at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory.getFacade(RTCFacadeFactory.java:67) at com.ibm.team.build.internal.hjplugin.RTCScm.checkout(RTCScm.java:727) at hudson.model.AbstractProject.checkout(AbstractProject.java:1394) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1593) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) ERROR: RTC : checkout failure: Built toolkit directory not found at: /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit If I go to the machine "ncedemeter01" and do "ls -l /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit" I get this: ncedemeter01.francelab.fr.ibm.com% ls -l /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit total 39556 -rwxrwxrwx 1 jenkins solver 345035 May 18 01:37 apache-mime4j-0.6.jar -rwxrwxrwx 1 jenkins solver4254 May 18 01:37 BuildToolkitTaskDefs.xml -rwxrwxrwx 1 jenkins solver 6451214 May 18 01:37 com.ibm.icu_4.2.1.v20100412.jar -rwxrwxrwx 1 jenkins solver 125529 May 18 01:37 com.ibm.team.build.client_3.0.500.v20130315_0142.jar -rwxrwxrwx 1 jenkins solver 33873 May 18 01:37 com.ibm.team.build.client.nl1_3.0.4.v201305091351.jar -rwxrwxrwx 1 jenkins solver 15034 May 18 01:37 com.ibm.team.build.client.nl2_3.0.3.v201211091526.jar -rwxrwxrwx 1 jenkins solver 705908 May 18 01:37 com.ibm.team.build.common_3.1.400.v20130415_0257.jar -rwxrwxrwx 1 jenkins solver 57437 May 18 01:37 com.ibm.team.build.common.nl1_3.1.2.v201305091351.jar -rwxrwxrwx 1 jenkins solver 25873 May 18 01:37 com.ibm.team.build.common.nl2_3.1.2.v201305091343.jar -rwxrwxrwx 1 jenkins solver 282616 May 18 01:37 com.ibm.team.build.toolkit_3.0.500.v20130428_0234.jar -rwxrwxrwx 1 jenkins solver 98538 May 18 01:37 com.ibm.team.build.toolkit.nl1_3.0.5.v201305091352.jar -rwxrwxrwx 1 jenkins solver 42498 May 18 01:37 com.ibm.team.build.toolkit.nl2_3.0.5.v201305091343.jar -rwxrwxrwx 1 jenkins solver 50586 May 18 01:37 com.ibm.team.calm.foundation.client_3.1.200.v20120924_1445.jar -rwxrwxrwx 1 jenkins solver 26751 May 18 01:37 com.ibm.team.calm.foundation.client.nl1_3.1.2.v201305091352.jar -rwxrwxrwx 1 jenkins solver 12261 May 18 01:37 com.ibm.team.calm.foundation.client.nl2_3.1.1.v201305091343.jar -rwxrwxrwx 1 jenkins solver 290464 May 18 01:37 com.ibm.team.calm.foundation.common_3.1.300.v20130509_0147.jar -rwxrwxrwx 1 jenkins solver 48849 May 18 01:37 com.ibm.team.calm.foundation.common.nl1_3.1.2.v201305091352.jar -rwxrwxrwx 1 jenkins solver 21678 May 18 01:37 com.ibm.team.calm.foundation.common.nl2_3.1.2.v201305091343.jar -rwxrwxrwx 1 jenkins solver9346 May 18 01:37 com.ibm.team.dev.jdojo.runtime.common_3.0.500.v20130415_0257.jar -rwxrwxrwx 1 jenkins solver 62036 May 18 01:37 com.ibm.team.enterprise.automation.common_3.1.200.v20120924_1445.jar -rwxrwxrwx 1 jenkins
[JIRA] [configurationslicing] (JENKINS-19051) The configuration slicing crashes whenever I try to change an SCM Timer
Julian Payne created JENKINS-19051 The configuration slicing crashes whenever I try to change an SCM Timer Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: configurationslicing Created: 02/Aug/13 3:44 PM Description: Whenever I try to change any SCM Timer entries I get a crash like this: Stack trace javax.servlet.ServletException: java.lang.UnsupportedOperationException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project This looks like it will work - it is a bit cumbersome though and will need to be done by hand for any multi-configuration project that uses RTC. Are you planning a solution in the RTC plugin to prevent a checkout in the main job or some other solution that does not require this manual fix? 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I tried this and in fact it does not seem to work? Building on master in workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob/jobs/RunAsfTests10/workspace/RunAsfTests10/jdk=IBM-JDK-7 RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "JenkinsRunAsfTests10" ... FATAL: RTC : checkout failure: Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob/jobs/RunAsfTests10/workspace/RunAsfTests10/jdk=IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob com.ibm.team.filesystem.client.FileSystemStatusException: Status ERROR: com.ibm.team.filesystem.client code=0 Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob/jobs/RunAsfTests10/workspace/RunAsfTests10/jdk=IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob null at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:309) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:1) at com.ibm.team.filesystem.client.internal.SharingManager.register(SharingManager.java:1002) at com.ibm.team.build.internal.hjplugin.rtc.RepositoryConnection.checkout(RepositoryConnection.java:363) at com.ibm.team.build.internal.hjplugin.rtc.RTCFacade.checkout(RTCFacade.java:387) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory$RTCFacadeWrapper.invoke(RTCFacadeFactory.java:92) at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:107) at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:31) at hudson.FilePath.act(FilePath.java:906) As you can see the 2 checkout directories are adjacent and not nested but it still complains about the sandbox (maybe because they are both using the same repository workspace)? 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project What I am trying to do is fairly simple. I have a Jenkins job that builds a maven project using the maven goals "clean deploy". As part of these goals the unit tests are being run and reported by Jenkins (and/or RTC now that you have added the RTC build support). What I wanted to do with the multi-configuration project is run the maven project with the goals "clean test" but with different JDK's as we have seen some problems moving between JDK6 and JDK 7. Hence I created several JDK's in my Jenkins configuration and then I created a multi-configuration project and selected my different JDK's. 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-18794) Configuration slicing is failing with Maven 3.1.0
Julian Payne created JENKINS-18794 Configuration slicing is failing with Maven 3.1.0 Issue Type: Bug Affects Versions: current Assignee: mdonohue Components: configurationslicing Created: 17/Jul/13 10:21 AM Description: The configuration slicing (1.37) in the latest version of Jenkins (1.523) is failing with Maven 3.1.0: Caused by: java.lang.NullPointerException at configurationslicing.maven.MavenVersionSlicer$MavenVersionSlicerSpec.getBuilders(MavenVersionSlicer.java:78) at configurationslicing.maven.MavenVersionSlicer$MavenVersionSlicerSpec.getValues(MavenVersionSlicer.java:56) at configurationslicing.maven.MavenVersionSlicer$MavenVersionSlicerSpec.getValues(MavenVersionSlicer.java:30) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at configurationslicing.ConfigurationSlicing.getDynamic(ConfigurationSlicing.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:379) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) Due Date: 19/Jul/13 12:00 AM Project: Jenkins Labels: maven Priority: Major Reporter: Julian Payne 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I will look at your suggestions - thanks. However it seems to me that the problem is that the RTC plugin is doing a checkout in the root project and it is this checkout that is causing the problem? If you look at the trace that I sent you will see that the "configured sub-projects" are checking out the code correctly in a sub-project (but using the same workspace because that is how multi-configuration projects are defined in Jenkins). The nesting comes from the initial checkout in the root project by the RTC plugin which is superflous as we are not going to do any builds in the root project? Can you confirm that the multi-configuration project does work with the RTC plugin and if yes could you provide me with an example so that I can see what I am doing wrong in my configuration? Thanks again for your help. 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-15935) Can't build using maven 3.1.0 latest release candidate
Julian Payne commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate I have this error with the release version of Maven 3.1.0. This is stopping us from using the latest version of Maven. 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-15935) Can't build using maven 3.1.0 latest release candidate
Julian Payne updated JENKINS-15935 Cant build using maven 3.1.0 latest release candidate Making this critical as 3.1.0 is now the latest release version of Maven. Change By: Julian Payne (15/Jul/13 9:46 AM) Priority: Major Critical 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-15935) Can't build using maven 3.1.0 latest release candidate
Julian Payne commented on JENKINS-15935 Cant build using maven 3.1.0 latest release candidate The (alpha status) is a bug on the Maven download page - there was an alpha build available on this page but this is now the final build of 3.1.0. See http://maven.apache.org/docs/3.1.0/release-notes.html Thanks. 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Julian Payne commented on JENKINS-18691 Team Concert plugin is adding components to a workspace Heather - that does indeed fix my problem - I should have known this - it is complicated but I realize that it is not a problem of the plugin. Please close this issue. If you have a chance to discuss with the RTC team it would be nice to have the default behaviour being that when you choose just a subset of components the flow is scoped appropriately. 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Julian Payne created JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: teamconcert Created: 11/Jul/13 9:04 AM Description: I have a multi-configuration project that is configured to run a job with different JDK versions that is configured as shown below: - Source Code Management Rational Team Concert (RTC) RTC repository connection (julianpa...@fr.ibm.com@https://rtcdemeter.francelab.fr.ibm.com:9443/jazz) Just accept and fetch from a build workspace Build workspace Configuration Matrix JDK IBM-JDK-7 Oracle-JDK-7 IBM-JDK-6 The problem seems to come from the fact that the "top-level" build: --- Started by user julianpa...@fr.ibm.com Building on master in workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "JenkinsRunAsfTests10" ... RTC Checkout : Fetching files to fetch destination "/data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace" ... RTC Checkout : Fetching Completed Triggering IBM-JDK-7 Triggering Oracle-JDK-7 IBM-JDK-7 completed with result FAILURE Oracle-JDK-7 completed with result FAILURE Finished: FAILURE Then the individual builds try to do a checkout in their private workspace: --- Started by upstream project "RunAsfTests10" build number 2 originally caused by: Started by user julianpa...@fr.ibm.com Building on master in workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "JenkinsRunAsfTests10" ... FATAL: RTC : checkout failure: Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace com.ibm.team.filesystem.client.FileSystemStatusException: Status ERROR: com.ibm.team.filesystem.client code=0 Cannot create sandbox at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 because one already exists at /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace null at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:309) at com.ibm.team.filesystem.client.internal.copyfileareas.CopyFileAreaManager.createCopyFileArea(CopyFileAreaManager.java:1) at com.ibm.team.filesystem.client.internal.SharingManager.register(SharingManager.java:1002) at com.ibm.team.build.internal.hjplugin.rtc.RepositoryConnection.checkout(RepositoryConnection.java:363) Due Date: 12/Jul/13 12:00 AM Fix Versions: current Project: Jenkins Priority: Major Reporter: Julian Payne 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 -- 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
[JIRA] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Julian Payne created JENKINS-18691 Team Concert plugin is adding components to a workspace Issue Type: Bug Affects Versions: current Assignee: Julian Payne Components: teamconcert Created: 10/Jul/13 1:02 PM Description: When creating a workspace that only includes 1 component from a stream the Team Concert build is adding all the other components to the workspace when creating the milestone. My builds are configured using the option "Just accept and fetch from a build workspace". Due Date: 10/Jul/13 12:00 AM Project: Jenkins Labels: plugin scm Priority: Major Reporter: Julian Payne 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Julian Payne assigned JENKINS-18691 to Unassigned Team Concert plugin is adding components to a workspace Change By: Julian Payne (10/Jul/13 1:03 PM) Assignee: JulianPayne 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 -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
