[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title Klaus Schniedergers commented on JENKINS-53858 Re: Deadlock on EC2 resources For what it's worth - I noticed frequent lockups during mass node provisioning with 1.41 (on jenkins 2.150). I deployed 1.42-rc823.17ad3043e0e0 and haven't seen any more lockups since. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title Klaus Schniedergers commented on JENKINS-45719 Re: Description for a pipeline run is not compatible and cannot be disabled Adding this to the startup options worked to disable display of descriptions for runs in BlueOcean (haven't tried in recent versions): -Dblueocean.feature.run.description.enabled=false Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53359) job-dsl has deprecated concurrentBuild() on pipeline jobs
Title: Message Title Klaus Schniedergers commented on JENKINS-53359 Re: job-dsl has deprecated concurrentBuild() on pipeline jobs Thanks, that seems to work, Grigor Lechev. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53359) job-dsl has deprecated concurrentBuild() on pipeline jobs
Title: Message Title
Klaus Schniedergers commented on JENKINS-53359
Re: job-dsl has deprecated concurrentBuild() on pipeline jobs
Workaround:
pipelineJob('jobname') {
configure {
(it / 'concurrentBuild').setValue('false')
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-53359) job-dsl has deprecated concurrentBuild() on pipeline jobs
Title: Message Title Klaus Schniedergers commented on JENKINS-53359 Re: job-dsl has deprecated concurrentBuild() on pipeline jobs When looking into the config.xml, it seems that it's still `false` - so what should the replacement be for the supposedly-deprecated `concurrentBuild(false)` in pipeline jobs? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-37300) Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder
Title: Message Title Klaus Schniedergers commented on JENKINS-37300 Re: Update to version 1.22: ClassNotFoundException: com.joelj.jenkins.eztemplates.InheritenceStep.EzTemplateBuilder Running into the same issue when using latest LTS (2.7.4) plus "stable" plugins. Rolling multijob back to 1.21 fixes it, but I think it should be respun because otherwise every multijob user that updates plugins will see this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34381) Setting buildName via job-dsl does not enable before/after build options
Title: Message Title
Klaus Schniedergers created an issue
Jenkins / JENKINS-34381
Setting buildName via job-dsl does not enable before/after build options
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2016/Apr/21 11:27 PM
Environment:
Jenkins 1.651.1 with build-name-setter 1.6.3 and job-dsl 1.45
Priority:
Minor
Reporter:
Klaus Schniedergers
When using the "buildName" wrapper for a job via job-DSL, neither the "runAtStart" nor "runAtEnd" options are enabled, so the build name is never set. Setting these options is not supported by job-DSL either.
These seem to be newly supported options for build-name-setter. They are enabled by default when configuring a build name via GUI, but disabled when using Job-DSL.
With build-name-setter 1.5.1:
"build-name-setter@1.5.1">
#${BUILD_NUMBER} custom name
With build-name-setter 1.6.3:
[JIRA] [stashnotifier-plugin] (JENKINS-32817) stashnotifier-plugin credentials are broken
Title: Message Title Klaus Schniedergers commented on JENKINS-32817 Re: stashnotifier-plugin credentials are broken I see the same issue, on Jenkins 1.642.2 + stash-notifier 1.10.2. 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-19743) Massive parallel builds sometimes cause errors in LogRotation
Title: Message Title Klaus Schniedergers commented on JENKINS-19743 Re: Massive parallel builds sometimes cause errors in LogRotation I am seeing the same (SEVERE: Failed to rotate log), on 1.625.3 (most recent LTS). Once the SEVERE log entries start, Jenkins service starts to use all CPU it can get and becomes very slow/unresponsive. 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-20795) Jenkins hangs/unresponsive occasionally (with one core at100%)
Title: Message Title Klaus Schniedergers closed an issue as Cannot Reproduce This no longer happened on any instance for a long time. Jenkins / JENKINS-20795 Jenkins hangs/unresponsive occasionally (with one core at100%) Change By: Klaus Schniedergers Status: Open Closed Resolution: Cannot Reproduce 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-32019) Simple workflow hangs on "allocate node"
Title: Message Title Klaus Schniedergers edited a comment on JENKINS-32019 Re: Simple workflow hangs on "allocate node" It seems to be is related to the build-blocker plugin - after disabling updating build-blocker to 1.7.2 the workflow ran as expected. 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-32019) Simple workflow hangs on "allocate node"
Title: Message Title Klaus Schniedergers resolved as Duplicate Duplicate of JENKINS-29295 Jenkins / JENKINS-32019 Simple workflow hangs on "allocate node" Change By: Klaus Schniedergers 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] [workflow-plugin] (JENKINS-32019) Simple workflow hangs on "allocate node"
Title: Message Title Klaus Schniedergers commented on JENKINS-32019 Re: Simple workflow hangs on "allocate node" It seems to be related to the build-blocker plugin - after disabling build-blocker the workflow ran as expected. 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-32019) Simple workflow hangs on "allocate node"
Title: Message Title Klaus Schniedergers updated an issue Jenkins / JENKINS-32019 Simple workflow hangs on "allocate node" Change By: Klaus Schniedergers Priority: Critical Minor 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-32019) Simple workflow hangs on "allocate node"
Title: Message Title
Klaus Schniedergers updated an issue
Jenkins / JENKINS-32019
Simple workflow hangs on "allocate node"
Change By:
Klaus Schniedergers
This workflow: {quote} node {echo "hello world"} {quote} results in: {quote} Started by user anonymous[Workflow] Allocate node : StartStill waiting to schedule taskWaiting for next available executor {quote} There are plenty of executors available, and other non-workflow jobs are able to allocate one. I see the same issue on separate similarly-configured Jenkins instances.Log: {quote} Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: SEVERE: Timer task hudson.model.Queue$MaintainTask@2054b466 failedDec 10 12:55:11 ip-172-29-0-82 [jenkins]: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask cannot be cast to hudson.model.AbstractProjectDec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.getBuildBlockerProperty(BuildBlockerQueueTaskDispatcher.java:199)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canTake(BuildBlockerQueueTaskDispatcher.java:108)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.model.Queue$JobOffer.canTake(Queue.java:301)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.model.Queue.maintain(Queue.java:1544)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.model.Queue$MaintainTask.doRun(Queue.java:2709)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.lang.Thread.run(Thread.java:745) {quote}
Add Comment
[JIRA] [workflow-plugin] (JENKINS-32019) Simple workflow hangs on "allocate node"
Title: Message Title
Klaus Schniedergers updated an issue
Jenkins / JENKINS-32019
Simple workflow hangs on "allocate node"
Change By:
Klaus Schniedergers
This workflow:{quote}node \ {echo "hello world" \ }{quote}results in:{quote}Started by user anonymous[Workflow] Allocate node : StartStill waiting to schedule taskWaiting for next available executor{quote}There are plenty of executors available, and other non-workflow jobs are able to allocate one. I see the same issue on separate similarly-configured Jenkins instances.Log:{quote}Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: SEVERE: Timer task hudson.model.Queue$MaintainTask@2054b466 failedDec 10 12:55:11 ip-172-29-0-82 [jenkins]: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask cannot be cast to hudson.model.AbstractProjectDec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.getBuildBlockerProperty(BuildBlockerQueueTaskDispatcher.java:199)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canTake(BuildBlockerQueueTaskDispatcher.java:108)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.model.Queue$JobOffer.canTake(Queue.java:301)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.model.Queue.maintain(Queue.java:1544)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.model.Queue$MaintainTask.doRun(Queue.java:2709)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at java.lang.Thread.run(Thread.java:745){quote}
Add Comment
[JIRA] [workflow-plugin] (JENKINS-32019) Simple workflow hangs on "allocate node"
Title: Message Title
Klaus Schniedergers created an issue
Jenkins / JENKINS-32019
Simple workflow hangs on "allocate node"
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
10/Dec/15 9:00 PM
Environment:
1.625.3 (Jenkins core) 1.11 (workflow plugin)
Priority:
Critical
Reporter:
Klaus Schniedergers
This workflow:
node { echo "hello world" }
results in:
Started by user anonymous [Workflow] Allocate node : Start Still waiting to schedule task Waiting for next available executor
There are plenty of executors available, and other non-workflow jobs are able to allocate one. I see the same issue on separate similarly-configured Jenkins instances.
Log:
Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: SEVERE: Timer task hudson.model.Queue$MaintainTask@2054b466 failed Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask cannot be cast to hudson.model.AbstractProject Dec 10 12:55:11 ip-172-29-0-82 [jenkins]: #011at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.getBuildBlockerProperty(BuildBlocker
[JIRA] [job-dsl-plugin] (JENKINS-28217) job_dsl's scm->git->clean should enable the "clean" option
Title: Message Title
Klaus Schniedergers commented on JENKINS-28217
Re: job_dsl's scm->git->clean should enable the "clean" option
Thanks Daniel, changing the DSL code to this made it work.
freeStyleJob('Sandbox/clean-test') {
scm {
git {
remote {
url('ssh://g...@xxx.yyy.com/sandbox')
}
clean()
}
}
}
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-28217) job_dsl's scm->git->clean should enable the "clean" option
Title: Message Title Klaus Schniedergers commented on JENKINS-28217 Re: job_dsl's scm->git->clean should enable the "clean" option The "scm->git->clean()" directive seems to work for some other more complex generated jobs on the same server though. 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-28217) job_dsl's scm->git->clean should enable the "clean" option
Title: Message Title
Klaus Schniedergers created an issue
Jenkins / JENKINS-28217
job_dsl's scm->git->clean should enable the "clean" option
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
04/May/15 9:14 PM
Environment:
(Latest LTS/stable versions) Jenkins: 1.596.2 Job DSL plugin: 1.32 Git Plugin: 2.3.5 Git client plugin: 1.17.0
Priority:
Minor
Reporter:
Klaus Schniedergers
This job_dsl script does not enable the "clean before/after checkout" option:
freeStyleJob('Sandbox/clean-test') {
scm {
git('ssh://g...@xxx.yyy.com/sandbox') {
clean(true)
}
}
}
Resulting XML:
[...]
ssh://g...@xxx.yyy.com/sandbox
**
2
false
false
false
false
false
false
false
false
false
Default
false
[JIRA] [job-dsl-plugin] (JENKINS-27368) job-dsl folder should support using only a name argument
Klaus Schniedergers
created JENKINS-27368
job-dsl folder should support using only a name argument
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
11/Mar/15 6:41 PM
Description:
I converted my Job-DSL scripts to the 1.30 syntax changes, and tried:
[...]
folder("Sandbox")
[...]
"Process DSL" complained about:
FATAL: No signature of method: sandbox.folder() is applicable for argument types: (java.lang.String) values: [Sandbox]
Possible solutions: folder(groovy.lang.Closure), folder(java.lang.String, groovy.lang.Closure), find(), collect(), queue(java.lang.String), sleep(long)
groovy.lang.MissingMethodException: No signature of method: sandbox.folder() is applicable for argument types: (java.lang.String) values: [Sandbox]
The workaround is to add an empty closure like this:
folder("Sandbox) {}
but I would expect it to work without it.
Environment:
Job-DSL 1.30
Jenkins 1.596.1
Project:
Jenkins
Priority:
Minor
Reporter:
Klaus Schniedergers
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] [email-ext-plugin] (JENKINS-26867) Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll
Klaus Schniedergers edited a comment on JENKINS-26867 Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll The update to token-macro 1.10 fixed it (it was 1.5.1). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-26867) Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll
Klaus Schniedergers commented on JENKINS-26867 Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll The update to token-macro 1.10 fixed it (it was 1.5). 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] [email-ext-plugin] (JENKINS-26867) Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll
Klaus Schniedergers commented on JENKINS-26867 Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll Daniel - indeed I do (manage by Chef). So I assume you have a hunch of what causes this? 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] [email-ext-plugin] (JENKINS-26867) Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll
Klaus Schniedergers
updated JENKINS-26867
Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll
Change By:
Klaus Schniedergers
(09/Feb/15 9:29 PM)
Description:
I get the same error with any email-ext usage, even when the job has
nothgin else
no build steps or other post-build steps
configured:{code}Checking if email needs to be generatedEmail was triggered for: AlwaysSending email for trigger: AlwaysNOT overriding default server settings, using Mailer to create sessionERROR: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exceptionjava.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/AbstractBuild;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String; at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:72) at hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:647) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:535) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:306) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:297) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:244) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1791) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240){code}
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] [email-ext-plugin] (JENKINS-26867) Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll
Klaus Schniedergers created JENKINS-26867 Error when using email-ext 2.39 with Jenkins LTS 1.580.3: java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 09/Feb/15 9:29 PM Description: I get the same error with any email-ext usage, even when the job has nothgin else configured: Checking if email needs to be generated Email was triggered for: Always Sending email for trigger: Always NOT overriding default server settings, using Mailer to create session ERROR: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exception java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/AbstractBuild;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String; at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:72) at hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:647) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:535) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:306) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:297) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:244) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1791) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins LTS 1.580.3 on Ubuntu 14.04 email-ext 2.39 Using localhost / port 25 for email Project: Jenkins Priority: Minor Reporter: Klaus Schniedergers 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] [envinject] (JENKINS-14437) envinject fails to "really" set/override build parameters
Klaus Schniedergers commented on JENKINS-14437 envinject fails to "really" set/override build parameters This started to happen to our instance after a restart (it worked before).' I am setting an environment variable via "Prepare an environment for the run->Properties Content", but it is not set in a build step. Jenkins: LTS 1.532.3 EnvInject: 1.89 It's affecting all jobs/projects. 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-10593) Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL
Klaus Schniedergers commented on JENKINS-10593 Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL This would solve my problem...I'm trying to restrict authenticated users from configuring just one job, but "authenticated" has job config permissions in global security. Did this ever get solved somehow? (without having to buy Cloudbee's product) 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-20795) Jenkins hangs/unresponsive occasionally (with one core at100%)
Klaus Schniedergers updated JENKINS-20795 Jenkins hangs/unresponsive occasionally (with one core at100%) Change By: Klaus Schniedergers (27/Nov/13 7:25 PM) Summary: Jenkins hangs/ unrepsonsive unresponsive occasionally (with one core at100%) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20795) Jenkins hangs/unrepsonsive occasionally (with one core at100%)
Klaus Schniedergers created JENKINS-20795 Jenkins hangs/unrepsonsive occasionally (with one core at100%) Issue Type: Bug Assignee: Unassigned Attachments: dump20131126-0826.txt Components: core Created: 27/Nov/13 7:24 PM Description: About once every 1-2 weeks, our Jenkins service stops responding, i.e. the web page is not responding. The symptoms are "top" showing 100% for a Java process (on a many-cores box, so it looks like only one core is stuck at 100%). There are not obvious issues/errors in the log that are leasing up to this issue. A thread dump is attached. Environment: Jenkins 1.539 on Ubuntu 12.04 LTS Project: Jenkins Priority: Major Reporter: Klaus Schniedergers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20532) HTTP session count
Klaus Schniedergers commented on JENKINS-20532 HTTP session count I see the same issue in our 1.539 instance. What's worse is that I see a significant increase in sessions before the service becomes unresponsive and has to be restarted. Currently we have ~200 sessions in the counter, but only ~12 sessions listed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
