[JIRA] (JENKINS-37902) Summary Display Plugin Does not Expand Variables used in "Files to parse"
Title: Message Title
Philippe Nobili updated an issue
Jenkins / JENKINS-37902
Summary Display Plugin Does not Expand Variables used in "Files to parse"
Change By:
Philippe Nobili
It seems that variables are not expanded in the "Files to parse" field which limits the use of the plugin in some cases. E.g. the following doesn't work:{code}Files to parse = somepath / my/path/ ${AVAR}/*.xml{code}Sorry if I missed it.Cheers,Phil.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed
Title: Message Title James Dumay commented on JENKINS-37921 Re: SSE failures and deadlocking with github auth plugin installed This should prevent the thread starvation https://github.com/jenkinsci/sse-gateway-plugin/pull/8 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title sergio costa commented on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC Hello, I think that is not the same issue, because Lance says that it gives error after 3rd attempt but in my case never worked before, not even once. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title Roy Lu commented on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC Can you still reproduce it? Have you try confirm the user permission? Or try the latest version? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-37921
SSE failures and deadlocking with github auth plugin installed
Change By:
Michael Neale
When running blue ocean with github auth enabled, SSE events often don't arrive when running in mvn hpi:run mode. Jenkins can "lock up" (all web threads busy) and blocking SSE threads were noted in a thread dump.This hasn't been observed running in the wild (eg on dogfood), but is worth investigation as it is a bit of a DOS problem if it is "real". To reproduce: run blueocean via mvn hpi:runSetup brand new workspaceInstall github authorization plugin https://wiki.jenkins-ci.org/display/JENKINS/GitHub+OAuth+PluginFollow its instructions for setting up an app and callbackCreate a pipeline (simple one will do, anything really, a few shell steps)Run the pipeline a few times from blue ocean - notice SSE events will not arriveKeep clicking around.When the dashboard looks "broken" or it stops responding, try to go to the classic UI and you will see it is waiting on a socket. It is at this point I took a thread dump. Thread dump that showed blocking SSE threads: {noformat}"Handling POST /jenkins/sse-gateway/configure from 0:0:0:0:0:0:0:1 : qtp1780682194-650" #650 prio=5 os_prio=31 tid=0x7fec9106a800 nid=0xac4b waiting for monitor entry [0x73dcd000] java.lang.Thread.State: BLOCKED (on object monitor) at org.jenkinsci.plugins.ssegateway.Endpoint.doConfigure(Endpoint.java:165) - waiting to lock <0x0007b5b05cd8> (a java.lang.String) at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) 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$11.dispatch(MetaClass.java:380) 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$SSEListe
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37921 SSE failures and deadlocking with github auth plugin installed (needs investigation) Change By: Michael Neale Summary: SSE failures and deadlocking with github auth plugin installed (needs investigation) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed
Title: Message Title Michael Neale commented on JENKINS-37921 Re: SSE failures and deadlocking with github auth plugin installed I think this is worth investigating, including james proposed fixes (alarming for a product manager to pick up concurrent code but here we are !). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed
Title: Message Title Michael Neale stopped work on JENKINS-37921 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed
Title: Message Title Michael Neale started work on JENKINS-37921 Change By: Michael Neale Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-37921 SSE failures and deadlocking with github auth plugin installed (needs investigation) Change By: Michael Neale Assignee: Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37921 SSE failures and deadlocking with github auth plugin installed (needs investigation) Change By: Michael Neale Sprint: 1.0-beta-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title Michael Neale edited a comment on JENKINS-37921 Re: SSE failures and deadlocking with github auth plugin installed (needs investigation) [~tfennelly] I think this is worth investigating, including james proposed fixes (alarming for a product manager to pick up concurrent code but here we are !). This hasn't been seen "in the wild" but myself and Ivan can reliably reproduce this. I took a thread dump to see what was locking things up. Currently only impacting when github oauth plugin is installed (and only in some cases) but it may highlight some underlying issue that may bite hard. Its only marked as important as this does stop you from accessing classic for a while (it does seem to get unblocked eventually). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-37921
SSE failures and deadlocking with github auth plugin installed (needs investigation)
Change By:
Michael Neale
When running blue ocean with github auth enabled, SSE events often don't arrive when running in mvn hpi:run mode. Jenkins can "lock up" (all web threads busy) and blocking SSE threads were noted in a thread dump.This hasn't been observed running in the wild (eg on dogfood), but is worth investigation as it is a bit of a DOS problem if it is "real". To reproduce: run blueocean via mvn hpi:runSetup brand new workspaceInstall github authorization plugin https://wiki.jenkins-ci.org/display/JENKINS/GitHub+OAuth+PluginFollow its instructions for setting up an app and callbackCreate a pipeline (simple one will do, anything really, a few shell steps)Run the pipeline a few times from blue ocean - notice SSE events will not arriveKeep clicking around. (see video link above for what I do to see this). When the dashboard looks "broken" or it stops responding, try to go to the classic UI and you will see it is waiting on a socket. It is at this point I took a thread dump. Thread dump that showed blocking SSE threads: {noformat}"Handling POST /jenkins/sse-gateway/configure from 0:0:0:0:0:0:0:1 : qtp1780682194-650" #650 prio=5 os_prio=31 tid=0x7fec9106a800 nid=0xac4b waiting for monitor entry [0x73dcd000] java.lang.Thread.State: BLOCKED (on object monitor) at org.jenkinsci.plugins.ssegateway.Endpoint.doConfigure(Endpoint.java:165) - waiting to lock <0x0007b5b05cd8> (a java.lang.String) at sun.reflect.GeneratedMethodAccessor211.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) 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$11.dispatch(MetaClass.java:380) 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(PluginSer
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37921 SSE failures and deadlocking with github auth plugin installed (needs investigation) Change By: Michael Neale Sprint: 1.0-beta- 2 1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37368) Serious performances issues caused by DownstreamPassCondition RunListener
Title: Message Title Arnaud Héritier commented on JENKINS-37368 Re: Serious performances issues caused by DownstreamPassCondition RunListener Oleg Nenashev are you maintaining this plugin to be the assignee or are you proposing yourself to help us on it ? Maybe with Allan we could help to propose a PR if you can guide us ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37368) Serious performances issues caused by DownstreamPassCondition RunListener
Title: Message Title Arnaud Héritier edited a comment on JENKINS-37368 Re: Serious performances issues caused by DownstreamPassCondition RunListener [~oleg_nenashev] are you maintaining this plugin to be the assignee or are you proposing yourself to help us on it ?Maybe with Allan [~allan_burdajewicz] we could help to propose a PR if you can guide us ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33201) Java JSON exception with an empty parametrized build.
Title: Message Title Oleg Nenashev commented on JENKINS-33201 Re: Java JSON exception with an empty parametrized build. Goutham Nithyananda I'm not sure what you're asking about, but it's definitely better to continue discussion in jenkinsci-dev ML instead of the closed ticket. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title Michael Neale commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks I see that Andrew has moved pipeline config to using them - so does that mean it has been released? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37917) Review permissions API for multi-branch pipeline
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37917 Review permissions API for multi-branch pipeline Change By: Michael Neale Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37763) Ad number of "queued" and "running" jobs as properties to Pipeline object
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37763 Ad number of "queued" and "running" jobs as properties to Pipeline object Change By: Michael Neale Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title Michael Neale edited a comment on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks I see that Andrew has moved pipeline config to using them - so does that mean it has been released?Also a question, if some steps are in stage blocks, and some outside, how does that look? (in clasic script). cc [~jamesdumay] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title Michael Neale edited a comment on JENKINS-37921 Re: SSE failures and deadlocking with github auth plugin installed (needs investigation) [~tfennelly] I think this is worth investigating, including james proposed fixes (alarming for a product manager to pick up concurrent code but here we are !). This hasn't been seen "in the wild" but myself and Ivan can reliably reproduce this. I took a thread dump to see what was locking things up. Currently only impacting when github oauth plugin is installed (and only in some cases) but it may highlight some underlying issue that may bite hard. Its only marked as important as this does stop you from accessing classic for a while (it does seem to get unblocked eventually). If this isn't as serious as it looks, can bump down the priority. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37368) Serious performances issues caused by DownstreamPassCondition RunListener
Title: Message Title Oleg Nenashev commented on JENKINS-37368 Re: Serious performances issues caused by DownstreamPassCondition RunListener Arnaud Héritier I kinda maintain it, but unfortunately I do not have much personal time for plugins. Too many TODOs in other areas. No chance to get anything fixed in this plugin by the end of September. Ownership of this plugin was a kind of the assignment by my employer, so you can follow-up with PMs if you want to get a short-term resolution. If you create a PR, I'll do my best to review and integrate it ASAP Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35432) Scheduled builds crash after running for more than 8 hours
Title: Message Title Mikael Norée commented on JENKINS-35432 Re: Scheduled builds crash after running for more than 8 hours I have the same problem using Jenkins 2.20 and TFS-plugin 5.1.0. After a 2-3 days all jobs start failing with same message in output. Fixed by restarting Jenkins service on the windows server. 15:31:06 FATAL: null 15:31:06 java.lang.StackOverflowError 15:31:06 at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:295) 15:31:06 at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304) 15:31:06 at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304) 15:31:06 at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304) ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Florian Miedniak commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job We would also very, very appreciate seeing this solved: Currently we're having several more or less awkward workarounds for this: Let the jenkins job get the necessary info from a properties file, which is either located in the jobs' workspace or inside a version control system "Ask" the user by sending an email and parse the reply Note: Yes, there now is the workflow plugin, which admittetly makes the construction of pipelines much more easier and already allows for entering parameters on manual approval steps. But waiting for user input results in the pipeline job to be keep "running", which feels (at least IMO) not very well, especially if the manual approval takes a long time (days or even weeks) ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Torsten Kleiber commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job That is the same reason why I don't have switched to pipeline (formerly workflow) plugin. Please vote for the corresponding Issue: https://issues.jenkins-ci.org/browse/JENKINS-37515 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37515) pipeline input blocks the executor
Title: Message Title Kanstantsin Shautsou commented on JENKINS-37515 Re: pipeline input blocks the executor I think the issue will be with workspace. Executor will hold workspace that may be needed for continuation after input. Some adittional non-blocking input maybe needs to be created? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Florian Miedniak commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job @Torsten Kleiber: Great to hear, others are dealing with the same problems Do you have any workaround found for the "stalling pipeline issue"? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title Torsten Kleiber commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job Unfortunatly not. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37920) DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener
Title: Message Title Kirill Merkushev commented on JENKINS-37920 Re: DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener GitHubWebHook.Listener is a deprecated extension point and not recommended to use. It exists only for backward compatibility. If you want to receive more events and payload, then you should extend this class: https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/extension/GHEventsSubscriber.java The working example is DefaultPushGHEventSubscriber and https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/PingGHEventSubscriber.java One more example can be found here: https://github.com/KostyaSha/github-integration-plugin/blob/master/github-pullrequest-plugin/src/main/java/org/jenkinsci/plugins/github/pullrequest/webhook/GHPullRequestSubscriber.java Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37920) DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener
Title: Message Title Kirill Merkushev closed an issue as Done Jenkins / JENKINS-37920 DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener Change By: Kirill Merkushev Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37582) Stacktrace when creating Users/Group
Title: Message Title Andreas Daubner commented on JENKINS-37582 Re: Stacktrace when creating Users/Group I have the same issue here. It happens everytime I create a new group for the RBAC Enterprise plugin. I can create a group, the error appears. After that I can assign a role and everything looks good, but the role has no (or at least limited) effect. E.g. I can create new jobs but cannot read a template from a higher folder level. Also jobs created from a template cannot be modified by users in these groups. I can reproduce the issue on my test server as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37895) Option to "skip" a locked section if a newer build already completed it
Title: Message Title Roman Baeriswyl commented on JENKINS-37895 Re: Option to "skip" a locked section if a newer build already completed it Regarding the documentation, the concurrency property of a Stage (which is now deprecated) could exactly do this: The stage command lets you mark certain sections of a build as being constrained by limited concurrency (or, later, unconstrained). Newer builds are always given priority when entering such a throttled stage; older builds will simply exit early if they are preëmpted. This really is now a missing feature for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31683) p4-plugin out of memory with large depots on 32 bit java
Title: Message Title Paul Allen commented on JENKINS-31683 Re: p4-plugin out of memory with large depots on 32 bit java Thank you for checking again, there was nothing specific in 1.4.6 release for the memory issue. We have a reproduction case here and it seems to be something in the p4java API, we are investigating and will let you know what we find. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37895) Option to "skip" a locked section if a newer build already completed it
Title: Message Title Roman Baeriswyl commented on JENKINS-37895 Re: Option to "skip" a locked section if a newer build already completed it Just found out that this should be possible to achieve with the milestone step. Hopefully that will get released soon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36660 Re: Acceptance tests for nested project and funky branch name regressions Code changed in jenkins User: Thorsten Scherler Path: package.json src/main/js/api/git.js src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/blueocean/bluePipelineBranch.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/main/js/page_objects/blueocean/bluePipelines.js src/main/js/page_objects/classic_jenkins/computer.js src/main/js/page_objects/classic_jenkins/folderCreate.js src/main/js/page_objects/classic_jenkins/jobUtils.js src/main/js/page_objects/classic_jenkins/multibranchCreate.js src/main/js/page_objects/classic_jenkins/pipeline.js src/main/js/util/url.js src/test/java/io/jenkins/blueocean/EdgeCasesTest.java src/test/java/io/jenkins/blueocean/QueuedTest.java src/test/js/edgeCases/folder.js src/test/js/log-karaoke/freestyle.js src/test/js/log-karaoke/noStages.js src/test/js/log-karaoke/stages.js src/test/js/queued.js src/test/js/smoke.js src/test/resources/multibranch_1/Jenkinsfile src/test/resources/multibranch_1/TEST-failure.TestThisWillFailAbunch.xml src/test/resources/multibranch_1/TEST-failure.TestThisWontFail.xml http://jenkins-ci.org/commit/blueocean-acceptance-test/ebad36c457146cba0fbf822875df39659e6520fc Log: [FIX JENKINS-36660] WIP Acceptance tests for nested project and funky branch name regressions (#26) Added git api for creating local git repos for testing stash JENKINS-36660 WIP implementing creation of folder and a freestyle project within the nested path. JENKINS-36660 WIP remove obsolete variable JENKINS-36660 WIP waiting for ever when uncommenting, seems that sse is not getting informed JENKINS-36660 Add tests for JENKINS-36618 JENKINS-36660 Extending multibranch AT implementing creation of job JENKINS-36660 Add fixme note so tom knows where the problems lies JENKINS-36660 first working version of creating multibranch in folders J
[JIRA] (JENKINS-36618) jobs can have the same name in different folders, but ui only shows one of them
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36618 Re: jobs can have the same name in different folders, but ui only shows one of them Code changed in jenkins User: Thorsten Scherler Path: package.json src/main/js/api/git.js src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/blueocean/bluePipelineBranch.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/main/js/page_objects/blueocean/bluePipelines.js src/main/js/page_objects/classic_jenkins/computer.js src/main/js/page_objects/classic_jenkins/folderCreate.js src/main/js/page_objects/classic_jenkins/jobUtils.js src/main/js/page_objects/classic_jenkins/multibranchCreate.js src/main/js/page_objects/classic_jenkins/pipeline.js src/main/js/util/url.js src/test/java/io/jenkins/blueocean/EdgeCasesTest.java src/test/java/io/jenkins/blueocean/QueuedTest.java src/test/js/edgeCases/folder.js src/test/js/log-karaoke/freestyle.js src/test/js/log-karaoke/noStages.js src/test/js/log-karaoke/stages.js src/test/js/queued.js src/test/js/smoke.js src/test/resources/multibranch_1/Jenkinsfile src/test/resources/multibranch_1/TEST-failure.TestThisWillFailAbunch.xml src/test/resources/multibranch_1/TEST-failure.TestThisWontFail.xml http://jenkins-ci.org/commit/blueocean-acceptance-test/ebad36c457146cba0fbf822875df39659e6520fc Log: [FIX JENKINS-36660] WIP Acceptance tests for nested project and funky branch name regressions (#26) Added git api for creating local git repos for testing stash JENKINS-36660 WIP implementing creation of folder and a freestyle project within the nested path. JENKINS-36660 WIP remove obsolete variable JENKINS-36660 WIP waiting for ever when uncommenting, seems that sse is not getting informed JENKINS-36660 Add tests for JENKINS-36618 JENKINS-36660 Extending multibranch AT implementing creation of job JENKINS-36660 Add fixme note so tom knows where the problems lies JENKINS-36660 first working version of creating multibranch in folders
[JIRA] (JENKINS-37922) PROMOTED_TIMESTAMP doesn't expose timestamp of the promoted build
Title: Message Title Balthasar Nebel created an issue Jenkins / JENKINS-37922 PROMOTED_TIMESTAMP doesn't expose timestamp of the promoted build Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2016/Sep/02 9:38 AM Environment: Jenkins v2.7.2, promoted builds plugin v2.27 Priority: Major Reporter: Balthasar Nebel According to JENKINS-32993 the PROMOTED_TIMESTAMP variable should expose the timestamp of the promoted build, but now it has the timestamp of the promotion time. Add Comment
[JIRA] (JENKINS-35847) Developer should see a condensed version of the change summary
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35847 Re: Developer should see a condensed version of the change summary Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js http://jenkins-ci.org/commit/blueocean-acceptance-test/97e9bd70c6f7807266b823c24fab5f15d7133416 Log: Merge remote-tracking branch 'origin/master' into JENKINS-35847 Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/d8528c200f68...97e9bd70c6f7 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36177) Acceptance test for Multi-Branch flow
Title: Message Title Thorsten Scherler updated JENKINS-36177 Jenkins / JENKINS-36177 Acceptance test for Multi-Branch flow Change By: Thorsten Scherler Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title Thorsten Scherler updated JENKINS-36660 Jenkins / JENKINS-36660 Acceptance tests for nested project and funky branch name regressions Change By: Thorsten Scherler Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35847) Developer should see a condensed version of the change summary
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35847 Re: Developer should see a condensed version of the change summary Code changed in jenkins User: Thorsten Scherler Path: package.json src/main/js/api/git.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/edgeCases/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/b587c8baea42c97ae32e13fbc02662a3ab20bac7 Log: FIX Jenkins-35847 (#28) Added git api for creating local git repos for testing stash JENKINS-36660 WIP implementing creation of folder and a freestyle project within the nested path. JENKINS-36660 WIP remove obsolete variable JENKINS-36660 WIP waiting for ever when uncommenting, seems that sse is not getting informed JENKINS-36660 Add tests for JENKINS-36618 JENKINS-36660 Extending multibranch AT implementing creation of job JENKINS-36660 Add fixme note so tom knows where the problems lies JENKINS-36660 first working version of creating multibranch in folders JENKINS-36660 fix class name JENKINS-36660 add more test to cover various regressions. The close modal test is breaking my balls though since the opener url is equal to the current location but only in AT. JENKINS-36660 Implement regression testing for all tabs when they should show data. Add commit script for the git repo. JENKINS-36660 remove legacy folder
[JIRA] (JENKINS-36660) Acceptance tests for nested project and funky branch name regressions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36660 Re: Acceptance tests for nested project and funky branch name regressions Code changed in jenkins User: Thorsten Scherler Path: package.json src/main/js/api/git.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/edgeCases/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/b587c8baea42c97ae32e13fbc02662a3ab20bac7 Log: FIX Jenkins-35847 (#28) Added git api for creating local git repos for testing stash JENKINS-36660 WIP implementing creation of folder and a freestyle project within the nested path. JENKINS-36660 WIP remove obsolete variable JENKINS-36660 WIP waiting for ever when uncommenting, seems that sse is not getting informed JENKINS-36660 Add tests for JENKINS-36618 JENKINS-36660 Extending multibranch AT implementing creation of job JENKINS-36660 Add fixme note so tom knows where the problems lies JENKINS-36660 first working version of creating multibranch in folders JENKINS-36660 fix class name JENKINS-36660 add more test to cover various regressions. The close modal test is breaking my balls though since the opener url is equal to the current location but only in AT. JENKINS-36660 Implement regression testing for all tabs when they should show data. Add commit script for the git repo. JENKINS-36660 remove legacy folder
[JIRA] (JENKINS-35847) Developer should see a condensed version of the change summary
Title: Message Title Thorsten Scherler updated JENKINS-35847 Jenkins / JENKINS-35847 Developer should see a condensed version of the change summary Change By: Thorsten Scherler Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36618) jobs can have the same name in different folders, but ui only shows one of them
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36618 Re: jobs can have the same name in different folders, but ui only shows one of them Code changed in jenkins User: Thorsten Scherler Path: package.json src/main/js/api/git.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/edgeCases/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/b587c8baea42c97ae32e13fbc02662a3ab20bac7 Log: FIX Jenkins-35847 (#28) Added git api for creating local git repos for testing stash JENKINS-36660 WIP implementing creation of folder and a freestyle project within the nested path. JENKINS-36660 WIP remove obsolete variable JENKINS-36660 WIP waiting for ever when uncommenting, seems that sse is not getting informed JENKINS-36660 Add tests for JENKINS-36618 JENKINS-36660 Extending multibranch AT implementing creation of job JENKINS-36660 Add fixme note so tom knows where the problems lies JENKINS-36660 first working version of creating multibranch in folders JENKINS-36660 fix class name JENKINS-36660 add more test to cover various regressions. The close modal test is breaking my balls though since the opener url is equal to the current location but only in AT. JENKINS-36660 Implement regression testing for all tabs when they should show data. Add commit script for the git repo. JENKINS-36660 remove legacy folder
[JIRA] (JENKINS-37182) Can't connect to a working svn server with username and password
Title: Message Title julien etienne commented on JENKINS-37182 Re: Can't connect to a working svn server with username and password same problem with jenkins 1.642.4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37923) Hot swap while debugging
Title: Message Title Joachim Nilsson created an issue Jenkins / JENKINS-37923 Hot swap while debugging Issue Type: New Feature Assignee: Daniel Spilker Components: gradle-jpi-plugin Created: 2016/Sep/02 10:43 AM Priority: Major Reporter: Joachim Nilsson Running debug with Maven supports hot swap of code. I would like to see this feature also for Gradle builds. It may be possible to explore the Gradle continuous builds feature for this purpose https://docs.gradle.org/current/userguide/continuous_build.html. That would possibly mean that the server must be spawned as an external java process, which also gives opportunity to set debug flags and port as parameter or configuration inside the build script instead of GRADLE_OPTS before starting Gradle. Add Comment
[JIRA] (JENKINS-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-37914 Many Times JENKINS_HOME is Invalid Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37914 Many Times JENKINS_HOME is Invalid Change By: Mark Waite Component/s: gitlab-hook-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37831) Favoriting on Matrix style project broken
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-37831 Favoriting on Matrix style project broken Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37920) DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener
Title: Message Title Dominic Scheirlinck commented on JENKINS-37920 Re: DefaultPushGHEventSubscriber does not pass important details of the webhook to GitHubWebHook.Listener Thank you very much for the hints. I'll have a go at implementing the better extension point. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title Mark Waite resolved as Cannot Reproduce I'm unable to reproduce the bug. Can you provide detailed instructions to duplicate the bug in an environment which is accessible to me? I created the JENKINS-37914 branch in my [jenkins-bugs repository|], and added a Jenkinsfile to verify the output is as expected. I used the multi-branch jenkins-bugs job in my docker instance to run that job. It worked as I expected, consistently showing the correct working directory. I checked several variations while exploring the problem included running an ant script, running a shell script, using a hard coded value for JENKINS_HOME, and using an environment variable reference for the value of JENKINS_HOME. Jenkins / JENKINS-37914 Many Times JENKINS_HOME is Invalid Change By: Mark Waite Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37914) Many Times JENKINS_HOME is Invalid
Title: Message Title Mark Waite edited a comment on JENKINS-37914 Re: Many Times JENKINS_HOME is Invalid I'm unable to reproduce the bug. Can you provide detailed instructions to duplicate the bug in an environment which is accessible to me?I created the [JENKINS-37914 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37914] in my [jenkins-bugs repository| https://github.com/MarkEWaite/jenkins-bugs ], and added a [Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-37914/Jenkinsfile] to verify the output is as expected. I used the multi-branch jenkins-bugs job in my [docker instance|https://github.com/MarkEWaite/docker/tree/lts-with-plugins] to run that job. It worked as I expected, consistently showing the correct working directory.I checked several variations while exploring the problem included running an ant script, running a shell script, using a hard coded value for JENKINS_HOME, and using an environment variable reference for the value of JENKINS_HOME. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23865) Jenkins Jobs Hanging while running junit tests
Title: Message Title pankaj bisht commented on JENKINS-23865 Re: Jenkins Jobs Hanging while running junit tests @George Kraft : Could you please provide following info : which Fedora and Jenkins version you are using ? You have used Fedora machine only for Master Jenkins or slave VMs as well? Thanks in advance. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37894) Unmarshall error when provisoning instance
Title: Message Title Rafael Ximenes updated an issue Jenkins / JENKINS-37894 Unmarshall error when provisoning instance Change By: Rafael Ximenes Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37899) Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance
Title: Message Title Mark Waite commented on JENKINS-37899 Re: Git client does not call CredentialsProvider.snapshot() when adding credentials to a SmartCredentialsProvider that will be used on a remote instance Thanks for the insight. Passphrase protected private keys in the git plugin have been a source of puzzlement to me for a very long time. There are several bug reports that they don't work in various ways. Oddly, I have a docker instance which I run in two very different environments where passphrase protected private keys work on slaves, but don't work on the master (of that docker instance). I've spent time creating various intentionally interesting ssh passphrases (trivial characters, interesting special characters, etc.), yet still haven't understood the failure cases well enough. I can't explain why my passphrase protected slave cases work, since I think they are the precise case you're describing should fail. I'll investigate further while evaluating git client PR207 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37854) Docker Build and Publish not building
Title: Message Title Evanilson Abril commented on JENKINS-37854 Re: Docker Build and Publish not building Are u able to help or not ? I need to update my products Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37924) Job Import fail with HTTP 403
Title: Message Title Santosh Duddelli created an issue Jenkins / JENKINS-37924 Job Import fail with HTTP 403 Issue Type: Bug Assignee: Unassigned Attachments: Jenkins-Job-Import-Issue.JPG Components: job-import-plugin Created: 2016/Sep/02 12:21 PM Priority: Critical Reporter: Santosh Duddelli I am trying to import jenkins job from an instance running on Jenkins 1.651 running on Ubuntu OS to Jenkins 2.7.2 running on windows 10 The import job fail with error message DataIntegrity FAILED - Server returned HTTP response code: 403 for URL: http://jenkins.hyd.mangstor.com:8080/job/DataIntegrity//config.xml Please let me know how to fix the issue Even the import job failed from Ubuntu instance to another ubuntu instance Add Comment
[JIRA] (JENKINS-37925) Show full log only shows 10000 lines
Title: Message Title James Sharpe created an issue Jenkins / JENKINS-37925 Show full log only shows 1 lines Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/02 12:24 PM Priority: Minor Reporter: James Sharpe If the log is longer than 10,000 lines then the show complete log button at the top of the live output only shows the first 10,000 lines. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35310) ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it
Title: Message Title Jostein Gogstad commented on JENKINS-35310 Re: ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it Authentication tokens doesn't work, as Jesse pointed out. The following endpoints works for triggering indexing and builds in multibranch projects: curl -isk -u gitlab:5d7b834xxx6c1e0c9f3 -X POST https://myjenkins.internal.com/job/my_multibranch_job/job/Branches/build HTTP/1.1 302 Found ... It gives 302, but it both indexes and trigger builds on branches with new commits. Since the authentication token doesn't work, you'll have to use an user level authentication token and use it as password in a BASIC authentication scheme, you'll find the user authentication token under https://myjenkins.internal.com/user/USERNAME/configure (press "Show token"). If your SCM-vendor doesn't support explicitly specifying BASIC credentials (gitlab has no configuration for this), you can embed it in the url. Our push hook in GitLab is https://gitlab:5d7b834xxx6c1e0c...@myjenkins.internal.com/job/my_multibranch_job/job/Branches/build Finally if you want to trigger build on specific branches in a multibranch pipeline, they can be triggered as such curl -isk -u gitlab:5d7b834xxx6c1e0c9f3 -X POST https://myjenkins.internal.com/job/my_multibranch_job/job/Branches/job/develop/build HTTP/1.1 201 Created Hope that helps Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35310) ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it
Title: Message Title
Jostein Gogstad edited a comment on JENKINS-35310
Re: ComputedFolder shows BuildAuthorizationToken configuration but does not actually support it
Authentication tokens doesn't work, as Jesse pointed out. The following endpoints works for triggering indexing and builds in multibranch projects:{code:none}curl -isk -u gitlab:5d7b834xxx6c1e0c9f3 -X POST https://myjenkins.internal.com/job/my_multibranch_job/job/Branches/buildHTTP/1.1 302 Found...{code}It gives {{302}}, but it both indexes and trigger builds on branches with new commits. Since the authentication token doesn't work, you'll have to use an user level authentication token and use it as password in a BASIC authentication scheme, you'll find the user authentication token under https://myjenkins.internal.com/user/USERNAME/configure (press "Show token"). If your SCM-vendor doesn't support explicitly specifying BASIC credentials (gitlab has no configuration for this), you can embed it in the url. Our push hook in GitLab is https://gitlab:5d7b834xxx6c1e0c...@myjenkins.internal.com/job/my_multibranch_job/job/Branches/buildFinally if you want to trigger build builds on specific branches in a multibranch pipeline, they can be triggered as such{code:none}curl -isk -u gitlab:5d7b834xxx6c1e0c9f3 -X POST https://myjenkins.internal.com/job/my_multibranch_job/job/Branches/job/develop/buildHTTP/1.1 201 Created{code}Hope that helps
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and
[JIRA] (JENKINS-37926) Job configuration settings lost and Jenkins crashes if setting "This project is parameterized" is set with no parameter added.
Title: Message Title Serafeim Tgrds created an issue Jenkins / JENKINS-37926 Job configuration settings lost and Jenkins crashes if setting "This project is parameterized" is set with no parameter added. Issue Type: Bug Assignee: Serafeim Tgrds Attachments: jenkins_bug.png, jenkins_bug.txt Components: core Created: 2016/Sep/02 12:38 PM Environment: Jenkins 2.7.2 Debian GNU/Linux 7.11 (wheezy) Java version 1.8.0_91 Priority: Major Reporter: Serafeim Tgrds In the job configuration page if you select "This project is parameterized" and then you do not set a parameter and click save or apply, Jenkins will crash. Add Comment
[JIRA] (JENKINS-37814) missing icon in script console
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37814 missing icon in script console Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37814) missing icon in script console
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37814 Re: missing icon in script console Code changed in jenkins User: Raphael Pionke Path: core/src/main/resources/lib/hudson/scriptConsole.jelly http://jenkins-ci.org/commit/jenkins/a6e1b0bebfe9dc46b3c919c917a1be4438207af7 Log: [FIXED JENKINS-37814] make the icon of the script console configurable (#2528) make the icon of the script console configurable we don't need an extra variable use Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37927) Display image related metadata along with image
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-37927 Display image related metadata along with image Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: image-gallery-plugin Created: 2016/Sep/02 12:56 PM Priority: Minor Reporter: Ioannis Moutsatsos Provide a mechanism to display image related metadata along with the image. Especially with scientific images, being able to annotate them with metadata would be extremely useful. By metadata I don't mean 'dumb metadata' such image dimensions, file size etc but rather 'smart' metadata generated by the sam eprocess that generates the images. For example, parameters of the analysis, sample type, experimental conditions etc. Add Comment
[JIRA] (JENKINS-37741) gitlab oauth plugin:GitlabAPIException
Title: Message Title Mohamed EL Habib commented on JENKINS-37741 Re: gitlab oauth plugin:GitlabAPIException Hello, Please can you test using a version 1.0.7 or 1.0.8. we update the used version of the gitlab-api if you still have the problem, can you provide more details: http request/response for example. Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Alessandro Dionisi commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace We have written a script and scheduled it with cron: Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml #TODO handle folders with spaces IFS=$'\n' #find empty job directories & form the new folder structure for workspace directories emptydirs_jobs=$(find . -type d -empty | cut -d '/' -f2-6) emptydirs_workspace=$(find . -type d -empty | cut -d '/' -f2,4,6) #remove the corresponding directory from workspace for i in $emptydirs_workspace; do rm -rf /var/jenkins_home/workspace/$i done #remove empty directories from jobs for j in $emptydirs_jobs; do rm -rf /var/jenkins_home/jobs/$j done I hope this can help you until a fix is provided. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jen
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title
Alessandro Dionisi edited a comment on JENKINS-2111
Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace
We have written a script and scheduled it with cron:{code: bash none }#TODO handle folders with spacesIFS=$'\n'#find empty job directories & form the new folder structure for workspace directoriesemptydirs_jobs=$(find . -type d -empty | cut -d '/' -f2-6)emptydirs_workspace=$(find . -type d -empty | cut -d '/' -f2,4,6)#remove the corresponding directory from workspacefor i in $emptydirs_workspace; dorm -rf /var/jenkins_home/workspace/$idone#remove empty directories from jobsfor j in $emptydirs_jobs; dorm -rf /var/jenkins_home/jobs/$jdone{code}I hope this can help you until a fix is provided.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Tom Smith commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Hi, We are also experiencing a similar or the same issue. Our build is affected every other build ie we get a "Success", followed by a "Failure". Nothing I have attempted changes this behaviour, I have tried adding/removing additional credentials for the SVN external, full checkouts instead of svn updates, clearing out the .subversion directory all to no avail. No changes for https://subversion.local/svn/web/frontpage since the previous build hudson.util.IOException2: revision check failed on https://subversion.local/svn/web/common_src/trunk/php at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:793) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:398) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:863) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:699) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
[JIRA] (JENKINS-37809) Throttling based on parameters does not work in Pipelines
Title: Message Title
Aaron Lunsford updated an issue
Jenkins / JENKINS-37809
Throttling based on parameters does not work in Pipelines
Change By:
Aaron Lunsford
h3. Configuration # Pipeline job with parameters # Execute concurrent builds if necessary: true # Throttle Concurrent Builds: true # Prevent multiple jobs with identical parameters from running concurrently: true h3. Notes - Job parameters are defined as part of the pipeline setup with the {{properties}} command - This is also an issue when properties are not defined as part of the pipeline setup, and are configured through the UI directly h3. Problem When throttling based on one of the job's parameters, the plugin does not prevent multiple builds from running concurrently when the defined parameter is the same.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-37809) Throttling based on parameters does not work in Pipelines
Title: Message Title
Aaron Lunsford edited a comment on JENKINS-37809
Re: Throttling based on parameters does not work in Pipelines
I did some more digging on the issue and it looks like problem is in the {{getParametersFromWorkUnit()}} method. On Freestyle jobs, the conditional that checks {{unit.context.actions}} gets populated with values, but for Pipeline jobs it does not. The {{WorkUnit}} object that is passed to {{getParametersFromWorkUnit()}} for a normal job looks like this: { { noformat} hudson.model.queue.WorkUnit@53acb86e[work=Working] {noformat } } , where "Working" is the name of the job. For Pipeline jobs, it looks like { { noformat} hudson.model.queue.WorkUnit@496091d7[work=part of Throttle-this #11] {noformat } } , where "Throttle-this" is the name of the job and "#11" is the build number.To try and summarize:Freestyle jobs where the plugin works:{noformat}- WorkUnit object: hudson.model.queue.WorkUnit@53acb86e[work=Working]- WorkUnit.context: hudson.model.queue.WorkUnitContext@14401e37- WorkUnit.context.actions: [hudson.model.ParametersAction@7e92e075, hudson.model.CauseAction@1d3d3d46]{noformat}Pipeline jobs where the plugin does not work:{noformat}- WorkUnit object: hudson.model.queue.WorkUnit@496091d7[work=part of Throttle-this #11]- WorkUnit.context: hudson.model.queue.WorkUnitContext@47a7768b- WorkUnit.context.actions: []{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@go
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title
Tom Smith edited a comment on JENKINS-31455
Re: Build instability with "ISVNAuthentication provider did not provide credentials"
Hi,We are also experiencing a similar or the same issue. Our build is affected every other build ie we get a "Success", followed by a "Failure". Nothing I have attempted changes this behaviour, I have tried adding/removing additional credentials for the SVN external, full checkouts instead of svn updates, clearing out the .subversion directory all to no avail. Jenkins: 2.20 Subversion Plugin: 2.6Credentials Plugin: 2.1.4 {code:java}No changes for https://subversion.local/svn/web/frontpage since the previous buildhudson.util.IOException2: revision check failed on https://subversion.local/svn/web/common_src/trunk/php at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:793) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:398) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:863) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:699) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:118) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1049) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:189) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java
[JIRA] (JENKINS-36948) return all selected values, when gets the default value
Title: Message Title Boguslaw Klimas commented on JENKINS-36948 Re: return all selected values, when gets the default value Any update for this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37304) Always redirected to login page after successfull login, resulting in 403 error (after upgrade ftom 1.642.2 to 2.7.1)
Title: Message Title Sysadmins MRM commented on JENKINS-37304 Re: Always redirected to login page after successfull login, resulting in 403 error (after upgrade ftom 1.642.2 to 2.7.1) Any hint on this would be highly appreciated. Nothing has been changed, except deploying the new version. Deploying older versions we never ran into this problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37928) "agent" section without value causes NPE
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-37928 "agent" section without value causes NPE Change By: Andrew Bayer Environment: Pipeline Model 0.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37928) "agent" section without value causes NPE
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37928 "agent" section without value causes NPE Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/02 2:12 PM Priority: Minor Reporter: Andrew Bayer If you specify "agent" without an argument, you get an NPE: BUG! exception in phase 'canonicalization' in source unit 'WorkflowScript' unexpected NullpointerException at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1058) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:591) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:212) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.NullPointerException: Cannot get property 'objectExpression' on null object at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60) at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:172) at org.codehaus.groovy.runt
[JIRA] (JENKINS-37930) docker.build throws NoSuchMethodError
Title: Message Title
Bryan Hunt created an issue
Jenkins / JENKINS-37930
docker.build throws NoSuchMethodError
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker-build-publish-plugin
Created:
2016/Sep/02 2:15 PM
Environment:
Jenkins 2.7.3 Docker Build and Publish plugin 1.3.1
Priority:
Blocker
Reporter:
Bryan Hunt
When I try to build an image, I get a NoSuchMethodError. My build stage looks like:
stage 'image'
docker.withRegistry('https://build:18000', 'svcnvmetrics')
{
dev image = docker.build("${app}_documents:${version}", "--build-arg APP=${app} -f ${appDir}/Dockerfile ${buildDir}")
echo "Pushing image"
image.push()
echo "Done pushing image"
}
Removing intermediate container 6b4bf7510ed9
Successfully built 54794364b1e5
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timeout
[Pipeline] End of Pipeline
java.lang.NoSuchMethodError: No such DSL method 'dev' found among steps [archive, bat, build, catchError, checkout, deleteDir, dir, dockerFingerprintFrom, dockerFingerprintRun, echo, emailext, emailextrecipients, error, fileExists, git, input, isUnix, load, mail, nexusArtifactUploader, node, parallel, properties, pwd, readFile, readTrusted, retry
[JIRA] (JENKINS-37929) WorkUnitContext.actions does not populate for Pipeline steps
Title: Message Title Aaron Lunsford created an issue Jenkins / JENKINS-37929 WorkUnitContext.actions does not populate for Pipeline steps Issue Type: Bug Assignee: Jesse Glick Components: pipeline Created: 2016/Sep/02 2:15 PM Environment: Jenkins v2.13 Priority: Major Reporter: Aaron Lunsford I found this while filing JENKINS-37809. It seems like WorkUnitContext objects created by Pipeline steps do not have their parameters storied in the .actions field. The plugin works by calling getCurrentWorkUnit() on a node's Executor, uses that WorkUnit's .context to get the WorkUnitContext object, then gets its parameters by referencing the .actions field. That field is populated for builds running on executors for Freestyle jobs, but does not for Pipeline jobs. I don't really know much Java or understand the internal workings of Jenkins, so I'm afraid I can't supply much more detail than that. I put as many relevant details as I could in JENKINS-37809 and decided to file a bug with the main pipeline component, as it seems like that is where the underlying issue exists. Thanks!
[JIRA] (JENKINS-37928) "agent" section without value causes NPE
Title: Message Title Andrew Bayer started work on JENKINS-37928 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37928) "agent" section without value causes NPE
Title: Message Title Andrew Bayer updated JENKINS-37928 Jenkins / JENKINS-37928 "agent" section without value causes NPE Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37928) "agent" section without value causes NPE
Title: Message Title Andrew Bayer commented on JENKINS-37928 Re: "agent" section without value causes NPE PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/4 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37852) Cannot build new job with TFS plugin 5. Results in Querying for remote changeset at '$/[tfspath]/WIP/WebService' as of 'D2016-08-31T12:59:01Z'... Query returned no result! FATAL
Title: Message Title Joseph Hoppe updated an issue Jenkins / JENKINS-37852 Cannot build new job with TFS plugin 5. Results in Querying for remote changeset at '$/[tfspath]/WIP/WebService' as of 'D2016-08-31T12:59:01Z'... Query returned no result! FATAL: null java.lang.NullPointerException at hudson.plugins.tfs.model.Project.ext Change By: Joseph Hoppe I'm trying to add a new project to Jenkins after upgrading the TFS plugin from 3.2 to 5.0 - actually it's 5 . 1. Some projects work, but one specifically doesn't.I'm getting the following error:Started by user TCBuilding in workspace E:\Jenkins\jobs\[jobName]\workspaceQuerying for remote changeset at '$/[tfspath]/WIP/WebService' as of 'D2016-08-31T12:59:01Z'...Query returned no result!FATAL: nulljava.lang.NullPointerException at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:273) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:268) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:284) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:359) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:308) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Sending e-mails to: joseph.ho...@example.comFinished: FAILUREI've tried adding DefaultCollection to the TFS URL.The polling log reports:Started on Aug 31, 2016 8:04:00 AMDone. Took 5.4 secNo changesI looked at JENKINS-33280, and manually put together the URL as the issue suggests. The URL to the TFS server works, so it seems like the job's TFS settings are correct.Please let me know if I can provide any more information. Add Comment
[JIRA] (JENKINS-37931) PR build can use PR's head/merge Jenkinsfile insted of master branch.
Title: Message Title ma pi created an issue Jenkins / JENKINS-37931 PR build can use PR's head/merge Jenkinsfile insted of master branch. Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Sep/02 2:58 PM Priority: Minor Reporter: ma pi In PR build, Jenkins says Loading trusted files from base branch master at [master HEAD] rather than [PR HEAD] I understand this behavior.(for security) but I want the option that use 'untrusted file' for try new build/jenkinsfile without brake the master branch. Add Comment
[JIRA] (JENKINS-36468) Tasks fail to run on ECS after upgrade to 1.4
Title: Message Title Luis Silva commented on JENKINS-36468 Re: Tasks fail to run on ECS after upgrade to 1.4 I managed to trace the problem to an empty Jenkins URL on the plugin config. On version 1.4 you introduced a new field to set the Jenkins URL. When I upgraded the plugin that field stayed empty and the plugin wasn't falling back to the Global jenkins url. As soon as I set the jenkinsURL config field to a correct value, the plugin started working. Now, even if I delete the contents of the url field on plugin config, it will get auto populated with the value from the Global jenkins url settings so the plugin continues to work just fine. So, I draw two conclusions from this: During the upgrade process from 1.3 something is not being correctly handled in order to populate the plugin's jenkins url field. When clearing the plugin's url field and saving I would expect it to stay empty the next time I loaded the jenkins settings page and the plugin should just internally get the global jenkins setting and use it. Instead, it is actually copying the global setting value and populating the config field with it (setting a value on the jenkins config.xml). I would never expect a plugin to set a value in the config.xml when I explicitly empty the field. Please consider these two inputs for an eventual improvement on the way the plugin works. You can either close this issue or use it to track an update to the plugin. Thanks for your help. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36687) Refactor RunPipeline to use HAL hrefs in internal logic
Title: Message Title Cliff Meyers updated JENKINS-36687 Jenkins / JENKINS-36687 Refactor RunPipeline to use HAL hrefs in internal logic Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35794) Developer wants to re-run a failing or unstable result from the activity tab
Title: Message Title Cliff Meyers updated JENKINS-35794 Jenkins / JENKINS-35794 Developer wants to re-run a failing or unstable result from the activity tab Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35796) Developer can stop the run of an executing pipeline
Title: Message Title Cliff Meyers updated JENKINS-35796 Jenkins / JENKINS-35796 Developer can stop the run of an executing pipeline Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36974) Developer can stop a run from the activity tab
Title: Message Title Cliff Meyers updated JENKINS-36974 Jenkins / JENKINS-36974 Developer can stop a run from the activity tab Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35789) Developer can re-run a completed pipeline
Title: Message Title Cliff Meyers updated JENKINS-35789 Jenkins / JENKINS-35789 Developer can re-run a completed pipeline Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-37932 Error if no "agent" specified Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/02 3:09 PM Environment: Pipeline Model 0.1 Priority: Minor Reporter: Patrick Wolf If you specify "agent" without an argument, you get an NPE: BUG! exception in phase 'canonicalization' in source unit 'WorkflowScript' unexpected NullpointerException at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1058) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:591) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:212) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: java.lang.NullPointerException: Cannot get
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-37932 Error if no "agent" specified Change By: Patrick Wolf Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title
Patrick Wolf updated an issue
Jenkins / JENKINS-37932
Error if no "agent" specified
Change By:
Patrick Wolf
If you create a pipeline model with no {{agent}} specified you get an error message:{code}org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 3: Missing required section 'agent' @ line 3, column 1. pipeline{ ^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1073) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:591) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:213) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE{code}Rather than throwing an error should we default to no label node: { { agent label:""} }
Add Comment
[JIRA] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Title: Message Title Oleg Nenashev commented on JENKINS-18578 Re: Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable I'm going to change the default cache location in remoting 3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title
Patrick Wolf updated an issue
Jenkins / JENKINS-37932
Error if no "agent" specified
Change By:
Patrick Wolf
If you specify " create a pipeline model with no {{ agent " without an argument, }} specified you get an NPE error message :{code} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: BUG! exception in phase 'canonicalization' in source unit ' WorkflowScript : 3: Missing required section ' unexpected NullpointerException agent' @ line 3, column 1. pipeline{ ^1 error at org.codehaus.groovy.control. ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control. CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java: 1058 1073 ) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:591) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:569) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:546) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:410) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:373) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java: 212 213 ) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by Finished : java.lang.NullPointerException: Cannot get property 'objectExpression' on null object FAILURE at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60) {code} at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:172) at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java Rather than throwing an error should we default to no label node : 47) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:296) at org.jenkinsci.plugins.pipeline.modeldefinition.parser.ModelParser.matchMethodName(ModelParser.groovy:505) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:210) at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:59) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:52) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.cal
[JIRA] (JENKINS-37932) Error if no "agent" specified
Title: Message Title Patrick Wolf commented on JENKINS-37932 Re: Error if no "agent" specified Michael Neale Kohsuke Kawaguchi James Dumay Andrew Bayer let's discuss this Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37930) docker.build throws NoSuchMethodError
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-37930 docker.build throws NoSuchMethodError Change By: Carlos Sanchez Priority: Blocker Trivial Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37930) docker.build throws NoSuchMethodError
Title: Message Title Carlos Sanchez commented on JENKINS-37930 Re: docker.build throws NoSuchMethodError java.lang.NoSuchMethodError: No such DSL method 'dev' maybe you meant def Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37930) docker.build throws NoSuchMethodError
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-37930 docker.build throws NoSuchMethodError Change By: Carlos Sanchez Component/s: docker-workflow-plugin Component/s: docker-build-publish-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37930) docker.build throws NoSuchMethodError
Title: Message Title Carlos Sanchez closed an issue as Not A Defect Jenkins / JENKINS-37930 docker.build throws NoSuchMethodError Change By: Carlos Sanchez Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37933) NPE when adding shared library
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-37933 NPE when adding shared library Issue Type: Bug Assignee: Jesse Glick Components: workflow-cps-global-lib-plugin Created: 2016/Sep/02 3:30 PM Priority: Major Reporter: Patrick Wolf When trying to add a new shared library on Jenkins master (system config) I get an NPE when specifying "master" or "Master" branch to load implicitly. Cannot validate default version. java.lang.NullPointerException at com.cloudbees.plugins.credentials.matchers.IdMatcher.(IdMatcher.java:56) at com.cloudbees.plugins.credentials.CredentialsMatchers.withId(CredentialsMatchers.java:132) at jenkins.plugins.git.AbstractGitSCMSource.getCredentials(AbstractGitSCMSource.java:423) at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:180) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:357) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:278) at org.jenkinsci.plugins.workflow.libs.LibraryConfiguration$DescriptorImpl.doCheckDefaultVersion(LibraryConfiguration.java:195) 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:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) 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.
