[JIRA] [s3-plugin] (JENKINS-14470) S3 Plugin switches credential profiles
Title: Message Title Alexander A commented on JENKINS-14470 Re: S3 Plugin switches credential profiles Hoang Tran, it sounds weird. Could you provide any details (stacktrace, uploading/downloading or both, etc)? 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] [jiratestresultreporter-plugin] (JENKINS-34904) JiraTestResultReporter - Host name may not be null
Title: Message Title Andrei Tuicu started work on JENKINS-34904 Change By: Andrei Tuicu 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] [jiratestresultreporter-plugin] (JENKINS-34904) JiraTestResultReporter - Host name may not be null
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34904 Re: JiraTestResultReporter - Host name may not be null Code changed in jenkins User: Andrei Tuicu Path: src/main/java/org/jenkinsci/plugins/JiraTestResultReporter/JiraTestDataPublisher.java http://jenkins-ci.org/commit/JiraTestResultReporter-plugin/d0235007835d568a47973b7e206f7f62d769bc23 Log: Fix JENKINS-34904 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] [s3-plugin] (JENKINS-34780) Files from the entry path are not copied to S3 bucket's root directory relatively
Title: Message Title Alexander A commented on JENKINS-34780 Re: Files from the entry path are not copied to S3 bucket's root directory relatively So, if I understood correctly, we have some file structure: parent/a/c.txt parant/b/d.txt 1. Old behavior for matcher parent/** in bucket you have something like parent/c.txt parent/d.txt 2. New behavior: parent/a/c.txt parent/b/d.txt ? 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] [s3-plugin] (JENKINS-34780) Files from the entry path are not copied to S3 bucket's root directory relatively
Title: Message Title Alexander A commented on JENKINS-34780 Re: Files from the entry path are not copied to S3 bucket's root directory relatively If I misunderstood and you see "old behavior", it's 100% bug 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] [s3-plugin] (JENKINS-14470) S3 Plugin switches credential profiles
Title: Message Title Alexander A updated an issue Jenkins / JENKINS-14470 S3 Plugin switches credential profiles Change By: Alexander A Comment: [~hoang], it sounds weird. Could you provide any details (stacktrace, uploading/downloading or both, etc)? 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] [s3-plugin] (JENKINS-34780) Files from the entry path are not copied to S3 bucket's root directory relatively
Title: Message Title Joshua Spence commented on JENKINS-34780 Re: Files from the entry path are not copied to S3 bucket's root directory relatively I don't quite understand your example so let me provide my own... We are using the S3 plugin to upload `x/y/z/**` to `s3://my-bucket`. Previously, `x/y/z/a.txt` and `x/y/z/a/b.txt` would be uploaded to `s3://my-bucket/a.txt` and `s3://my-bucket/a/b.txt` respectively. With the latest version, `x/y/z/a.txt` and `x/y/z/a/b.txt` are uploaded to `s3://my-bucket/x/y/z/a.txt` and `s3://my-bucket/x/y/z/a/b.txt`. 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] [s3-plugin] (JENKINS-34780) Files from the entry path are not copied to S3 bucket's root directory relatively
Title: Message Title Thai Pham commented on JENKINS-34780 Re: Files from the entry path are not copied to S3 bucket's root directory relatively Not quite correct. Source directory structure parent/a/c.txt parent/b/d.txt Matcher pattern parent/** Content of the bucket - pre-0.10.1 a/c.txt b/d.txt Content of the bucket - 0.10.1 parent/a/c.txt parent/b/d.txt 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
[JIRA] [git-parameter-plugin] (JENKINS-34425) Git parameter plugin skips one build number while populating tags
Title: Message Title Shao HK commented on JENKINS-34425 Re: Git parameter plugin skips one build number while populating tags Hi, Can u add some function that display the git logs detail info in the interface 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-parameter-plugin] (JENKINS-34425) Git parameter plugin skips one build number while populating tags
Title: Message Title Shao HK updated an issue Jenkins / JENKINS-34425 Git parameter plugin skips one build number while populating tags Change By: Shao HK 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] [buildresult-trigger-plugin] (JENKINS-13793) Build isn't triggered after reboot
Title: Message Title Mengesteab Ghebreyesus commented on JENKINS-13793 Re: Build isn't triggered after reboot The issue is in progress for a very long time. Will it at all be resolved. For us it is not minor issue. Thank you. 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] [violations-plugin] (JENKINS-34205) Add support for workflow/pipeline to the violations plugin
Title: Message Title Per Östman updated an issue Jenkins / JENKINS-34205 Add support for workflow/pipeline to the violations plugin Change By: Per Östman Labels: workflow 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] [violations-plugin] (JENKINS-34205) Add support for workflow/pipeline to the violations plugin
Title: Message Title Per Östman commented on JENKINS-34205 Re: Add support for workflow/pipeline to the violations plugin Second this - please add 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] [s3-plugin] (JENKINS-34780) Files from the entry path are not copied to S3 bucket's root directory relatively
Title: Message Title Alexander A commented on JENKINS-34780 Re: Files from the entry path are not copied to S3 bucket's root directory relatively Now I see, thanks for clarification. I will fix it in next release. 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] [_unsorted] (JENKINS-34969) "Waiting for next available executor on master" though many executors on the master is idle
Title: Message Title Satheesh Rajendran created an issue Jenkins / JENKINS-34969 "Waiting for next available executor on master" though many executors on the master is idle Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2016/May/20 8:30 AM Environment: Fedora 23 ppc64le 4.2.3-300.fc23.ppc64le Jenkins 2.0 Priority: Blocker Reporter: Satheesh Rajendran Though many executors are available, the jobs are getting queued waiting for executor on master collapse Build Queue (11) Project1 Project2 Project4 Project3 Project5 Project6 ... Build Executor Status master 1 Idle 2 Idle 3 Idle 4 Idle 5 Idle 6 Idle 7 Idle 8 Idle 9 Idle 10 Idle 11 Idle 12 Idle 13 Idle 14 Idle 15 Idle
[JIRA] [groovy-plugin] (JENKINS-34970) Display advanced details in job config for a groovy script if data is in there by default
Title: Message Title Axel Heider created an issue Jenkins / JENKINS-34970 Display advanced details in job config for a groovy script if data is in there by default Issue Type: Improvement Assignee: vjuranek Components: groovy-plugin Created: 2016/May/20 8:34 AM Environment: Groovy Plugin V1.24 Priority: Major Reporter: Axel Heider Display advanced details in the job config for a groovy script if data is in there. Currently this is not displayed by default, which is a bit inconvenient. We have certain config parameters there and these are easily forgotten if they are not visible. Another solution could be making "Variable bindings" not an advanced parameters if the option "Groovy script file" is selected. This is the way to pass parameters to the script.
[JIRA] [groovy-plugin] (JENKINS-31920) System groovy, Variables Binding & Classpath properties don't evaluate jenkions variables
Title: Message Title
Axel Heider commented on JENKINS-31920
Re: System groovy, Variables Binding & Classpath properties don't evaluate jenkions variables
If a build runs, the current dir is always the workspace. Why do you use the $WORKSPACE variable then instead of just a relative path that is passed to build.project.getWorkspace().child("myFile.txt") in you script?
Not sure about the classpath, maybe you really need $WORKSPACE there to reference things from our workspace. Then this feature would make sense here
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] [groovy-plugin] (JENKINS-31920) System groovy, Variables Binding & Classpath properties don't evaluate jenkions variables
Title: Message Title
Axel Heider edited a comment on JENKINS-31920
Re: System groovy, Variables Binding & Classpath properties don't evaluate jenkions variables
If a build runs, the current dir is always the workspace. Why do you use the {{$WORKSPACE}} variable then instead of just a relative path that is passed to {{build.project.getWorkspace().child("myFile.txt")}} in you your script?Not sure about the classpath, maybe you really need {{$WORKSPACE}} there to reference things from our workspace. Then this feature would make sense here
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] [patch-parameter-plugin] (JENKINS-28984) "patch.diff" is a bad name as env variable due to the dot
Title: Message Title Axel Heider commented on JENKINS-28984 Re: "patch.diff" is a bad name as env variable due to the dot work-around in a shell script is using: printenv patch.diff. That should solve the practical problem. But the name patch.diff is still not the best choice. I understand that is cannot be dropped for compatibility reasons, but another env var name like "patch_file" could be introduced in addition. 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] [conditional-buildstep-plugin] (JENKINS-34971) Conditional build step plugin does not mark build a s unstable
Title: Message Title Roman Wieczorek created an issue Jenkins / JENKINS-34971 Conditional build step plugin does not mark build a s unstable Issue Type: Bug Assignee: Dominik Bartholdi Attachments: screen.jpg Components: conditional-buildstep-plugin Created: 2016/May/20 8:49 AM Environment: Windows Jenkins ver. 1.651.2 conditional-buildstep 1.3.3 Priority: Minor Reporter: Roman Wieczorek "Conditional build step-single" shows nice field: "On evaluation failure" with options "Fail the build" or mark build as unstable. Unfortunatly this is not working. Example 1 Run? = Never On evaluation failure = "Mark the build unstable" Builder = "Execute windows batch command" Command = "echo run builder" It should mark all builds as unstable and not run the builder. It does not run builder but does not mark build as unstable. Example 2 - more reliable Run? = Execute Windows batch Command Command = which notinpath On evaluation failure =
[JIRA] [conditional-buildstep-plugin] (JENKINS-34971) Conditional build step plugin does not mark build a s unstable
Title: Message Title Roman Wieczorek commented on JENKINS-34971 Re: Conditional build step plugin does not mark build a s unstable Seem that analysis was wrong, or maybe documentation should be changed somehow? 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] [gradle-jpi-plugin] (JENKINS-34945) Build fails for jenkinsCore >= 2.0
Title: Message Title Daniel Spilker started work on JENKINS-34945 Change By: Daniel Spilker 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] [gradle-jpi-plugin] (JENKINS-34945) Build fails for jenkinsCore >= 2.0
Title: Message Title Daniel Spilker commented on JENKINS-34945 Re: Build fails for jenkinsCore >= 2.0 Ah, sorry, my fault. See https://github.com/jenkinsci/gradle-jpi-plugin/pull/79 Fredrik Bruzelius can you test the 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] [core] (JENKINS-34751) StackOverflowError in Groovy scripts
Title: Message Title Daniel Spilker assigned an issue to Daniel Spilker Jenkins / JENKINS-34751 StackOverflowError in Groovy scripts Change By: Daniel Spilker Assignee: vjuranek Daniel Spilker 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] [p4-plugin] (JENKINS-34972) P4 plugin poll request cannot be done
Title: Message Title Daniel Ordowski created an issue Jenkins / JENKINS-34972 P4 plugin poll request cannot be done Issue Type: Bug Assignee: Unassigned Attachments: jenkins.log Components: p4-plugin Created: 2016/May/20 8:59 AM Environment: Jenkins version is ver. 1.609.1, P4 plugin: 1.39, Linux Ubuntu: 14.04.03 LTS 64 bit, web browser: Google Chrome: 50.0.2661.94 m, Orcale JRE: 1.8.0_51 Labels: scm plugin Priority: Minor Reporter: Daniel Ordowski Hello all. I have found an issue in the p4-plugin. When I set "Pin build at Perforce Label" in (job's configuration), for example as PLABEL, and I create PLABEL variable as a String parameter, then I cannot do poll request because the variable
[JIRA] [junit-plugin] (JENKINS-34879) TestSuite fails for AssumptionViolatedException
Title: Message Title Martin Wegner closed an issue as Not A Defect https://github.com/eXparity/hamcrest-date/issues/18 Jenkins / JENKINS-34879 TestSuite fails for AssumptionViolatedException Change By: Martin Wegner Status: Open Closed 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] [junit-plugin] (JENKINS-34879) TestSuite fails for AssumptionViolatedException
Title: Message Title Martin Wegner commented on JENKINS-34879 Re: TestSuite fails for AssumptionViolatedException OK it was not a Jenkins bug: https://github.com/eXparity/hamcrest-date/issues/18 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-34973) Workflow scripts not permitted to use apache http client get method
Title: Message Title
Tobias Larscheid updated an issue
Jenkins / JENKINS-34973
Workflow scripts not permitted to use apache http client get method
Change By:
Tobias Larscheid
When using {{new GetMethod(url)}}from{{import org.apache.commons.httpclient.HttpClient }} {{ import org.apache.commons.httpclient.methods.GetMethod}}directly in a Workflow script pasted into the UI, everything works as expected.When the script is loaded with the file loader plugin during the Workflow script, the following error occurs:{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new org.apache.commons.httpclient.methods.GetMethod java.lang.String}}No pending script approval is generated.
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-34973) Workflow scripts not permitted to use apache http client get method
Title: Message Title
Tobias Larscheid created an issue
Jenkins / JENKINS-34973
Workflow scripts not permitted to use apache http client get method
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/May/20 9:02 AM
Environment:
Jenkins 2.3 from Docker Hub, Pipeline Plugin 2.0
Priority:
Critical
Reporter:
Tobias Larscheid
When using
new GetMethod(url)
from
{{import org.apache.commons.httpclient.HttpClient import org.apache.commons.httpclient.methods.GetMethod}}
directly in a Workflow script pasted into the UI, everything works as expected.
When the script is loaded with the file loader plugin during the Workflow script, the following error occurs:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new org.apache.commons.httpclient.methods.GetMethod java.lang.String
No pending script approval is generated.
[JIRA] [core] (JENKINS-34244) After selecting an item type, it is not obvious that the user needs to click the 'OK' button to advance to the next page
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-34244 Re: After selecting an item type, it is not obvious that the user needs to click the 'OK' button to advance to the next page The PR associated to this issue is pending to be merged by a Jenkins core committer. 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] [conditional-buildstep-plugin] (JENKINS-34971) Conditional build step plugin does not mark build a s unstable
Title: Message Title Roman Wieczorek edited a comment on JENKINS-34971 Re: Conditional build step plugin does not mark build a s unstable Seem that analysis was wrong, or maybe I think documentation should be changed somehow is missleading. What does mean that evaluation failures ? Does not it return a bolean value allways? 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] [groovy-plugin] (JENKINS-34974) Pass shell object to groovy script
Title: Message Title Axel Heider created an issue Jenkins / JENKINS-34974 Pass shell object to groovy script Issue Type: Improvement Assignee: vjuranek Components: groovy-plugin Created: 2016/May/20 9:09 AM Priority: Trivial Reporter: Axel Heider Pass the current "shell" object in the binding to the grovvy script. That would simplify loading and running other groovy scripts from the workspace. Currently I'm using static loadScriptFromWorkspace(build, fileName, loader=null) def scriptFile = build.project.getWorkspace().child(fileName) def cl = loader ?: Jenkins.getInstance().getPluginManager().uberClassLoader def groovyShell = new GroovyShell(cl) return groovyShell.parse(scriptFile.read().newReader()) } And this is invoked with loadScriptFromWorkspace(build, "foo.groovy", this.class.classLoader) With a "shell" object, I can skip the classloader part. static loadScriptFromWorkspace(groovyShell, fileName) buil
[JIRA] [ssh-agent-plugin] (JENKINS-34930) ClassCastException when trying to start ssh-agent
Title: Message Title bart van Wissen commented on JENKINS-34930 Re: ClassCastException when trying to start ssh-agent I don't have that plugin, but I did a find plugins -name bcprov -print and discovered that there are two other plugins which come with bouncycastle: plugins/ec2/WEB-INF/lib/bcprov-jdk15-140.jar plugins/ssh-agent/WEB-INF/lib/bcprov-jdk15on-1.47.jar plugins/vagrant/WEB-INF/classes/vendor/gems/jruby/1.8/gems/bouncy-castle-java-1.5.0146.1/lib/bcprov-jdk15-146.jar I cannot disable the ec2 plugin though, because it manages our slaves. 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] [delivery-pipeline-plugin] (JENKINS-34041) Improve Delivery Pipeline plugin stylesheets
Title: Message Title Tommy Tynjä commented on JENKINS-34041 Re: Improve Delivery Pipeline plugin stylesheets Support for themes implemented and merged to master. Also bundled alternative "contrast" theme alongside the default theme. Feature will be part of next release. 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] [delivery-pipeline-plugin] (JENKINS-34041) Improve Delivery Pipeline plugin stylesheets
Title: Message Title Tommy Tynjä resolved as Fixed Jenkins / JENKINS-34041 Improve Delivery Pipeline plugin stylesheets Change By: Tommy Tynjä 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] [all-changes-plugin] (JENKINS-34975) Unable to restart jenkins
Title: Message Title Balakumaran R created an issue Jenkins / JENKINS-34975 Unable to restart jenkins Issue Type: Bug Assignee: wolfs Attachments: Error.txt Components: all-changes-plugin Created: 2016/May/20 9:14 AM Priority: Critical Reporter: Balakumaran R Hi , we are not able to restart jenkins , can you please help us with it. The exceptions are attached in the file. Add Comment
[JIRA] [p4-plugin] (JENKINS-29979) Workflow plugin unable to save perforce paramters
Title: Message Title Paul Allen commented on JENKINS-29979 Re: Workflow plugin unable to save perforce paramters Thank you Kyle for offering to help; there is a fair amount of development work to do, so it will be a few weeks before I have a SNAPSHOT release for you to test. I will let you know as soon as the dev work is done. 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] [deployment-notification-plugin] (JENKINS-34976) Deployment trigger does not seem to work
Title: Message Title Marcin Pikulski created an issue Jenkins / JENKINS-34976 Deployment trigger does not seem to work Issue Type: Bug Assignee: Félix Belzunce Arcos Components: deployment-notification-plugin Created: 2016/May/20 9:23 AM Environment: Jenkins 2.5 deployment-notification-plugin 1.4 puppet-plugin 1.1 Priority: Major Reporter: Marcin Pikulski I created two jobs: one that builds atrifact, second one that has deployment notification trigger setup to watch for artifacts from first job. I also defined promotion criteria in first job - to promote when deployed. What happens: promotion criteria is executed when deployed (via puppet) second job never gets executed - trigger did not schedule a build. All fingerprints are recorded, promotion displays a deployment What should happen:
[JIRA] [_unsorted] (JENKINS-34977) Unable to launch jenkins - HTTP response code: 503
Title: Message Title bharath g created an issue Jenkins / JENKINS-34977 Unable to launch jenkins - HTTP response code: 503 Issue Type: New Feature Assignee: bharath g Components: _unsorted Created: 2016/May/20 9:38 AM Environment: version - 1.486, UNIX, Java JDK 1.6 Labels: jenkins exception Priority: Critical Reporter: bharath g Hi, When I try to execute jenkins restart, by using below command java -jar /usr/local/apache-tomcat-7.0.23/webapps/jenkins/WEB-INF/jenkins-cli.jar -s http://fiespx0311.adinfra.net:9090/jenkins/ restart I get the below error: Exception in thread "main" java.io.IOException: Server returned HTTP response code: 503 for URL: http://fiespx0311.adinfra.net:9090/jenkins/cli at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1459) at hudson.cli.FullDuplexHttpStream.(FullDuplexHttpStream.java:77) at hudson.cli.CLI.connectViaHttp(CLI.java:156) at hudson.cli.CLI.(CLI.java:140) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:68) at hudson.cli.CLI
[JIRA] [workflow-plugin] (JENKINS-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Alexander Kanevskiy commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables bump. without being able to use variables in pipeline from scm is practically making pipeline type of job useless, as can't be integrated e.g. with Github pull requests processing. 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] [_unsorted] (JENKINS-34977) Unable to launch jenkins - HTTP response code: 503
Title: Message Title bharath g updated an issue Jenkins / JENKINS-34977 Unable to launch jenkins - HTTP response code: 503 Change By: bharath g Issue Type: New Feature Bug 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] [ssh-agent-plugin] (JENKINS-34930) ClassCastException when trying to start ssh-agent
Title: Message Title bart van Wissen commented on JENKINS-34930 Re: ClassCastException when trying to start ssh-agent Removing the vagrant subdirectory seems to have done the trick. 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] [workflow-plugin] (JENKINS-34645) for in loop over result of String.split() gives NotSerializableException
Title: Message Title Csongor Somogyi reopened an issue I just checked it's still occurring with the latest patches installed. $ for p in $(find . -type d -maxdepth 1 | sed 's/\.\///' | sort); do echo $p; grep Plugin-Version $p/META-INF/MANIFEST.MF; done find: warning: you have specified the -maxdepth option after a non-option argument -type, but options are not positional (-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other arguments. . grep: ./META-INF/MANIFEST.MF: No such file or directory ace-editor Plugin-Version: 1.1 ant Plugin-Version: 1.3 antisamy-markup-formatter Plugin-Version: 1.3 branch-api Plugin-Version: 1.8 build-name-setter Plugin-Version: 1.6.5 build-pipeline-plugin Plugin-Version: 1.5.2 build-timeout Plugin-Version: 1.16 build-timestamp Plugin-Version: 1.0.1 build-with-parameters Plugin-Version: 1.3 cloudbees-folder Plugin-Version: 5.10 copyartifact Plugin-Version: 1.38 credentials Plugin-Version: 1.28 credentials-binding Plugin-Version: 1.7 dashboard-view Plugin-Version: 2.9.7 durable-task Plugin-Version: 1.9 dynamicparameter Plugin-Version: 0.2.0 email-ext Plugin-Version: 2.42 extended-choice-parameter Plugin-Version: 0.72 extensible-choice-parameter Plugin-Version: 1.3.2 external-monitor-job Plugin-Version: 1.4 git Plugin-Version: 2.4.4 git-client Plugin-Version: 1.19.6 git-server Plugin-Version: 1.6 handlebars Plugin-Version: 1.1.1 hidden-parameter Plugin-Version: 0.0.4 icon-shim Plugin-Version: 2.0.3 javadoc Plugin-Version: 1.3 jquery Plugin-Version: 1.11.2-0 jquery-detached Plugin-Version: 1.2.1 junit Plugin-Version: 1.13 ldap Plugin-Version: 1.12 mailer Plugin-Version: 1.17 mapdb-api Plugin-Version: 1.0.6.0 matrix-auth Plugin-Version: 1.3.2 matrix-project Plugin-Version: 1.6 maven-info Plugin-Version: 0.2.0 maven-plugin Plugin-Version: 2.12.1 momentjs Plugin-Version: 1.1.1 nexus-artifact-uploader Plugin-Version: 2.1.2 pam-auth Plugin-Version: 1.2 parameterized-trigger Plugin-Version: 2.30 pipeline-build-step Plugin-Version: 2.0 pipeline-input-step Plugin-Version: 2.0 pipeline-rest-api Plugin-Version: 1.4 pipeline-stage-step Plugin-Version: 2.1 pipeline-stage-view Plugin-Version: 1.4 plain-credentials Plugin-Version: 1.1 random-string-parameter Plugin-Version: 1.0 role-strategy Plugin-Version: 2.2.0 scm-api Plugin-Version: 1.2 scriptler Plugin-Version: 2.9 script-security Plugin-Version: 1.19 ssh Plugin-Version: 2.4 ssh-agent Plugin-Version: 1.10 ssh-credentials Plugin-Version: 1.12 ssh-slaves Plugin-Version: 1.11 structs Plugin-Version: 1.1 subversion Plugin-Version: 2.5.7 timestamper Plugin-Version: 1.8.2 token-macro Plugin-Version: 1.12.1 validating-string-parameter Plugin-Version: 2.3 windows-slaves Plugin-Version: 1.1 workflow-aggregator Plugin-Version: 2.1 workflow-api Plugin-Version: 2.0 workflow-basic-steps Plugin-Version: 2.0 workflow-cps Plugin-Version: 2.2 workflow-cps-global-lib Plugin-Version: 2.0 workflow-durable-task-step Plugin-Version: 2.0 workflow-job Plugin-Version: 2.1 workflow-multibranch Plugin-Version: 2.3 workflow-scm-step Plugin-Version: 2.0 workflow-step-api Plugin-Version: 2.0 workflow-support Plugin-Version: 2.0 ws-cleanup Plugin-Version: 0.29 Jenkins / JENKINS-34645 for in loop over result of String.split() gives NotSerializableException
[JIRA] [cvs-plugin] (JENKINS-33016) Jenkins doesn't detect CVS polling on Pipeline (Workflow) Job
Title: Message Title Michael Clarke commented on JENKINS-33016 Re: Jenkins doesn't detect CVS polling on Pipeline (Workflow) Job Sorry Jesse Glick, who is that comment aimed at? Is there an issue with the pull request, or are you implying that plugin maintainers should be checking the compatibility of their plugin with each Jenkins version? 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Edgars B. commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Stumbled upon this issue immediately after trying parallel builds. Been open for 5 years now, so I guess you can simply check for 'mspdbsrv.exe' and leave it alone? 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Edgars B. edited a comment on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Stumbled upon this issue immediately after trying parallel builds. Been open for 5 years now, so I guess you can simply check for 'mspdbsrv.exe' and leave it alone? Please free us of our pain. 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] [conditional-buildstep-plugin] (JENKINS-34971) Conditional build step plugin does not mark build a s unstable
Title: Message Title Roman Wieczorek commented on JENKINS-34971 Re: Conditional build step plugin does not mark build a s unstable Currently docs says: "If the evaluation of a run condition fails, should the build fail, be marked unstable, run the build step ... A run condition evaluation may fail to run cleanly - especially if it is dependent on expanding tokens provided by the Token Macro Plugin and the values are expected to be present or look like a certain type i.e. be a number." Maybe it could be: "Action to take when can not evaluate condition - this is not same as evaluating to false. Should the builder run? Build marked as failed or unstable? A run condition evaluation may fail to run cleanly - especially if it is dependent on expanding tokens provided by the Token Macro Plugin and the values are expected to be present or look like a certain type i.e. be a number." " 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-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title Alex Ng commented on JENKINS-23846 Re: Jenkins Maven support doesn't handle version ranges in parent definitions When will this problem being fixed? And any workaround? 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] [chroot-plugin] (JENKINS-34978) Please stop swallowing exceptions and debug output
Title: Message Title Jo Shields created an issue Jenkins / JENKINS-34978 Please stop swallowing exceptions and debug output Issue Type: Improvement Assignee: Unassigned Components: chroot-plugin Created: 2016/May/20 10:24 AM Priority: Minor Reporter: Jo Shields It can take a few tries to get the chroot plugin working properly, but when it fails, it is entirely opaque as to why. Nothing gets logged to the Jenkins log - exceptions aren't shown, STDERR from pbuilder isn't available, etc. It can make it super difficult to work out the cause of problems, especially when it happens in production but not the test environment your debugger is attached to. Add Comment
[JIRA] [port-allocator-plugin] (JENKINS-34979) Port allocation duplicate on "Concurrent builds"
Title: Message Title Rick Oosterholt created an issue Jenkins / JENKINS-34979 Port allocation duplicate on "Concurrent builds" Issue Type: Bug Assignee: Andres Rodriguez Components: port-allocator-plugin Created: 2016/May/20 10:27 AM Environment: Jenkins Version: 2.5 OS: Ubuntu Guess it is introduced in Jenkins 2.0? Was there a rewrite in how plugins are loaded when running concurrent? Its own classloader? Priority: Minor Reporter: Rick Oosterholt When configuring a "Pooled TCP port", the pool assignment is not unique when the build is performed concurrently (see "Execute concurrent builds if necessary"). Never had an issue before and problem seems to be introduced after we updated to Jenkins 2.0. Easy repro: create new job with "Pooled TCP port" and "Execute concurrent builds if necessary" options execute build multiple times see console output: same
[JIRA] [s3-plugin] (JENKINS-14470) S3 Plugin switches credential profiles
Title: Message Title SCM/JIRA link daemon commented on JENKINS-14470 Re: S3 Plugin switches credential profiles Code changed in jenkins User: Akbashev Alexander Path: src/main/java/hudson/plugins/s3/callable/S3Callable.java http://jenkins-ci.org/commit/s3-plugin/4bcdbf30074176a46758e0b14d2c9816769dbd02 Log: JENKINS-14470: S3 Plugin switches credential profiles (#88) JENKINS-14470: S3 Plugin switches credential profiles 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-34743) 2.2 Maven Installations - System Configuration Missing
Title: Message Title Fran Garcia commented on JENKINS-34743 Re: 2.2 Maven Installations - System Configuration Missing Can you explain how to do the workaround? I am also having this issue and copying the hudson.tasks.Maven.xml didn't make the trick. 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-34980) Add a description attribute for each step to be show in stage log overview
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-34980 Add a description attribute for each step to be show in stage log overview Issue Type: Improvement Assignee: Jesse Glick Attachments: 2016-05-19_12h01_20.png Components: workflow-plugin Created: 2016/May/20 10:37 AM Priority: Minor Reporter: Emilio Escobar A good improvement would be to add an (optional) description attribute to each step that is show in the stage logs overview (see attachment). Advantage: better overview and better relation between logs and script Add Comment
[JIRA] [core] (JENKINS-34952) Draw item categories
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-34952 Draw item categories Change By: Manuel Jesús Recena Soto Priority: Critical Major 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-34952) Draw item categories
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-34952 Draw item categories Change By: Manuel Jesús Recena Soto The current implementation of item categorization needs to be improved in order to draw the categories in the UI. Actually the items is being drawn in _flat mode_ (all item in a listing).The proposal here is:# Only draw a category if *2 or more* items are members of that category# Only draw the categories if there are *3 or more* categories that qualify to be drawnThis issues has been discussed with [~gusreiber] in a offline. 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] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title Oleg Nenashev commented on JENKINS-19445 Re: Jobs randomly stuck with "building remotely on slave-name" message Dorian Daumiller Jenkins 2 LTS - yes 1.651.3 - under review: https://github.com/jenkinsci/jenkins/pull/2357 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] [_unsorted] (JENKINS-34969) "Waiting for next available executor on master" though many executors on the master is idle
Title: Message Title Oleg Nenashev commented on JENKINS-34969 Re: "Waiting for next available executor on master" though many executors on the master is idle Please provide... Jenkins log (at least FINE level) List of installed plugins (with versions) Output of Jenkins Queue API with maximum depth. E.g. JENKINS_URL/jenkins/queue/api/json?pretty=true&depth=999 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] [publish-over-dropbox-plugin] (JENKINS-34937) Cannot create new credentials of type Dropbox
Title: Message Title Anatoliy D commented on JENKINS-34937 Re: Cannot create new credentials of type Dropbox hello, facing exactly the same issue. Ubuntu# java -version java version "1.8.0_72" Java(TM) SE Runtime Environment (build 1.8.0_72-b15) Java HotSpot(TM) 64-Bit Server VM (build 25.72-b15, mixed mode) 14.04.4 LTS I've tried to install it on jeknins latest 1.6.x version, got this problem first, then tried to disable firewall, then upgraded to 2.5 - no luck, then upgraded all plugins - no luck, added -Djava.net.preferIPv4Stack=true, disabled IPv6 completely, removed all ipv6 entries from /etc/hosts, tried to access Jenkins via Nginx reverse-proxy and directly - no luck. Restarted jenkins after each step, exception message did not change. I'm not sure it it's a bug or my server misconfiguration. Any idea what else I can check ? Would be great to know what address:port it tries to connect when throwing this exception: Caused by: java.lang.IllegalArgumentException: org.jenkinsci.plugins.publishoverdropbox.domain.model.RestException: Failed to open connection to server at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:540) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:777) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:674) ... 76 more Caused by: org.jenkinsci.plugins.publishoverdropbox.domain.model.RestException: Failed to open connection to server at org.jenkinsci.plugins.publishoverdropbox.domain.JsonObjectRequest.execute(JsonObjectRequest.java:114) at org.jenkinsci.plugins.publishoverdropbox.domain.Dropbox.readAccessTokenFromWeb(Dropbox.java:296) at org.jenkinsci.plugins.publishoverdropbox.domain.Dropbox.convertAuthorizationToAccessCode(Dropbox.java:269) at org.jenkinsci.plugins.publishoverdropbox.impl.DropboxTokenImpl.(DropboxTokenImpl.java:49) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:525) ... 79 more Caused by: org.jenkinsci.plugins.publishoverdropbox.domain.model.RestException: HTTP 400 error Bad Request : code doesn't exist or has expired at org.jenkinsci.plugins.publishoverdropbox.domain.JsonObjectRequest.execute(JsonObjectRequest.java:109) ... 87 more Add Comment
[JIRA] [workflow-plugin] (JENKINS-33020) Unable to Trigger builds remotely (e.g., from scripts)
Title: Message Title Patrick Reinhart commented on JENKINS-33020 Re: Unable to Trigger builds remotely (e.g., from scripts) I just tried to do the same thing on Jenkins 2.5 but there the remote trigger option is gone... Use the LTS Jenkins Version with the actual Pipeline plugins and create a new Pipeline item using the "Pipeline script from SCM" definition with the URL https://github.com/reinhapa/junit-compat.git Set the "Trigger builds remotely (e.g., from scripts)" option under Build Triggers After saving and re-open the build trigger setting for remote triggering is no longer active. Used Versions: Jenkins 1.642.2 Pipeline-Multibranch: 1.13 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] [valgrind-plugin] (JENKINS-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Mika Karjalainen created an issue Jenkins / JENKINS-34981 Make valgrind-plugin compatible with pipeline Issue Type: Improvement Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 2016/May/20 11:44 AM Priority: Major Reporter: Mika Karjalainen Valgrind result publishing should be possible also from pipeline scripts. To support this the plugin would need to be refactored according to pipeline development instructions: https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md Add Comment
[JIRA] [text-finder-plugin] (JENKINS-34983) Make text finder plugin compatible with pipeline
Title: Message Title Mika Karjalainen created an issue Jenkins / JENKINS-34983 Make text finder plugin compatible with pipeline Issue Type: Improvement Assignee: drlewis Components: text-finder-plugin Created: 2016/May/20 12:03 PM Priority: Major Reporter: Mika Karjalainen Running text finder build step should be possible also from pipeline scripts. To support this the plugin would need to be refactored according to pipeline development instructions: https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md Add Comment
[JIRA] [promoted-builds-plugin] (JENKINS-34982) Add configure block in DSL for promotions
Title: Message Title Marcin Pikulski created an issue Jenkins / JENKINS-34982 Add configure block in DSL for promotions Issue Type: New Feature Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/May/20 12:03 PM Priority: Minor Reporter: Marcin Pikulski Currently Job DSL plugin supports promoted builds plugin by extension point (see JENKINS-29776 , JENKINS-21750 ). Unfortunately there is no support for deployment notification plugin and there is no configure block available for promotion conditions so it is impossible to add that criteria. Adding a configure block would allow any condition to be added when necessary. Add Comment
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Steve Brain edited a comment on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Hi,I noticed that if the .gimodules submodule name is not the same as the path spec the submodule update fails by trying to use the name.submodule defined like this fails [submodule "rpm"] path = linux/rpm url = ../rpm.git with error > git config --get submodule.rpm.url # timeout=60 > git submodule update --init --recursive rpm # timeout=100FATAL: Command "git submodule update --init --recursive rpm" returned status code 1:stdout: stderr: error: pathspec 'rpm' did not match any file(s) known to git.Did you forget to 'git add'?the workaround is to name the submodule the same as the path [submodule "linux/rpm"] path = linux/rpm url = ../rpm.git using git 2.5.0-beta5git-client 1.20.0-beta3 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-33020) Unable to Trigger builds remotely (e.g., from scripts)
Title: Message Title
Patrick Reinhart edited a comment on JENKINS-33020
Re: Unable to Trigger builds remotely (e.g., from scripts)
I just tried to do the same thing on Jenkins 2.5 but there the remote trigger option is gone...Use the LTS Jenkins Version with the actual Pipeline plugins and create a new {{ Pipeline -Multibranch}} item using the {{ " Pipeline script from SCM " }} definition with the URL [https://github.com/reinhapa/junit-compat.git]Set the {{ " Trigger builds remotely (e.g., from scripts) " }} option under *Build Triggers*After saving and re-open the build trigger setting for remote triggering is no longer active.+Used Versions:+Jenkins 1.642.2Pipeline-Multibranch: 1.13
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] [lockable-resources-plugin] (JENKINS-34892) lock step in Pipeline should allow creation of implicit locks
Title: Message Title Nigel Harniman commented on JENKINS-34892 Re: lock step in Pipeline should allow creation of implicit locks Should this say: that prevents other builds of this job from entering 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] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name
Title: Message Title Piotr Musiał commented on JENKINS-34512 Re: error in build-name-setter plugin - Set build name Do you know when it could be solved ? 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-34984) Cannot save jenkins configuration
Title: Message Title Axay Deole created an issue Jenkins / JENKINS-34984 Cannot save jenkins configuration Issue Type: Bug Assignee: Unassigned Attachments: Jenkins err.png Components: core Created: 2016/May/20 12:38 PM Environment: In-house Priority: Blocker Reporter: Axay Deole I have recently upgraded jenkins on latest version & I'm trying to make changes in the configuration through Manage jenkins > Configure > but it is not getting saved & throwing following message - A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.
[JIRA] [build-name-setter-plugin] (JENKINS-34512) error in build-name-setter plugin - Set build name
Title: Message Title Lev Mishin commented on JENKINS-34512 Re: error in build-name-setter plugin - Set build name Unfortunately no, I just don't have time I hope that I will back to it in June 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] [other] (JENKINS-34984) Cannot save jenkins configuration
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-34984 Cannot save jenkins configuration Clearly a bug in Jira test result reporter plugin, unfortunately there's no issue tracker component for it. Change By: Daniel Beck Component/s: other 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] [lockable-resources-plugin] (JENKINS-34853) plugin inpact by SECURITY-170
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-34853 plugin inpact by SECURITY-170 Change By: Antonio Muñiz Assignee: Antonio Muñiz 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] [lockable-resources-plugin] (JENKINS-34853) plugin inpact by SECURITY-170
Title: Message Title Antonio Muñiz started work on JENKINS-34853 Change By: Antonio Muñiz 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] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Julien Faixo commented on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Same issue here. OS: Windows Server 2012 R2 Jenkins: 2.5, all plugins up to date (20/05/2016) Unable to run any bat command (the first one hangs and never returns). Same workarounds as said : in order to stop the task : click on the red cross on the build in order to send a killing signal, then go to the console output and click the "Terminate" link in order to be able to build something : stick with the Freestyle projects for now It makes Pipeline unusable on Windows. 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] [swarm-plugin] (JENKINS-26620) SWARM - swarm client should read password from file
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-26620 SWARM - swarm client should read password from file Change By: Peter Jönsson Status: Open Closed 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] [swarm-plugin] (JENKINS-28917) Swarm CLI with latest Jenkins Slave Jar
Title: Message Title Peter Jönsson resolved as Fixed Jenkins / JENKINS-28917 Swarm CLI with latest Jenkins Slave Jar Change By: Peter Jönsson 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] [swarm-plugin] (JENKINS-25064) Swarm toollocations don't work for all tools
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-25064 Swarm toollocations don't work for all tools Change By: Peter Jönsson Status: Resolved Closed Assignee: Kohsuke Kawaguchi Peter Jönsson 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] [swarm-plugin] (JENKINS-34718) Get a new release of swarm client plugin
Title: Message Title Peter Jönsson commented on JENKINS-34718 Re: Get a new release of swarm client plugin Samuel Beaulieu Sorry for the delay, I performed a new release today. 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] [swarm-plugin] (JENKINS-34718) Get a new release of swarm client plugin
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-34718 Get a new release of swarm client plugin Change By: Peter Jönsson Status: Open Closed 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] [docker-workflow-plugin] (JENKINS-34503) Add username/password support for docker registry
Title: Message Title
Gijs Kunze commented on JENKINS-34503
Re: Add username/password support for docker registry
AWS has it's own authentication system. To more completely describe the situation:
We have a small master (no executors) and by default, no slaves. Slaves are automatically provisioned using the Amazon EC2 plugin. The slaves have an IAM Instance Role which give the instance (virtual machine) permission to execute certain actions, in this case, it's allowed to use the registry. AWS API SDKs and the CLI (which is installed on our slaves) can then infer the credentials they need to call Amazon APIs (credentials are a key and a secret key and the system uses a complex-ish HTTP request signing algorithm). To log in to a registry, normally, you use one of these API calls to request temporary credentials with which you can log in to the registry.
Currently, what I do in my workflow script is manually log in with a shell command:
def dockerLogin() {
sh "aws --region=eu-west-1 ecr get-login > DOCKER_LOGIN"
sh readFile("DOCKER_LOGIN")
}
The aws ecr get-login command returns a shell command which you can execute to log in to docker (It returns something like docker login -u AWS -p very-long-password-here -e none https://registry-endpoint-here).
get-login is a convenience function which outputs a shell command to execute, but there is another command get-credentials which outputs a JSON object containing the username, password and endpoint (the endpoint doesn't change). A longer version where we have the proper credentials could look something like this:
def dockerLogin() {
sh "aws --region=eu-west-1 ecr get-authorization-token > DOCKER_LOGIN"
def text = readFile("DOCKER_LOGIN")
def json = new JsonSlurper().parseText(text)
def authorizationData = json['authorizationData'][0]
def String token = authorizationData['authorizationToken']
def endpoint = authorizationData['proxyEndpoint']
def auth = new String(token.decodeBase64()).split(":", 2)
sh "/usr/bin/docker login -u ${auth[0]} -p ${auth[1]} -e none ${endpoint}"
}
Honestly, this workaround seems to work fine and for us at least there is no huge need for a "proper" way of logging in but in the back of my mind, I feel this could be done nicer.
Add Comment
[JIRA] [slave-status-plugin] (JENKINS-18785) SWARM Plugin > Slave connection reset issue
Title: Message Title Peter Jönsson closed an issue as Not A Defect Jenkins / JENKINS-18785 SWARM Plugin > Slave connection reset issue Change By: Peter Jönsson Status: Open Closed 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] [swarm-plugin] (JENKINS-21455) commons codec error
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-21455 commons codec error Change By: Peter Jönsson Status: Open Closed 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] [swarm-plugin] (JENKINS-32923) Jenkins remoting goesn't honour -noreconnect option
Title: Message Title Peter Jönsson commented on JENKINS-32923 Re: Jenkins remoting goesn't honour -noreconnect option Pull requests are always welcome Christopher Batey 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] [swarm-plugin] (JENKINS-28148) Fail to create a swarm when using a toolLocations with whitespaces.
Title: Message Title Peter Jönsson resolved as Fixed Jenkins / JENKINS-28148 Fail to create a swarm when using a toolLocations with whitespaces. Change By: Peter Jönsson 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] [openstack-cloud-plugin] (JENKINS-34100) Launch of cloud slave fails with "No route to host"
Title: Message Title
Peter Hansen edited a comment on JENKINS-34100
Re: Launch of cloud slave fails with "No route to host"
I experience the same problem here. The logfile says: {{ [05/20/16 13:01:45] [SSH] Opening SSH connection to 192.168.1.36:22.No route to hostERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.ha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA=java.lang.IllegalStateException: Connection is not established! at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connection.java:1030) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:212) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:172) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1212) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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)[05/20/16 13:01:48] Launch failed - cleaning up connection[05/20/16 13:01:48] [SSH] Connection closed. }} When manually launching the agent using the Jenkins UI after some minutes the problem does not occur. Is there any workaround? How to automatically reschedule the start of the agent?
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 ht
[JIRA] [openstack-cloud-plugin] (JENKINS-34100) Launch of cloud slave fails with "No route to host"
Title: Message Title
Peter Hansen commented on JENKINS-34100
Re: Launch of cloud slave fails with "No route to host"
I experience the same problem here. The logfile says: {{[05/20/16 13:01:45] [SSH] Opening SSH connection to 192.168.1.36:22. No route to host ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. ha:WB+LCP9b85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA=java.lang.IllegalStateException: Connection is not established! at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connection.java:1030) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:212) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:172) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1212) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) [05/20/16 13:01:48] Launch failed - cleaning up connection [05/20/16 13:01:48] [SSH] Connection closed.}}
When manually launching the agent using the Jenkins UI after some minutes the problem does not occur.
Is there any workaround? How to automatically reschedule the start of the agent?
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
[JIRA] [swarm-plugin] (JENKINS-28917) Swarm CLI with latest Jenkins Slave Jar
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-28917 Swarm CLI with latest Jenkins Slave Jar Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-26558) createSlave Node name collision avoidance creates dead nodes
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-26558 createSlave Node name collision avoidance creates dead nodes Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-29232) Swarm client fails to close sockets during master discovery
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-29232 Swarm client fails to close sockets during master discovery Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-31918) Workflow Parallel task causing serialization error with Swarm Node
Title: Message Title Peter Jönsson closed an issue as Won't Fix Jenkins / JENKINS-31918 Workflow Parallel task causing serialization error with Swarm Node Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-10215) New swarm client release needed with latest slave.jar classes embedded
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-10215 New swarm client release needed with latest slave.jar classes embedded Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-34593) provide an option to delete existing slaves with the same name
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-34593 provide an option to delete existing slaves with the same name Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-24995) New Swarm Slave Wont Work
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-24995 New Swarm Slave Wont Work Change By: Peter Jönsson Status: Resolved Closed 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] [github-oauth-plugin] (JENKINS-17539) Swarm clients fail to connect if GitHub for authentication
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-17539 Swarm clients fail to connect if GitHub for authentication Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-25002) Using : as separator for tool location is not the best choice on Windows
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-25002 Using : as separator for tool location is not the best choice on Windows Change By: Peter Jönsson Status: Resolved Closed 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] [swarm-plugin] (JENKINS-28148) Fail to create a swarm when using a toolLocations with whitespaces.
Title: Message Title Peter Jönsson closed an issue as Fixed Jenkins / JENKINS-28148 Fail to create a swarm when using a toolLocations with whitespaces. Change By: Peter Jönsson Status: Resolved Closed 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-32509) javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.slaves.DumbSlave from
Title: Message Title Jason Azze commented on JENKINS-32509 Re: javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.slaves.DumbSlave from We discovered the cause of our inability to save slave configurations. It may provide a clue for s s. We had a job that would reboot slaves after long test runs. This job contained some groovy code that marked a slave offline or online and updated the offline reason. This script worked well with Jenkins 1.466.2, but for 1.642.3 the groovy code was updating the slave's configuration in memory and, presumably due to some changes in the schema between the old and new Jenkins versions, setting some value which prevented the serialization. We fixed our script to play nice with the API changes, and the problem is gone. The original reporter for this issue wasn't having the serialization problem. I notice that their stack trace contains "Failed to create a temporary file in /var/lib/jenkins/nodes/node007". That smells like a permissions 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-33663) Upgrade wizard step #1: recommended plugin installation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33663 Re: Upgrade wizard step #1: recommended plugin installation Code changed in jenkins User: Keith Zantow Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/jenkins/install/InstallState.java core/src/main/java/jenkins/install/InstallStateFilter.java core/src/main/java/jenkins/install/InstallUtil.java core/src/main/java/jenkins/install/SetupWizard.java core/src/main/java/jenkins/install/UpgradeWizard.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/resources/jenkins/install/SetupWizard/authenticate-security-token.jelly core/src/main/resources/jenkins/install/SetupWizard/client-scripts.jelly core/src/main/resources/jenkins/install/SetupWizard/footer.jelly core/src/main/resources/jenkins/install/SetupWizard/index.jelly core/src/main/resources/jenkins/install/SetupWizard/wizard-ui.jelly core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts.jelly core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts.properties core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts_fr.properties core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts_lt.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer.jelly core/src/main/resources/jenkins/install/UpgradeWizard/footer.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer_fr.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer_lt.properties core/src/main/resources/jenkins/install/pluginSetupWizard.properties core/src/main/resources/jenkins/model/Jenkins/login.jelly core/src/main/resources/jenkins/model/Jenkins/loginError.jelly core/src/main/resources/lib/layout/html.jelly test/src/test/java/jenkins/install/InstallUtilTest.java test/src/test/java/jenkins/install/SetupWizardTest.java test/src/test/java/jenkins/install/UpgradeWizardTest.java test/src/test/java/jenkins/util/SystemPropertiesTest.java war/gulpfile.js war/src/main/js/api/pluginManager.js war/src/main/js/pluginSetupWizardGui.js war/src/main/js/templates/pluginSelectList.hbs war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/js/templates/successPanel.hbs war/src/main/js/templates/upgradePanel.hbs war/src/main/js/templates/upgradeSkippedPanel.hbs war/src/main/js/templates/upgradeSuccessPanel.hbs war/src/main/js/upgradeWizard.js war/src/main/js/util/jenkins.js war/src/main/less/pluginSetupWizard.less war/src/main/webapp/WEB-INF/web.xml war/src/main/webapp/css/style.css war/src/test/js/pluginSetupWizard-spec.js http://jenkins-ci.org/commit/jenkins/20cb8fdde819ab6a00140f6c987bb9dddaff7483 Log: Merge pull request #2281 from kzantow/JENKINS-33663-upgrade-wizard JENKINS-33663 - Upgrade wizard Compare: https://github.com/jenkinsci/jenkins/compare/74d0412d74a6...20cb8fdde819 Add Comment
[JIRA] [core] (JENKINS-34676) Outdated version of js-modules causes loading issues on JS module conflicts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34676 Re: Outdated version of js-modules causes loading issues on JS module conflicts Code changed in jenkins User: kzantow Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/jenkins/install/InstallState.java core/src/main/java/jenkins/install/InstallStateFilter.java core/src/main/java/jenkins/install/InstallUtil.java core/src/main/java/jenkins/install/SetupWizard.java core/src/main/java/jenkins/install/UpgradeWizard.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/resources/jenkins/install/SetupWizard/authenticate-security-token.jelly core/src/main/resources/jenkins/install/SetupWizard/client-scripts.jelly core/src/main/resources/jenkins/install/SetupWizard/footer.jelly core/src/main/resources/jenkins/install/SetupWizard/index.jelly core/src/main/resources/jenkins/install/SetupWizard/wizard-ui.jelly core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts.jelly core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts.properties core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts_fr.properties core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts_lt.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer.jelly core/src/main/resources/jenkins/install/UpgradeWizard/footer.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer_fr.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer_lt.properties core/src/main/resources/jenkins/install/pluginSetupWizard.properties core/src/main/resources/jenkins/model/Jenkins/login.jelly core/src/main/resources/jenkins/model/Jenkins/loginError.jelly core/src/main/resources/lib/layout/html.jelly test/src/test/java/jenkins/install/InstallUtilTest.java test/src/test/java/jenkins/install/SetupWizardTest.java test/src/test/java/jenkins/install/UpgradeWizardTest.java test/src/test/java/jenkins/util/SystemPropertiesTest.java war/gulpfile.js war/src/main/js/api/pluginManager.js war/src/main/js/pluginSetupWizardGui.js war/src/main/js/templates/pluginSelectList.hbs war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/js/templates/successPanel.hbs war/src/main/js/templates/upgradePanel.hbs war/src/main/js/templates/upgradeSkippedPanel.hbs war/src/main/js/templates/upgradeSuccessPanel.hbs war/src/main/js/upgradeWizard.js war/src/main/js/util/jenkins.js war/src/main/less/pluginSetupWizard.less war/src/main/webapp/WEB-INF/web.xml war/src/main/webapp/css/style.css war/src/test/js/pluginSetupWizard-spec.js http://jenkins-ci.org/commit/jenkins/89a24abcb0eabc36c7281979d1620c92b6a128a9 Log: [FIX JENKINS-33663] - Upgrade wizard Add Upgrade Wizard Add 'replace' handlebars method in jenkins.js Fix state transitions to follow a single basic pattern Suggested plugins selected by default Add an install state for INITIAL_SECURITY_SETUP Removed duplicate setupWizard.js on page [FIX JENKINS-34676] Exclude plugins which are already installed when determining platform Change 'snooze' to not look like a 'close' button Make sure unlock screen doesn't show up after new install Add compatibility check when offering suggested plugins More appropriate handling of security token filter
[JIRA] [core] (JENKINS-33663) Upgrade wizard step #1: recommended plugin installation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33663 Re: Upgrade wizard step #1: recommended plugin installation Code changed in jenkins User: kzantow Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/jenkins/install/InstallState.java core/src/main/java/jenkins/install/InstallStateFilter.java core/src/main/java/jenkins/install/InstallUtil.java core/src/main/java/jenkins/install/SetupWizard.java core/src/main/java/jenkins/install/UpgradeWizard.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/resources/jenkins/install/SetupWizard/authenticate-security-token.jelly core/src/main/resources/jenkins/install/SetupWizard/client-scripts.jelly core/src/main/resources/jenkins/install/SetupWizard/footer.jelly core/src/main/resources/jenkins/install/SetupWizard/index.jelly core/src/main/resources/jenkins/install/SetupWizard/wizard-ui.jelly core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts.jelly core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts.properties core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts_fr.properties core/src/main/resources/jenkins/install/UpgradeWizard/client-scripts_lt.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer.jelly core/src/main/resources/jenkins/install/UpgradeWizard/footer.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer_fr.properties core/src/main/resources/jenkins/install/UpgradeWizard/footer_lt.properties core/src/main/resources/jenkins/install/pluginSetupWizard.properties core/src/main/resources/jenkins/model/Jenkins/login.jelly core/src/main/resources/jenkins/model/Jenkins/loginError.jelly core/src/main/resources/lib/layout/html.jelly test/src/test/java/jenkins/install/InstallUtilTest.java test/src/test/java/jenkins/install/SetupWizardTest.java test/src/test/java/jenkins/install/UpgradeWizardTest.java test/src/test/java/jenkins/util/SystemPropertiesTest.java war/gulpfile.js war/src/main/js/api/pluginManager.js war/src/main/js/pluginSetupWizardGui.js war/src/main/js/templates/pluginSelectList.hbs war/src/main/js/templates/pluginSelectionPanel.hbs war/src/main/js/templates/successPanel.hbs war/src/main/js/templates/upgradePanel.hbs war/src/main/js/templates/upgradeSkippedPanel.hbs war/src/main/js/templates/upgradeSuccessPanel.hbs war/src/main/js/upgradeWizard.js war/src/main/js/util/jenkins.js war/src/main/less/pluginSetupWizard.less war/src/main/webapp/WEB-INF/web.xml war/src/main/webapp/css/style.css war/src/test/js/pluginSetupWizard-spec.js http://jenkins-ci.org/commit/jenkins/89a24abcb0eabc36c7281979d1620c92b6a128a9 Log: [FIX JENKINS-33663] - Upgrade wizard Add Upgrade Wizard Add 'replace' handlebars method in jenkins.js Fix state transitions to follow a single basic pattern Suggested plugins selected by default Add an install state for INITIAL_SECURITY_SETUP Removed duplicate setupWizard.js on page [FIX JENKINS-34676] Exclude plugins which are already installed when determining platform Change 'snooze' to not look like a 'close' button Make sure unlock screen doesn't show up after new install Add compatibility check when offering suggested plugins More appropriate handling of security token filter
[JIRA] [core] (JENKINS-33663) Upgrade wizard step #1: recommended plugin installation
Title: Message Title Keith Zantow resolved as Fixed Jenkins / JENKINS-33663 Upgrade wizard step #1: recommended plugin installation Change By: Keith Zantow 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-34532) Change setup wizard 'Website' text label to icon
Title: Message Title Keith Zantow started work on JENKINS-34532 Change By: Keith Zantow 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.
