[JIRA] (JENKINS-43027) Force continue build execution on failure of previous build steps
Title: Message Title Naresh Gunda commented on JENKINS-43027 Re: Force continue build execution on failure of previous build steps wolfs: Hey thanks for the solution. First one worked for me too. But the problem is, this is marking the jenkins job as successful even if the testcases are failed. It would be great if the build is also marked as failure. Second solution will not work in my case. Because in the second execute shell im extracting the files from android emulator. If i move execute shell to post build action, i cannot extract the files from emulator as emulator will be killed before post build action are executed. 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-32779) Spot instance hit cap when sharing a AMI
Title: Message Title Joshua Ma commented on JENKINS-32779 Re: Spot instance hit cap when sharing a AMI We've had this issue on and off for the past few months, so it spans several versions. Currently on 1.36 and seeing this. We have 4 configs all using the same AMI. Caps: 6, 40, 5, 25 Currently running: 2, 18, 5, 19 (total of 44) We now can't run anymore. We had 46, I terminated 2, and now I can't launch 2, so somehow it let me get to a number it doesn't like. I bumped our "40" cap to "45", hoping that would let me launch 1 more, but I still get "java.lang.Exception: Cloud or AMI instance cap would be exceeded for: c4.large.gittest.spot" I added a log recorder, and it says: "Available Total Slaves: 56 Available AMI slaves: -12 AMI: ami-99022c87 TemplateDesc: c4.large.gittest.spot" I don't know where -12 is coming from, but that's probably related. 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 Félix Belzunce Arcos updated an issue Jenkins / JENKINS-42831 Enable StartTls is always TRUE in the UI Change By: Félix Belzunce Arcos 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-22874) Ability to configure thresholds for each Warnings parser used
Title: Message Title Arno Moonen commented on JENKINS-22874 Re: Ability to configure thresholds for each Warnings parser used This is something I'm also looking for. Has anyone worked on this yet? Also, which plugins would need to change for this to happen, just the warnings-plugin or also the analysis-core 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-20161) 500s when requesting /job/{jobname}/api/python w/ "run" parameter for nonexistent project
Title: Message Title
Luke Fielke commented on JENKINS-20161
Re: 500s when requesting /job/{jobname}/api/python w/ "run" parameter for nonexistent project
I'm also seeing this issue on Jenkins 2.32.3. Creating a new free style job, adding a run parameter and typing a non-existent job name in the job name field can also trigger this. The JSON and XML API URLs also error and show similar stacktraces. The stacktrace from the XML one:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletF
[JIRA] (JENKINS-34121) IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3
Title: Message Title Oleg Nenashev commented on JENKINS-34121 Re: IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3 Mallikarjuna Manoj Kandala 1) Upgrade to Jenkins 2.32.1 or above 2) Go to the Global Security Configuration in Manage Jenkins 3) Ensure that JNLP4 is allowed in protocol security settings 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-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-43038 Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins Please provide a full exception stacktrace at least 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-42861) Jenkins references shut down service stacktrace.jenkins-ci.org
Title: Message Title Oleg Nenashev updated JENKINS-42861 Jenkins / JENKINS-42861 Jenkins references shut down service stacktrace.jenkins-ci.org Change By: Oleg Nenashev 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-42861) Jenkins references shut down service stacktrace.jenkins-ci.org
Title: Message Title Oleg Nenashev started work on JENKINS-42861 Change By: Oleg Nenashev 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-43027) Force continue build execution on failure of previous build steps
Title: Message Title wolfs commented on JENKINS-43027 Re: Force continue build execution on failure of previous build steps Do you collect the JUnit xml files via the JUnit post build action? If you do and you have failing tests your build will be marked as unstable. 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-43057) Unable to access job parameter to select slave
Title: Message Title
Ralf Welt created an issue
Jenkins / JENKINS-43057
Unable to access job parameter to select slave
Issue Type:
Bug
Assignee:
ikedam
Components:
groovy-label-assignment-plugin
Created:
2017/Mar/23 8:13 AM
Environment:
Jenkins ver. 1.642.4.2 (CloudBees Jenkins Enterprise 15.11) Windows 7 SP1 64 Bit Firfox/IE/Chrome
Priority:
Major
Reporter:
Ralf Welt
I want to use Groovy label-assignment plugin on a Multi Job to select by parameter on which slave a sub job should be executed (I already tried Node-parameter-plugin without success) The job gets run on the slave selected by the return value. However, I am not able to evaluate the parameters of the sub job. The method from help does not get the value of the parameter binding.getVariables().get("variable-name"); nor does ANY of the procedures described on the Internet (Stack Overflow for example) Please help. Many thanks in advance!
Add Comment
[JIRA] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Thorsten Meinl commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Since we switched from freestyle jobs to pipelines (a very decision if you as me), about every second jobs fails with this error which makes Windows slaves pretty much unusable. It has never been a problem before, therefore my guess is that is has something to do with pipelines. Here's a strack trace, which always looks the same: java.io.IOException: remote file operation failed: C:\Users\jenkins\slave\workspace\g.knime.product.full_master-6YACVMZPMCFFZKR6NNQZEQAJGOVHWVVS2MSXJGRRFPLNAY2WNRWQ at hudson.remoting.Channel@2eed4a92:Channel to /xxx.xxx.xxx.xxx hudson.remoting.ChannelClosedException: channel is already closed at hudson.FilePath.act(FilePath.java:992) at hudson.FilePath.act(FilePath.java:974) at hudson.FilePath.mkdirs(FilePath.java:1157) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:77) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:65) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:604) at hudson.remoting.Request.call(Request.java:130) at hudson.remoting.Channel.call(Channel.java:821) at hudson.FilePath.act(FilePath.java:985) ... 12 more Caused by: java.io.IOException: Unexpected EOF while receiving the data from the channel. FIFO buffer has been already closed at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:617) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) ... 5 more Caused by: org.jenkinsci.remoting.nio.FifoBuffer$CloseCause: Buffer close has been requested at org.jenkinsci.remoting.nio.FifoBuffer.close(FifoBuffer.java:426) at org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport.closeR(NioChannelHub.java:332) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:565) ... 6 more I'm happy to debug this further if someone tells me what to do.
[JIRA] (JENKINS-42963) Jenkins 2.51 breaks XUnitPublisher step in Pipeline
Title: Message Title Oleg Nenashev commented on JENKINS-42963 Re: Jenkins 2.51 breaks XUnitPublisher step in Pipeline Please provide a full system log for Jenkins 2.51, starting from the Jenkins startup 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-42933) NPE - Can't read property file
Title: Message Title Oleg Nenashev commented on JENKINS-42933 Re: NPE - Can't read property file When Jenkins starts up, there is no guarantee that the Jenkins instance is available, though it should always happen for plugin initialization. Could you please provide a code sample of "at com.my.package.Main" ? 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-43058) Slave to Agent Renaming: Role Strategy Plugin
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-43058 Slave to Agent Renaming: Role Strategy Plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2017/Mar/23 8:30 AM Priority: Minor Reporter: Oleg Nenashev There are some minor fixes required Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43059) Representation of localized strings from powershell scripts was broken
Title: Message Title Roman Gordeev created an issue Jenkins / JENKINS-43059 Representation of localized strings from powershell scripts was broken Issue Type: Bug Assignee: Unassigned Components: powershell-plugin Created: 2017/Mar/23 8:35 AM Environment: Windows 8.1 x64, powershell v4.0, Jenkins ver. 2.32.3, PowerShell plugin 1.3 Priority: Minor Reporter: Roman Gordeev I Add Comment
[JIRA] (JENKINS-43035) expression does not see imported classes
Title: Message Title Stefan Gasterstädt commented on JENKINS-43035 Re: _expression_ does not see imported classes According to your groovy-unit-test [libraryObjectInWhenExpression.groovy](https://github.com/abayer/pipeline-model-definition-plugin/blob/12a0443c5cece4a4a3b04f16d51a4f3f0bd3b2ca/pipeline-model-definition/src/test/resources/libraryObjectInWhenExpression.groovy), this looks exactly similar to my situation. Thank you, that was a fast reaction. 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-43059) Representation of localized strings from powershell scripts was broken
Title: Message Title Roman Gordeev updated an issue Jenkins / JENKINS-43059 Representation of localized strings from powershell scripts was broken Change By: Roman Gordeev I need to use localised localized strings ( cyrillic Cyrillic ) at my powershell routines.When i use it directly from powershell it works fine; but then i invoke scripts as powerhell powershell build step they are broken by extra decoding.e.g."тест" during execution represents as " �,D�?�," at execution log but loks looks normally at UI at step definition.I suppose that some conversion broke it when render content to ps1 script.I also have -Dfile.encoding=UTF8 at my java options. 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/
[JIRA] (JENKINS-43059) Representation of localized strings from powershell scripts was broken
Title: Message Title Roman Gordeev updated an issue Jenkins / JENKINS-43059 Representation of localized strings from powershell scripts was broken Change By: Roman Gordeev I need to use localised strings (cyrillic) at my powershell routines.When i use it directly from powershell it works fine; but then i invoke scripts as powerhell build step they are broken by extra decoding.e.g."тест" during execution represents as " �,D�?�," at execution log but loks normally at UI at step definition.I suppose that some conversion broke it when render content to ps1 script.I also have -Dfile.encoding=UTF8 at my java options. 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-43035) expression does not see imported classes
Title: Message Title Stefan Gasterstädt edited a comment on JENKINS-43035 Re: _expression_ does not see imported classes According to your groovy-unit-test [libraryObjectInWhenExpression.groovy ]( | https://github.com/abayer/pipeline-model-definition-plugin/blob/12a0443c5cece4a4a3b04f16d51a4f3f0bd3b2ca/pipeline-model-definition/src/test/resources/libraryObjectInWhenExpression.groovy ) ] , this looks exactly similar to my situation.Thank you, that was a fast reaction. 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-33433) jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch
Title: Message Title Raphaël UNIQUE commented on JENKINS-33433 Re: jobs fail to "parse changelog" for pull requests with "catch-up" merges from destination branch for us: 2.0.8 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-43060) No success notification is being send
Title: Message Title Timo Schmidt created an issue Jenkins / JENKINS-43060 No success notification is being send Issue Type: Bug Assignee: Unassigned Attachments: output.txt, Screen Shot 2017-03-23 at 10.24.17.png Components: hipchat-plugin Created: 2017/Mar/23 9:28 AM Priority: Major Reporter: Timo Schmidt I do only get occasionly success/failed notifications from the HipChat plugin. You can see my configuration in the screenshot. The cut out terminal output is attached as well. I am using plugin version 2.1.1 Add Comment
[JIRA] (JENKINS-43061) Closures return early if they include a method call
Title: Message Title
Mark J. Becker created an issue
Jenkins / JENKINS-43061
Closures return early if they include a method call
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2017/Mar/23 9:30 AM
Environment:
Jenkins 2.32.1, Pipeline Groovy 2.29, Groovy 2.4.7, latest Pipeline plugins (as of 03/23/17)
Labels:
groovy pipeline
Priority:
Major
Reporter:
Mark J. Becker
Problem It seems that in a pipeline, Groovy closures are returned early if you call a method inside them. The closure then only returns the return value of the called method. I provided a minimal sample to reproduce the bug below. Steps to Reproduce
Execute the following code in a Jenkins pipeline
class Foo {
Closure cl = { String a ->
return "Say: ${this.bar(a)}"
}
String bar(String a) {
return "Hello ${a}."
}
}
Foo f = new Foo()
String output = f.getCl()("World")
echo(output)
It does not matter if the c
[JIRA] (JENKINS-42900) Job-DSL stash notifier creates "Unreadable Data".
Title: Message Title
Daniel Christophis commented on JENKINS-42900
Re: Job-DSL stash notifier creates "Unreadable Data".
Same issue just occured to me. I think because of changes in StashNotifier plugin (https://github.com/jenkinsci/stashnotifier-plugin) stashServerBaseUrl, stashUserName, stashUserPassword and ignoreUnverifiedSSLPeer are obsolete for job configuration in DSL. In my opinion this must be fixed in Job-DSL-Plugin (https://github.com/jenkinsci/job-dsl-plugin) See: https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy#L1028 and perhaps also: https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy As for a temporary workarround you can define you DSL code with a configure block:
configure {
it / 'publishers' << 'org.jenkinsci.plugins.stashNotifier.StashNotifier' {
includeBuildNumberInKey(true) // set false or remove item
commitSha1('') // set commit hash or remove item
}
}
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, sen
[JIRA] (JENKINS-42933) NPE - Can't read property file
Title: Message Title
Loic Pelleau updated an issue
Jenkins / JENKINS-42933
NPE - Can't read property file
Change By:
Loic Pelleau
{code:java}java.lang.NullPointerExceptionat hudson.Plugin.getConfigXml(Plugin.java:289)at hudson.Plugin.load(Plugin.java:262)at com.my.package.Main.(Main.java:43)at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)at java.lang.reflect.Constructor.newInstance(Constructor.java:423)at java.lang.Class.newInstance(Class.java:442)at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:419)at hudson.PluginManager$2$1$1.run(PluginManager.java:405)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$8.runTask(Jenkins.java:925)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745){code}I extends the hudson.Plugin class. Hence, I have a plugin starting at startup.When executing `load()` method from Hudson.Plugin.`save()` method works. Line causing NPE in hudson.Plugin (l.289) :{code:java}return new XmlFile(Jenkins.XSTREAM, new File(Jenkins.getInstance().getRootDir(),wrapper.getShortName()+".xml"));{code}Maybe a problem with the initialization of Jenkins.XSTREAM? class com.my.package.Main: {code:java}package com.my.package;import java.util.*;import java.util.logging.*;import java.io.*;import net.sf.json.*;import org.kohsuke.stapler.*;import hudson.*;import hudson.model.*;import hudson.model.queue.*;import hudson.model.Descriptor.FormException;import jenkins.model.*;public class Main extends Plugin {public boolean activated;public String job;public List packagesFilter;@DataBoundConstructorpublic Main(boolean activated, String job, List packagesFilter) {try {load();} catch (Exception e) {e.printStackTrace();}}public void configure(StaplerRequest req, JSONObject form) throws IOException, FormException {//... var instantiationsave();}public void start() throws Exception {load();}public void stop() {}public boolean getActivated() {return activated;}public String getJob() {return job;}public List getPackagesFilter() {return packagesFilter;}}{code}
[JIRA] (JENKINS-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Giacomo Boccardo created an issue Jenkins / JENKINS-43062 SSH Host Key Verifiers are not configured for all SSH slaves Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 2017/Mar/23 9:37 AM Priority: Minor Reporter: Giacomo Boccardo Since the last update of SSH Slaves plugin, the following warning is shown: SSH Host Key Verifiers are not configured for all SSH slaves on this Jenkins instance. This could leave these slaves open to man-in-the-middle attacks. Update your slave configuration to resolve this. I have three slaves, whose "Launch method" is "Launch agent via Java Web Start" for two of them and "Launch slave agents via SSH" for the third one. Does the warning refer only to the last one? The "Host Key Verification Strategy" I set is "Known hosts file Verification Strategy". What should I do to avoid that warning? Add Comment
[JIRA] (JENKINS-42900) Job-DSL stash notifier creates "Unreadable Data".
Title: Message Title
Daniel Christophis edited a comment on JENKINS-42900
Re: Job-DSL stash notifier creates "Unreadable Data".
Same issue just occured to me. I think because of changes in StashNotifier plugin ([https://github.com/jenkinsci/stashnotifier-plugin)]stashServerBaseUrl, stashUserName, stashUserPassword and ignoreUnverifiedSSLPeer are obsolete for job configuration in DSL. In my opinion this must be fixed in Job-DSL-Plugin ([https://github.com/jenkinsci/job-dsl-plugin)]See: [https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy#L1028]and perhaps also: [https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy] As for a temporary workarround you can define you your DSL code with a configure block: {code:java}configure {it / 'publishers' << 'org.jenkinsci.plugins.stashNotifier.StashNotifier' {includeBuildNumberInKey(true) // set false or remove itemcommitSha1('') // set commit hash or remove item}}{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-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title
Giacomo Boccardo updated an issue
Jenkins / JENKINS-43062
SSH Host Key Verifiers are not configured for all SSH slaves
Change By:
Giacomo Boccardo
Since the last update of SSH Slaves plugin, the following warning is shown: {code:java}SSH Host Key Verifiers are not configured for all SSH slaves on this Jenkins instance. This could leave these slaves open to man-in-the-middle attacks. Update your slave configuration to resolve this.{code}I have three slaves, whose "Launch method" is "Launch agent via Java Web Start" for two of them and "Launch slave agents via SSH" for the third one.Does the warning refer only to the last one?The "Host Key Verification Strategy" I set is "Known hosts file Verification Strategy". What should I do to avoid that warning?
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-42834) Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
Title: Message Title sébastien glon commented on JENKINS-42834 Re: Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..." same on jenkins 2.45 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-38813) NullPointerException accessing params variable with Subversion tag
Title: Message Title
Jip Ver commented on JENKINS-38813
Re: NullPointerException accessing params variable with Subversion tag
Hej there, I'm working on automating all the jenkins build and deploy jobs and pipelines. All of it works, except, that the pipeline does not seem to pick up the subversion tag. I've installed the latest version and dependent plugins of workflow-cps so my nullpointer exeption is gone now. But in stead of that the result of this input is now 'NULL': (so the svntag seems to be empty?)
// Pipeline script:
node {
def RELEASE_UNIT_NUMBER = params.RELEASE_UNIT_NUMBER
echo "nummer: ${RELEASE_UNIT_NUMBER}"
}
// console output
Started by user Jip
[Pipeline] node
Running on master in D:\Apps\Jenkins2\workspace\912_SVNTAG_Parametrized_groovy_PIPELINE
[Pipeline] {
[Pipeline] echo
nummer: null
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
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 G
[JIRA] (JENKINS-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Giacomo Boccardo commented on JENKINS-43062 Re: SSH Host Key Verifiers are not configured for all SSH slaves I read the source code and I can answer to myself: that warning refers only to slaves launched via SSH; the "Known hosts file Verification Strategy" is sufficient to avoid that warning. So, I changed something random in the configuration of the SSH slave, saved, reverted the change and saved again and the warning disappeared. Solved the problem, but quite frustrating Before someone asks me, I restarted Jenkins after upgrading the plugin, so that's not the reason of this 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-43001) BlueOcean editor does not offer "save" without run
Title: Message Title Adrien Lecharpentier commented on JENKINS-43001 Re: BlueOcean editor does not offer "save" without run Even outside of Blue Ocean, when you create a MultiBranch Pipeline, once you saved the configuration, Jenkins will browse the SCM repository, discover the branches with Jenkinsfile and run a first build for those branches. This is the normal behavior. Are you describing the same behavior? Are you creating a simple Pipeline job or a MultiBranch Pipeline job (relying on Jenkinsfile)? 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-42933) NPE - Can't read property file
Title: Message Title Oleg Nenashev commented on JENKINS-42933 Re: NPE - Can't read property file Whatever you are trying to do, it won't work with this code. The pluginStratergy depends on the availability of the default constructor. In your case there is no such constructor, because you defined the parameterized one. The code line numbers in your stacktrace are not aligned with the provided class, hence I suppose you are building something different. I would start from insuring that all constructors are in place and that you have a valid pom.xml. Please also attach it 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-42933) NPE - Can't read property file
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42933 NPE - Can't read property file Change By: Oleg Nenashev Component/s: _unsorted Component/s: core 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-42933) NPE - Can't read property file
Title: Message Title
Loic Pelleau updated an issue
Jenkins / JENKINS-42933
NPE - Can't read property file
Change By:
Loic Pelleau
{code:java}java.lang.NullPointerExceptionat hudson.Plugin.getConfigXml(Plugin.java:289)at hudson.Plugin.load(Plugin.java:262)at com.my.package.Main.(Main.java:43)at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)at java.lang.reflect.Constructor.newInstance(Constructor.java:423)at java.lang.Class.newInstance(Class.java:442)at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:419)at hudson.PluginManager$2$1$1.run(PluginManager.java:405)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$8.runTask(Jenkins.java:925)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745){code}I extends the hudson.Plugin class. Hence, I have a plugin starting at startup.When executing `load()` method from Hudson.Plugin.`save()` method works. Line causing NPE in hudson.Plugin (l.289):{code:java}return new XmlFile(Jenkins.XSTREAM, new File(Jenkins.getInstance().getRootDir(),wrapper.getShortName()+".xml"));{code}Maybe a problem with the initialization of Jenkins.XSTREAM? class com.my.package.Main: {code:java}package com.my.package;import java.util.*;import java.util.logging.*;import java.io.*;import net.sf.json.*;import org.kohsuke.stapler.*;import hudson.*;import hudson.model.*;import hudson.model.queue.*;import hudson.model.Descriptor.FormException;import jenkins.model.*;public class Main extends Plugin {public boolean activated;public String job;public List packagesFilter;@DataBoundConstructorpublic Main(boolean activated, String job, List packagesFilter) {try {load();} catch (Exception e) {e.printStackTrace();}}public void configure(StaplerRequest req, JSONObject form) throws IOException, FormException {//... var instantiationsave();}public void start() throws Exception {load();}public void stop() {}public boolean getActivated() {return activated;}public String getJob() {return job;}public List getPackagesFilter() {return packagesFilter;}}{code}
[JIRA] (JENKINS-42933) NPE - Can't read property file
Title: Message Title Loic Pelleau commented on JENKINS-42933 Re: NPE - Can't read property file I understood my mistake. The code I showed you was not the one which was the problem. I called the `load()` method in the constructor (in this case just Main(), without parameters) instead of calling it in `start()`. 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-42933) NPE - Can't read property file
Title: Message Title Loic Pelleau closed an issue as Fixed Jenkins / JENKINS-42933 NPE - Can't read property file Change By: Loic Pelleau 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-42933) NPE - Can't read property file
Title: Message Title Loic Pelleau commented on JENKINS-42933 Re: NPE - Can't read property file However I can't see the values of my properties in the config page. They are not loaded in the jelly. Is it because of the constructor @DataBoundConstructor not called? 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-37717) CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Title: Message Title
Andy Wang commented on JENKINS-37717
Re: CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
I've read JENKINS-35367, but still don't get how to use {CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"} in pipeline. Is it right to put it in a template and use it? An example would be nice. Thank you!
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-42732) Unable to push file into slack with Slack file upload plugin
Title: Message Title Phani Kumar updated an issue Jenkins / JENKINS-42732 Unable to push file into slack with Slack file upload plugin Change By: Phani Kumar Attachment: Capture.PNG Attachment: Capture2.PNG Attachment: Capture3.PNG 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-42732) Unable to push file into slack with Slack file upload plugin
Title: Message Title Phani Kumar commented on JENKINS-42732 Re: Unable to push file into slack with Slack file upload plugin Hello Shitij Goyal , Please find attached for reference 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-40482) Support promoted-builds plugin
Title: Message Title Boguslaw Klimas commented on JENKINS-40482 Re: Support promoted-builds plugin Hi Ebrahim Moshaya I looked at this, but i don't understand, how git-parameter plugin would have supported 'Promoted Builds', I can support only those things which have definited url to git repository (directly or indirectly) . Could you describe something more 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-37717) CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Title: Message Title
David van Laatum updated an issue
Jenkins / JENKINS-37717
CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Change By:
David van Laatum
Following doesn't work in pipelineemailext body: '$ \ {CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"}', subject: 'Test email', to: 'user.em...@mycompany.com' It would be good to have this in place to get changeset from last successful build
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-37717) CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Title: Message Title
David van Laatum commented on JENKINS-37717
Re: CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
emailext body: '${CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"}', subject: 'Test email', to: 'user.em...@mycompany.com'
Should work
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-42933) NPE - Can't read property file
Title: Message Title Oleg Nenashev commented on JENKINS-42933 Re: NPE - Can't read property file Hi Loic Pelleau. The plugin extension point is not fully configurable itself (no descriptor). It is a low-level extension, which behaves slightly differently. It is possible to make global configuration via it (e.g. see https://github.com/jenkinsci/ownership-plugin/tree/master/src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPlugin.java and its resources: https://github.com/jenkinsci/ownership-plugin/tree/master/src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPlugin), but I am not sure this is the best approach in 2017. If you just need to specify Global settings in the Global Configuration or Global Security page, consider the GlobalConfiguration extension point: http://javadoc.jenkins-ci.org/jenkins/model/GlobalConfiguration.html 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-42961) Unable to see LoadRunner Controller during build execution
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-42961 Unable to see LoadRunner Controller during build execution Change By: Yafim Kazak Issue Type: Bug Story 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-42961) Unable to see LoadRunner Controller during build execution
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-42961 Unable to see LoadRunner Controller during build execution Change By: Yafim Kazak Priority: Critical Trivial 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-28075) Want to see the LoadRunner controller execute when runing from Jenkins
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-28075 Want to see the LoadRunner controller execute when runing from Jenkins Change By: Yafim Kazak Issue Type: Story New Feature 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-42961) Unable to compile the plugin
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-42961 Unable to compile the plugin Change By: Yafim Kazak Summary: Unable to see LoadRunner Controller during build execution compile the 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-28075) Show LoadRunner controller window while runing from Jenkins
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-28075 Show LoadRunner controller window while runing from Jenkins Change By: Yafim Kazak Summary: Want to see the Show LoadRunner controller execute when window while runing from Jenkins 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-28075) Show LoadRunner controller window while runing from Jenkins
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-28075 Show LoadRunner controller window while runing from Jenkins Change By: Yafim Kazak We upgraded Have an ability in the plugin Jenkins job to 3.0.7 for the HP LoadRunner and now we can't enable to see HPE LoadRunner controller window if checked in the Controller execute during a build configuration . Is there some setting we have misconfigured? 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Juri Strumpflohner commented on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder same here. We just upgraded to 2.32.3 a couple of days ago and now I have this issue. Didn't have it before, at least I did not notice anything. 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-42961) Unable to compile the plugin
Title: Message Title Yafim Kazak commented on JENKINS-42961 Re: Unable to compile the plugin Hi, I can't understand the issue from this screenshot. As long as you cloned our master branch from the repository - and changed only this line, it should work. You will need the *.hpi file - this is the file that's uploaded to Jenkins. If you supply any upload space, I will push the last build with this change (the hpi is bigger then allowed here). Please reach out at kazak [at] hpe [dot] com. On the feature - It's on our road plan but I can't commit on our next release. 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Juri Strumpflohner edited a comment on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder same here. We just upgraded to 2.32.3 a couple of days ago and now I have this issue. Didn't have it before, at least I did not notice anything. The question is, can I delete them safely? 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-42933) NPE - Can't read property file
Title: Message Title Loic Pelleau commented on JENKINS-42933 Re: NPE - Can't read property file I don't know if this extension point is appropriate: I need to do others tasks at startup (launch a thread), but I can see in the documentation "Convenient base class for extensions that contributes to the system configuration page but nothing else". 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-40482) Support promoted-builds plugin
Title: Message Title Ebrahim Moshaya updated an issue Jenkins / JENKINS-40482 Support promoted-builds plugin Change By: Ebrahim Moshaya Attachment: image-2017-03-23-11-13-37-285.png 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-40482) Support promoted-builds plugin
Title: Message Title Ebrahim Moshaya updated an issue Jenkins / JENKINS-40482 Support promoted-builds plugin Change By: Ebrahim Moshaya Attachment: image-2017-03-23-11-15-08-714.png 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-40482) Support promoted-builds plugin
Title: Message Title Ebrahim Moshaya commented on JENKINS-40482 Re: Support promoted-builds plugin Hi Boguslaw Klimas, Use case for supporting the promoted build plugin would be to promote git tags for several repositories for production deployments. For example: I have 5 repositories with Git Tags. I would have have one promotion with 5 x Git Parameters, one for each repository which I would then be able to list out all the tags for each repository and promote them for release to production. Is there any chance we can get the list of tags/branches from the "Use repository" field? The ssh keys are installed on the Jenkins machines but still the promotion shows blank when it lists out the tags/branches. If it really needs to fetch the credentials from the SCM configuration, could you not change it so that we can also override that and provide credentials through the git parameter 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-43063) Issue not getting created in GitHub
Title: Message Title Phani Kumar created an issue Jenkins / JENKINS-43063 Issue not getting created in GitHub Issue Type: Bug Assignee: Daniel Lo Nigro Attachments: Capture4.PNG, Capture5.PNG Components: github-issues-plugin Created: 2017/Mar/23 11:20 AM Environment: Production Priority: Trivial Reporter: Phani Kumar I just want to create an issue for my build failure in GitHub but I am getting No GitHub config available for this job, GitHub Issue Notifier will not run! Error: GitHub property not configured It would be a great help to me if I could get some help around this Add Comment
[JIRA] (JENKINS-43007) Missing update of plugin description
Title: Message Title Daniel Beck resolved as Fixed Fixed by https://github.com/jenkins-infra/jenkins-infra/pull/706 Jenkins / JENKINS-43007 Missing update of plugin description Change By: Daniel Beck Status: Open 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-42538) Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave
Title: Message Title Elliott Jones commented on JENKINS-42538 Re: Build Flow jobs stuck waiting on next available executor when using label parameter to restrict job to vpshere slave I also had this issue https://issues.jenkins-ci.org/browse/JENKINS-41384 and thus had to apply jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true 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-43057) Unable to access job parameter to select slave
Title: Message Title ikedam assigned an issue to Unassigned Rather sounds an issue of multijob-plugin. Jenkins / JENKINS-43057 Unable to access job parameter to select slave Change By: ikedam Component/s: multijob-plugin Component/s: groovy-label-assignment-plugin Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you
[JIRA] (JENKINS-43064) ec2computerlauncher needs instance status as well as state
Title: Message Title Alan Loughlin created an issue Jenkins / JENKINS-43064 ec2computerlauncher needs instance status as well as state Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2017/Mar/23 11:26 AM Priority: Minor Reporter: Alan Loughlin EC2ComputerLauncher only waits for aws to return a running state, which doesn't mean that the user-data has executed. The agent and init launcher execute before the instance status returns ok, which can mean that user-data hasn't executed yet. This means that by installing docker and adding user to docker group in user data could be run after the first open ssh session to the instance. So that session can not use docker. Alternative is to add a wait clause in EC2ComputerLauncher. but seems too hacky. http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/ec2/model/SummaryStatus.html Add Comment
[JIRA] (JENKINS-43057) Unable to access job parameter to select slave
Title: Message Title ikedam commented on JENKINS-43057 Re: Unable to access job parameter to select slave There're few documentations for miltijob plugin. I don't know how to use it, or how it works internally. 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-43034) Multibranch plugin has broken URL
Title: Message Title Mike Delaney updated an issue Jenkins / JENKINS-43034 Multibranch plugin has broken URL Change By: Mike Delaney Component/s: categorized-view-plugin Component/s: bitbucket-branch-source-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-43034) Multibranch plugin has broken URL
Title: Message Title Mike Delaney updated an issue Jenkins / JENKINS-43034 Multibranch plugin has broken URL Change By: Mike Delaney When using the Bitbucket Branch source plugin, the URL provided is broken unless you're at the Bitbucket project page; where you can ;look at the scan log and Bitbucket configuration.To reproduce this: * Setup Jenkins 2.5 ** Bitbucket Branch source plugin 2.1.1 * * Categorized View plugin 1.9; * Add a new view that uses the categorized view * Setup a new Bitbucket mutli - branch job * Observe the URL that is provided will result in a 404.- Mike D. 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Johan Svensson commented on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder Juri Strumpflohner, you probably have an old process running from the previous version. Close all jenkins processes including any old ones, remove all of the temp files and start it up. That's how I solved it and I'm pretty sure it's safe. 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-43065) Task Scanner Plugin - Ignore case broken
Title: Message Title Erik Newton created an issue Jenkins / JENKINS-43065 Task Scanner Plugin - Ignore case broken Issue Type: Bug Assignee: Ulli Hafner Components: tasks-plugin Created: 2017/Mar/23 11:40 AM Environment: Ubuntu Server LTS 2.32.3 Windows Build Client Task Scanner Plugin 4.50 Priority: Minor Reporter: Erik Newton A project with 'todo' lower case in the source code. Jenkins configured to scan for 'TODO' upper case but with 'Ignore case' option selected. On the project summary page, the graph indicates the correct number of TODO items. When you click on the graph to view the details, all the subsequent views are missing the lower case items. As a workaround, I entered 'TODO, todo' in the Task Tags field, but this would miss mixed case in the source. Add Comment
[JIRA] (JENKINS-43027) Force continue build execution on failure of previous build steps
Title: Message Title Naresh Gunda commented on JENKINS-43027 Re: Force continue build execution on failure of previous build steps NO i was not doing that, Now i'm able to mark build as unstable. Thanks a lot. 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-43066) With pipeline, tools does not setup properly the environment
Title: Message Title
Olivier Dupré created an issue
Jenkins / JENKINS-43066
With pipeline, tools does not setup properly the environment
Issue Type:
Bug
Assignee:
Unassigned
Components:
nodejs-plugin
Created:
2017/Mar/23 11:44 AM
Environment:
Running latest version of Jenkins on Docker, with all nodejs (4 to 7) installed in my Dockerfile. Using latest ndejs-plugin version.
Priority:
Major
Reporter:
Olivier Dupré
Hi, The `tools{nodejs 'xxx'}` and `tool name: 'xxx'` do not select the appropriate nodejs when there is several installations of nodejs. I made a full description on stackoverflow: http://stackoverflow.com/questions/42261382/jenkins-pipeline-select-nodejs-version-python-version Cheers, Olivier
Add Comment
[JIRA] (JENKINS-43067) Cannot create nodes from Cloud Configuration since Jenkins 2.51
Title: Message Title Cesar Tron-Lozai created an issue Jenkins / JENKINS-43067 Cannot create nodes from Cloud Configuration since Jenkins 2.51 Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/23 11:58 AM Labels: cloud node Priority: Blocker Reporter: Cesar Tron-Lozai Since I've upgraded to 2.51 I cannot build jobs running on Slave provided by my Cloud. I use the Amazon-ecs-plugin (https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Container+Service+Plugin) to generate Nodes on demand. It has been working for months. Now the builds get stuck at: Still waiting to schedule task Jenkins doesn’t have label docker I have a valid cloud configuration that provides Nodes for the label `Docker` Add Comment
[JIRA] (JENKINS-43027) Force continue build execution on failure of previous build steps
Title: Message Title wolfs closed an issue as Not A Defect Jenkins / JENKINS-43027 Force continue build execution on failure of previous build steps Change By: wolfs 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-43068) Result Page of findbugs plugin have wrong links
Title: Message Title Ronald Weg created an issue Jenkins / JENKINS-43068 Result Page of findbugs plugin have wrong links Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin Created: 2017/Mar/23 12:02 PM Environment: Jenkins 2.5.1 Findbugs 4.6.9 Priority: Minor Reporter: Ronald Weg When I look at the findbugs result page and click on types, I see the types and the count of the warnings of this type When I click to one type I expect to see only the findbugs warnings of this type, but the system shows the warning of all types again. The link shows to the path /findbugsResult/category.xxx/ but it shouöld show to/findbugsResult/type.xxx/ Add Comment
[JIRA] (JENKINS-38813) NullPointerException accessing params variable with Subversion tag
Title: Message Title
Jip Ver updated an issue
Jenkins / JENKINS-38813
NullPointerException accessing params variable with Subversion tag
Change By:
Jip Ver
Comment:
Hej there,I'm working on automating all the jenkins build and deploy jobs and pipelines. All of it works, except, that the pipeline does not seem to pick up the subversion tag. I've installed the latest version and dependent plugins of workflow-cps so my nullpointer exeption is gone now. But in stead of that the result of this input is now 'NULL': (so the svntag seems to be empty?) {code:java}// Pipeline script:node { def RELEASE_UNIT_NUMBER = params.RELEASE_UNIT_NUMBERecho "nummer: ${RELEASE_UNIT_NUMBER}"}{code}{code:java}// console outputStarted by user Jip[Pipeline] nodeRunning on master in D:\Apps\Jenkins2\workspace\912_SVNTAG_Parametrized_groovy_PIPELINE[Pipeline] {[Pipeline] echonummer: null[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{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...@goo
[JIRA] (JENKINS-42834) Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..."
Title: Message Title Reinhold Füreder commented on JENKINS-42834 Re: Sporadical log warnings "badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp..." Based on Sebastien's comment I re-checked in all the remaining old Jenkins logs and I am sorry for having to admit: these sporadical logs were really there before as well! The oldest log line is from 2017-12-14 The very first one and a single one in the very past: 2017-01-17 15:56:13 Then 25x on 2017-03-03 And the ones above in the issue description (Again I am not sure if that helps a lot...) 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-43068) Result Page of findbugs plugin has wrong links
Title: Message Title Ronald Weg updated an issue Jenkins / JENKINS-43068 Result Page of findbugs plugin has wrong links Change By: Ronald Weg Summary: Result Page of findbugs plugin have has wrong links 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-40456) First time builds are not reporting to Bitbucket
Title: Message Title
Adrian Carriger edited a comment on JENKINS-40456
Re: First time builds are not reporting to Bitbucket
Hi [~flagbit], thanks for the awesome plugin! I'm also experiencing the issue and have created a [minimal repo|https://bitbucket.org/dt-acarriger/bitbucket-build-status-notifier-plugin-issue/commits/branch/issue-example] to demonstrate what I'm experiencing.h1. Steps to reproduce # Create a mutlibranch Jenkins (v2.51) project with a [Jenkinsfile like this|https://bitbucket.org/dt-acarriger/bitbucket-build-status-notifier-plugin-issue/src/513089d10b7be34940347c3661f7eb88e05b5bd9/Jenkinsfile?at=master&fileviewer=file-view-default] ** This does [post to Bitbucket|https://bitbucket.org/dt-acarriger/bitbucket-build-status-notifier-plugin-issue/commits/branch/master] # Create a branch, publish it, make a commit ** This does not post to Bitbucket # Make another change on the branch ** This does post to Bitbucketh1. No Error MessageIn the Jenkins log for the build that does not post to Bitbucket there is no error message and there is no success message.h1. LogHere is the log for the build that does not post to BitbucketBranch indexing > git rev-parse --is-inside-work-tree # timeout=10Setting origin to g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git > git config remote.origin.url g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10using GIT_ASKPASS to set credentials Bitbucket Notify > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*Seen branch in repository origin/issue-exampleSeen branch in repository origin/masterSeen 2 remote branchesObtained Jenkinsfile from be3deb74d3c0f1f489c64e76827606ece518131b[Pipeline] nodeRunning on master in /Users/acarriger/.jenkins/workspace/tifier-plugin_issue-example-7CIO4G3WKWGDSZ73ZRBWZTTA265YQQSKAEKGOJOPCLK5RW635WYQ[Pipeline] \{[Pipeline] checkoutCloning the remote Git repositoryCloning repository g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git > git init /Users/acarriger/.jenkins/workspace/tifier-plugin_issue-example-7CIO4G3WKWGDSZ73ZRBWZTTA265YQQSKAEKGOJOPCLK5RW635WYQ # timeout=10Fetching upstream changes from g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git > git --version # timeout=10using GIT_ASKPASS to set credentials Bitbucket Notify > git fetch --tags --progress g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git # timeout=10Fetching upstream changes from g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.gitusing GIT_ASKPASS to set credentials Bitbucket Notify > git fetch --tags --progress g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git +refs/heads/*:refs/remotes/origin/*Checking out Revision be3deb74d3c0f1f489c64e76827606ece518131b (issue-example) > git config core.sparsecheckout # timeout=10 > git checkout -f be3deb74d3c0f1f489c64e76827606ece518131bFirst time build. Skipping changelog.[Pipeline] stage[Pipeline] \{ (test)[Pipeline] bitbucketStatusNotify[Pipeline] bitbucketStatusNotify[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCE
[JIRA] (JENKINS-26825) JobDSL plugin doesn't reset customWorkspace setting
Title: Message Title S H commented on JENKINS-26825 Re: JobDSL plugin doesn't reset customWorkspace setting Any progress on this 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-42575) GIT Parameter latest version plugin is not showing the revision numbers in dropdown list
Title: Message Title Boguslaw Klimas commented on JENKINS-42575 Re: GIT Parameter latest version plugin is not showing the revision numbers in dropdown list Hi, Maybe You have a big repository. When repository is a big plugin need more time to get and show revisions, especially when workspace is empty. Do you have set 'Branch' option in git-parameter configuration? 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-36765) Pipeline: Send notification "Back to normal" state
Title: Message Title
Jan Viktorin commented on JENKINS-36765
Re: Pipeline: Send notification "Back to normal" state
Hello, this code:
pipeline {
...
}
post {
success {
def previousResult = currentBuild.previousBuild?.result
if (previousResult && previousResult != currentBuild.result) {
emailext attachLog: true, to: "${env.MAINTAINERS}", subject: "Fixed: ${env.JOB_NAME} #${currentBuild.number}",
body: "See ${env.BUILD_URL} for details."
}
}
}
produces:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 44: Expected a step @ line 44, column 13.
def previousResult = currentBuild.previousBuild?.result
^
WorkflowScript: 45: Expected a step @ line 45, column 13.
if (previousResult && previousResult != currentBuild.result) {
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 Gro
[JIRA] (JENKINS-43069) NPE on exit - getEffectiveBrowser/getSwarm
Title: Message Title Ethan Thornburg created an issue Jenkins / JENKINS-43069 NPE on exit - getEffectiveBrowser/getSwarm Issue Type: Bug Assignee: Unassigned Attachments: image-2017-03-23-09-08-49-026.png, image-2017-03-23-09-10-11-536.png Components: p4-plugin Created: 2017/Mar/23 1:11 PM Environment: Jenkins 2.32.2 P4 Plugin 1.5.1 P4 Server Version: P4D/NTX64/2016.2/1487173 Windows 10 Labels: perforce p4-plugin NPE repositorybrowser Priority: Blocker Reporter: Ethan Thornburg I am getting an NPE on exit that is causing my build to fail. I am hoping it is misconfiguration, so the resolution will be simple. F:\Jenkins\jobs\Omniwar\workspace>exit 0 FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.p4.client.ConnectionHelper.getSwarm(ConnectionHelper.java:544) at org.jenkinsci.plugins.p4.PerforceScm.guessBrowser(PerforceScm.java:225) at hudson.scm.SCM.getEffectiveBrowser(SCM.java:146) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:911) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:879) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349) at hudso
[JIRA] (JENKINS-42508) Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public"
Title: Message Title Benjamin Manuel commented on JENKINS-42508 Re: Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public" Not sure if this applies at all to the original reporter, but I have seen the same issue when using a reverse proxy with OIDC authentication. We believe that some request at the end of the job is being blocked due to jenkins not being authenticated. Everything works properly if we turn off authentication, so we are fairly certain that the authentication is a factor. We are working on tracking down which request is happening on the external address to cause this. I will update here when we find anything. 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-39529) OutOfMemoryError when viewing and/or recording test results
Title: Message Title Ming Li commented on JENKINS-39529 Re: OutOfMemoryError when viewing and/or recording test results Have very similar issue.. Happens from time to time. Increasing heap memory does not help too much -Xmx4096m Any help? 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-43069) NPE on exit - getEffectiveBrowser/getSwarm
Title: Message Title
Ethan Thornburg updated an issue
Jenkins / JENKINS-43069
NPE on exit - getEffectiveBrowser/getSwarm
Change By:
Ethan Thornburg
I am getting an NPE on exit that is causing my build to fail. I am hoping it is misconfiguration, so the resolution will be simple. I am running the build via "Build Now". {code:java}F:\Jenkins\jobs\Omniwar\workspace>exit 0 FATAL: nulljava.lang.NullPointerException at org.jenkinsci.plugins.p4.client.ConnectionHelper.getSwarm(ConnectionHelper.java:544) at org.jenkinsci.plugins.p4.PerforceScm.guessBrowser(PerforceScm.java:225) at hudson.scm.SCM.getEffectiveBrowser(SCM.java:146) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:911) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:879) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1753) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE{code}It looks like it is looking for a browser and decides that that browser should be Swarm. I do not have any repo browser installed and the "Repository browser" setting is set to Auto. Full configuration can be found below.!image-2017-03-23-09-08-49-026.png! !image-2017-03-23-09-10-11-536.png!
Add Comment
This message was s
[JIRA] (JENKINS-20161) 500s when requesting /job/{jobname}/api/python w/ "run" parameter for nonexistent project
Title: Message Title
Daniel Beck commented on JENKINS-20161
Re: 500s when requesting /job/{jobname}/api/python w/ "run" parameter for nonexistent project
Vivek Pandey Jesse Glick I wonder whether https://github.com/stapler/stapler/pull/106 would (allow to) fix this?
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-42575) GIT Parameter latest version plugin is not showing the revision numbers in dropdown list
Title: Message Title gajendra mani tripathi commented on JENKINS-42575 Re: GIT Parameter latest version plugin is not showing the revision numbers in dropdown list Just few more information: Repository is not big (pretty small ) Revision number is coming in drop down but human can`t see it (but if you select it and print over console, you will be able to see it) if we downgrade this plugin the things are fine (but we lose some new updated feature) 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-39529) OutOfMemoryError when viewing and/or recording test results
Title: Message Title Ming Li updated an issue Jenkins / JENKINS-39529 OutOfMemoryError when viewing and/or recording test results Change By: Ming Li 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-43039) Blue Ocean Test Results fail to load over https
Title: Message Title Jonathan Brito commented on JENKINS-43039 Re: Blue Ocean Test Results fail to load over https Michael Neale the above link works as expected. It appears to be trying to load the json representation of the test results: https://jenkins.madmobile.com/blue/rest/organizations/jenkins/pipelines/Concierge/pipelines/Concierge%20Internal%20Build/runs/16/testReport/result/ James Dumay I will capture a log in a few minutes here. 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-43039) Blue Ocean Test Results fail to load over https
Title: Message Title Jonathan Brito updated an issue Jenkins / JENKINS-43039 Blue Ocean Test Results fail to load over https Change By: Jonathan Brito Attachment: jenkins.har 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-36935) java.lang.ClassNotFoundException: org.bouncycastle.openssl.PEMReader
Title: Message Title sébastien glon commented on JENKINS-36935 Re: java.lang.ClassNotFoundException: org.bouncycastle.openssl.PEMReader It's good for me on Jenkins 2.45 and ssh-agent 1.14 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-43070) Allow naming of parameter separators
Title: Message Title Adam Spiers created an issue Jenkins / JENKINS-43070 Allow naming of parameter separators Issue Type: Improvement Assignee: Unassigned Components: parameter-separator-plugin Created: 2017/Mar/23 1:51 PM Priority: Minor Reporter: Adam Spiers The parameter separator plugin is a very nice feature! Given that it's clearly intended for use in jobs which have a lot of parameters, I think it would be helpful if it was possible to give a name (i.e. a simple text string field) to each separator, which would be displayed immediately below the , effectively allowing each chunk of parameters to be given a section name. Add Comment
[JIRA] (JENKINS-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-40432 writeMavenPom throws class cast exception when creating a new pom file Change By: Jesse Glick Status: Open Resolved 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-43071) Overall/Administer permission seems to be required for linting
Title: Message Title
Wouter Hünd created an issue
Jenkins / JENKINS-43071
Overall/Administer permission seems to be required for linting
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Mar/23 2:07 PM
Environment:
Jenkins 2.23.3, Pipeline: Model Definition 1.1.1
Priority:
Minor
Reporter:
Wouter Hünd
It seems that the Overall/Administer permission is required to perform:
ssh -p ${JENKINS_PORT} ${USERNAME}@${JENKINS_HOST} declarative-linter < pipeline
Without this permission the following output is generated:
ERROR:${USERNAME} is missing the N/A/GenericRead permission
It seems there is no way to allow non-administrators to perform this action.
[JIRA] (JENKINS-43069) NPE on exit - getEffectiveBrowser/getSwarm
Title: Message Title
Ethan Thornburg updated an issue
Jenkins / JENKINS-43069
NPE on exit - getEffectiveBrowser/getSwarm
Change By:
Ethan Thornburg
I am getting an NPE on exit that is causing my build to fail. I am hoping it is misconfiguration, so the resolution will be simple. I am running the build via "Build Now".{code:java}F:\Jenkins\jobs\Omniwar\workspace>exit 0 FATAL: nulljava.lang.NullPointerException at org.jenkinsci.plugins.p4.client.ConnectionHelper.getSwarm(ConnectionHelper.java:544) at org.jenkinsci.plugins.p4.PerforceScm.guessBrowser(PerforceScm.java:225) at hudson.scm.SCM.getEffectiveBrowser(SCM.java:146) at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:911) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:879) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:349) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1753) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Finished: FAILURE{code}It looks like it is looking for a browser and decides that that browser should be Swarm. I do not have any repo browser installed (i.e. I'm not using Swarm, P4Web, etc.) and the "Repository browser" setting is set to Auto. Full configuration can be found below.!image-2017-03-23-09-08-49-026.png! !image-2017-03-23-09-10-11-536.png!
Add Comment
[JIRA] (JENKINS-42895) Pipeline stage view is not showing the stages visually
Title: Message Title Frédéric Meyrou commented on JENKINS-42895 Re: Pipeline stage view is not showing the stages visually HI, I have the same problem here. Config : Jenkins ver. 2.32.3 TLS + Windows Server 2012R2 + JDK 1.8 + Pipeline: Stage View Plugin Pipeline Stage View Plugin. 2.6 Pipeline: Job Defines a new job type for pipelines and provides their generic user interface. 2.10 _javascript_ GUI Lib: Handlebars bundle plugin _javascript_ GUI Lib: Handlebars bundle plugin. 1.1.1 _javascript_ GUI Lib: Moment.js bundle plugin _javascript_ GUI Lib: Moment.js bundle plugin. 1.1.1 Pipeline: REST API Plugin Provides a REST API to access pipeline and pipeline run data.
[JIRA] (JENKINS-43072) jenkinsci/jnlp not connecting to master
Title: Message Title KENNETH RITHVIK created an issue Jenkins / JENKINS-43072 jenkinsci/jnlp not connecting to master Issue Type: Bug Assignee: Carlos Sanchez Attachments: image-2017-03-23-19-38-45-101.png, image-2017-03-23-19-39-19-888.png Components: kubernetes-plugin Created: 2017/Mar/23 2:09 PM Priority: Minor Reporter: KENNETH RITHVIK the jnlp-slave cannot connect to the master. I sending the computer.jnlpmac and computer.name arguements to the container, but the computer.jnlpmac gets sent twice. Add Comment
[JIRA] (JENKINS-40096) Stage View is missing after Plugin update
Title: Message Title Frédéric Meyrou commented on JENKINS-40096 Re: Stage View is missing after Plugin update Please see my commment in https://issues.jenkins-ci.org/browse/JENKINS-42895 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-42931) Upload spec does not resolve placeholders in target path
Title: Message Title
Dima Nevelev commented on JENKINS-42931
Re: Upload spec does not resolve placeholders in target path
Unfortunately we were unable to reproduce this issue. Please provide us through Github an example of a Jenkinsfile which reproduces the problem. The script we used:
node("remote") {
def server = Artifactory.server 'localhost-8081-admin-password'
def downloadSpec = """{
"files": [
{
"pattern": "CliTestsSpec/*/gerrit-acceptance-framework-2.12.1.jar",
"target": "local/com/google/gerrit/gerrit-acceptance-framework/2.12.1-SNAPSHOT/gerrit-acceptance/gerrit-acceptance-framework-2.12.1.jar",
"recursive": "true",
"flat": "true"
}
]
}"""
def uploadSpec = """{
"files": [
{
"pattern": "local/${organization}/${moduleName}/(.*?)/(.*?)/(.*?)-SNAPSHOT/(.*?)/(.*?).jar",
"regexp" : true,
"target": "${repositoryName}/${organization}/${moduleName}/{1}/{2}/{3}/{4}/{5}.jar"
}
]
}"""
def buildInfo2 = server.download spec: downloadSpec
def buildInfo1 = server.upload spec: uploadSpec
buildInfo1.append buildInfo2
server.publishBuildInfo buildInfo1
}
The log output:
Started by user admin
[Pipeline] node
Running on a in /Users/diman/sandbox/jenkins-agent-home-service/workspace/JENKINS-42931
[Pipeline] {
[Pipeline] getArtifactoryServer
[Pipeline] artifactoryDownload
Beginning to resolve Build Info published dependencies.
The file '/Users/diman/sandbox/jenkins-agent-home-service/workspace/JENKINS-42931/local/com/google/gerrit/gerrit-acceptance-framework/2.12.1-SNAPSHOT/gerrit-acceptance/gerrit-acceptance-framework-2.12.1.jar' exists locally.
Finished resolving Build Info published dependencies.
[Pipeline] artifactoryUpload
For pattern: local/com/google/(.*?)/(.*?)/(.*?)-SNAPSHOT/(.*?)/(.*?).jar 1 artifacts were found.
Deploying artifact: http://localhost:8081/artifactory/aql-a1/com/google/gerrit/gerrit-acceptance-framework/2.12.1/gerrit-acceptance/gerrit-acceptance-framework-2.12.1.jar
[Pipeline] publishBuildInfo
Deploying build info to: http://localhost:8081/artifactory/api/build
Build successfully deployed. Browse it in Artifactory under http://localhost:8081/artifactory/webapp/builds/JENKINS-42931/4
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
Add Comment
[JIRA] (JENKINS-42575) GIT Parameter latest version plugin is not showing the revision numbers in dropdown list
Title: Message Title Boguslaw Klimas commented on JENKINS-42575 Re: GIT Parameter latest version plugin is not showing the revision numbers in dropdown list Could you add jenkins.log and console log from web browser? (or some screenshot) 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-43055) "List of flow heads unset for CpsFlowExecution[null]" Warning
Title: Message Title Kenny N commented on JENKINS-43055 Re: "List of flow heads unset for CpsFlowExecution[null]" Warning Jesse Glick - If there's extra logging information that I can add to this to make it easier to reproduce or debug, let me know. Currently, our build system is unstable and freezes up on seemingly minor build steps. 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.
