[JIRA] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title klou created an issue Jenkins / JENKINS-28195 Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter-plugin Created: 04/May/15 7:09 AM Environment: Priority Sorter 3.0, CloudBees Folder 4.7 Jenkins 1.612 running under Tomcat 8 on JDK 1.8.45 64Bit, Windows Server 2008 Priority: Blocker Reporter: klou After upgrade to Priority Sorter 3.0 and defining the new Priority Groups Jenkins doesn't schedule any more jobs but just throws NPE: May 04, 2015 8:08:10 AM SEVERE hudson.triggers.SafeTimerTask run Timer task hudson.model.Queue$MaintainTask@eccba45 failed java.lang.NullPointerException at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:80) at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:76) at java.util.TimSort.countRunAndMakeAscending(TimSort.java:351) at java.util.TimSort.sort(TimSort.java:216) at java.util.Arrays.sort(Arrays.java:1512) at java.util.ArrayList.sort(ArrayList.java:1454) at java.util.Collections.sort(Collections.java:175) at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:76
[JIRA] [gradle-jpi-plugin] (JENKINS-28196) Why is findbugs is listed as a dependancy?
Title: Message Title Andrew Sumner created an issue Jenkins / JENKINS-28196 Why is findbugs is listed as a dependancy? Issue Type: Bug Assignee: Daniel Spilker Components: gradle-jpi-plugin Created: 04/May/15 7:11 AM Priority: Minor Reporter: Andrew Sumner Any reason findbugs is listed as a dependancy in the uploaded pom file? Does this mean it's been added to my hpi file? findbugs annotations 1.0.0 runtime http://repo.jenkins-ci.org/releases/com/inedo/buildmaster/inedo-buildmaster/1.1/ (Apologies if I am misusing jira for this question, wasn't sure what was correct forum for this) Add Comment
[JIRA] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title
klou updated an issue
Jenkins / JENKINS-28195
Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Change By:
klou
After upgrade to Priority Sorter 3.0 and defining the new Priority Groups Jenkins doesn't schedule any more jobs but just throws NPE:{noformat}May 04, 2015 8:08:10 AM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.model.Queue$MaintainTask@eccba45 failedjava.lang.NullPointerException at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:80) at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:76) at java.util.TimSort.countRunAndMakeAscending(TimSort.java:351) at java.util.TimSort.sort(TimSort.java:216) at java.util.Arrays.sort(Arrays.java:1512) at java.util.ArrayList.sort(ArrayList.java:1454) at java.util.Collections.sort(Collections.java:175) at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:76) at hudson.model.Queue.maintain(Queue.java:1342) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2457) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){noformat}Priority Sorter Log itself looks very much normal and priorities seem to be assigned as expected. There are no exceptions in that log:{noformat}[...]New Item: Id: 20542, JobName: XXX-Sync-Rsync-Repository with ..., jobGroupId: 2, reason: , priority: 1, weight: 1.0, status: WAITING Evaluating JobGroup [0] ... Evaluating JobGroup [1] ... Evaluating JobGroup [2] ... Evaluating strategies ...Evaluating strategy [Job Triggered by a Upstream Build] ...Evaluating strategy [Take the priority from Property on the Job] ... No applicable strategy - Using JobGroup defaultMay 04, 2015 8:07:02 AM FINE jenkins.advancedqueue.ItemTransitionLogger logBuilableItemBuildable: Id: 20542, JobName: ***-Sync-Rsync-Repository with ***, jobGroupId: 2, reason: , priority: 1, weight: 1.0, status: BUILDABLEMay 04, 2015 8:11:02 AM FINER PrioritySorter.Queue.ItemsNew Item: Id: 20543, JobName: ADMIN_***_Install_RTS_***-slave8, jobGroupId: 6, reason: , priority: 3, weight: 3.0, status: WAITING Evaluating JobGroup [0] ... Evaluating JobGroup [1] ... Evaluating JobGroup [2] ... Evaluating JobGroup [3] ... Evaluating JobGroup [4] ... Evaluating JobGroup [5] ... Checking for Job Property inclusion for [*** Unit Tests]... Checking for Cloudbees Folder inclusion ...Evaluating Folder [ADMIN_***_Install_RTS] ... No match ... Evaluating JobGroup [6] ... Evaluating strategies ...Evaluating strategy [Job Triggered by a Upstream Build] ...Evaluating strategy [Take the priority from Propert
[JIRA] [core] (JENKINS-28197) Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
Title: Message Title Flominator created an issue Jenkins / JENKINS-28197 Jenkins requires Java5 or later, but you are running 1.5.0_07-b03 Issue Type: Bug Assignee: Unassigned Components: core Created: 04/May/15 7:46 AM Environment: Jenkins ver. 1.610 Labels: java java5 Priority: Minor Reporter: Flominator I think the summary is pretty much self explaining: I always expected Java 1.5 to be Java5. Am I wrong? Jenkins requires Java5 or later, but you are running 1.5.0_07-b03 from C:\Progra mme\Java\jre1.5.0_07 java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java
[JIRA] [core] (JENKINS-28197) Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
Title: Message Title Flominator updated an issue Jenkins / JENKINS-28197 Jenkins requires Java5 or later, but you are running 1.5.0_07-b03 Change By: Flominator I think the summary is pretty much self explaining: I always expected Java 1.5 to be Java5. Am I wrong? Message should be a little more precise ... Jenkins requires Java5 or later, but you are running 1.5.0_07-b03 from C:\Programme\Java\jre1.5.0_07java.lang.UnsupportedClassVersionError: Bad version number in .class fileat java.lang.ClassLoader.defineClass1(Native Method)at java.lang.ClassLoader.defineClass(Unknown Source)at java.security.SecureClassLoader.defineClass(Unknown Source)at java.net.URLClassLoader.defineClass(Unknown Source)at java.net.URLClassLoader.access$100(Unknown Source)at java.net.URLClassLoader$1.run(Unknown Source)at java.security.AccessController.doPrivileged(Native Method)at java.net.URLClassLoader.findClass(Unknown Source)at java.lang.ClassLoader.loadClass(Unknown Source)at java.lang.ClassLoader.loadClass(Unknown Source)at java.lang.ClassLoader.loadClassInternal(Unknown Source)at java.lang.Class.getDeclaredMethods0(Native Method)at java.lang.Class.privateGetDeclaredMethods(Unknown Source)at java.lang.Class.getMethod0(Unknown Source)at java.lang.Class.getMethod(Unknown Source)at Main._main(Main.java:202)at Main.main(Main.java:98) Thanks,Flo Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you
[JIRA] [gradle-jpi-plugin] (JENKINS-28196) Why is findbugs is listed as a dependancy?
Title: Message Title Daniel Spilker resolved as Fixed This has been fixed in version 0.11.0. Jenkins / JENKINS-28196 Why is findbugs is listed as a dependancy? Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [template-project-plugin] (JENKINS-24537) No e-mail when using other/template post-build steps
Title: Message Title Tom Ghyselinck commented on JENKINS-24537 Re: No e-mail when using other/template post-build steps This is still an issue with the latest releases: Jenkins 1.596.2 Email Extension Plugin 2.40 Matrix Project Plugin 1.4.1 It only applies to the configuration: Trigger only parent job When any of the axis Job from the matrix Job fails, I expect an e-mail for the parent Job, but that seems not to work. When changing to Trigger for each configuration, we correctly get an e-mail for every failing axis build. But that is just what we don't want. We want a single e-mail for the (complete) Matrix Job, showing all failing axis builds. It seems really an issue related to the combination of the Matrix Project Plugin and Email Extension Plugin. Thank you in advance for looking into this! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nodejs-plugin] (JENKINS-28198) IllegalArgumentException after saving main configuration
Title: Message Title
Yves Schumann created an issue
Jenkins / JENKINS-28198
IllegalArgumentException after saving main configuration
Issue Type:
Bug
Assignee:
Unassigned
Components:
nodejs-plugin
Created:
04/May/15 8:11 AM
Priority:
Blocker
Reporter:
Yves Schumann
After updating Jenkins to 1.611 I'm unable to configure NodeJS. If I hit the save button on Jenkins main configuratino page, I got an IllegalArgumentException. See the following stacktrace:
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class jenkins.plugins.nodejs.tools.NodeJSInstallation from {"name":"0.10.x","home":"","properties":{"stapler-class-bag":"true","hudson-tools-InstallSourceProperty":{"installers":{"id":"0.10.31","npmPackages":"bower@1.3.9 grunt-cli@0.1.13 karma@0.12.16 karma-cli@0.0.4","npmPackagesRefreshHours":"72","kind":"hudson.plugins.nodejs.tools.NodeJSInstaller"
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:46)
at huds
[JIRA] [nodejs-plugin] (JENKINS-28198) IllegalArgumentException after saving main configuration
Title: Message Title Yves Schumann updated an issue Jenkins / JENKINS-28198 IllegalArgumentException after saving main configuration Change By: Yves Schumann Attachment: Stacktrace.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ghprb-plugin] (JENKINS-28199) The GH PR builder plugin loses the GH access token periodically
Title: Message Title Marius Gedminas created an issue Jenkins / JENKINS-28199 The GH PR builder plugin loses the GH access token periodically Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 04/May/15 8:49 AM Environment: Jenkins 1.612, ghprb-plugin 1.17 Priority: Major Reporter: Marius Gedminas The GitHub Pull Request Builder stops building pull requests once a week. The logs say it cannot access my (private) GitHub repositories. I check the configuration and notice that the Access Token field is empty. I copy the access token, hit Apply, and it works, for a while. Next week the situation repeats. I'm tracking the Jenkins configuration in Git using the SCM Sync configuration plugin. It shows a commit 'Modification on configuration(s) by SYSTEM' that modifies org.jenkinsci.plugins.ghprb.GhprbTrigger.xml to remove: username password accessToken
[JIRA] [github-plugin] (JENKINS-27477) github-plugin does not work with "insteadOf" in git url
Title: Message Title Kanstantsin Shautsou edited a comment on JENKINS-27477 Re: github-plugin does not work with "insteadOf" in git url Could you PR your proposed changes for further discussion? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [warnings-plugin] (JENKINS-28174) Limit a Console Parser to a build step
Title: Message Title Florian Reinhard commented on JENKINS-28174 Re: Limit a Console Parser to a build step I'll add examples for "false positives" as i encounter them: This is a line that i see when i run doxygen generation: Problems running dot: exit code=-1, command='dot', arguments='"D:/jenkins/jobs/myjob/WORKSP~1/BUILDT~1/somefolder/doxydoc/html/d6/d52/structt_something_collgraph.dot" -Tpng -o "D:/jenkins/jobs/myjob/WORKSP~1/BUILDT~1/somefolder/doxydoc/html/d6/d52/structt_somethingcoll_graph.png"' This line is then matched by the "Texas Instruments" parser. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title
Andrei Costescu commented on JENKINS-27708
Re: Concurrent build limits not honored on Jenkins 1.607
It seems to be fixed for me as well (I reported duplicate
JENKINS-28084
).
But now the same (as in above comment) happened to me multiple times: jobs get stuck from time to time in queue. Nothing else running, but they just won't start. If I cancel ('x' button) them from queue and start them again manually they do start.
I don't have a Build Blocker Plugin installed.
Can I check something more when I see this happening again to pinpoint the cause? Should we reopen or create separate bug report?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-28191) Job configuration screen stuck on LOADING due to a JavaScript TypeError
Title: Message Title Daniel Beck commented on JENKINS-28191 Re: Job configuration screen stuck on LOADING due to a _javascript_ TypeError Report needs full list of plugins and versions. If reproducible with these out of the box, we'll need to do a 'binary search' for the responsible plugin. Any chance you could assist with that? Is this a regression after a Jenkins update or plugin update/install? What recent config changes did you perform? Does this affect all browsers? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28197) Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
Title: Message Title Daniel Beck commented on JENKINS-28197 Re: Jenkins requires Java5 or later, but you are running 1.5.0_07-b03 Jenkins has required Java 6 for a long time, and recently moved to requiring Java 7. I'll try to find the source of that message and update it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28197) Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-28197 Jenkins requires Java5 or later, but you are running 1.5.0_07-b03 Change By: Daniel Beck Assignee: Daniel Beck Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28197) Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
Title: Message Title Daniel Beck commented on JENKINS-28197 Re: Jenkins requires Java5 or later, but you are running 1.5.0_07-b03 Where and when exactly does that message appear? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28194) job-dsl-plugin fails to
Title: Message Title Daniel Spilker resolved as Not A Defect This is a common question. I just updated the FAQ on the wiki to answer this: https://github.com/jenkinsci/job-dsl-plugin/wiki/Frequently-Asked-Questions#why-does-a-method-defined-in-an-outer-scope-takes-precedence-of-a-method-defined-in-an-inner-scope Jenkins / JENKINS-28194 job-dsl-plugin fails to Change By: Daniel Spilker Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Daniel Beck commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] I am sure it is not a network issue as I tried pinging the network from system start-up till the problem occurs. Why are you so sure about this? Pinging does not keep a connection open. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Vassilena Treneva commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] Hi Daniel, I will rephrase - I am sure that pinging the master from the slave is fine as I initially suspect some kind of network failure. Do you have some suggestion that can help me debug or resolve my problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28197) Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
Title: Message Title
Flominator updated an issue
Jenkins / JENKINS-28197
Jenkins requires Java5 or later, but you are running 1.5.0_07-b03
Message appears in console window after starting Jenkins from this batch file:
@echo off call batch\backup_config.bat
C: cd %ProgramFiles% cd Java
echo Scanning for java runtime environment FOR /F "delims=#" %%f IN ('dir /s /b /on java.exe') DO ( SET javapath=%%f )
IF "%javapath%"=="" (echo no java runtime environment found pause exit 1)
echo JRE found at %javapath% - now starting Jenkins echo on %javapath% -Djavax.net.ssl.trustStore=X:\hudstore -Djavax.net.ssl.trustStorePassword=123456 -jar x:\jenkins.war rem 2> c:\log_%COMPUTERNAME%.txt pause exit
Change By:
Flominator
Environment:
Jenkins ver. 1.610 Windows XP SP3
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins I
[JIRA] [_test] (JENKINS-28193) Unable to Log in to Jenkins with only Crome but its working fine in All other browsers
Title: Message Title Daniel Beck resolved as Not A Defect Not a bug. This is not a support site. Jenkins / JENKINS-28193 Unable to Log in to Jenkins with only Crome but its working fine in All other browsers Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nodejs-plugin] (JENKINS-28198) IllegalArgumentException after saving main configuration
Title: Message Title Daniel Beck resolved as Duplicate Should be fixed in 1.612. Jenkins / JENKINS-28198 IllegalArgumentException after saving main configuration Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28120) Jenkins core to require Java7
Title: Message Title Jan Geertsma commented on JENKINS-28120 Re: Jenkins core to require Java7 I have installed 1.612 but it broke one build, so I reverted to 1.611 Our Jenkins uses Java 1.8, the slave uses 1.7, but the broken build is a Maven project that depends on Java 1.6. In the job configuration the JDK is set to 1.6 and I tried the optional maven parameter -Dmaven.compiler.executable=/opt/java/jdk-1.6/bin/javac. In 1.612 I get a line in the console output which says " JENKINS-18403 ] JDK 5 not supported to run Maven" ... but I didn't specify JDK5, also restarting the build slaves didn't help. I applaud the upgrade to Java7 and I would like to upgrade our projects to Java7 or Java8, but some legacy code makes it complicated. 07:23:55 [BuildJob] $ /opt/java/jdk-1.6/bin/java -cp /opt/data/jenkins-agent/maven32-agent.jar:/opt/maven/apache-maven-3/boot/plexus-classworlds-2.5.1.jar:/opt/maven/apache-maven-3/conf/logging jenkins.maven3.agent.Maven32Main /opt/maven/apache-maven-3 /opt/data/jenkins-agent/slave.jar /opt/data/jenkins-agent/maven32-interceptor.jar /opt/data/jenkins-agent/maven3-interceptor-commons.jar 46882 07:23:56 <===[JENKINS REMOTING CAPACITY]===>channel started 07:23:56 ERROR: [JENKINS-18403] JDK 5 not supported to run Maven; retrying with slave Java and setting compile/test properties to point to /opt/java/jdk-1.6 07:23:56 maven32-agent.jar already up to date 07:23:56 maven32-interceptor.jar already up to date 07:23:56 maven3-interceptor-commons.jar already up to date 07:23:56 [BuildJob] $ /opt/java/jdk1.7.0_72/jre/bin/java -cp /opt/data/jenkins-agent/maven32-agent.jar:/opt/maven/apache-maven-3/boot/plexus-classworlds-2.5.1.jar:/opt/maven/apache-maven-3/conf/logging Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [xunit-plugin] (JENKINS-28190) New version of xUnit is NOT showing jBehave plugin.
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-28190 New version of xUnit is NOT showing jBehave plugin. Change By: Daniel Beck Component/s: xunit-plugin Component/s: accelerated-build-now-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build
Title: Message Title Daniel Beck commented on JENKINS-28188 Re: StringIndexOutOfBoundsException when no root cause for the build When a build has no root cause (possible when firing the job programmatically), Are you sure you're triggering the build correctly? scheduleBuild etc. all add a cause IIRC. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28200) update plugin makes timeout error
Title: Message Title sivajothi Dharmalingam created an issue Jenkins / JENKINS-28200 update plugin makes timeout error Issue Type: Bug Assignee: Unassigned Attachments: Capture.JPG Components: core Created: 04/May/15 11:20 AM Priority: Critical Reporter: sivajothi Dharmalingam Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [slack-plugin] (JENKINS-28201) Slack plugin check boxes for Include Test Summary and Notify Repeated Failure toggle wrong feature
Title: Message Title Jason Januzelli created an issue Jenkins / JENKINS-28201 Slack plugin check boxes for Include Test Summary and Notify Repeated Failure toggle wrong feature Issue Type: Bug Assignee: Unassigned Components: slack-plugin Created: 04/May/15 11:21 AM Environment: Jenkins 1.596.1, Slack Notification Plugin 1.7, Chrome Version 42.0.2311.90 m, Firefox 31.0 Priority: Minor Reporter: Jason Januzelli Checking Include Test Summary actually sets true in job configuration file and displays Notify Repeated Failure as checked. And then checking Notify Repeated Failure actually sets true in job configuration file and displays Include Test Summary as checked. Add Comment
[JIRA] [core] (JENKINS-28200) update plugin makes timeout error
Title: Message Title sivajothi Dharmalingam started work on JENKINS-28200 Change By: sivajothi Dharmalingam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26657) File context menu missing when installing Slave under windows with jnlp
Title: Message Title Daniel Beck assigned an issue to Unassigned Jenkins / JENKINS-26657 File context menu missing when installing Slave under windows with jnlp Change By: Daniel Beck Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-23151) codemirror-mode on f:textarea broken (was: Execute shell build step text not saved properly)
Title: Message Title Daniel Beck commented on JENKINS-23151 Re: codemirror-mode on f:textarea broken (was: Execute shell build step text not saved properly) vjuranek This should be resolved, right? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28200) update plugin makes timeout error
Title: Message Title sivajothi Dharmalingam updated an issue Jenkins / JENKINS-28200 update plugin makes timeout error Change By: sivajothi Dharmalingam Jenkins-> Manage Jenkins-> Manage plugins-> Advanced-> check now. when click checknow, it's make error like in attachment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build
Title: Message Title Damien Coraboeuf commented on JENKINS-28188 Re: StringIndexOutOfBoundsException when no root cause for the build Hi Daniel, I'm using the following piece of code: final AbstractProject job = ... List parameterValues = ... Jenkins.getInstance().getQueue() .schedule2( job, 0, new ParametersAction(parameterValues), new CauseAction(getCause(channel)) ); where getCause returns a custom cause. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build
Title: Message Title
Damien Coraboeuf edited a comment on JENKINS-28188
Re: StringIndexOutOfBoundsException when no root cause for the build
Hi Daniel,I'm using the following piece of code:{code}final AbstractProject job = ...List parameterValues = ...Jenkins.getInstance().getQueue().schedule2(job,0,new ParametersAction(parameterValues),new CauseAction(getCause(channel)));{code}where {{getCause}} returns a custom cause. My initial code in {{getCause}} was actually an anonymous class for the {{Cause}} implementation, and that causes actually the problem. By replacing the anonymous {{Cause}} implementation by a top level class fixed the problem on my side.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [envinject-plugin] (JENKINS-28188) StringIndexOutOfBoundsException when no root cause for the build
Title: Message Title
Damien Coraboeuf edited a comment on JENKINS-28188
Re: StringIndexOutOfBoundsException when no root cause for the build
Hi Daniel,I'm using the following piece of code:{code}final AbstractProject job = ...List parameterValues = ...Jenkins.getInstance().getQueue().schedule2(job,0,new ParametersAction(parameterValues),new CauseAction(getCause(channel)));{code}where {{getCause}} returns a custom cause.My initial code in {{getCause}} was actually returning an anonymous class for the {{Cause}} implementation, and that causes actually caused the problem. By replacing the anonymous {{Cause}} implementation by a top level class fixed the problem on my side.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title Magnus Sandberg commented on JENKINS-28195 Re: Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception What happens is that the sorter is instructed to sort items it has not seen before, the sorter should be informed of the items existence as it enters the queue. Did you start with an empty queue after the update or did you have items in the queue when you updated? Did you restart Jenkins after the update? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [naginator-plugin] (JENKINS-26637) naginator not running at all for multi-configuration job
Title: Message Title Arthur Garnier commented on JENKINS-26637 Re: naginator not running at all for multi-configuration job Hi ! Same problem for me, I would like to rerun only failed/unstable which contains "UNSTABLE", but this param is skipped ? All failed/unstable build run again... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28200) update plugin makes timeout error
Title: Message Title Daniel Beck commented on JENKINS-28200 Re: update plugin makes timeout error Are you working on this, or why did you change the issue status? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title Daniel Beck commented on JENKINS-28195 Re: Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception Plugins can only be updated after a restart. However when shutting down Jenkins cleanly, it saves the queue, and loads it upon restart. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title klou commented on JENKINS-28195 Re: Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception Yes, I had restart my Jenkins for updating the plugin. But yes: In my case there had been saved items in the queue from the time before shut down. Just like commented by Daniel. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title Magnus Sandberg commented on JENKINS-28195 Re: Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception Yes, the questions was rather if you had items in the queue in this specific situation. Just trying to figure out where the glitch is. I obviously need to handle this more gracefully but I would also like to understand where it fails because it shouldn't be possible to happen. My guess is that this is a start-up issue and if you empty the queue and re-queue your jobs after restart it will work. Just a guess, educated, but still ... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-25272) remoting-2.46.jar breaks JDK 5 Maven builds
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-25272 remoting-2.46.jar breaks JDK 5 Maven builds Change By: Jesse Glick Component/s: maven-plugin Component/s: remoting Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-25272) remoting-2.46.jar breaks JDK 5 Maven builds
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-25272 remoting-2.46.jar breaks JDK 5 Maven builds Change By: Jesse Glick Labels: Java5 Maven UnsupportedClassVersionError lts lts-candidate regression remoting Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
Title: Message Title Jesse Glick resolved as Duplicate Essentially a duplicate of JENKINS-25272. (BTW the Jenkins class loaders are in fact modular, as in OSGi. The problem here is that the slave agent shares code with the master, and the Maven plugin runs some of that same code also in the Maven process. It is just a foolish design.) Jenkins / JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28120) Jenkins core to require Java7
Title: Message Title Jesse Glick commented on JENKINS-28120 Re: Jenkins core to require Java7 Jan Geertsma see JENKINS-25272. You must now set the job configuration to JDK 7 or higher. The message is just out of date; what is not supported to run Maven is any version of Java older than what the Jenkins master itself requires. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-28189) Don't resume on restart
Title: Message Title Jesse Glick resolved as Won't Fix No real use case other than working around JENKINS-25550, which is normally done by deleting the build. Jenkins / JENKINS-28189 Don't resume on restart Change By: Jesse Glick Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-28187) redefining "node" causes unrecoverable hang
Title: Message Title Jesse Glick commented on JENKINS-28187 Re: redefining "node" causes unrecoverable hang Do you have a complete script to reproduce with? What is my_node? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26964) post-build action statuses handling
Title: Message Title Jesse Glick resolved as Fixed Not sure why JIRA link daemon did not notice the merge here. Jenkins / JENKINS-26964 post-build action statuses handling Change By: Jesse Glick Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-28063) Triggering the same job twice results in zombie workflow run
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28063 Re: Triggering the same job twice results in zombie workflow run Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildQueueListener.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerAction.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerListener.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/90f9e44d498e167d6ab7fd3ef744ac0980ea65ae Log: [FIXED JENKINS-28063] BuildTriggerAction must implement FoldableAction and multiple instances checked. Otherwise any redundant upstream builds never receive notification of the downstream build’s completion, and hang. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-28063) Triggering the same job twice results in zombie workflow run
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28063 Triggering the same job twice results in zombie workflow run Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-28063) Triggering the same job twice results in zombie workflow run
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28063 Re: Triggering the same job twice results in zombie workflow run Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildQueueListener.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerAction.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerListener.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/1c8d22ab0ee7471d0ceb56b03070579d873bf9b8 Log: Merge pull request #121 from jglick/coalesced-build- JENKINS-28063 JENKINS-28063 Handle redundant upstream builds Compare: https://github.com/jenkinsci/workflow-plugin/compare/408efbcfbc2f...1c8d22ab0ee7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28167) job-dsl-plugin fails to work on Jenkins ver. 1.557
Title: Message Title Daniel Spilker commented on JENKINS-28167 Re: job-dsl-plugin fails to work on Jenkins ver. 1.557 This is a bug in Jenkins core, at least in versions 1.557, 1.558 and 1.559. I tested 1.560 and the 1.554.2 LTS release and both do not show the bug. I opened a pull request to increase the minimum supported Jenkins core version to the 1.565 LTS release line. See https://github.com/jenkinsci/job-dsl-plugin/pull/471. If you are using older releases, it's recommended to use the LTS releases. See https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line. You could upgrade or downgrade to the nearest LTS release, e.g. 1.554.3 or 1.565.3. The Job DSL plugin will work in both. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27441 Re: hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/Run.java core/src/test/java/hudson/model/RunTest.java http://jenkins-ci.org/commit/jenkins/3bb39bbf1c1066570ef8a5a0c265befe6b0aec38 Log: Merge pull request #1591 from vb-linetco/patch-1 [FIXED JENKINS-27441] avoid IOOBE in getLog when called with 0 Compare: https://github.com/jenkinsci/jenkins/compare/43188ec7a333...3bb39bbf1c10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27441 hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27441) hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0
Title: Message Title Oleg Nenashev commented on JENKINS-27441 Re: hudson.model.Run.getLog throws IndexOutOfBoundsException when called with 0 Marked the issue as lts-candidate. The fix should be released in jenkins-1.613 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28167) job-dsl-plugin fails to work on Jenkins ver. 1.557
Title: Message Title Daniel Spilker resolved as Fixed Jenkins / JENKINS-28167 job-dsl-plugin fails to work on Jenkins ver. 1.557 Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28167) job-dsl-plugin fails to work on Jenkins ver. 1.557
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28167 Re: job-dsl-plugin fails to work on Jenkins ver. 1.557 Code changed in jenkins User: Daniel Spilker Path: Vagrantfile docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/CoreVersionASTTransformationSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContextSpec.groovy job-dsl-plugin/build.gradle http://jenkins-ci.org/commit/job-dsl-plugin/08a42d269b62cde2a88229d7e3a249aa064ab520 Log: Merge pull request #471 from CoreMedia/ JENKINS-28167 JENKINS-28167 updated minimum Jenkins core version to 1.565 Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/5db908747fe3...08a42d269b62 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE created an issue Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 04/May/15 1:29 PM Priority: Major Reporter: Raphaël UNIQUE after upgrading from 2.38.2 to 2.39, html content in html email is not correct. v2.38.2: Compte rendu d'installation sur WMS11DEV Veuillez trouver la liste des patchs installés sur l'environnement WMS11DEV : v 2.39: Compte rendu d'installation sur WMS11DEV Veuillez trouver la liste des patchs installés sur l'environnement WMS11DEV : the correct content is with Compte rendu d'installation sur WMS11DEV
[JIRA] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Alex Earl commented on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 In the subject you list 2.40, but in the comment you only list 2.39. Which version are you actually using? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title
Raphaël UNIQUE updated an issue
Jenkins / JENKINS-28202
groovy templates do not work after upgrading to 2.40
Change By:
Raphaël UNIQUE
we use many job sending email with groovy templates. after upgrading from 2.38.2 to 2. 39 40 version of the plugin , html content we have this error ( in html email is not correct.v2.38.2: {noformat}< the mail body >Compte rendu d'installation sur WMS11DEVVeuillez trouver la liste des patchs installés sur l'environnement WMS11DEV ) : {noformat}v 2 Groovy Template file [test . 39:{noformat}< groovy] was not found in $JENKINS_HOME / head>Compte rendu d'installation sur WMS11DEV email-templates. Veuillez trouver la liste des patchs installés sur l'environnement WMS11DEV :{noformat} we have in the correct default content is with : $ { noformat SCRIPT, template="test.groovy" } Compte rendu d'installation sur WMS11DEV{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Change By: Raphaël UNIQUE Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Change By: Raphaël UNIQUE Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE commented on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 sory, i was cloning an existing a previous issue. all is now up to date Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mailer-plugin] (JENKINS-4481) Send e-mails in a fixed width font
Title: Message Title Alex Earl commented on JENKINS-4481 Re: Send e-mails in a fixed width font Emails are sent in plain text, so there is no real control over the font that the email client uses to display the content. If you want to control the font, try using email-ext. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title
Raphaël UNIQUE updated an issue
Jenkins / JENKINS-28202
groovy templates do not work after upgrading to 2.40
Change By:
Raphaël UNIQUE
we use many job jobs sending email with groovy templates.after upgrading to 2.40 version of the plugin, we have this error (in the mail body):Groovy Template file [test.groovy] was not found in $JENKINS_HOME/email-templates.we have in the default content: ${SCRIPT, template="test.groovy"}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [mailer-plugin] (JENKINS-4481) Send e-mails in a fixed width font
Title: Message Title Alex Earl resolved as Won't Fix Jenkins / JENKINS-4481 Send e-mails in a fixed width font Change By: Alex Earl Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28203) unable to login via jenkins cli with active directory
Title: Message Title marlene cote created an issue Jenkins / JENKINS-28203 unable to login via jenkins cli with active directory Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 04/May/15 1:38 PM Environment: windows server jenkins cli NameMaven IDLicense Jenkins war org.jenkins-ci.main:jenkins-war:1.611 The MIT license Spring Framework: Web MVC org.springframework:spring-webmvc:2.5.6.SEC03 The Apache Software License, Version 2.0 Commons BeanUtils commons-beanutils:commons-beanutils:1.8.3 The Apache Software License, Version 2.0 Bouncy Castle Provider org.bouncycastle:bcprov-jdk15on:1.47 Bouncy Castle Licence oro oro:oro:2.0.8 The Apache Software License, Version 2.0 Task Reactor org.jenkins-ci:task-reactor:1.4 MIT License dom4j org.jenkins-ci.dom4j:dom4j:1.6.1-jenkins-4 BSD License Groovy org.codehaus.groovy:groovy-all:1.8.9 The Apache Software License, Version 2.0 ASM Analysis org.ow2.asm:asm-analysis:4.0 BSD StAX API stax:stax-api:1.0.1 The Apache Software License, Version 2.0 SSH CLI client authenticator org.jenkins-ci.modules:ssh-cli-auth:1.2 MIT License Google Guice - Core Library com.google.inject:guice:4.0-beta The Apache Software License, Version 2.0 commons-jelly-tags-xml commons-jelly:commons-jelly-tags-xml:1.1 The Apache Software License, Version 2.0 ASM Commons org.ow2.asm:asm-commons:4.0 BSD Custom Acess Modifier annotations org.kohsuke:access-modifier-annotation:1.4 MIT License jCIFS org.samba.jcifs:jcifs:1.3.17-kohsuke-1 GNU Lesser General Public License, version 2.1 Spring Framework: DAO org.springframework:spring-dao:1.2.9 The Apache Software License, Version 2.0 JLine jline:jline:0.9.94 BSD Spring Framework: AOP org.springframework:spring-aop:2.5.6.SEC03 The Apache Software License, Version 2.0 HttpClient commons-httpclient:commons-httpclient:3.1 Apache License Annotation Indexer org.jenkins-ci:annotation-indexer:1.7 MIT License jnr-posix com.github.jnr:jnr-posix:3.0.1 Common Public License - v 1.0 GNU General Public License Version 2 GNU Lesser General Public License Version 2.1 Woodstox org.codehaus.woodstox:wstx-asl:3.2.9 The Apache Software License, Version 2.0 Spring Framework: Core org.springframework:spring-core:2.5.
[JIRA] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title klou commented on JENKINS-28195 Re: Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception Thanks Magnus. I will give purging the queue and then updating a try tomorrow morning in our Jenkins maintenance window (7-8 CEST). Please also let me know if you need any other information and I'll try to provide it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mailer-plugin] (JENKINS-2550) Email should be sent when build node is taken offline.
Title: Message Title Alex Earl resolved as Won't Fix This doesn't belong in the mailer plugin, whose usage is for job emailing. A separate plugin would be best suited for this. Jenkins / JENKINS-2550 Email should be sent when build node is taken offline. Change By: Alex Earl Status: Reopened Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Alex Earl commented on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 Can you verify the value of JENKINS_HOME? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28204) Manage Jenkins -> Configure -> Save: JSONException
Title: Message Title Tom Ghyselinck created an issue Jenkins / JENKINS-28204 Manage Jenkins -> Configure -> Save: JSONException Issue Type: Bug Assignee: Unassigned Components: core Created: 04/May/15 1:44 PM Environment: Jenkins 1.596.2 Priority: Blocker Reporter: Tom Ghyselinck Hi, I get the following error while trying to save the Jenkins global configuration: javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["advanced"] is not a Boolean. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.interna
[JIRA] [prioritysorter-plugin] (JENKINS-28195) Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception
Title: Message Title Magnus Sandberg commented on JENKINS-28195 Re: Jenkins not scheduling any jobs after upgrade to Priority Sorter 3.0 but giving exception It would be great if you have the possibility to test with an empty queue, hopefully it works. The problem might (probably will) reoccur on each restart with existing queue so I will fix this as soon as I can. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ircbot-plugin] (JENKINS-22042) IRCBot disconnects after long idle
Title: Message Title Nick Hovaker commented on JENKINS-22042 Re: IRCBot disconnects after long idle @kutzi I will once it happens again on my instance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-28205) Add File Path and Add Foribidden File Path text boxes missing
Title: Message Title Joshua Shinn created an issue Jenkins / JENKINS-28205 Add File Path and Add Foribidden File Path text boxes missing Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 04/May/15 1:51 PM Priority: Minor Reporter: Joshua Shinn Text boxes for Add File Path and Add Forbidden File Path are missing from Gerrit Event setup. They appear only after an event is saved for the first time. Add Comment This messa
[JIRA] [mailer-plugin] (JENKINS-27933) mailer-plugin does not support mail adresses without an @-sign anymore
Title: Message Title Alex Earl resolved as Duplicate Jenkins / JENKINS-27933 mailer-plugin does not support mail adresses without an @-sign anymore Change By: Alex Earl Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Dirk von Husen commented on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 Seems like we have similar issues with only BuildBlocker (not the throttle concurrent builds plugin) installed. But we´re still running on 1610. Just looks like queued blocked builds are not triggert (or the regex check) again after one blocking build finished. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-13086) Clone to directory named for repository
Title: Message Title Lieven Cardoen commented on JENKINS-13086 Re: Clone to directory named for repository Is there already a solution for this without using the multiple-SCM plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-28206) Build selector "Downstream build of" should be usable as parameter filter
Title: Message Title Tom Ghyselinck created an issue Jenkins / JENKINS-28206 Build selector "Downstream build of" should be usable as parameter filter Issue Type: Improvement Assignee: Unassigned Components: copyartifact-plugin Created: 04/May/15 2:11 PM Environment: Jenkins 1.596.2 CopyArtifact Plugin 1.35 Priority: Major Reporter: Tom Ghyselinck In JENKINS-24626, we agreed to create a "Downstream build of" build selector. This works in the case that you always want to use the Last successful build which matches the upstream project. IMHO, the "Downstream build of" selector should be additional to the other build selectors. E.g. In our build environment we (mostly) need the case where we want to select: The Last promoted build From a Job which has is a "Downstream build of" a given configuration Possibly som
[JIRA] [copyartifact-plugin] (JENKINS-28206) Build selector "Downstream build of" should be usable as parameter filter
Title: Message Title Tom Ghyselinck updated an issue Jenkins / JENKINS-28206 Build selector "Downstream build of" should be usable as parameter filter Change By: Tom Ghyselinck Labels: copyartifact filter parameter parameterized Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Change By: Raphaël UNIQUE Attachment: screenshot-3.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28114) Update to 1.610 causing main Jenkins config page to throw
Title: Message Title Pulkit Singhal commented on JENKINS-28114 Re: Update to 1.610 causing main Jenkins config page to throw How did this get resolved? I don't see any mention of a solution Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-28206) Build selector "Downstream build of" should be usable as parameter or source filter
Title: Message Title Tom Ghyselinck updated an issue Jenkins / JENKINS-28206 Build selector "Downstream build of" should be usable as parameter or source filter Change By: Tom Ghyselinck Summary: Build selector "Downstream build of" should be usable as parameter or source filter Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cvs-plugin] (JENKINS-28207) Using varibale as branch name
Title: Message Title vikram bhimbar created an issue Jenkins / JENKINS-28207 Using varibale as branch name Issue Type: Task Assignee: Unassigned Components: cvs-plugin Created: 04/May/15 2:16 PM Labels: configuration jenkins branch slaves Priority: Major Reporter: vikram bhimbar Hi, I have a master project which calls a slave project from it. Now i want to define a CVS branch as variable from master project and this VARIABLE should be used by slave project as branch name and checkout using same. How to do this? Thanks, VIkram Add Comment
[JIRA] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE commented on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 verified: screenshot-3.png JENKINS_HOME=/appli/jenkins Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Change By: Raphaël UNIQUE Attachment: mail_result.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [copyartifact-plugin] (JENKINS-28206) Build selector "Downstream build of" should be usable as parameter or source filter
Title: Message Title Tom Ghyselinck commented on JENKINS-28206 Re: Build selector "Downstream build of" should be usable as parameter or source filter I have a suggestion for JENKINS-24890 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Change By: Raphaël UNIQUE Attachment: jenkins_home_cfg.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Raphaël UNIQUE updated an issue Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Change By: Raphaël UNIQUE Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-12731) Reducing the steps required for initial lockdown of a Jenkins instance (open ports, default permissions, etc.)
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-12731 Reducing the steps required for initial lockdown of a Jenkins instance (open ports, default permissions, etc.) I disagree with the plugin suggestion. As this affects services offered by Jenkins out of the box, and security, a plugin would be the wrong way to go IMO. Could be done in an 'initial setup wizard' (like the suggested reworking of bundled plugins), at least in parts. Change By: Daniel Beck Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title Alex Earl resolved as Fixed Fixed issue with check for file extension. Jenkins / JENKINS-28202 groovy templates do not work after upgrading to 2.40 Change By: Alex Earl Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [email-ext-plugin] (JENKINS-28202) groovy templates do not work after upgrading to 2.40
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28202 Re: groovy templates do not work after upgrading to 2.40 Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/AbstractEvalContent.java http://jenkins-ci.org/commit/email-ext-plugin/d5af533cb9ccb1d91be01d76738263fd6b4f24df Log: Fix JENKINS-28202 Fixed check for file extension Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26657) File context menu missing when installing Slave under windows with jnlp
Title: Message Title Christopher Biel commented on JENKINS-26657 Re: File context menu missing when installing Slave under windows with jnlp We also run Jenkins Master (and Slaves) on VMWare ESXi. I can also verify that the connection seem to be established (Master shows Slave as connected) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-26657) File context menu missing when installing Slave under windows with jnlp
Title: Message Title Alex Earl commented on JENKINS-26657 Re: File context menu missing when installing Slave under windows with jnlp Hmmm, I don't have a way to test with VMWare ESXi, I'll try with VMWare player to see if that makes a difference. What OS's are you running? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [instant-messaging-plugin] (JENKINS-28208) Crash with J9 1.6
Title: Message Title
Adrien CLERC created an issue
Jenkins / JENKINS-28208
Crash with J9 1.6
Issue Type:
Bug
Assignee:
kutzi
Components:
instant-messaging-plugin
Created:
04/May/15 3:09 PM
Environment:
Java J9 1.6 instant-messaging version 1.35
Priority:
Major
Reporter:
Adrien CLERC
After updating from 1.30 to 1.35, I encountered the following stack trace:
{{SEVERE: Failed Loading plugin ircbot Throwable occurred: java.io.IOException: Unable to load hudson.plugins.ircbot.PluginImpl from ircbot at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:422) at hudson.PluginManager$2$1$1.run(PluginManager.java:371) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:905) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931) at java.lang.Thread.run(Thread.java:738) Caused by: java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=hudson/plugins/im/IMPlugin, offset=6 at java.lang.ClassLoader.defineClassImpl(Native Method) at java.lang.ClassL
[JIRA] [testlink-plugin] (JENKINS-28209) [Testlink] : Junit test case are not running into testlink "not run"
Title: Message Title Simon LEFILS created an issue Jenkins / JENKINS-28209 [Testlink] : Junit test case are not running into testlink "not run" Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Conf.png, Conf2.png, junit_14_41_43.371.xml, result_JENKINS.png, Testsuite_on_Testlink.png Components: testlink-plugin Created: 04/May/15 3:12 PM Environment: WIN 7 Labels: plugins Priority: Blocker Reporter: Simon LEFILS Jenkins: 1.6010 Plugin of Testlink: 3.10 Testlink application: 1.9.13 I've connected a WIN 7 Slave machine on JENKINS. On this machine I have Squish that run an automatic test case. On my job, I’ve attached Testlink plugin and S
[JIRA] [script-security-plugin] (JENKINS-28154) IllegalArgumentException thrown when some binary operators are used
Title: Message Title
Adrien CLERC commented on JENKINS-28154
Re: IllegalArgumentException thrown when some binary operators are used
This indeed VERY annoying. The sandbox seems to apply to matrix combination filters. E.g.
!( ( distribution==/^opensuse13./ && VERSION<="1.53" ) || ( distribution==/^sles10./ && VERSION>="1.53" ) )
gives the following stack trace: {{SEVERE: Failed Loading job boost Throwable occurred: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runti me.ScriptBytecodeAdapter matchRegex java.lang.Object java.lang.Object at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:164) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:102) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:115) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43) at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.callStatic(StaticMetaMethodSite.java:99) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177) at Script1.run(Script1.groovy:1) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:139) at hudson.matrix.FilterScript.evaluate(FilterScript.java:45) at hudson.matrix.FilterScript.apply(FilterScript.java:85) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101) at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:638) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:505) at hudson.model.Items.load(Items.java:322) at jenkins.model.Jenkins$17.run(Jenkins.java:2655) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:905) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931) at java.lang.Thread.run(Thread.java:738)}}
I hope this is fixable, otherwise, the "use sandbox as default" should be reverted.
[JIRA] [script-security-plugin] (JENKINS-28154) IllegalArgumentException thrown when some binary operators are used
Title: Message Title
Adrien CLERC edited a comment on JENKINS-28154
Re: IllegalArgumentException thrown when some binary operators are used
This indeed VERY annoying. The sandbox seems to apply to matrix combination filters. E.g.{{!( ( distribution==~/^opensuse13.*/ && VERSION<="1.53" ) || ( distribution==~/^sles10.*/ && VERSION>="1.53" ) )}}gives the following stack trace: {{ SEVERE: Failed Loading job boostThrowable occurred: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.ScriptBytecodeAdapter matchRegex java.lang.Object java.lang.Objectat org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:164)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:102)at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:115)at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:112)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)at java.lang.reflect.Method.invoke(Method.java:611)at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.callStatic(StaticMetaMethodSite.java:99)at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177)at Script1.run(Script1.groovy:1)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:139)at hudson.matrix.FilterScript.evaluate(FilterScript.java:45)at hudson.matrix.FilterScript.apply(FilterScript.java:85)at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101)at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91)at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:638)at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:505)at hudson.model.Items.load(Items.java:322)at jenkins.model.Jenkins$17.run(Jenkins.java:2655)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:905)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:908)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:931)at java.lang.Thread.run(Thread.java:738) }} I hope this is fixable, otherwise, the "use sandbox as default" should be reverted.
[JIRA] [core] (JENKINS-20967) Cloud provisioning called when Jenkins is quieting Down
Title: Message Title Kanstantsin Shautsou commented on JENKINS-20967 Re: Cloud provisioning called when Jenkins is quieting Down Any news? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [labeled-test-groups-publisher-plugin] (JENKINS-20979) Publish Test Results in Labeled Groups is waiting for a checkpoint on
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20979 Re: Publish Test Results in Labeled Groups is waiting for a checkpoint on Code changed in jenkins User: Adam Berry Path: src/main/java/hudson/plugins/labeledgroupedtests/LabeledTestResultGroupPublisher.java http://jenkins-ci.org/commit/labeled-test-groups-publisher-plugin/31f0c42c4df480fc7ac5d5bf8edf629790c052b6 Log: [FIXED JENKINS-20979] Do not block on build step monitor. Fixes the serialization issue in concurrently running builds. This is consistent with the similar fixes in other jenkins plugins. EP-97 Authored by: Slava Gurevich , Adam Berry Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [labeled-test-groups-publisher-plugin] (JENKINS-20979) Publish Test Results in Labeled Groups is waiting for a checkpoint on
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20979 Re: Publish Test Results in Labeled Groups is waiting for a checkpoint on Code changed in jenkins User: Larry Bordowitz Path: src/main/java/hudson/plugins/labeledgroupedtests/LabeledTestResultGroupPublisher.java http://jenkins-ci.org/commit/labeled-test-groups-publisher-plugin/6a3fdf5a6e1ff660e548657e13063e8ec450f445 Log: Merge pull request #3 from Altiscale/ JENKINS-20979 [FIXED JENKINS-20979] Do not block on build step monitor. Fixes the serialization issue in concurrently running builds. Compare: https://github.com/jenkinsci/labeled-test-groups-publisher-plugin/compare/853aaabe8eb3...6a3fdf5a6e1f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
