[JIRA] [core] (JENKINS-26601) StackOverflow Maven Job Parse Poms
Geoff Cummings commented on JENKINS-26601 StackOverflow Maven Job Parse Poms It seem to happen if the pom uses a parent which is not in the workspace or the local maven repository. So using a basic pom which has the jenkins parent pom as its parent: with 1.598 it gives the stack trace. with 1.597 the parent pom downloaded from our nexus server, and builds ok. 1.598 will build as the parent pom is available in the local maven repository. 1.598 will fail if I delete the parent pom from the local maven repository, or update the job to use a maven repository local to the workspace which is empty. The basic pom can be found here: https://github.com/gcummings/JENKINS-26601 1.598 First time build. Skipping changelog. Parsing POMs FATAL: null java.lang.StackOverflowError at java.lang.Exception.init(Exception.java:102) at java.lang.ReflectiveOperationException.init(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.init(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) 1.597 Parsing POMs Downloaded artifact http:///nexus/content/groups/aepona-group/org/jenkins-ci/main/pom/1.598/pom-1.598.pom Discovered a new module org.jenkins-ci.main:org.jenkins-ci.bug Jenkins Test Pom 26601 Modules changed, recalculating dependency graph [workspace] $ java -Xmx4096m -XX:MaxPermSize=1024m -Dmaven.findbugs.jvmargs=-XX:MaxPermSize=1024m -Dmaven.test.failure.ignore=false -cp //plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.6.jar://tools/Maven/Maven_3.1.0/boot/plexus-classworlds-2.4.2.jar://tools/Maven/Maven_3.1.0/conf/logging jenkins.maven3.agent.Maven31Main //tools/Maven/Maven_3.1.0 //war/WEB-INF/lib/remoting-2.49.jar //plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.6.jar //plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.6.jar 52190 ===[JENKINS REMOTING CAPACITY]===channel started 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] [core] (JENKINS-26601) StackOverflow Maven Job Parse Poms
Geoff Cummings edited a comment on JENKINS-26601 StackOverflow Maven Job Parse Poms It seem to happen if the pom uses a parent which is not in the workspace or the local maven repository. So using a basic pom which has the jenkins parent pom as its parent: with 1.598 it gives the stack trace. with 1.597 the parent pom downloaded from our nexus server, and builds ok. 1.598 will build as the parent pom is available in the local maven repository. 1.598 will fail if I delete the parent pom from the local maven repository, or update the job to use a maven repository local to the workspace which is empty. The basic pom can be found here: https://github.com/gcummings/JENKINS-26601 1.598 First time build. Skipping changelog. Parsing POMs FATAL: null java.lang.StackOverflowError at java.lang.Exception.init(Exception.java:102) at java.lang.ReflectiveOperationException.init(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.init(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor195.invoke(Unknown Source) 1.597 Parsing POMs Downloaded artifact http:///nexus/content/groups/public/org/jenkins-ci/main/pom/1.598/pom-1.598.pom Discovered a new module org.jenkins-ci.main:org.jenkins-ci.bug Jenkins Test Pom 26601 Modules changed, recalculating dependency graph [workspace] $ java -Xmx4096m -XX:MaxPermSize=1024m -Dmaven.findbugs.jvmargs=-XX:MaxPermSize=1024m -Dmaven.test.failure.ignore=false -cp //plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.6.jar://tools/Maven/Maven_3.1.0/boot/plexus-classworlds-2.4.2.jar://tools/Maven/Maven_3.1.0/conf/logging jenkins.maven3.agent.Maven31Main //tools/Maven/Maven_3.1.0 //war/WEB-INF/lib/remoting-2.49.jar //plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.6.jar //plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.6.jar 52190 ===[JENKINS REMOTING CAPACITY]===channel started 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] [core] (JENKINS-26601) StackOverflow Maven Job Parse Poms
Geoff Cummings commented on JENKINS-26601 StackOverflow Maven Job Parse Poms Also happens on master CentOS, JDK 1.7.0_55 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] [core] (JENKINS-26601) StackOverflow Maven Job Parse Poms
Geoff Cummings created JENKINS-26601 StackOverflow Maven Job Parse Poms Issue Type: Bug Assignee: Unassigned Components: core, maven-plugin Created: 26/Jan/15 11:08 AM Description: Hi, After upgrading from 1.596 to 1.598 I am unable to run any Maven Jobs I am getting the following StackOverFlow Error. Parsing POMs ERROR: Failed to parse POMs java.io.IOException: remote file operation failed: /tr/j/jh2/workspace/Cannon_Test_maven at hudson.remoting.Channel@4d4d472e:01-Cannon2: java.io.IOException: Remote call on 01-Cannon2 failed at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:959) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1718) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.IOException: Remote call on 01-Cannon2 failed at hudson.remoting.Channel.call(Channel.java:760) at hudson.FilePath.act(FilePath.java:978) ... 8 more Caused by: java.lang.StackOverflowError at java.lang.ReflectiveOperationException.init(ReflectiveOperationException.java:89) at java.lang.reflect.InvocationTargetException.init(InvocationTargetException.java:72) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy30.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy30.lookup(Unknown Source) ... 1000 lines repeating ... at com.sun.proxy.$Proxy30.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at ..remote call to 01-Cannon2(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) ... 9 more Project: Jenkins Priority: Blocker Reporter: Geoff Cummings 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] [core] (JENKINS-26601) StackOverflow Maven Job Parse Poms
Geoff Cummings commented on JENKINS-26601 StackOverflow Maven Job Parse Poms going to 1.597 has stopped the error 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] [timestamper] (JENKINS-23867) Incompatibility with Jenkins 1.572 or later
Geoff Cummings commented on JENKINS-23867 Incompatibility with Jenkins 1.572 or later New div layout does not have an element with id 'navigation' causing the _javascript_ to fail. I have submitted a pull request to fix this: https://github.com/jenkinsci/timestamper-plugin/pull/9 all feedback welcome thanks Geoff 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] [throttle-concurrents] (JENKINS-23558) ThrottleCategoryProvider Extension Point
Geoff Cummings commented on JENKINS-23558 ThrottleCategoryProvider Extension Point This sounds like a useful improvement. I don't know how to create the extension point but would be interested in trying to use it to create new throttling rules. Is anyone planning to implement it anytime soon? Geoff 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] [tracking-git] (JENKINS-23659) tracking-git: Use parameter or environment variable to specify which build to track
Geoff Cummings created JENKINS-23659 tracking-git: Use parameter or environment variable to specify which build to track Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: tracking-git Created: 02/Jul/14 3:25 PM Description: Hi, I would like to be able to use a build parameter to choose which build of the project to track instead of only the lastSuccessful, lastFailed etc... example configuration: Create project_B, Add RunParameter Name: VERSION_TO_BUILD Project: Project_A Filter: Stable Builds Only Enable Track Git source of another project. Project to Track: Project_A Build to Track: By Number Build Number: $VERSION_TO_BUILD_NUMBER Behaviour When I click Build on Project B I will be shown a dropdown containing a list of Stable builds for project_A. I select one of the builds, lets say #10, and click Build. Run parameter plugin will populate the environment variable VERSION_TO_BUILD_NUMBER = 10 the Tracking Git plugin will resolve the $VERSION_TO_BUILD_NUMBER and track Project A build #10 thanks Geoff Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] [tracking-git] (JENKINS-23659) tracking-git: Use parameter or environment variable to specify which build to track
Geoff Cummings commented on JENKINS-23659 tracking-git: Use parameter or environment variable to specify which build to track Added first pass at this in the following pull request: https://github.com/jenkinsci/tracking-git-plugin/pull/1/ current state: Not pretty but it works so please provide feedback and advice... 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] [throttle-concurrents] (JENKINS-12093) Allow per-project category throttling on the same job
Geoff Cummings commented on JENKINS-12093 Allow per-project category throttling on the same job Pull request submitted for this: https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/20 Currently no UI changes, but it will allow () Throttle by project alone () Also throttle by one or more categories per existing code, if project values are 0, then no throttling by project will occur. all feedback welcome. Geoff 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] [throttle-concurrents] (JENKINS-23368) Thottle Concurrent Builds - enforce start interval/delay between running builds.
Geoff Cummings created JENKINS-23368 Thottle Concurrent Builds - enforce start interval/delay between running builds. Issue Type: Improvement Affects Versions: current Assignee: Geoff Cummings Components: throttle-concurrents Created: 09/Jun/14 9:10 AM Description: We have a test job which takes an hour to run. I have enabled concurrent builds and use throttle concurrent build plugin to restrict to one build per node and limit to only 3 concurrent builds at a time. Current behaviour during a busy period: 1:00 - build triggered - starts building #1 1:05 - build triggered - starts building #2 1:10 - build triggered - starts building #3 1:15 - build triggered - #4 waits in queue 1:25 - build triggered - merged into #4, waits in queue 1:30 - build triggered - merged into #4, waits in queue 1:50 - build triggered - merged into #4, waits in queue 2:00 - build #finished, build #4 starts no other builds can start until the first build finishes at 2:00 Desired Behaviour: If no builds are currently running and a build is triggered, I want it to start as soon as possible. When the next build is triggered, if there is still a build running, I want it to wait a specified number of minutes, eg 20 minutes, after the previous build started executing. 1:00 - build triggered - starts building #1 1:05 - build triggered - #2 waits in queue 1:10 - build triggered - merged into #2, waits in queue 1:15 - build triggered - merged into #2, waits in queue 1:20 - 20 minute interval from last build passed, build #2 starts executing 1:25 - build triggered - #3 waits in queue 1:30 - build triggered - merged into #3, waits in queue 1:40 - 20 minute interval from last build passed, build #3 starts executing 1:50 - build triggered - #4 waits in queue 2:00 - build #1 finished, 20 minute interval from last build passed, build #4 starts executing This will allow a build to start as soon as possible if there are no other builds running but also allow staggered builds starting every 20 minutes during a busy period. It should only delay if the last build is still running, if the last build failed we would not want to delay for 20 minutes to retry! Hopefully that makes some sense. Geoff Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] [throttle-concurrents] (JENKINS-23368) Thottle Concurrent Builds - enforce start interval/delay between running builds.
Geoff Cummings updated JENKINS-23368 Thottle Concurrent Builds - enforce start interval/delay between running builds. Change By: Geoff Cummings (09/Jun/14 9:19 AM) Description: Wehaveatestjobwhichtakesanhourtorun.Ihaveenabledconcurrentbuildsandusethrottleconcurrentbuildplugintorestricttoonebuildpernodeandlimittoonly3concurrentbuildsatatime.Currentbehaviourduringabusyperiod:1:00-buildtriggered-startsbuilding#11:05-buildtriggered-startsbuilding#21:10-buildtriggered-startsbuilding#31:15-buildtriggered-#4waitsinqueue1:25-buildtriggered-mergedinto#4,waitsinqueue1:30-buildtriggered-mergedinto#4,waitsinqueue1:50-buildtriggered-mergedinto#4,waitsinqueue2:00-build#finished,build#4startsnootherbuildscanstartuntilthefirstbuildfinishesat2:00DesiredBehaviour:Ifnobuildsarecurrentlyrunningandabuildistriggered,Iwantittostartassoonaspossible.Whenthenextbuildistriggered,ifthereisstillabuildrunning,Iwantittowaitaspecifiednumberofminutes,eg20minutes,afterthepreviousbuildstartedexecuting.1:00-buildtriggered-startsbuilding#11:05-buildtriggered-#2waitsinqueue1:10-buildtriggered-mergedinto#2,waitsinqueue1:15-buildtriggered-mergedinto#2,waitsinqueue1:20-20minuteintervalfromlastbuild passed started ,build#2startsexecuting1:25-buildtriggered-#3waitsinqueue1:30-buildtriggered-mergedinto#3,waitsinqueue1:40-20minuteintervalfromlastbuild passed started ,build#3startsexecuting1:50-buildtriggered-#4waitsinqueue2:00-build#1finished,20minuteintervalfromlastbuild passed started ,build#4startsexecutingThiswillallowabuildtostartassoonaspossibleiftherearenootherbuildsrunningbutalsoallowstaggeredbuildsstartingevery20minutesduringabusyperiod.Itshouldonlydelayifthelastbuildisstillrunning,ifthelastbuildfailedwewouldnotwanttodelayfor20minutestoretry!Hopefullythatmakessomesense.Geoff 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] [throttle-concurrents] (JENKINS-23368) Thottle Concurrent Builds - enforce start interval/delay between running builds.
Geoff Cummings commented on JENKINS-23368 Thottle Concurrent Builds - enforce start interval/delay between running builds. Hi, Pull request submitted: https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/21 thanks Geoff 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] [core] (JENKINS-22755) RunParameter no longer displays the Full Display Name
Geoff Cummings
created JENKINS-22755
RunParameter no longer displays the Full Display Name
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
24/Apr/14 11:30 PM
Description:
The toString() method of Run.java was changed recently to no return the FullDisplayName
public String toString() {
-return getFullDisplayName();
+return project.getFullName() + " #" + number;
i think the RunParameter just uses the toString() method when displaying so now does not display the Full Display Name which was very useful
option value="${run.externalizableId}"${run}/option
Project:
Jenkins
Priority:
Major
Reporter:
Geoff Cummings
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] [findbugs] (JENKINS-19096) Findbugs Reporting not working with Maven 3.1
Geoff Cummings commented on JENKINS-19096 Findbugs Reporting not working with Maven 3.1 Hi, Just noticed some of our Maven 3.1 builds are not reporting findbugs errors due to this issue. I will set them to Maven 3.0.x for now. Any ideas on how to fix this? thanks Geoff 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] [core] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Geoff Cummings commented on JENKINS-20682 Starting Jenkins with defined --webroot or JETTY_HOME not working. The following worked better for me: Set the jetty.home to Jenkins directory on the java opts when starting Jenkins -Djetty.home=$JENKINS_HOME Create a directory called "work" in Jenkins Home directory, or wherever you have set jetty.home That will cause Jetty to use that work directory instead of whatever the java.io.tmpdir property is set to. 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] [core] (JENKINS-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Geoff Cummings created JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Issue Type: Bug Assignee: bklarson Attachments: jenkinsQueueDeadlock.log Components: core, prioritysorter Created: 17/Dec/13 9:13 AM Description: Found one Java-level deadlock: = "Handling GET /jenkins/view/Portal/ : RequestHandlerThread[#12]": waiting to lock monitor 0x1a449d08 (object 0x000419d757e8, a hudson.ExtensionList$Lock), which is held by "QueueSorter.installDefaultQueueSorter" "QueueSorter.installDefaultQueueSorter": waiting to lock monitor 0x1ae56c48 (object 0x00041895e0f0, a hudson.model.Queue), which is held by "Queue.init" "Queue.init": waiting to lock monitor 0x1a449d08 (object 0x000419d757e8, a hudson.ExtensionList$Lock), which is held by "QueueSorter.installDefaultQueueSorter" Environment: Jenkins 1.544 Project: Jenkins Priority: Critical Reporter: Geoff Cummings 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Geoff Cummings created JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue Issue Type: Bug Affects Versions: current Assignee: abayer Components: throttle-concurrents Created: 17/Dec/13 2:34 PM Description: Jenkins had stopped responding to browser requests for Jenkins pages and I think it may be caused by the recent upgrade to Throttle Concurrent Builds 1.8.1 Requests were getting blocked waiting on 0x0004181e4520 "Handling GET /jenkins/ : RequestHandlerThread[#171]" daemon prio=10 tid=0x168ee800 nid=0x193b waiting for monitor entry [0x4335b000] java.lang.Thread.State: BLOCKED (on object monitor) at hudson.model.Queue.getItems(Queue.java:687) - waiting to lock 0x0004181e4520 (a hudson.model.Queue) at hudson.model.Queue$CachedItemList.get(Queue.java:216) at hudson.model.Queue.getApproximateItemsQuickly(Queue.java:717) at hudson.model.View.getApproximateQueueItemsQuickly(View.java:483) at sun.reflect.GeneratedMethodAccessor355.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) This seems to be waiting on Throttle Concurrent Builds code. Further dumps after 10 minutes, 20 minutes and 30 minutes showed this same stack trace. "Thread-126" daemon prio=10 tid=0x2aaae0529800 nid=0x1785 runnable [0x4659] java.lang.Thread.State: RUNNABLE at java.util.WeakHashMap$HashIterator.hasNext(WeakHashMap.java:875) at java.util.AbstractCollection.toArray(AbstractCollection.java:139) at java.util.ArrayList.init(ArrayList.java:164) at hudson.plugins.throttleconcurrents.ThrottleJobProperty.getCategoryProjects(ThrottleJobProperty.java:141) - locked 0x00041a79b778 (a java.util.HashMap) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:118) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:90) at hudson.model.Queue.isBuildBlocked(Queue.java:937) at hudson.model.Queue.maintain(Queue.java:1006) - locked 0x0004181e4520 (a hudson.model.Queue) at hudson.model.Queue$1.call(Queue.java:303) at hudson.model.Queue$1.call(Queue.java:300) at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:69) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:724) Locked ownable synchronizers: - None CPU usage was at ~100% for this thread for the 30 minutes that I was watching it before I restarted Jenkins. (6021 = 0x1785) PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 6021 rcbuild_ 35 10 18.0g 6.2g 32m R 99.7 19.7 30:45.97 java I have rolled back to Throttle Concurrent Builds 1.8 for now. Still learning how to investigate thread dumps but please let me know if there is anything I can do to help. Environment: Jenkins 1.544 Project: Jenkins Priority: Critical Reporter: Geoff Cummings 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
[JIRA] [core] (JENKINS-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Geoff Cummings
commented on JENKINS-20989
PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Some of the downstream builds might be configured for All, lastCompleted, lastSuccessful and others for lastStable. Multiple downstream builds might have different requirements. It would be better to have this config in one place, the downstream jobs, and not have to work around this change and require additional logic in the upstream build to determine what RunParameter to pass to the downstream job.
It worked as expected when the Run#getLastStableBuild used to be like:
public RunT getLastStableBuild() {
RunT r = getLastBuild();
while (r != null
(r.isBuilding() || r.getResult().isWorseThan(Result.SUCCESS)))
r = r.getPreviousBuild();
return r;
}
It no longer works after it was changed to use the Permalink
public RunT getLastStableBuild() {
return (RunT)Permalink.LAST_STABLE_BUILD.resolve(this);
}
The State.POST_PRODUCTION seems to be for this very scenario, where the build result is now final and it is now ok to trigger other builds as described in JENKINS-980
private static enum State {
/**
* Build is completed now, and the status is determined,
* but log files are still being updated.
*
* The significance of this state is that Jenkins
* will now see this build as completed. Things like
* "triggering other builds" requires this as pre-condition.
* See JENKINS-980.
*/
POST_PRODUCTION,
In the Run#execute method, I think we should update the PeepholePermalinks as soon as we change state and before we trigger fireCompleted on the listeners
Currently the Permalinks are updated in a fireCompleted event on a listener, the same as triggering downstream jobs. But they seem to be updated after the other builds are triggered.
// advance the state.
// the significance of doing this is that Jenkins
// will now see this build as completed.
// things like triggering other builds requires this as pre-condition.
// see issue #980.
//
state = State.POST_PRODUCTION;
if (listener != null) {
try {
job.cleanUp(listener);
} catch (Exception e) {
handleFatalBuildProblem(listener,e);
// too late to update the result now
}
RunListener.fireCompleted(this,listener);
listener.finished(result);
listener.closeQuietly();
}
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] [core] (JENKINS-20989) PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered
Geoff Cummings created JENKINS-20989 PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 12/Dec/13 3:20 PM Description: Scenario ProjectA triggers ProjectB ProjectB has a RunParameter for ProjectA with a filter set for Successful Builds Only. The Run Parameter uses the PeepholePermalink to determine the LastSuccessful build. When ProjectA completes successfully, it will trigger a build of ProjectB before the PeepholePermalink cache is updated. This causes the RunParameter to default to the previous successful build of ProjectA, not the one which has just completed. Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] [parameters] (JENKINS-20974) RunParameter with filtering enabled incorrectly includes builds which have not yet completed
Geoff Cummings created JENKINS-20974 RunParameter with filtering enabled incorrectly includes builds which have not yet completed Issue Type: Bug Assignee: Geoff Cummings Components: parameters Created: 11/Dec/13 9:49 PM Description: Builds have are still in progress can have a result of SUCCESS and so be included in a RunParamter which has filtering enabled. It should only include completed builds so we know the build result will not change. Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] [conditional-buildstep] (JENKINS-19976) NoClassDefFoundError when deleting jobs
Geoff Cummings
edited a comment on JENKINS-19976
NoClassDefFoundError when deleting jobs
I also started getting
java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper.getContainedBuilders(Lhudson/model/Project;Ljava/lang/Class;)Ljava/util/List;
This happens after upgrading to 1.3.2 on two Jenkins 1.538 installations when I try to delete a job, even after restarting Jenkins.
I had to downgrade to 1.3.1
Only thing I notice is that the method signature has changed:
-public static T extends BuildStep ListT getContainedBuilders(Project?, ? p, ClassT type) {
+public static T extends BuildStep ListT getContainedBuilders(AbstractProject?, ? ap, ClassT type) {
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] [conditional-buildstep] (JENKINS-19976) NoClassDefFoundError when deleting jobs
Geoff Cummings
commented on JENKINS-19976
NoClassDefFoundError when deleting jobs
I also started getting
java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper.getContainedBuilders(Lhudson/model/Project;Ljava/lang/Class;)Ljava/util/List;
This happens after upgrading to 1.3.2 on two Jenkins 1.538 installations when I try to delete a job, even after restarting Jenkins.
I had to downgrade to 1.3.1
Only thing I notice is that the method signature has changed:
-public static T extends BuildStep ListT getContainedBuilders(Project?, ? p, ClassT type) {
+public static T extends BuildStep ListT getContainedBuilders(AbstractProject?, ? ap, ClassT type) {
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] [conditional-buildstep] (JENKINS-19976) NoClassDefFoundError when deleting jobs
Geoff Cummings
edited a comment on JENKINS-19976
NoClassDefFoundError when deleting jobs
I also started getting
java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper.getContainedBuilders(Lhudson/model/Project;Ljava/lang/Class;)Ljava/util/List;
This happens after upgrading to 1.3.2 on two Jenkins 1.538 installations when I try to delete a job, even after restarting Jenkins.
I had to downgrade to 1.3.1
Only thing I notice is that the method signature has changed:
-public static T extends BuildStep ListT getContainedBuilders(Project?, ? p, ClassT type) {
+public static T extends BuildStep ListT getContainedBuilders(AbstractProject?, ? ap, ClassT type) {
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] [call-remote-job] (JENKINS-18616) Build with paramters using wrong url
Geoff Cummings closed JENKINS-18616 as Fixed Build with paramters using wrong url Thanks very much!! working now, I think your plugin will be very useful!! Change By: Geoff Cummings (05/Jul/13 8:26 AM) Status: Resolved Closed 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] [call-remote-job] (JENKINS-18616) Build with paramters using wrong url
Geoff Cummings created JENKINS-18616 Build with paramters using wrong url Issue Type: Bug Affects Versions: current Assignee: takeshi ito Components: call-remote-job Created: 04/Jul/13 6:59 AM Description: When calling a build with paramters you need to use the following url: http://server/job/myjob/buildWithParameters?PARAMETER=Value currently it is using http://server/job/myjob/build?PARAMETER=Value Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] [call-remote-job] (JENKINS-18616) Build with paramters using wrong url
Geoff Cummings commented on JENKINS-18616 Build with paramters using wrong url Information from jenkins wiki: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build 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] [core] (JENKINS-18116) text() function does not work in xpath evaluation on XML API
Geoff Cummings commented on JENKINS-18116 text() function does not work in xpath evaluation on XML API hmm.. 403 if I try a wget, but chrome gives the Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. wget "https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text()" --2013-06-20 12:28:55-- https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text() Resolving ci.jenkins-ci.org (ci.jenkins-ci.org)... 63.246.20.93 Connecting to ci.jenkins-ci.org (ci.jenkins-ci.org)|63.246.20.93|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2013-06-20 12:28:55 ERROR 403: Forbidden. 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] [core] (JENKINS-18116) text() function does not work in xpath evaluation on XML API
Geoff Cummings edited a comment on JENKINS-18116 text() function does not work in xpath evaluation on XML API hmm.. 403 if I try a wget, but chrome gives the Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. wget "https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text()" --2013-06-20 12:28:55-- https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text() Resolving ci.jenkins-ci.org (ci.jenkins-ci.org)... 63.246.20.93 Connecting to ci.jenkins-ci.org (ci.jenkins-ci.org)|63.246.20.93|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2013-06-20 12:28:55 ERROR 403: Forbidden. 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] [core] (JENKINS-18116) text() function does not work in xpath evaluation on XML API
Geoff Cummings edited a comment on JENKINS-18116 text() function does not work in xpath evaluation on XML API hmm.. 403 if I try a wget, but chrome gives the Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. wget "https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text()" --2013-06-20 12:28:55-- https://ci.jenkins-ci.org/view/Jenkins%20core/api/xml?xpath=/listView/job[1]/name/text() Resolving ci.jenkins-ci.org (ci.jenkins-ci.org)... 63.246.20.93 Connecting to ci.jenkins-ci.org (ci.jenkins-ci.org)|63.246.20.93|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2013-06-20 12:28:55 ERROR 403: Forbidden. 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] [core] (JENKINS-7844) A Filter to sort jobs by last run time.
Geoff Cummings commented on JENKINS-7844 A Filter to sort jobs by last run time. Yeah I would also like to sort by last Ran! 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] [envinject] (JENKINS-16316) global variable not updated
Geoff Cummings
commented on JENKINS-16316
global variable not updated
I think it is related to the following code in EnvironmentVariablesNodeLoader:
for (NodeProperty? nodeProperty : Hudson.getInstance().getGlobalNodeProperties()) {
if (nodeProperty instanceof EnvironmentVariablesNodeProperty) {
EnvironmentVariablesNodeProperty variablesNodeProperty = (EnvironmentVariablesNodeProperty) nodeProperty;
EnvVars envVars = variablesNodeProperty.getEnvVars();
EnvInjectEnvVars envInjectEnvVars = new EnvInjectEnvVars(logger);
configNodeEnvVars.putAll(envVars);
envInjectEnvVars.resolveVars(configNodeEnvVars, nodeEnvVars);
}
}
Without the "Prepare jobs environment" checked, the if statement above resolves to false so env vars are not updated i think.
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] [core] (JENKINS-17355) LogRotator does not delete Maven Artifacts
Geoff Cummings closed JENKINS-17355 as Fixed LogRotator does not delete Maven Artifacts Change By: Geoff Cummings (28/May/13 11:11 AM) Status: Resolved Closed 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] [core] (JENKINS-17355) LogRotator does not delete Maven Artifacts
Geoff Cummings resolved JENKINS-17355 as Fixed LogRotator does not delete Maven Artifacts Resolved is 1.515 Freed 100GB of disk space. Change By: Geoff Cummings (28/May/13 11:11 AM) 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 -- 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] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Geoff Cummings
commented on JENKINS-17508
The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
This fix has allowed me to reclaim 100GB of disk space - thanks!!
Note to Tomek:
As far as I know, artifacts refers to files in the followin directories:
${jenkins_home}/jobs/${jobname}/modules/${moduleName}/builds/${build_number}/archive
and not modules/SOME_MODULE/builds
this may be the # of builds to keep option
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] [embeddable-build-status] (JENKINS-17038) unknown.png (No such file or directory)
Geoff Cummings closed JENKINS-17038 as Fixed unknown.png (No such file or directory) Change By: Geoff Cummings (28/May/13 11:18 AM) Status: Resolved Closed 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] [embeddable-build-status] (JENKINS-17038) unknown.png (No such file or directory)
Geoff Cummings resolved JENKINS-17038 as Fixed unknown.png (No such file or directory) Change By: Geoff Cummings (28/May/13 11:18 AM) 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 -- 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-17553) Archived artifacts of Maven Modules are no longer cleaned up
Geoff Cummings commented on JENKINS-17553 Archived artifacts of Maven Modules are no longer cleaned up Looks like duplicate of JENKINS-17355 and JENKINS-17508 After update to 1.515 I was able to reclaim 100GB of artifacts from maven modules. I think we can mark this as 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 -- 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] [core] (JENKINS-18116) text() function does not work in xpath evaluation on XML API
Geoff Cummings commented on JENKINS-18116 text() function does not work in xpath evaluation on XML API This has been disabled for security. For more infirmation and details on how to manually enable it again please see JENKINS-16877 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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Still got an error Jenkins Email Extension Plugin This plugin is a replacement for Jenkins's email publisher 2.29.2 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include No signature of method: java.lang.String.entry() is applicable for argument types: (java.util.LinkedHashMap, jenkins.model.MasterBuildConfiguration.config$_run_closure1) values: [[title:# of executors, field:numExecutors], ...] Possible solutions: every(), intern(), any(), next(), next(), every(groovy.lang.Closure) Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include No signature of method: java.lang.String.entry() is applicable for argument types: (java.util.LinkedHashMap, jenkins.model.MasterBuildConfiguration.config$_run_closure1) values: [[title:# of executors, field:numExecutors], ...] Possible solutions: every(), intern(), any(), next(), next(), every(groovy.lang.Closure) Status Code: 500 Exception: Stacktrace: groovy.lang.MissingMethodException: No signature of method: java.lang.String.layout() is applicable for argument types: (java.util.LinkedHashMap, hudson.security.GlobalSecurityConfiguration.index$_run_closure1) values: [[norefresh:true, permission:Permission[class hudson.model.Hudson,Administer], ...], ...] Possible solutions: wait() at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55) 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] [email-ext] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Sorry, I had to rush out earlier... I applied my change to my main jenkins environment earlier and emails seem to be working correctly and I have not got a MissingMethodException so I am hopeful... Any additional testing would be welcome 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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly My errors dont always mention sidepanel, see above for 2 examples... But posting this in the chance they may be related: They only seem to happen with Email Ext plugin version 2.29 installed, and only after one of my jobs triggers an email using this plugin. I have it configured to use a custom groovy template. Initial testing suggests the error doesnt happen if it sends a blank email instead of using the template.. I do not see the error if I downgrade the plugin to 2.28 Does anyone else have a similar setup? Do you use this plugin? 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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Still got an error. Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.String), center(java.lang.Number, java.lang.CharSequence), every(), every(groovy.lang.Closure) Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.String), center(java.lang.Number, java.lang.CharSequence), every(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) Exception: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/lib/form/descriptorList.jelly:84:76: st:include No signature of method: java.lang.String.optionalBlock() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:svnmerge_integratable, title:Accept Integration from Subversion feature branches, ...]] Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.515.jar!/lib/form/descriptorList.jelly:84:76: st:include No signature of method: java.lang.String.optionalBlock() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:svnmerge_integratable, title:Accept Integration from Subversion feature branches, ...]] at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) Jenkins Email Extension Plugin This plugin is a replacement for Jenkins's email publisher 2.29.1 Downgrade to 2.28 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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I'm wondering why its always java.lang.String. java.lang.String.header() java.lang.String.optionalBlock() java.lang.String.queue() java.lang.String.entry() 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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings
commented on JENKINS-17910
groovy.lang.MissingMethodException in sidepanel.jelly
I'm new to groovy, so this is a guess, but is it possible that the MethodMissingHandler in ScriptContent.Java is impacting other groovy code?
https://github.com/jenkinsci/email-ext-plugin/blob/4a6c1446ff95591a511cec527f2e5702c07a0c6d/src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java
GroovyShell shell = createEngine(Collections.singletonMap("methodMissing", (Object)InvokerHelper.getMethodPointer(handler, "methodMissing")));
shell.evaluate("Script.metaClass.methodMissing = methodMissing");
the exceptions are due to missingMethodExceptions
seems to happen after groovyTemplate email is sent which would execute this code
GroovyShell is created with the uberclassloader, would this cause metaClass changes to Script to remain and impact other functionality...
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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Doesn't show how to fix it, but suggests that shells are not always self contained: http://stackoverflow.com/questions/1612569/how-do-i-undo-meta-class-changes-after-executing-groovyshell 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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I am getting similar errors, but it is not always sidepanel.jelly 07-May-2013 14:56:53 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.CharSequence), center(java.lang.Number, java.lang.String), every(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) 07-May-2013 14:38:16 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include No signature of method: java.lang.String.entry() is applicable for argument types: (java.util.LinkedHashMap, jenkins.model.MasterBuildConfiguration.config$_run_closure1) values: [[title:# of executors, field:numExecutors], ...] Possible solutions: every(), intern(), any(), next(), next(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) 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] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
Geoff Cummings edited a comment on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly I am getting similar errors, but it is not always sidepanel.jelly 07-May-2013 14:56:53 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/hudson/PluginManager/table.jelly:49:41: st:include No signature of method: java.lang.String.header() is applicable for argument types: () values: [] Possible solutions: center(java.lang.Number), center(java.lang.Number), center(java.lang.Number, java.lang.CharSequence), center(java.lang.Number, java.lang.String), every(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:175) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) 07-May-2013 14:38:16 org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tr/j/jh/war/WEB-INF/lib/jenkins-core-1.514.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include No signature of method: java.lang.String.entry() is applicable for argument types: (java.util.LinkedHashMap, jenkins.model.MasterBuildConfiguration.config$_run_closure1) values: [[title:# of executors, field:numExecutors], ...] Possible solutions: every(), intern(), any(), next(), next(), every(groovy.lang.Closure) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) 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-17713) Maven Module links are now broken - missing Job Name
Geoff Cummings created JENKINS-17713 Maven Module links are now broken - missing Job Name Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 23/Apr/13 10:47 AM Description: Links to Maven modules are now generating an incorrect url Navigating to the following url: http://server_url/jenkins/job/JOB_NAME/modules I am presented with a list of Maven Modules. The link for each module is now: http://server_url/jenkins/job/maven.group.id$maven.artifact.id/ it should be: http://server_url/jenkins/job/JOB_NAME/maven.group.id$maven.artifact.id/ Also Note, This page used to display Maven Modules named as the Name value in its pom.xml It now displays them as JOB_NAME » maven.group.id:maven.artifact.id Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Geoff Cummings commented on JENKINS-17508 The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503. Wondering if it's related to this change: What's new in 1.503 (2013/02/26) "Discard old build records" behavior is now pluggable, allowing plugins to define custom logic. 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] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
Geoff Cummings commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Also seeing this after upgrade from 1.506 to 1.508 and Jenkins promoted builds plugin 2.9 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] (JENKINS-17355) LogRotator does not delete Maven Artifacts
Geoff Cummings
created JENKINS-17355
LogRotator does not delete Maven Artifacts
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
26/Mar/13 11:45 AM
Description:
For our maven jobs we deploy the artifacts to a Nexus Maven repository.
This requires that I do not select the "Disable automatic artifact archiving" option.
I have configured the LogRotator Discard old builds to keep the last 30 builds, but only keep 1 build with artifacts.
In multimodule maven builds the following directory is deleted:
${jenkins_home}/jobs/${jobname}/archive
The following directories are not deleted:
${jenkins_home}/jobs/${jobname}/modules/${moduleName}/builds/65/archive
Is there another way to deploy the artifacts to nexus and retain a build history without having to keep all the module artifacts?
Project:
Jenkins
Priority:
Major
Reporter:
Geoff Cummings
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] (JENKINS-6744) Need Good Run parameter
Geoff Cummings edited a comment on JENKINS-6744 Need Good Run parameter I have had a go at adding filtering based on Build result, this will also allow you to filter out jobs which have not completed yet. I am new at this so all feedback welcome!! https://github.com/jenkinsci/jenkins/pull/738 thanks Geoff 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] (JENKINS-6744) Need Good Run parameter
Geoff Cummings assigned JENKINS-6744 to Geoff Cummings Need Good Run parameter Change By: Geoff Cummings (14/Mar/13 2:39 PM) Assignee: huybrechts GeoffCummings 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] (JENKINS-6744) Need Good Run parameter
Geoff Cummings commented on JENKINS-6744 Need Good Run parameter Yes, I think it is the same as JENKINS-7280 "works just like the existing "Run Parameter", but is filtered to only include builds that have finished and didn't fail" 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] (JENKINS-6744) Need Good Run parameter
Geoff Cummings commented on JENKINS-6744 Need Good Run parameter I have had a go at adding filtering based on Build result, this will also allow you to filter out jobs which have not completed yet. I am new at this so all feedback welcome!! https://github.com/jenkinsci/jenkins/pull/728 thanks Geoff 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] (JENKINS-7280) run parameters show builds that have not completed or have failed / unstable
Geoff Cummings commented on JENKINS-7280 run parameters show builds that have not completed or have failed / unstable I have had a go at adding filtering based on Build result, this will also allow you to filter out jobs which have not completed yet. I am new at this so all feedback welcome!! https://github.com/jenkinsci/jenkins/pull/728 thanks Geoff 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] (JENKINS-7280) run parameters show builds that have not completed or have failed / unstable
Geoff Cummings assigned JENKINS-7280 to Geoff Cummings run parameters show builds that have not completed or have failed / unstable Change By: Geoff Cummings (05/Mar/13 8:55 PM) Assignee: GeoffCummings 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] (JENKINS-7280) run parameters show builds that have not completed or have failed / unstable
Geoff Cummings started work on JENKINS-7280 run parameters show builds that have not completed or have failed / unstable Change By: Geoff Cummings (05/Mar/13 9:03 PM) Status: Open InProgress 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] (JENKINS-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
Geoff Cummings commented on JENKINS-15865 Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin Thanks for looking into it Kutzi. It is fixed in 1.504 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] (JENKINS-17038) unknown.png (No such file or directory)
Geoff Cummings created JENKINS-17038 unknown.png (No such file or directory) Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 04/Mar/13 9:00 AM Description: Hi, Thanks for adding an unknown badge for disabled builds. It looks like unknown.png has not been committed to the repository. https://github.com/jenkinsci/embeddable-build-status-plugin/tree/master/src/main/webapp/status This is causing the plugin to fail with the following error: WARNING: Failed to instantiate. Skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.io.FileNotFoundException: /tr/j/jh/plugins/embeddable-build-status/status/unknown.png (No such file or directory) at org.jenkinsci.plugins.badge.BadgeActionFactory.init(BadgeActionFactory.java:20) Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] (JENKINS-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
Geoff Cummings commented on JENKINS-15865 Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin Hi Kutzi, Not been able to see if it is caused by your change, but it looked slightly related to what is mentioned in the following commit message: https://github.com/jenkinsci/jenkins/commit/7fb1ad44d5aa26f2b0c6717c589b6d2be698224d Dont know enough about how this all works yet!! [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137) at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56) at hudson.maven.agent.ComponentConfiguratorFilter.configureComponent(ComponentConfiguratorFilter.java:49) at hudson.maven.agent.PluginManagerInterceptor$MojoIntercepter.configureComponent(PluginManagerInterceptor.java:146) at org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1357) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:724) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:468) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:154) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) I think it looks identical, apart from some line numbers slightly different in some lines at the bottom of the stack track at hudson.maven.MavenBuilder.call(MavenBuilder.java:154) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) This message is automatically generated by JIRA.
[JIRA] (JENKINS-17001) Multiple Shared Objects Groovy scripts cannot modify the same environment variable
Geoff Cummings
created JENKINS-17001
Multiple Shared Objects Groovy scripts cannot modify the same environment variable
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
shared-objects
Created:
28/Feb/13 11:09 AM
Description:
I have some legacy builds which require different versions of maven and grails to be set on the PATH.
I have setup some profiles for each version of maven
PATH = "MVN_221_DIR/bin:" + build.environment.PATH;
map.put("PATH", PATH);
and profiles to set the version of grails
PATH = "GRAILS_136_DIR/bin:" + build.environment.PATH;
map.put("PATH", PATH);
What I would like is a final PATH which contains both changes.
"GRAILS_136_DIR/bin:MVN_221_DIR/bin:original_path"
Actual result is just:
"GRAILS_136_DIR/bin:original_path"
It looks like the results of the steps are not added until the very end of the process, so modifications and new env variables added by step 1 are not available to step 2.
Project:
Jenkins
Priority:
Major
Reporter:
Geoff Cummings
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] (JENKINS-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
Geoff Cummings commented on JENKINS-15865 Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin I have retested using the steps mentioned above using https://github.com/ahjones/broken-failsafe-maven I received the same error. 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] (JENKINS-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
Geoff Cummings commented on JENKINS-15865 Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin Getting this error again after upgrading to 1.503 Wondering if it may be related to this change: https://github.com/jenkinsci/jenkins/commit/954a368c5612b7d7e7619277aca420c7c4930517 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] (JENKINS-15865) Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin
Geoff Cummings reopened JENKINS-15865 Jenkins build fails with fatal error for Maven 2 build of project with maven-failsafe-plugin Change By: Geoff Cummings (27/Feb/13 11:32 PM) Resolution: Fixed Status: Resolved Reopened 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] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
Geoff Cummings commented on JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf I was able to get the text() functionality back by setting hudson.model.Api.INSECURE=true when starting jenkins Please see the following link: https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-02-16 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] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
Geoff Cummings commented on JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf I am also getting the same problem after upgrading from 1.501 to 1.502 http://jenkins_url/job/job_name/lastSuccessfulBuild/api/xml?xpath=/*/numberreturns the following number100/number http://jenkins_url/job/job_name/lastSuccessfulBuild/api/xml?xpath=/*/number/text() returns ERROR 403: Forbidden 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] (JENKINS-16662) Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds
Geoff Cummings commented on JENKINS-16662 Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds new pull request. https://github.com/jenkinsci/parameterized-trigger-plugin/pull/35 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] (JENKINS-16662) Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds
Geoff Cummings created JENKINS-16662 Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds Issue Type: Improvement Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 06/Feb/13 11:22 AM Description: I would like to be able to perform conditional logic after triggering a blocking build without changing the build status. Currenty the TRIGGERED_BUILD_NUMBER is exported as an environment variable. It would also be useful to export the TRIGGERED_BUILD_RESULT which could be used in later build steps. Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] (JENKINS-16662) Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds
Geoff Cummings commented on JENKINS-16662 Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds I have created the following pull request for this: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/34 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] (JENKINS-16582) Add uberClassLoader to Shared Objects Groovy Scripts
Geoff Cummings created JENKINS-16582 Add uberClassLoader to Shared Objects Groovy Scripts Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: shared-objects Created: 31/Jan/13 9:35 PM Description: I am unable to import some classes into Shared Objects Groovy Scripts. EnvInject - ERROR - SEVERE ERROR occurs: startup failed: Script1.groovy: 2: unable to resolve class hudson.scm.SubversionSCM @ line 2, column 1. import hudson.scm.SubversionSCM; Initial investigation: GroovySharedObjectType.java GroovyShell groovyShell = new GroovyShell() Looking at how it was implemented in Environment Inject plugin, the following seems to fix my issue: GroovyShell shell = new GroovyShell(Hudson.getInstance().getPluginManager().uberClassLoader); Project: Jenkins Priority: Major Reporter: Geoff Cummings 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] (JENKINS-16582) Add uberClassLoader to Shared Objects Groovy Scripts
Geoff Cummings commented on JENKINS-16582 Add uberClassLoader to Shared Objects Groovy Scripts Created a pull request with this change: https://github.com/jenkinsci/shared-objects-plugin/pull/1 Still learning about this, so please let me know if there is a better way to do it. 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] (JENKINS-15918) RunParameter environment variabes contain . character
Geoff Cummings
updated JENKINS-15918
RunParameter environment variabes contain . character
Change By:
Geoff Cummings
(10/Dec/12 9:09 AM)
Description:
TheRunParametercreates2environmentvariableswhichcontaina.character.Icannotreferencetheseenvironmentvariablesfromabashscriptduetothischaracter.envPARAMETER_X=http://xxx/jenkins/job/ASE_CI/2072/PARAMETER_X.number=2072PARAMETER_X.jobName=ASE_CIecho${
PARAMETER_NAME
PARAMETER_X
.number}${
PARAMETER_NAME
PARAMETER_X
.number}:badsubstitutionCanyoualsocreateenvironmentvariableswhichuseanunderscore?PARAMETER_XPARAMETER_X_NUMBERPARAMETER_X_JOBNAME
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
[JIRA] (JENKINS-15918) RunParameter environment variabes contain . character
Geoff Cummings
updated JENKINS-15918
RunParameter environment variabes contain . character
Change By:
Geoff Cummings
(26/Nov/12 12:17 PM)
Description:
TheRunParametercreates2environmentvariableswhichcontaina.character.Icannotreferencetheseenvironmentvariablesfromabashscriptduetothischaracter.env
PARAMETER_NAME
PARAMETER_X
=http://xxx/jenkins/job/ASE_CI/2072/
PARAMETER_NAME
PARAMETER_X
.number=2072
PARAMETER_NAME
PARAMETER_X
.jobName=ASE_CIecho${PARAMETER_NAME.number}${PARAMETER_NAME.number}:badsubstitutionCanyoualsocreateenvironmentvariableswhichuseanunderscore?
PARAMETER_NAME
PARAMETER_X
PARAMETER_NAME_NUMBER
PARAMETER_X_NUMBER
PARAMETER_NAME_NAME
PARAMETER_X_JOBNAME
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
[JIRA] (JENKINS-14657) Embeddable Build Status Plugin url issue
Geoff Cummings updated JENKINS-14657 Embeddable Build Status Plugin url issue Updating component to newly created 'embeddable-build-status' component Change By: Geoff Cummings (12/Oct/12 2:36 PM) Labels: embeddable-build-status jenkinsplugin Component/s: embeddable-build-status Component/s: plugin 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
[JIRA] (JENKINS-15510) Embeddable Build Status plugin displays a Running badge for disabled jobs.
Geoff Cummings created JENKINS-15510 Embeddable Build Status plugin displays a Running badge for disabled jobs. Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 12/Oct/12 2:38 PM Description: The Embeddable Build Status plugin is displaying running.png when a project is disabled. running.png is the default option in the switch statement. default: file = "running.png"; Project: Jenkins Priority: Major Reporter: Geoff Cummings 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
[JIRA] (JENKINS-14056) Run Groovy scripts from files and environment variables
Geoff Cummings commented on JENKINS-14056 Run Groovy scripts from files and environment variables Hi, thanks for getting the changes in so quickly. I also need to access build parameters and environment variables. I am still learning about Jenkins and Groovy, but I have found I can access them with the following: def thr = Thread.currentThread() def build = thr.executable // get build parameters def buildVariablesMap = build.getBuildVariables() // get all environment variables for the build def buildEnvVarsMap = build.envVars String jobName = buildEnvVarsMap?.JOB_NAME Please advise if there is a better way to access this information many thanks Geoff 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
[JIRA] (JENKINS-14056) Run Groovy scripts from files and environment variables
Geoff Cummings edited a comment on JENKINS-14056 Run Groovy scripts from files and environment variables Hi, thanks for getting the changes in so quickly. I also need to access build parameters and environment variables. I am still learning about Jenkins and Groovy, but I have found I can access them with the following: def thr = Thread.currentThread() def build = thr.executable // get build parameters def buildVariablesMap = build.buildVariables // get all environment variables for the build def buildEnvVarsMap = build.envVars String jobName = buildEnvVarsMap?.JOB_NAME Please advise if there is a better way to access this information many thanks Geoff 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
[JIRA] (JENKINS-14056) Run Groovy scripts from files and environment variables
Geoff Cummings commented on JENKINS-14056 Run Groovy scripts from files and environment variables It sound like this change is the same as what I am currently trying to do: I would like to have a shared groovy script which could calculate environment variables. I would then like to be able to call this script from a job to set the environment variables for that job, instead of pasting the same groovy script into each job. 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
