[JIRA] (JENKINS-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title Tomasz Wojtun commented on JENKINS-42005 Re: Cannot provision when there are instances created from snapshot (google-compute-engine) This is now fixed in jclouds source, so we need to wait until new release. If someone needs the fix sooner, you can build jclouds of 2.0.x branch, and then jclouds-plugin itself. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42005) Cannot provision when there are instances created from snapshot (google-compute-engine)
Title: Message Title Tomasz Wojtun edited a comment on JENKINS-42005 Re: Cannot provision when there are instances created from snapshot (google-compute-engine) This is now fixed in jclouds source, so we need to wait until new release. If someone needs the fix sooner, you can build jclouds of from 2.0.x branch, and then jclouds-plugin itself. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34433) pipeline lock does not retry
Title: Message Title Zsolt Illés commented on JENKINS-34433 Re: pipeline lock does not retry In my case this does not solve the manual resource unlocking problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39593) Performance slow in 1.5 release
Title: Message Title Bruno P. Kinoshita commented on JENKINS-39593 Re: Performance slow in 1.5 release Working on this issue for 1..5.4. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39593) Performance slow in 1.5 release
Title: Message Title
Bruno P. Kinoshita commented on JENKINS-39593
Re: Performance slow in 1.5 release
Creating 1000 projects:
import hudson.model.*
def N = 1000
def sourceProject = 'JENKINS-39593'
for(i in (1..N))
{
def newName = 'DUMMY-PROJECT-' + i
def source = Hudson.instance.getJob(sourceProject)
def job = Hudson.instance.copy(source, newName)
job.save()
println(" $sourceProject copied as $newName")
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42824) Super Slow "Build with Parameters" loading
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42824 Re: Super Slow "Build with Parameters" loading Hi Jurgens H! That sounds like a very interesting use case! Let me know if you ever write/blog about how you are using the plugin. Ioannis Moutsatsos and myself are always keen to learn how the users of the plug-in are using it. I'm working on JENKINS-39593, for performance issues. This issue could - very likely - be related to yours. I have created one sample job, and 1000 other unrelated jobs. So far I'm just printing the job output, looking at how many times the parameters are executed, before I start measuring load/execution time (which takes longer). Feel free to chime in there in case you have time to reproduce your case in a test bed server with a similar approach. It would be grand if you could get a generic job like yours, with similar number of parameters, then run that script in JENKINS-39593, and see if you are able to reproduce the issue. If so, I would be happy to repeat your steps in my development environment and profile / debug the issue. Ta Bruno Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39593) Performance slow in 1.5 release
Title: Message Title Bruno P. Kinoshita commented on JENKINS-39593 Re: Performance slow in 1.5 release lsb want I was not able to reproduce the behaviour you described. With or without promoted builds plugin (not the simple version), my script gets executed just once. My sample job now has active-choices-plugin + promoted-builds-plugin together. Going to the promotion status triggers once. Going to build with parameters too. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39593) Performance slow in 1.5 release
Title: Message Title Bruno P. Kinoshita commented on JENKINS-39593 Re: Performance slow in 1.5 release Created a logger (org.biouno, log level ALL), so far the output looks consistent, executing the parameter only. Now will add more parameters (reactive now, before was using a choice parameter) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39593) Performance slow in 1.5 release
Title: Message Title Piotr Tempes commented on JENKINS-39593 Re: Performance slow in 1.5 release I am not using promoted-builds-plugin. To reproduce lag on form loading the only thing you need to have is active choices parameter (let's say a single select combobox) and let's say 10 active choices reactive reference parameters (formatted html type) pointing to active choices parameter plugin. Then you should definitely notice a lag during form loading. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42022) Remove 'Unix machines' from description
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42022 Re: Remove 'Unix machines' from description Code changed in jenkins User: Evaristo Gutiérrez Path: pom.xml src/main/resources/index.jelly http://jenkins-ci.org/commit/ssh-slaves-plugin/a2038d0f78eaf6017c3f28f7ccd7c5b1f865353b Log: JENKINS-42022 Remove 'unix machines' from plugin's description. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42022) Remove 'Unix machines' from description
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42022 Re: Remove 'Unix machines' from description Code changed in jenkins User: Oliver Gondža Path: pom.xml src/main/resources/index.jelly http://jenkins-ci.org/commit/ssh-slaves-plugin/e91e0e2d60b8121ac07a40f723c499041da21e23 Log: Merge pull request #42 from varyvol/JENKINS-42022 JENKINS-42022 Remove 'unix machines' from plugin's description. Compare: https://github.com/jenkinsci/ssh-slaves-plugin/compare/e97b0abf3c59...e91e0e2d60b8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42022) Remove 'Unix machines' from description
Title: Message Title Evaristo Gutierrez updated JENKINS-42022 Jenkins / JENKINS-42022 Remove 'Unix machines' from description Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42830) No such property: ci for class: groovy.lang.Binding when updating Multibranch plugins
Title: Message Title
Jonas created an issue
Jenkins / JENKINS-42830
No such property: ci for class: groovy.lang.Binding when updating Multibranch plugins
Issue Type:
Bug
Assignee:
Stephen Connolly
Components:
branch-api-plugin, pipeline-multibranch-defaults-plugin
Created:
2017/Mar/16 9:17 AM
Environment:
Jenkins 2.49 Pipeline: Multibranch 2.0.8 Branch API Plugin 2.14
Priority:
Blocker
Reporter:
Jonas
After updating "Pipeline: Multibranch" (1.11.1 -> 2.0.8) and "Branch API Plugin" (2.9.2 -> 2.14), I get the following error: Seen 45 remote branches Obtained Jenkinsfile from 3d130723653bda531006ae85801a10eed5fc6249{color:#9a}[Pipeline] End of Pipeline{color}groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:1) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor313.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
[JIRA] (JENKINS-42830) No such property: ci for class: groovy.lang.Binding when updating Multibranch plugins
Title: Message Title
Jonas updated an issue
Jenkins / JENKINS-42830
No such property: ci for class: groovy.lang.Binding when updating Multibranch plugins
Change By:
Jonas
After updating "Pipeline: Multibranch" (1.11.1 -> 2.0.8) and "Branch API Plugin" (2.9.2 -> 2.14), I get the following error: {quote} Seen 45 remote branchesObtained Jenkinsfile from 3d130723653bda531006ae85801a10eed5fc6249\{color:#9a}[Pipeline] End of Pipeline\{color}groovy.lang.MissingPropertyException: No such property: ci for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor313.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:74) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.
[JIRA] (JENKINS-39593) Performance slow in 1.5 release
Title: Message Title
Bruno P. Kinoshita commented on JENKINS-39593
Re: Performance slow in 1.5 release
That's interesting. My normal param was called once, whereas my reactive param was called three times. Removing the promoted builds plugin, the behaviour persists. Code for PARAM001:
println("PARAM001")
return [0,1,2,3,4]
PARAM002:
println("PARAM002")
return ["A", PARAM001, "C", PARAM001 + "111"]
Output of going to :
PARAM001
PARAM002
PARAM002 fallback...
PARAM002
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubs
[JIRA] (JENKINS-42795) REGRESSION: Bitbucket scan organization folder fails
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-42795 REGRESSION: Bitbucket scan organization folder fails Change By: Stephen Connolly Assignee: Antonio Muñiz Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42795) REGRESSION: Bitbucket scan organization folder fails
Title: Message Title Stephen Connolly updated JENKINS-42795 Jenkins / JENKINS-42795 REGRESSION: Bitbucket scan organization folder fails Change By: Stephen Connolly Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42795) REGRESSION: Bitbucket scan organization folder fails
Title: Message Title Stephen Connolly started work on JENKINS-42795 Change By: Stephen Connolly Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37369 Re: Multibranch Pipeline: Last build information is not propagated to Jenkins View Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/695f4b651427dc683a6c08c96e8a750904c56d03 Log: JENKINS-37369 Use HttpResponses.redirectViaContextPath Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37369 Re: Multibranch Pipeline: Last build information is not propagated to Jenkins View Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/PseudoRun/sidepanel.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/8eac7c15023886a86ce839dfb809c37736fff674 Log: JENKINS-37369 Expose the last computation for computed folders Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37369 Re: Multibranch Pipeline: Last build information is not propagated to Jenkins View Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/PseudoRun.java src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/Messages.properties src/main/resources/com/cloudbees/hudson/plugins/folder/computed/PseudoRun/sidepanel.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/4dda5fcd52893c83dc9f6d0a4b4950f53d816fc9 Log: Merge pull request #87 from stephenc/jenkins-37369 JENKINS-37369 Expose the last computation for computed folders Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/9645813fbe71...4dda5fcd5289 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Nikolas Falco commented on JENKINS-42675 Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page You right, I was miss the "Global Tools Configuration page" part. It's a know limitation because I have not decide if and how handle NPM config file in global. Personally I think that typical use case of global installation is install package that 99% does not come from corporate registry like phantom, bower, grunt and so on. Instead if you use corporate registry to install global packages as proxy becuase internet than configure jenkins proxy (it is supported). As workaround exist we move priority to Normal Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-42675 Override default NodeJS registry when installing in global mode on Global Tools Configuration page Change By: Nikolas Falco Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Nikolas Falco edited a comment on JENKINS-42675 Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page You right, I was miss the "Global Tools Configuration page" part. It's a know limitation because I have not decide if and how handle NPM config file in global.Personally I think that typical use case of global installation is install package that 99% does not come from corporate registry like phantom, bower, grunt and so on.Instead if you use corporate registry to install global packages as proxy becuase internet than configure jenkins proxy (it is supported).As workaround exist we move priority to Normal Other workaound is an environment variable *npm_config_*registry as describe [here|https://docs.npmjs.com/misc/config] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Nikolas Falco edited a comment on JENKINS-42675 Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page You right, I was miss the "Global Tools Configuration page" part. It's a know limitation because I have not decide if and how handle NPM config file in global.Personally I think that typical use case of global installation is install package that 99% does not come from corporate registry like phantom, bower, grunt and so on.Instead if you use corporate registry to install global packages as proxy becuase internet than configure jenkins proxy (it is supported).As workaround exist we move priority to NormalOther workaound workaround is add an environment variable (at node level or as global) like *npm_config_*registry as describe [here|https://docs.npmjs.com/misc/config] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42680) Creating a Folder as a child of ComputedFolder causes Jenkins to hang
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-42680 Creating a Folder as a child of ComputedFolder causes Jenkins to hang Change By: Stephen Connolly Assignee: Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42680) Creating a Folder as a child of ComputedFolder causes Jenkins to hang
Title: Message Title Stephen Connolly started work on JENKINS-42680 Change By: Stephen Connolly Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42680) Creating a Folder as a child of ComputedFolder causes Jenkins to hang
Title: Message Title Stephen Connolly updated JENKINS-42680 Jenkins / JENKINS-42680 Creating a Folder as a child of ComputedFolder causes Jenkins to hang Change By: Stephen Connolly Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42680) Creating a Folder as a child of ComputedFolder causes Jenkins to hang
Title: Message Title Stephen Connolly commented on JENKINS-42680 Re: Creating a Folder as a child of ComputedFolder causes Jenkins to hang So the issue is when there is any Folder that is a child of any AbstractFolder subclass that is not a Folder subclass (which explains how OrganizationFolder was OK, because all its children are not Folder subclasses) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41616) Non-trusted pull requests should use a probe against the trusted revision not the PR's revision
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41616 Re: Non-trusted pull requests should use a probe against the trusted revision not the PR's revision Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java http://jenkins-ci.org/commit/github-branch-source-plugin/8272f20a872ce4fbafb6417b00bdd5aea0a43e7b Log: [FIXED JENKINS-41616] Non-trusted pull requests should use a probe against the trusted revision not the PR's revision Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35475) Multibranch pipeline displays SCM views multiple times
Title: Message Title Stephen Connolly updated JENKINS-35475 Merged and will be in the next release Jenkins / JENKINS-35475 Multibranch pipeline displays SCM views multiple times Change By: Stephen Connolly Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. 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.co
[JIRA] (JENKINS-42829) [Regression] Jenkins pipeline start failing in on when/expression clause with custom method call with No such DSL method found among steps
Title: Message Title
Florian Mignotet commented on JENKINS-42829
Re: [Regression] Jenkins pipeline start failing in on when/_expression_ clause with custom method call with No such DSL method found among steps
Hi, Same kind of regression for me :
[...]
@NonCPS
def initStages() {
def jsonSlurper = new JsonSlurper()
def parameters = jsonSlurper.parseText(params.STAGES)
def stagesToRun = [
clean: parameters.fabrication.clean,
prepare: parameters.fabrication.prepare,
build: parameters.fabrication.build,
artifacts: parameters.fabrication.artifacts,
qa: parameters.tests.run
]
return stagesToRun
}
def stagesToRun = initStages()
[...]
pipeline {
agent {
label 'linux'
}
stages {
stage('Clean') {
when {
_expression_ {
stagesToRun['clean']
}
}
[...]
Now it returns the error :
groovy.lang.MissingPropertyException: No such property: stagesToRun for class: Script1
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:243)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onGetProperty(GroovyInterceptor.java:52)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:308)
at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28)
at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
at Script1.run(Script1.groovy:1)
It was working like a charm before the last update to Jenkins 2.50 and Pipeline Model Definition to 1.1.1
Add Comment
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Emmanuel Quincerot commented on JENKINS-41425 Re: Refreshing page with / in job name results in 404 When should it be released? The ticket did not appear in the changelog. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar started work on JENKINS-42831 Change By: Emilio Escobar Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-42831 Enable StartTls is always TRUE in the UI Issue Type: Bug Assignee: Emilio Escobar Components: active-directory-plugin Created: 2017/Mar/16 10:55 AM Environment: active-directory-plugin 2.2 Priority: Critical Reporter: Emilio Escobar Enable StartTls new option is always TRUE in the UI, even if you try to uncheck it. But, it is properly persisted on disk Add Comment
[JIRA] (JENKINS-42680) Creating a Folder as a child of ComputedFolder causes Jenkins to hang
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42680 Re: Creating a Folder as a child of ComputedFolder causes Jenkins to hang Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/relocate/StandardHandler.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/22f56ef80880c0b79842bcd5cb480c84fa27f6f4 Log: [FIXED JENKINS-42680] Prevent infinite loop when a Folder is a child of an AbstractFolder Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Stephen Connolly commented on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up You need to run periodically, if even once a week Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar started work on JENKINS-42831 Change By: Emilio Escobar Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar updated JENKINS-42831 Jenkins / JENKINS-42831 Enable StartTls is always TRUE in the UI Change By: Emilio Escobar Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Emilio Escobar stopped work on JENKINS-42831 Change By: Emilio Escobar Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41736 Re: Better descriptions for jenkins.branch.BranchEventCause Code changed in jenkins User: Stephen Connolly Path: docs/implementation.adoc src/main/java/jenkins/scm/api/SCMEvent.java src/main/java/jenkins/scm/api/SCMHeadEvent.java src/main/java/jenkins/scm/api/SCMNavigatorEvent.java src/main/java/jenkins/scm/api/SCMSourceEvent.java http://jenkins-ci.org/commit/scm-api-plugin/48c4030c7c5fc73636335bb1e369757f9da9b81d Log: Merge pull request #34 from stephenc/jenkins-41736 JENKINS-41736 Add ability for SCMEvents to describe themselves Compare: https://github.com/jenkinsci/scm-api-plugin/compare/6a5f70bcf451...48c4030c7c5f Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41736) Better descriptions for jenkins.branch.BranchEventCause
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41736 Re: Better descriptions for jenkins.branch.BranchEventCause Code changed in jenkins User: Stephen Connolly Path: docs/implementation.adoc src/main/java/jenkins/scm/api/SCMEvent.java src/main/java/jenkins/scm/api/SCMHeadEvent.java src/main/java/jenkins/scm/api/SCMNavigatorEvent.java src/main/java/jenkins/scm/api/SCMSourceEvent.java http://jenkins-ci.org/commit/scm-api-plugin/3ac7d128649d92ba9acbdad804021ab319944641 Log: JENKINS-41736 Add ability for SCMEvents to describe themselves Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42757) Wrong changelog displayed when using two repositories
Title: Message Title Manuel Cardenas commented on JENKINS-42757 Re: Wrong changelog displayed when using two repositories I've found that once that you upgrade git-branch-source to version 1.10.1 the problem does not persist. Thus, I think that we can close the issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41425) Refreshing page with / in job name results in 404
Title: Message Title Emmanuel Quincerot edited a comment on JENKINS-41425 Re: Refreshing page with / in job name results in 404 When should it be released?The ticket did not appear never appeared in the changelog Blue Ocean release notes . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42623) PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view"
Title: Message Title boris avney closed an issue as Cannot Reproduce Copied again from pipeline generator and it works. Probably syntax error due to bad copy paste from generator. Jenkins / JENKINS-42623 PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view" Change By: boris avney Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-42138) swarm-client-3.3-jar-with-dependencies is missing from repo.jenkins-ci.org
Title: Message Title spencer malone commented on JENKINS-42138 Re: swarm-client-3.3-jar-with-dependencies is missing from repo.jenkins-ci.org Looking at the file, I think that 3.3 might have just dropped the dependency-less jar, actually. 2.2's swarm-client-2.2.jar file is 28kb, but the one with dependencies is 1.3 mb 3.3's only available jar file is 1.5mb Could someone else confirm that the 3.3 jar has the dependencies baked in? Sadly, the jenkins puppet module is hard baked to use the swarm-client-jar-with-dependencies.jar file name pattern, so I can't easily test it at the moment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42757) Wrong changelog displayed when using two repositories
Title: Message Title Manuel Cardenas closed an issue as Fixed It does not show once that you upgrade git-branch-source to 1.10.1 Jenkins / JENKINS-42757 Wrong changelog displayed when using two repositories Change By: Manuel Cardenas Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit http
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Laurent TOURREAU commented on JENKINS-42675 Re: Override default NodeJS registry when installing in global mode on Global Tools Configuration page I agree with you regarding the global installation mainly concern 3rd party tools like bower, gulp, etc. It's our case. But in our company we use a corporate registry to achieve better network performance and avoid external traffic. The problem now if I set Jenkins proxy settings, the "No proxy" setting is ignored by "Global Tools Configuration" and I get HTTP 403. I tried to set --no-proxy "mycorporaterepo.mycompany.com" without any success. I also try --noproxy or --no_proxy option without any positive result. As workaround I set no_proxy environment variable beside JENKINS_HOME in my tomcat.conf script -> I can access to the internal repo now when Jenkins settings are enabled. The NodeJS plugin should be able to set no_proxy variable to deal with such requested feature. I change the priority to Major because to sum up, it involves two workarounds now: set --registry parameter in "Global npm packages to install" set no_proxy environment variable at Jenkins startup -> it could have other side effect on other Jenkins features. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop r
[JIRA] (JENKINS-42675) Override default NodeJS registry when installing in global mode on Global Tools Configuration page
Title: Message Title Laurent TOURREAU updated an issue Jenkins / JENKINS-42675 Override default NodeJS registry when installing in global mode on Global Tools Configuration page Change By: Laurent TOURREAU Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42829) [Regression] Jenkins pipeline start failing in on when/expression clause with custom method call with No such DSL method found among steps
Title: Message Title Andrew Bayer commented on JENKINS-42829 Re: [Regression] Jenkins pipeline start failing in on when/_expression_ clause with custom method call with No such DSL method found among steps Yeah, this is an unpleasant side effect of the fix for https://issues.jenkins-ci.org/browse/JENKINS-42498 - I'll be working on this today, as well as adding more regression tests. Sorry for the inconvenience. =( Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27519) NullPointerException on save config with svn+ssh connection
Title: Message Title Timotej Simunic commented on JENKINS-27519 Re: NullPointerException on save config with svn+ssh connection Same problem here. Any solutions or new informations ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42805) Connecting to JIRA behind a proxy fails
Title: Message Title Radek Antoniuk closed an issue as Duplicate Duplicate of JENKINS-25829 Jenkins / JENKINS-42805 Connecting to JIRA behind a proxy fails Change By: Radek Antoniuk Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27396) Elastic timeout
Title: Message Title ikedam updated JENKINS-27396 Jenkins / JENKINS-27396 Elastic timeout Change By: ikedam Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27396) Elastic timeout
Title: Message Title ikedam stopped work on JENKINS-27396 Change By: ikedam Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27396) Elastic timeout in pipeline
Title: Message Title ikedam updated an issue Jenkins / JENKINS-27396 Elastic timeout in pipeline Change By: ikedam Summary: Elastic timeout in pipeline Component/s: build-timeout-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title ikedam stopped work on JENKINS-26521 Change By: ikedam Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title ikedam updated JENKINS-26521 Jenkins / JENKINS-26521 timeout step should support breaking on inactivity, not just a fixed duration Change By: ikedam Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Alex Taylor commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Jesse Glick, so I have a decently reproducible case for a freestyle job as well where docker-commons needs to be updated(either with the CLI or with changing the .dockercfg file). It seems that with the 1.12 version of docker they changed the file which is needed to log you in from ~/.dockercfg to ~/.docker/config.json which means that it will not see your credentials. So if you have a Private repo in dockerhub it will not log you in properly. Environment: Jenkins 2.32.3(but I think jenkins version is irrelevant) Docker-commons: 1.6 Docker version 1.12 on the machine running the job Docker build and publish:1.3.2 Steps to reproduce: Have a freestyle job Have a private dockerhub repository Have a step which is building a docker container and pushing it to that private dockerhub repo Behavior: It fails with a unauthenticated error because the ~/.dockercfg file no longer works. The docker build and publish step leverages the docker commons plugin to log into private repos so this is a good case to see the failure. Expected Behavior It would upload the docker container to your repo Workaround: If you log into that dockerhub repo through the CLI in a shell step before the build and publish step, it will create a ~/.docker/config.json file which will retain your credentials until the end of the build. Then the build and publish will work normally So I suppose we could potentially create both files as a temporary fix until we move to the CLI? What are your thoughts guys? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title ikedam updated an issue Jenkins / JENKINS-26521 timeout step should support breaking on inactivity, not just a fixed duration Change By: ikedam Component/s: build-timeout-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42786) Allow users to rename files remotely in ftp server
Title: Message Title Bruno Cantisano updated an issue Jenkins / JENKINS-42786 Allow users to rename files remotely in ftp server Change By: Bruno Cantisano Issue Type: New Feature Task Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Jesse Prieur updated an issue Jenkins / JENKINS-42632 CCM Plugin Not Creating Trend Graph Change By: Jesse Prieur Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42832) Allow users to rename files remotely in ftp server
Title: Message Title Bruno Cantisano moved an issue Jenkins / JENKINS-42832 Allow users to rename files remotely in ftp server Change By: Bruno Cantisano Project: Plugin Hosting Requests Jenkins Key: HOSTING JENKINS - 299 42832 Workflow: HOSTING: Simple Issue Tracking Workflow JNJira + In-Review Status: To Do Open Component/s: ftppublisher-plugin Component/s: New Plugin Hosting Request Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42832) Allow users to rename files remotely in ftp server
Title: Message Title Bruno Cantisano started work on JENKINS-42832 Change By: Bruno Cantisano Resolution: Won't Fix Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42833) Cosmetic: mavenmoduleset.png not available on http site
Title: Message Title Sjoerd de Boer created an issue Jenkins / JENKINS-42833 Cosmetic: mavenmoduleset.png not available on http site Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2017/Mar/16 2:44 PM Environment: All straight out of the box. Windows Server 2012 / Jenkins 2.32.3 out of the box / Oracle java 6u45 Priority: Minor Reporter: Sjoerd de Boer Started with a clean Jenkins. Installed the maven plugin trought Jenkins. On clicking New Item the Maven logo is not visible. According to the html the picture mavenmoduleset.png should come from http:///static/3e6efa0b/plugin/maven/images/48x48/mavenmoduleset.png maven should be mave-plugin as that is name of the plugin. Add Comment
[JIRA] (JENKINS-42824) Super Slow "Build with Parameters" loading
Title: Message Title Jurgens H updated an issue Jenkins / JENKINS-42824 Super Slow "Build with Parameters" loading Change By: Jurgens H Attachment: config_configuresave.xml Attachment: config_generatedbydsl.xml Attachment: EnvValues.groovy Attachment: jobdsl.groovy Attachment: test.json Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed
[JIRA] (JENKINS-42834) Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-42834 Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..." Change By: Reinhold Füreder Environment: Jenkins v 2.50 Linux Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42824) Super Slow "Build with Parameters" loading
Title: Message Title Jurgens H commented on JENKINS-42824 Re: Super Slow "Build with Parameters" loading I failed to mention that we use Java Version 1.8.0_102 on our Jenkins Master By trying to set up a sample for you, I found something very interesting. We us Job DSL to generate our jobs. We have https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin version 1.58 installed. I generated SampleJob using the attached jobdsl.groovy. The test.json and scriptler script is also attached. Here are my scenarios: 1. With 767 jobs on my master, I generate the SampleJob using DSL, and immediately click "Build with Parameters" after SampleJob is generated... Results: The pages says "Connecting..." for 1 minutes 36 seconds. Then it loads for 1 minutes 44 seconds. When I change ENV field from "Test1" to "Test2", it takes another 1 minutes 45 seconds to reload. Config File from Jobs folder: config_generatedbydsl.xml 2. With 767 jobs on my master, I Configure and immediately Save the SampleJob in Jenkins, without any changes... Results: The pages says "Connecting..." for 24 seconds. Then it loads for 27 seconds. When I change ENV field from "Test1" to "Test2", it takes another 28 seconds to reload. Config File from Jobs folder: config_configuresave.xml Then I delete all the other 765 jobs. The only jobs left is the DSL job and SampleJob. 1. With 2 jobs on my master, I generate the SampleJob using DSL, and immediately click "Build with Parameters" after SampleJob is generated... Results: The pages says "Connecting..." for 22 seconds. Then it loads for 27 seconds. When I change ENV field from "Test1" to "Test2", it takes another 32 seconds to reload. Config File from Jobs folder: config_generatedbydsl.xml 2. With 2 jobs on my master, I Configure and immediately Save the SampleJob in Jenkins, without any changes... Results: The pages says "Connecting..." for 20 seconds. Then it loads for 29 seconds. When I change ENV field from "Test1" to "Test2", it takes another 28 seconds to reload. Config File from Jobs folder: config_configuresave.xml I hope this helps you. Thank you. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d
[JIRA] (JENKINS-42834) Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
Title: Message Title
Reinhold Füreder updated an issue
Jenkins / JENKINS-42834
Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
Change By:
Reinhold Füreder
Logs like this are appearing since upgrading to Jenkins v 2.50 (and also updating a few Jenkins Plugins):{noformat}**:/var/log/jenkins$ grep "badMessage" *jenkins.log:2017-03-14 10:28:01 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@4b64f1dd{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 10:36:05 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@24bff35f{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 11:05:21 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@df42f50{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 11:06:55 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1a14713f{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 11:08:52 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@81dfefb{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 11:11:08 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@124bb288{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 11:11:45 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@7db69510{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 11:11:50 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@10f69010{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 12:16:59 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@205aa4cf{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 14:46:36 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@6abce810{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-14 14:47:04 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1d079aba{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-15 10:06:11 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@24636165{r=1,c=false,a=IDLE,uri=}jenkins.log:2017-03-15 10:14:52 WARNING [org.eclipse.j
[JIRA] (JENKINS-42834) Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
Title: Message Title
Reinhold Füreder created an issue
Jenkins / JENKINS-42834
Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2017/Mar/16 2:50 PM
Environment:
Jenkins v 2.50
Priority:
Minor
Reporter:
Reinhold Füreder
Logs like this are appearing since upgrading to Jenkins v 2.50 (and also updating a few Jenkins Plugins):
**:/var/log/jenkins$ grep "badMessage" *
jenkins.log:2017-03-14 10:28:01 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@4b64f1dd{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 10:36:05 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@24bff35f{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:05:21 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@df42f50{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:06:55 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@1a14713f{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017-03-14 11:08:52 WARNING [org.eclipse.jetty.util.log.JavaUtilLog warn] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@81dfefb{r=1,c=false,a=IDLE,uri=}
jenkins.log:2017
[JIRA] (JENKINS-42835) Allow users to rename files remotely in ftp server
Title: Message Title Bruno Cantisano moved an issue Jenkins / JENKINS-42835 Allow users to rename files remotely in ftp server Change By: Bruno Cantisano Project: Plugin Hosting Requests Jenkins Key: HOSTING JENKINS - 300 42835 Workflow: HOSTING: Simple Issue Tracking Workflow JNJira + In-Review Component/s: ftppublisher-plugin Component/s: New Plugin Hosting Request Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42835) Allow users to rename files remotely in ftp server
Title: Message Title Bruno Cantisano stopped work on JENKINS-42835 Change By: Bruno Cantisano Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42835) Allow users to rename files remotely in ftp server
Title: Message Title Bruno Cantisano closed an issue as Not A Defect Jenkins / JENKINS-42835 Allow users to rename files remotely in ftp server Change By: Bruno Cantisano Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40037) Docker builds fail with "Build info capturing failed for docker image..." exception
Title: Message Title sébastien glon commented on JENKINS-40037 Re: Docker builds fail with "Build info capturing failed for docker image..." exception My jenkins master is on swarm cluster A and my slave is spawn on a second swarm cluster B. When i build image from my pipeline, i build on docker-in-Docker whit proxy configurer to point on my jenkins Master. If i check on debug, i can see buidinfo on my master but have not acces to my Docker-in-Docker and not register ImageId and Image Tag on DockerAgentUtil.registerImage method. Why this method check access on Docker Host? Is it possible add nodo info on BuildInfo for using them on method updateImageParentOnAgents? Because my Jenkins master have buildInfo but no acces to Docker-inDocker and jenkins slave have'n buidInfo and not updateImageParent. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Sorin Sbarnea edited a comment on JENKINS-41200 Re: Developer can see ANSI color in log file I would not consider the lack of ANSI support as a * minor * issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42836) Build parameter not expanded in script path
Title: Message Title
Brian Keyser updated an issue
Jenkins / JENKINS-42836
Build parameter not expanded in script path
Change By:
Brian Keyser
Steps to reproduce # Create a pipeline job # Add a build parameter to specify the URL of a git repository, $\{gitUrl} # Add a build parameter to specify the build script to execute, $\{script} # Within the Pipeline section ## Select "Pipeline script from SCM" ## Select "Git" for the SCM ## Enter $\{gitUrl} for the Repository URL ## Enter the branch to build ## Enter $\{script ) } for the "Script Path"Perform a "Build with Parameters" and enter values for the gitUrl and script values and select Build. The following error is reported{code:java}Mar 16, 2017 2:43:53 PM org.jenkinsci.plugins.workflow.job.WorkflowRun finishINFO: Worker #4 completed: FAILUREMar 16, 2017 2:43:53 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregisterWARNING: Owner[Worker/4:Worker #4] was not in the list to begin with: []Mar 16, 2017 2:43:53 PM io.jenkins.blueocean.events.PipelineEventListener$1 runSEVERE: Unexpected error publishing pipeline FlowNode event.java.util.concurrent.ExecutionException: hudson.AbortException: /var/jenkins_home/workspace/Worker@script/${script} not foundat com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)at io.jenkins.blueocean.events.PipelineEventListener$1.run(PipelineEventListener.java:226)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)Caused by: hudson.AbortException: /var/jenkins_home/workspace/Worker@script/${script} not foundat org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:136)at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:59)at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:232)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:404){code}If $\{script} is set to the location of a script, the job starts successfully.
[JIRA] (JENKINS-42836) Build parameter not expanded in script path
Title: Message Title
Brian Keyser created an issue
Jenkins / JENKINS-42836
Build parameter not expanded in script path
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline, scm-api-plugin
Created:
2017/Mar/16 3:05 PM
Priority:
Minor
Reporter:
Brian Keyser
Steps to reproduce
Create a pipeline job
Add a build parameter to specify the URL of a git repository, ${gitUrl}
Add a build parameter to specify the build script to execute, ${script}
Within the Pipeline section
Select "Pipeline script from SCM"
Select "Git" for the SCM
Enter ${gitUrl} for the Repository URL
Enter the branch to build
Enter ${script) for the "Script Path"
Perform a "Build with Parameters" and enter values for the gitUrl and script values and select Build. The following error is reported
Mar 16, 2017 2:43:53 PM org.jenkinsci.plugins.workflow.job.WorkflowRun finish
INFO: Worker #4 completed: FAILURE
Mar 16, 2017 2:43:53 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregister
WARNING:
[JIRA] (JENKINS-41200) Developer can see ANSI color in log file
Title: Message Title Sorin Sbarnea commented on JENKINS-41200 Re: Developer can see ANSI color in log file I would not consider the lack of ANSI support as minor issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41019) Check in into subfolder of current project
Title: Message Title Peter Simon commented on JENKINS-41019 Re: Check in into subfolder of current project Hi, Did you perhaps manage to recreate the problem? Péter Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42037) The VM Usage param. cannot be changed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42037 Re: The VM Usage param. cannot be changed Code changed in jenkins User: Claudiu Guiman Path: src/main/java/com/microsoft/azure/vmagent/AzureVMAgentTemplate.java src/main/resources/com/microsoft/azure/vmagent/AzureVMAgentTemplate/config.jelly http://jenkins-ci.org/commit/azure-vm-agents-plugin/039c5acfd3a2d0460b76c85269ad22d11337cc61 Log: Replace the f:slave-mode node with a dropdown menu so we can save the usageMode parameter [FIXED JENKINS-42037] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42037) The VM Usage param. cannot be changed
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-42037 The VM Usage param. cannot be changed Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42824) Super Slow "Build with Parameters" loading
Title: Message Title Jurgens H edited a comment on JENKINS-42824 Re: Super Slow "Build with Parameters" loading I failed to mention that we use Java Version 1.8.0_102 on our Jenkins MasterBy trying to set up a sample for you, I found something very interesting. We us use Job DSL to generate our jobs. We have [ https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin ] version 1.58 installed. I generated SampleJob using the attached jobdsl.groovy. The test.json and scriptler script is also attached.Here are my scenarios:1. With 767 jobs on my master, I generate the SampleJob using DSL, and immediately click "Build with Parameters" after SampleJob is generated...Results: The pages says "Connecting..." for 1 minutes 36 seconds. Then it loads for 1 minutes 44 seconds. When I change ENV field from "Test1" to "Test2", it takes another 1 minutes 45 seconds to reload.Config File from Jobs folder: config_generatedbydsl.xml2. With 767 jobs on my master, I Configure and immediately Save the SampleJob in Jenkins, without any changes...Results: The pages says "Connecting..." for 24 seconds. Then it loads for 27 seconds. When I change ENV field from "Test1" to "Test2", it takes another 28 seconds to reload.Config File from Jobs folder: config_configuresave.xmlThen I delete all the other 765 jobs. The only jobs left is the DSL job and SampleJob.1. With 2 jobs on my master, I generate the SampleJob using DSL, and immediately click "Build with Parameters" after SampleJob is generated...Results: The pages says "Connecting..." for 22 seconds. Then it loads for 27 seconds. When I change ENV field from "Test1" to "Test2", it takes another 32 seconds to reload.Config File from Jobs folder: config_generatedbydsl.xml2. With 2 jobs on my master, I Configure and immediately Save the SampleJob in Jenkins, without any changes...Results: The pages says "Connecting..." for 20 seconds. Then it loads for 29 seconds. When I change ENV field from "Test1" to "Test2", it takes another 28 seconds to reload.Config File from Jobs folder: config_configuresave.xmlI hope this helps you.Thank you. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3
[JIRA] (JENKINS-41138) Coverity - Job Failed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41138 Re: Coverity - Job Failed Code changed in jenkins User: Andrew Cho Path: src/main/java/jenkins/plugins/coverity/CoverityLauncher.java src/main/java/jenkins/plugins/coverity/CoverityTool/CoverityCommand.java src/main/java/jenkins/plugins/coverity/CoverityTool/CoverityToolHandler.java src/main/java/jenkins/plugins/coverity/ws/DefectReader.java http://jenkins-ci.org/commit/coverity-plugin/7f5570f37a5c9b94d5da8edf9bececb1bdb8a56e Log: Merge branch 'BZ100126' into 'jenkins19' Fix for #100126 & #101120 #100126 - JENKINS-41138 Coverity - Job Failed. With recent changes related to `CoverityLauncher`, `CoverityLauncherDecorator`, and all command classes, the intermediate directory was not setting up properly only when capturing the scripting languages. #101120 - Null exception message when CIM information is blank. Added null checks and the coverity plugin does not throw any NPE exceptions. Also, added logging in the DefectReader. The result of the build with this change is pass as it was with previous version whether that is the correct behaviour or not. See merge request !87 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41138) Coverity - Job Failed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41138 Re: Coverity - Job Failed Code changed in jenkins User: Andrew Cho Path: src/main/resources/jenkins/plugins/coverity/CoverityPublisher/help-isScriptSrc.html http://jenkins-ci.org/commit/coverity-plugin/a8360c5bb73396e9f037dc7a851f31eb1eea5766 Log: Merge branch 'BZ100126' into 'jenkins19' Fix for #100126 - JENKINS-41138 Coverity - Job Failed. Currently, we do not have enough information, which we asked the customer for more information to find the root cause of the problem, but have not heard back. However, with this changes, at least the users will know that if they want to capture and analyze scripting language source files, the files must exist in the build workspace. Fix: 100126  See merge request !65 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41138) Coverity - Job Failed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41138 Re: Coverity - Job Failed Code changed in jenkins User: Andrew Cho Path: src/main/java/jenkins/plugins/coverity/CoverityLauncher.java http://jenkins-ci.org/commit/coverity-plugin/94e32ea1d5978145b9275001962f4353676cd3c2 Log: JENKINS-41138 Coverity Job Failed. This is case when the Coverity plugin is used only for capturing scripting files. There was a problem with setting up the intermediate directory Fix: 100126 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41138) Coverity - Job Failed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41138 Re: Coverity - Job Failed Code changed in jenkins User: Andrew Cho Path: src/main/resources/jenkins/plugins/coverity/CoverityPublisher/help-isScriptSrc.html http://jenkins-ci.org/commit/coverity-plugin/9b41dab5c2031e58d7541a46eaa1dbdf5e68c491 Log: JENKINS-41138 Coverity - Job Failed. Currently, we do not have enough information, which we asked the customer for more information to find the root cause of the problem, but have not heard back. However, with this changes, at least the users will know that if they want to capture and analyze scripting language source files, the files must exist in the build workspace. Fix: 100126 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42824) Super Slow "Build with Parameters" loading
Title: Message Title Jurgens H updated an issue Jenkins / JENKINS-42824 Super Slow "Build with Parameters" loading Change By: Jurgens H Environment: Jenkins ver. 2.32.3, Active Choices Plug-in 1.5.3 or earlier, on Windows Server 2013 , Java Version 1.8.0_102 on master, Job DSL Plugin 1.58 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42736) Empty branch name results in failed pipeline graph visualisation
Title: Message Title Keith Zantow updated JENKINS-42736 Jenkins / JENKINS-42736 Empty branch name results in failed pipeline graph visualisation Change By: Keith Zantow Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42734) Adding a parallel branch with no name results in a slightly bad Jenkinsfile
Title: Message Title Keith Zantow resolved as Not A Defect Michael Neale please reopen this if you think we should do it, I think it would be best to just add to declarative validation instead of doing something custom with the editor, though, Jenkins / JENKINS-42734 Adding a parallel branch with no name results in a slightly bad Jenkinsfile Change By: Keith Zantow Status: In Progress Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsub
[JIRA] (JENKINS-42837) Copy Job replaces single "$" with double "$$" in echo commands in Jenkins
Title: Message Title ashutosh yadav created an issue Jenkins / JENKINS-42837 Copy Job replaces single "$" with double "$$" in echo commands in Jenkins Issue Type: Bug Assignee: Unassigned Components: copy-project-link-plugin Created: 2017/Mar/16 3:18 PM Labels: copy-job Priority: Major Reporter: ashutosh yadav I created one JOb in jenkins and created execute ssh script with echo command , in that echo command i was accessing some environment variables with $. I copied this JOb and created a new Job , but in the new job the echo command was disturbed and there were 2 $$ in place of single $. Add Comment
[JIRA] (JENKINS-42838) Support for additonal testlinkfields as environment variables
Title: Message Title Achim Zimmer created an issue Jenkins / JENKINS-42838 Support for additonal testlinkfields as environment variables Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: testlink-plugin Created: 2017/Mar/16 3:24 PM Priority: Minor Reporter: Achim Zimmer Actually there is a need additional information from a Testcase to be available in Jenkins build jobs. The field f.e. "version" of a testcase might be already retrieved from Testlink by the RPC call, but not set to an environment variable. Same interesting would be the short id like "PRJ-5" as available parameter in Jenkins. Is there any possibility to access these fields or maybe the possibility to configure the plugin to create environment variables based on available testcase fields? This feature would be very helpful. Add Comment
[JIRA] (JENKINS-42093) Can't work in workspace with spaces
Title: Message Title Thomas Tree updated an issue Jenkins / JENKINS-42093 Can't work in workspace with spaces Change By: Thomas Tree Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42093) Can't work in workspace with spaces
Title: Message Title Thomas Tree commented on JENKINS-42093 Re: Can't work in workspace with spaces Hello, this bug is very critical for us. We have some Projects Named with spaces and we at the moment the projects are not working. Started by GitLab push by tomcat667 [EnvInject] - Loading node environment variables. Building in workspace /var/lib/jenkins/jobs/Test-Web (QA)/workspace [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-r4W8JcH8Q9kJ/agent.20618 SSH_AGENT_PID=20621 [ssh-agent] Started. $ ssh-add "/var/lib/jenkins/jobs/Test-Web (QA)/workspace@tmp/private_key_6639950023827103741.key" rm: cannot remove ‘/var/lib/jenkins/jobs/Test-Web’: No such file or directory rm: cannot remove ‘(QA)/workspace@tmp/askpass_7451015691127031249.sh’: No such file or directory ERROR: Failed to run ssh-add Checking console output Recording test results Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42093) Can't work in workspace with spaces
Title: Message Title
Thomas Tree edited a comment on JENKINS-42093
Re: Can't work in workspace with spaces
Hello,this bug is very critical for us. We have some Projects Named with spaces and we at the moment the projects are not working. {code:java}Started by GitLab push by tomcat667[EnvInject] - Loading node environment variables.Building in workspace /var/lib/jenkins/jobs/Test-Web (QA)/workspace[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)$ ssh-agentSSH_AUTH_SOCK=/tmp/ssh-r4W8JcH8Q9kJ/agent.20618SSH_AGENT_PID=20621[ssh-agent] Started.$ ssh-add "/var/lib/jenkins/jobs/Test-Web (QA)/workspace@tmp/private_key_6639950023827103741.key"rm: cannot remove ‘/var/lib/jenkins/jobs/Test-Web’: No such file or directoryrm: cannot remove ‘(QA)/workspace@tmp/askpass_7451015691127031249.sh’: No such file or directoryERROR: Failed to run ssh-addChecking console outputRecording test results{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42816) Slave to Agent renaming leftovers
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-42816 Slave to Agent renaming leftovers Change By: Oleg Nenashev Assignee: Nicolas De Loof Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42839) Slave to Agent Renaming: Windows Slaves Plugin
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-42839 Slave to Agent Renaming: Windows Slaves Plugin Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42839) Slave to Agent Renaming: Windows Slaves Plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-42839 Slave to Agent Renaming: Windows Slaves Plugin Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: windows-slaves-plugin Created: 2017/Mar/16 3:43 PM Priority: Minor Reporter: Oleg Nenashev In Jenkins 2 "slaves" have been renamed to "agents". It would be useful to adjust this component, at least the plugin name, UI layout, Wiki and probably Javadoc Add Comment This message was sent by Atlassian JIRA (v7.3.0#
[JIRA] (JENKINS-42840) Slave to Agent Renaming: SSH Slaves Plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-42840 Slave to Agent Renaming: SSH Slaves Plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: windows-slaves-plugin Created: 2017/Mar/16 3:44 PM Priority: Minor Reporter: Oleg Nenashev In Jenkins 2 "slaves" have been renamed to "agents". It would be useful to adjust this component, at least the plugin name, UI layout, Wiki and probably Javadoc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sh
[JIRA] (JENKINS-42840) Slave to Agent Renaming: SSH Slaves Plugin
Title: Message Title Oleg Nenashev assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-42840 Slave to Agent Renaming: SSH Slaves Plugin Change By: Oleg Nenashev Assignee: Oleg Nenashev Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42840) Slave to Agent Renaming: SSH Slaves Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42840 Slave to Agent Renaming: SSH Slaves Plugin Change By: Oleg Nenashev Component/s: ssh-slaves-plugin Component/s: windows-slaves-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42841) Slave to Agent Renaming: Slave Installer Module
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-42841 Slave to Agent Renaming: Slave Installer Module Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 2017/Mar/16 3:44 PM Priority: Minor Reporter: Oleg Nenashev In Jenkins 2 "slaves" have been renamed to "agents". It would be useful to adjust this component, at least the plugin name, UI layout, Wiki and probably Javadoc Add Comment This message was sent by Atlassian JIRA (v7.3.0#730
