[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Francois Pilote commented on JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) I was able to reproduce this bug on jenkins 1.556. The problem was one of my project had a "lastSuccessfulBuild" file that was corrupted from a computer reset. (Windows Server 2008 R2) I manually recreated the file with a valid number and saved it. This modification got the queue and the builds going. The exception that caught my attention was the following : Caught exception evaluating: it.lastSuccessfulBuild.ARTIFACTS in /job/Dev_OnCommit/. Reason: java.lang.reflect.InvocationTargetException It was this project that the file was corrupted. I attached the faulty file even though it is probably not interesting. (only 3 bytes) FYI, we have a big jenkins setup (200+ jobs, 12+slaves (mac, pc, win, unix...)) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Francois Pilote updated JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) Change By: Francois Pilote (26/May/14 9:26 PM) Attachment: lastSuccessfulBuild__broken This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Francois Pilote edited a comment on JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) I was able to reproduce this bug on jenkins 1.556. The problem was one of my project had a "lastSuccessfulBuild" file that was corrupted from a computer reset. (Windows Server 2008 R2) I manually recreated the file with a valid number and saved it. This modification got the queue and the builds going. The exception that caught my attention was the following : Caught exception evaluating: it.lastSuccessfulBuild.ARTIFACTS in /job/Dev_OnCommit/. Reason: java.lang.reflect.InvocationTargetException It was this project that the file was corrupted. I attached the faulty file even though it is probably not interesting. (only 3 bytes) You can probably reproduce the bug with this file. FYI, we have a big jenkins setup (200+ jobs, 12+slaves (mac, pc, win, unix...)) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-20927) FATAL: ${NODE_NAME}: Found unresolved macro at '${NODE_NAME}'
Francois Pilote
commented on JENKINS-20927
FATAL: ${NODE_NAME}: Found unresolved macro at ${NODE_NAME}
We are getting same kind of error on our setup after upgrading our jenkins installation. (jenkins 1.556, perforce plugin 1.3.27)
I'm not sure if it is the jenkins upgrade that caused the problem or the plugin upgrade (or something else)
here is our stacktrace :
Using node: Prodrender004
FATAL: //RNG/Code/Mainline/... //${basename}-${hash}/...: Found unresolved macro at '//RNG/Code/Mainline/... //${basename}-${hash}/...'
hudson.plugins.perforce.utils.ParameterSubstitutionException: //RNG/Code/Mainline/... //${basename}-${hash}/...: Found unresolved macro at '//RNG/Code/Mainline/... //${basename}-${hash}/...'
at hudson.plugins.perforce.utils.MacroStringHelper.checkString(MacroStringHelper.java:97)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:64)
at hudson.plugins.perforce.PerforceSCM.getEffectiveProjectPath(PerforceSCM.java:689)
at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1300)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject._poll(AbstractProject.java:1490)
at hudson.model.AbstractProject.poll(AbstractProject.java:1399)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491)
at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Done. Took 2 ms
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-20927) FATAL: ${NODE_NAME}: Found unresolved macro at '${NODE_NAME}'
Francois Pilote
edited a comment on JENKINS-20927
FATAL: ${NODE_NAME}: Found unresolved macro at ${NODE_NAME}
EDIT : i reverted the perforce plugin to 1.3.26, then to 1.3.25 and had the same error. Version 1.3.24 works correctly.
We are getting same kind of error on our setup after upgrading our jenkins installation. (jenkins 1.556, perforce plugin 1.3.27)
I'm not sure if it is the jenkins upgrade that caused the problem or the plugin upgrade (or something else)
here is our stacktrace :
Using node: Prodrender004
FATAL: //RNG/Code/Mainline/... //${basename}-${hash}/...: Found unresolved macro at '//RNG/Code/Mainline/... //${basename}-${hash}/...'
hudson.plugins.perforce.utils.ParameterSubstitutionException: //RNG/Code/Mainline/... //${basename}-${hash}/...: Found unresolved macro at '//RNG/Code/Mainline/... //${basename}-${hash}/...'
at hudson.plugins.perforce.utils.MacroStringHelper.checkString(MacroStringHelper.java:97)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:64)
at hudson.plugins.perforce.PerforceSCM.getEffectiveProjectPath(PerforceSCM.java:689)
at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1300)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject._poll(AbstractProject.java:1490)
at hudson.model.AbstractProject.poll(AbstractProject.java:1399)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:462)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:491)
at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Done. Took 2 ms
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
