[JIRA] (JENKINS-30866) Getting a HTTP 411 Length required trying to trigger a build on remote jenkins server
Title: Message Title Harvinder Singh assigned an issue to Harvinder Singh Jenkins / JENKINS-30866 Getting a HTTP 411 Length required trying to trigger a build on remote jenkins server Change By: Harvinder Singh Assignee: Maurice W. Harvinder Singh Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51258) Click "Pipeline Syntax" link displayed NullPointerException
Title: Message Title charles kong created an issue Jenkins / JENKINS-51258 Click "Pipeline Syntax" link displayed NullPointerException Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-05-11 07:24 Priority: Blocker Reporter: charles kong When I click "Pipeline Syntax" link in a job's Configure, the page displayed NullPointerException as below, java.lang.NullPointerException at hudson.plugins.backlog.BacklogLinkAction.getUrlName(BacklogLinkAction.java:28) at hudson.model.Actionable.getDynamic(Actionable.java:350) at hudson.model.Job.getDynamic(Job.java:865) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:372) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) 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:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheContr
[JIRA] (JENKINS-51258) Click "Pipeline Syntax" link displayed NullPointerException
Title: Message Title charles kong updated an issue Jenkins / JENKINS-51258 Click "Pipeline Syntax" link displayed NullPointerException Change By: charles kong Environment: org.jenkins-ci.main:jenkins-war:2.107.3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50790) GitPluginTest are failing in the ATH
Title: Message Title Raul Arabaolaza updated JENKINS-50790 Jenkins / JENKINS-50790 GitPluginTest are failing in the ATH Change By: Raul Arabaolaza Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45990) Git plugin support for non standard branches during auto discover
Title: Message Title Florian Bäuerle commented on JENKINS-45990 Re: Git plugin support for non standard branches during auto discover I am working with VSTS and Jenkins. Since Multibranch Pipeline Jobs cannot detect branches outside refs/heads, I have to create an extra Pipeline Job which fetches refs/pull/* for verifying VSTS' pull-requests. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50972) broken link to jira in top level readme.md
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-50972 broken link to jira in top level readme.md Change By: Philipp Garbe Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50972) broken link to jira in top level readme.md
Title: Message Title Philipp Garbe resolved as Fixed Merged PR. Thank you! Jenkins / JENKINS-50972 broken link to jira in top level readme.md Change By: Philipp Garbe Status: Open Resolved Assignee: Jan Roehrich Philipp Garbe Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "J
[JIRA] (JENKINS-51259) Add documentation to Custom WAR Packager Mojo
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-51259 Add documentation to Custom WAR Packager Mojo Issue Type: Improvement Assignee: Oleg Nenashev Components: custom-war-packager Created: 2018-05-11 08:17 Priority: Minor Reporter: Oleg Nenashev Follow-up to https://github.com/jenkinsci/custom-war-packager/pull/26#discussion_r187395979 . It was somewhere in my plans, but it's better to have a tracking ticket for it. Having a documentaion for the CLI mode would be really helpful Add Comment
[JIRA] (JENKINS-51259) Add documentation to Custom WAR Packager Mojo and add Help Mojo
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51259 Add documentation to Custom WAR Packager Mojo and add Help Mojo Change By: Oleg Nenashev Summary: Add documentation to Custom WAR Packager Mojo and add Help Mojo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51259) Add documentation to Custom WAR Packager Mojo and add Help Mojo
Title: Message Title Oleg Nenashev started work on JENKINS-51259 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51259) Add documentation to Custom WAR Packager Mojo and add Help Mojo
Title: Message Title Oleg Nenashev updated JENKINS-51259 Jenkins / JENKINS-51259 Add documentation to Custom WAR Packager Mojo and add Help Mojo Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51062) JEP-200 issue with plugin Gradle Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51062 JEP-200 issue with plugin Gradle Plugin LTS backporting is not needed since we picked 2.121.x as a baseline Change By: Oleg Nenashev Labels: JEP-200 JEP-200-invalid lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51258) Click "Pipeline Syntax" link displayed NullPointerException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51258 Click "Pipeline Syntax" link displayed NullPointerException Change By: Oleg Nenashev Component/s: backlog-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51258) Click "Pipeline Syntax" link displayed NullPointerException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51258 Click "Pipeline Syntax" link displayed NullPointerException Change By: Oleg Nenashev Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51258) Click "Pipeline Syntax" link displayed NullPointerException
Title: Message Title Oleg Nenashev resolved as Duplicate Jenkins / JENKINS-51258 Click "Pipeline Syntax" link displayed NullPointerException Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51258) Click "Pipeline Syntax" link displayed NullPointerException
Title: Message Title Oleg Nenashev commented on JENKINS-51258 Re: Click "Pipeline Syntax" link displayed NullPointerException IIUC Backlog plugin just does not support Pipeline. It duplicates JENKINS-49396 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Oleg Nenashev commented on JENKINS-49396 Re: NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins From What I see Backlog plugin just does not support Pipeline. Due to whatever reason the property is Null in https://github.com/jenkinsci/backlog-plugin/blob/master/src/main/java/hudson/plugins/backlog/BacklogLinkAction.java#L28 It comes from this line: https://github.com/jenkinsci/backlog-plugin/blob/40f3bcf2e02584472eec6dfe55b54bb41ff24fe3/src/main/java/hudson/plugins/backlog/BacklogProjectProperty.java#L170 . It does not check the existence of the property and hence may pass null It is a trivial fix IMHO Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49396) NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49396 NPE at BacklogLinkAction.getUrlName in Pipeline jobs: Multiple Plugins Change By: Oleg Nenashev Labels: newbie-friendly pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title Oleg Nenashev commented on JENKINS-51253 Re: jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency FYI Daniel Beck Oliver Gondža Kohsuke Kawaguchi . Likely this is a regression due to the packaging issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Simon Watts commented on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Sam Van Oort thanks - back up and running Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51258) Click "Pipeline Syntax" link displayed NullPointerException
Title: Message Title Oleg Nenashev commented on JENKINS-51258 Re: Click "Pipeline Syntax" link displayed NullPointerException Added some diagnostics to the linked ticket Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51253 jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title Oliver Gondža commented on JENKINS-51253 Re: jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency Am I correct to understand this does not affects updating users as long as they do not call apt-get autoremove and for new installs this will require users to install (correct) java versions manually? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51253) jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency
Title: Message Title Mostyn Bramley-Moore commented on JENKINS-51253 Re: jenkins_2.107.3_all.deb depends on java being installed but no longer has this explicit dependency Oliver Gondža: correct. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28748) git plugin submodule update --init fails on large submodule
Title: Message Title Serhii Fedorenko commented on JENKINS-28748 Re: git plugin submodule update --init fails on large submodule I've had the same problem and solve it. I had checked .gitmodules file and found old links to submodules or duplicates. Then I removed that trash. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42483) Certain GDSL methods are not generated
Title: Message Title Olaf Märker commented on JENKINS-42483 Re: Certain GDSL methods are not generated Here are some more that are incorrect or missing: withCredentials parameter 'bindings' must be List instead of Map withEnv parameter 'overrides' must be List instead of Map Methods 'configFileProvider' and 'configFile' are missing method node has an optional parameter 'label'. With the current gdsl it is shown as mandatory in IDEA. Maybe we need here an additional 'node()' entry without label Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Olivier Lamy commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job uhm I have an issue with core java.lang.IllegalStateException: JENKINS-27530: cannot create a build with number 47 since that (or higher) is already in use among [5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 30, 32, 33, 34, 35, 36, 38, 39, 41, 42, 43, 44, 48, 49] Well I guess 47 is possible as not used Oleg Nenashev any idea? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title
Olivier Lamy edited a comment on JENKINS-13810
Re: Maven modules marked to wrong build when running concurrent job
uhm I have an issue with core :( {code:java}java.lang.IllegalStateException: JENKINS-27530: cannot create a build with number 47 since that (or higher) is already in use among [5, 6, 8, 9, 10, 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 30, 32, 33, 34, 35, 36, 38, 39, 41, 42, 43, 44, 48, 49]{code}Well I guess 47 is possible as not used :-)[~oleg_nenashev] [~jglick] any idea?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19129) Environment variables not expanded in plot configuration
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-19129 Environment variables not expanded in plot configuration Change By: Sorin Sbarnea Summary: Environment variables not expanded in plot configuration Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19130) environment variables aren't expanded by description setter
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-19130 environment variables aren't expanded by description setter Change By: Sorin Sbarnea Summary: environment variables aren't expanded by description setter Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Oleg Nenashev commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job Yes, I would expect core to handle such cases when parallel runs are enabled for AbstractProject. Unfortunately many APIs actually do not support it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51260) global environment variables are not expanded (interpolated) in pipelines
Title: Message Title
Sorin Sbarnea created an issue
Jenkins / JENKINS-51260
global environment variables are not expanded (interpolated) in pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, pipeline
Created:
2018-05-11 10:36
Priority:
Critical
Reporter:
Sorin Sbarnea
On Freestyle jobs defining a Jenkins global variable like this would work as expected:
XDG_CACHE_HOME=${HOME}/.cache/${EXECUTOR_NUMBER}
Note: behavior is the same regardless if brackets are used or not when you define the variables. Freestyle "set" result (correct):
XDG_CACHE_HOME=/home/builder/.cache/2
Pipeline "set" result (incorrect):
XDG_CACHE_HOME=${HOME}/.cache/${EXECUTOR_NUMBER}
This problem is essential because it prevents Jenkins administrators from using environment variables to fix/workaround execution problems. Effectively this breaks any job that needs to define variables that are relative to something else, like workspace, home,
[JIRA] (JENKINS-51261) JSON is UTF-8 only - discourage/disallow other encodings for JSON documents
Title: Message Title Christoph Obexer created an issue Jenkins / JENKINS-51261 JSON is UTF-8 only - discourage/disallow other encodings for JSON documents Issue Type: Bug Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2018-05-11 10:53 Priority: Minor Reporter: Christoph Obexer According to https://tools.ietf.org/html/rfc8259#section-8.1 JSON text exchanged between systems that are not part of a closed ecosystem MUST be encoded using UTF-8. Don't encourage users to create invalid JSON documents in noncompliant encodings or with BOMs. Add Comment
[JIRA] (JENKINS-51262) Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts.
Title: Message Title karthik h v created an issue Jenkins / JENKINS-51262 Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts. Issue Type: Task Assignee: Daniel Spilker Components: authorize-project-plugin, job-dsl-plugin Created: 2018-05-11 11:21 Environment: Dependencies Structs v.1.13 (required) Script Security v.1.25 (required) vSphere v.1.1.11 (optional) Config File Provider v.2.15.4 (optional) Managed Scripts v.1.3 (optional) Command Agent Launcher v.1.0 (implied) JDK Tool v.1.0 (implied) Labels: plugins jenkins Priority: Minor Reporter: karthik h v The issue we faced is job DSL plugin is not honoring groovy sandbox policies. we have installed structs plugin ** 1.13 version , Authorize Project plugin and Script Security plugin. Developer usually need to use "Sandbox" for executing groovy as it doesn't require any approval from administrators. We can see that this policy is working well in templates, pipelines and regular jobs. But it is failing when used in combination of "job dsl"and "Authorize Project plugin". This combination is expecting users who triggered job to have "Overall/RunScripts" access.This access cannot be given to developers. We configured job dsl to execute a groovy script in sandbox. For triggering this job, we used Authorization step with "Run as User who triggered Build". The build never executes and simply show waiting for next executor - even though that slave is idle. we can run the same build successfully as admin and have "RunScripts" access. As developers
[JIRA] (JENKINS-51262) Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts.
Title: Message Title karthik h v updated an issue Jenkins / JENKINS-51262 Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts. Change By: karthik h v Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51262) Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts.
Title: Message Title
karthik h v updated an issue
Jenkins / JENKINS-51262
Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts.
Change By:
karthik h v
{color:#1f497d}The issue we faced is job DSL plugin is not honoring groovy sandbox policies.{color}{color:#1f497d}we have installed structs plugin ** 1.13 version , Authorize Project plugin and Script Security plugin. {color}{color:#1f497d}Developer usually need to use "Sandbox" for executing groovy as it doesn't require any approval from administrators. {color}{color:#1f497d}We can see that this policy is working well in templates, pipelines and regular jobs. But it is failing when used in combination of " {color:#1f497d}{color:#1f497d}{color:#1f497d} job dsl"and "Authorize Project plugin". {color}{color }{color}{color}{color :# 1f497d 33 } {color:#1f497d}{color:#1f497d}{color:#1f497d} This combination is expecting users who triggered job to have "Overall/RunScripts" access.This access cannot be given to developers. {color}{color}{color}{color}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}We configured job dsl to execute a groovy script in sandbox. {color}{color}{color}{color}{color}{color}{color}{color}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}{color:#1f497d}For triggering this job, we used * Authorization * step with "Run as User who triggered Build". {color}{color}{color}{color}{color}{color}{color}{color} {color:#1f497d} The build never executes and simply show waiting for next executor - even though that slave is idle.{color} {color:#33} {color} {color:# 33}{color:# 1f497d}we can run the same build successfully as admin and have "RunScripts" access. As developers we don't have this access and it is showing waiting for executor.{color} {color} {color:#33} {color}
Add Comment
[JIRA] (JENKINS-51262) Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts.
Title: Message Title
karthik h v updated an issue
Jenkins / JENKINS-51262
Job dsl and Authorize Project plugin is not working with "Sandbox" policy for executing groovy scripts.
Change By:
karthik h v
{color:# 33}{color:# 1f497d}The issue we faced is job DSL plugin is not honoring groovy sandbox policies.{color} {color} {color:# 33}{color:# 1f497d}we have installed structs plugin 1.13 version , Authorize Project plugin and Script Security plugin. {color} {color} {color:# 33}{color:# 1f497d}Developer usually need to use "Sandbox" for executing groovy as it doesn't require any approval from administrators. {color} {color} {color:# 33}{color:# 1f497d}We can see that this policy is working well in templates, pipelines and regular jobs. But it is failing when used in combination of "job dsl"and "Authorize Project plugin". {color}{color }{color :#33} This combination is expecting users who triggered job to have "Overall/RunScripts" access.This access cannot be given to developers. We configured job dsl to execute a groovy script in sandbox. For triggering this job, we used Authorization step with "Run as User who triggered Build". The build never executes and simply show waiting for next executor - even though that slave is idle.{color}{color:#33} {color}{color:#33} {color:#1f497d} we can run the same build successfully as admin and have "RunScripts" access. As developers we don't have this access and it is showing waiting for executor.{color} {color} {color:#33} {color}
Add Comment
[JIRA] (JENKINS-47376) Fix lost support for global properties
Title: Message Title Carlos Sanchez resolved as Fixed This has been merged in 1.2.1 Jenkins / JENKINS-47376 Fix lost support for global properties Change By: Carlos Sanchez Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51150) Push prototype code to jenkinsci repo
Title: Message Title Share Cheng closed an issue as Fixed Jenkins / JENKINS-51150 Push prototype code to jenkinsci repo Change By: Share Cheng Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Mark Waite commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Benoit Sigoure have you tried the build from the pull request in your environment? It has been running well for Jacob Keller and would be good to have additional users report their results. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Thomas Becker commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads 2.53 is working fine until now. Thx for the fix! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50573 Re: Wrong username used for clone with Git 2.17 on Windows Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CredentialsTest.java http://jenkins-ci.org/commit/git-client-plugin/e2520d9a1a52fa210004e9a0d4cea42d97cf9fae Log: JENKINS-50573 Prefer URL username with ssh URL When using an ssh private key, the CliGitAPIImpl implementation previously passed a "-l" command line argument from the username associated with the ssh key. OpenSSH implementations prior to OpenSSH 7.7 would only use that command line argument if no username were included in the ssh URI. OpenSSH 7.7 changes the ssh command line argument parsing rules. Previously, the last user name specified would be used, including the user name in the URL. With OpenSSH 7.7, the first user name specified is used, even if a user name is specified in the URL. The command line: ssh -l jenkins g...@github.com:jenkinsci/git-client-plugin.git uses the username 'git' with OpenSSH versions before 7.7 and uses the username 'jenkins' with OpenSSH 7.7. OpenSSH 7.7 is included in Windows Git 2.17 and in OpenBSD 6.3. The CredentialsTest class can test this case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51263) try-catch is not working in declarative pipeline
Title: Message Title
Viachaslau Kabak created an issue
Jenkins / JENKINS-51263
try-catch is not working in declarative pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-05-11 12:36
Environment:
Jenkins 2.107.2
Priority:
Minor
Reporter:
Viachaslau Kabak
pipeline { stages { stage("Test") { script { try { echo "Any code with error" } catch(err) { echo "Error" } } } } } So the try-catch is not working in script section of declarative pipeline. It throws an exception and pipeline fails
Add Comment
[JIRA] (JENKINS-51263) try-catch is not working in declarative pipeline
Title: Message Title
Viachaslau Kabak updated an issue
Jenkins / JENKINS-51263
try-catch is not working in declarative pipeline
Change By:
Viachaslau Kabak
{code:java} pipeline \ { stages \ { stage("Test") \ { script \ { try \ { echo "Any code with error" } catch(err) \ { echo "Error" } } } } } {code } So the try-catch is not working in script section of declarative pipeline. It throws an exception and pipeline fails
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51263) try-catch is not working in declarative pipeline
Title: Message Title
Viachaslau Kabak updated an issue
Jenkins / JENKINS-51263
try-catch is not working in declarative pipeline
Change By:
Viachaslau Kabak
{code:java}pipeline { stages { stage("Test") { script { for (i in list){ try { echo "Any code with error" } catch(err) { echo "Error" } } } } } } {code} So the try-catch is not working in script section of declarative pipeline. It throws an exception and pipeline fails
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51264) Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-51264 Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins Issue Type: Bug Assignee: Stephen Connolly Components: maven-hpi-plugin Created: 2018-05-11 13:13 Priority: Minor Reporter: Stephen Connolly Background I have some code that takes a list of .hpi files on disk and builds a temporary throw-away update centre in a docker image providing those plugins. In order to ensure interoperability with other update centres, it needs to parse versions the same way that Jenkins does, namely by reading the Plugin-Version manifest entry. I then have some acceptance tests for my plugins that fire up a clean Jenkins instance, configure this update centre and download and install the plugin, thereby verifying the installation experience for new users. I am following Continuous Delivery using the model where the Maven Release Plugin creates the release but I do not push changes back to master, instead I push the tags *after* the acceptance tests pass (thus the tags only reflect actual releases) and furthermore, I drop the Nexus Staging repo if the acceptance tests fail. Because the release poms are never pushed back to master, the version in the pom.xml on master is *always* 1.x-SNAPSHOT I now want to write acceptance tests to verify upgrades from specific known versions. Additionally when testing locally, I have a need to update the development builds of the plugin. While I could just manually upload the plugins, this would not reflect the real user experience. I need a way to modify the plugin's generated manifest and substitute the Plugin-Version for my own plugin version. Proposed solution Add a snapshotPluginVersionOverride configuration option to the hpi goal. This would be the version to set in the Plugin-Version manifest entry *but only in the case where the project.version is actually a -SNAPSHOT version*
[JIRA] (JENKINS-51265) Run Result Recorder: Didn't find any test results to record
Title: Message Title Charles Whaples created an issue Jenkins / JENKINS-51265 Run Result Recorder: Didn't find any test results to record Issue Type: Bug Assignee: Ofir Shaked Attachments: FailedResultRecordingJenkinsSlave.txt Components: hp-application-automation-tools-plugin, qtest-plugin Created: 2018-05-11 13:17 Environment: Windows Server 2012 Priority: Minor Reporter: Charles Whaples When executing HPE tests from file system from a .mtbx, if multiple of the same jobs are running concurrently on the last build in the jenkins job queue will recognize that there are results available from the UFT tests. Attached is an output of the successfully built job - but failed to report successfully build Our process is similar to the following: We execute a master build job that parses a folder for available UFT tests, and kicks off each one as a new job through another build by dynamically creating a mtbx file. These jobs run UFT scripts as expected and will always output UFT Run Reports During the 'Post-Build Action' for Publishing HPE tests results the RunResultRecorder fails to find any test results to record Subsequently the qTest Plugin will fail to upload a result to our server. Important thing to note: We cannot use ALM for these parallel job executions
[JIRA] (JENKINS-51264) Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins
Title: Message Title Jesse Glick started work on JENKINS-51264 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51264) Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins
Title: Message Title Jesse Glick updated JENKINS-51264 Jenkins / JENKINS-51264 Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51264) Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51264 Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins Change By: Jesse Glick Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51265) Run Result Recorder: Didn't find any test results to record
Title: Message Title Charles Whaples updated an issue Jenkins / JENKINS-51265 Run Result Recorder: Didn't find any test results to record Change By: Charles Whaples Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51266) Statistics Gatherer plugin should be marked as dynamically loadable
Title: Message Title lucamilanesio created an issue Jenkins / JENKINS-51266 Statistics Gatherer plugin should be marked as dynamically loadable Issue Type: Bug Assignee: lucamilanesio Components: statistics-gatherer-plugin Created: 2018-05-11 13:42 Priority: Major Reporter: lucamilanesio I have tested the statistics-gatherer setup and it doesn't require any Jenkins restart. However, it is currently flagged as dynamicLoadable = MAYBE. Flag all the extensions to mark then dynamically loadable. Add Comment
[JIRA] (JENKINS-51266) Statistics Gatherer plugin should be marked as dynamically loadable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51266 Re: Statistics Gatherer plugin should be marked as dynamically loadable Code changed in jenkins User: Luca Milanesio Path: src/main/java/org/jenkins/plugins/statistics/gatherer/StatisticsConfiguration.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/BuildStepStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/ItemStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/QueueStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/RunStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/ScmStatsListener.java http://jenkins-ci.org/commit/statistics-gatherer-plugin/6f0073d6fcb80431ed0df1f79782029cc164794f Log: JENKINS-51266 Mark all extensions as dynamically loadable There are no reasons why this plugin should require a Jenkins restart. Mark all extensions as dynamically loadable so that no restarts will be required when installing it. Change-Id: I18b2264b44288b82b4985dff5a9a35ba8cfc09a4 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51264) Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51264 Re: Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins Code changed in jenkins User: Stephen Connolly Path: src/it/snapshot-version-override/invoker.properties src/it/snapshot-version-override/pom.xml src/it/snapshot-version-override/src/main/java/org/jenkinsci/tools/hpi/its/HelloWorldBuilder.java src/it/snapshot-version-override/src/main/resources/index.jelly src/it/snapshot-version-override/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/config.jelly src/it/snapshot-version-override/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/global.jelly src/it/snapshot-version-override/src/main/resources/org/jenkinsci/tools/hpi/its/HelloWorldBuilder/help-name.html src/it/snapshot-version-override/src/main/resources/org/jenkinsci/tools/hpi/its/Messages.properties src/it/snapshot-version-override/src/main/webapp/help-globalConfig.html src/it/snapshot-version-override/verify.groovy src/main/java/org/jenkinsci/maven/plugins/hpi/AbstractHpiMojo.java http://jenkins-ci.org/commit/maven-hpi-plugin/8ee9605c12b9d31568fcf856356b94eb3d69c7f4 Log: [FIXED JENKINS-51264] Add a snapshotPluginVersionOverride configuration option to hpi and hpl goals Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51264) Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51264 Re: Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/maven/plugins/hpi/AbstractHpiMojo.java http://jenkins-ci.org/commit/maven-hpi-plugin/43cf45163756bbf51af0011cde82829fe23326b0 Log: JENKINS-51264 Noting @since tags Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45916) Path is not getting set correctly in pipeline when there is a variable present
Title: Message Title
Michael Musenbrock commented on JENKINS-45916
Re: Path is not getting set correctly in pipeline when there is a variable present
Hi, I'm not sure if this is was Blanca Borro Escribano was referencing:
pipeline {
agent {
docker {
image 'alpine:latest'
}
}
environment {
PATHX = "${env.WORKSPACE}:${env.PATH}"
PATH = "${env.WORKSPACE}:${env.PATH}"
}
stages {
stage('Test') {
steps {
echo "PATH : ${env.PATH}"
echo "PATHX: ${env.PATHX}"
sh "printenv | grep PATH"
}
}
}
}
Which prints:
[Pipeline] echo PATH : /home/catroid/jenkins_slave2_emulator/workspace/test:/usr/local/bin:/usr/bin:/bin:/usr/games
[Pipeline] echo PATHX: /home/catroid/jenkins_slave2_emulator/workspace/test:/home/catroid/jenkins_slave2_emulator/workspace/test:/usr/local/bin:/usr/bin:/bin:/usr/games
[Pipeline] sh
[test] Running shell script
+ printenv
+ grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
CLASSPATH=
PATHX=/home/catroid/jenkins_slave2_emulator/workspace/test:/home/catroid/jenkins_slave2_emulator/workspace/test:/usr/local/bin:/usr/bin:/bin:/usr/games
So both variables are expanded correctly, but PATH is not passed to the environment of sh. Could also be a problem in the sh step. I'm also confused with the order of expansion: whether (in the environment stage) i put PATHX first or second, it seems that PATH gets always set first, because PATHX has the WORKSPACE variable content always prefixed twice
Add Comment
[JIRA] (JENKINS-48733) tools directive not setting PATH environment variable
Title: Message Title Michael Musenbrock commented on JENKINS-48733 Re: tools directive not setting PATH environment variable Same behavior with setting the PATH variable in the environment section, it does not seem to be passed to the 'sh' step. see https://issues.jenkins-ci.org/browse/JENKINS-45916?focusedCommentId=337539&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-337539 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51266) Statistics Gatherer plugin should be marked as dynamically loadable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51266 Re: Statistics Gatherer plugin should be marked as dynamically loadable Code changed in jenkins User: Luca Milanesio Path: src/main/java/org/jenkins/plugins/statistics/gatherer/StatisticsConfiguration.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/BuildStepStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/ItemStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/QueueStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/RunStatsListener.java src/main/java/org/jenkins/plugins/statistics/gatherer/listeners/ScmStatsListener.java http://jenkins-ci.org/commit/statistics-gatherer-plugin/b45a97267a79b2086e761b7274e72b7eab35fd36 Log: JENKINS-51266 Mark all extensions as dynamically loadable There are no reasons why this plugin should require a Jenkins restart. Mark all extensions as dynamically loadable so that no restarts will be required when installing it. Change-Id: I18b2264b44288b82b4985dff5a9a35ba8cfc09a4 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48458) Multiple jobs running in parallel on the same agent using the Docker Workflow Plugin withRegistry results in overwritten credentials
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-48458 Multiple jobs running in parallel on the same agent using the Docker Workflow Plugin withRegistry results in overwritten credentials Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41880) ConcurrentModificationException while creating docker image fingerprints
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41880 Re: ConcurrentModificationException while creating docker image fingerprints Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/docker/commons/fingerprint/DockerFingerprints.java http://jenkins-ci.org/commit/docker-commons-plugin/c38b852d4a9ebff98a0184748396959cdaeba129 Log: Merge pull request #69 from bjoernhaeuser/synchronise-on-project JENKINS-41880 Synchronise on Fingerprint Compare: https://github.com/jenkinsci/docker-commons-plugin/compare/e00c616a8476...c38b852d4a9e *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41880) ConcurrentModificationException while creating docker image fingerprints
Title: Message Title Jesse Glick updated JENKINS-41880 Jenkins / JENKINS-41880 ConcurrentModificationException while creating docker image fingerprints Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41880) ConcurrentModificationException while creating docker image fingerprints
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41880 Re: ConcurrentModificationException while creating docker image fingerprints Code changed in jenkins User: Björn Häuser Path: src/main/java/org/jenkinsci/plugins/docker/commons/fingerprint/DockerFingerprintAction.java src/main/java/org/jenkinsci/plugins/docker/commons/fingerprint/DockerFingerprints.java http://jenkins-ci.org/commit/docker-commons-plugin/63f655f11c9be6e79a5f9979dbfa3c2984f3ad2d Log: Synchronise on project I am not sure this makes any sense. I am just trying to solve this issue: https://issues.jenkins-ci.org/browse/JENKINS-41880 My thoughts: This is likely caused by changing the finger prints, the finger prints are scoped to the project (right?). If this is the case synchronising on the project could make sense. Also `addFromFacet` should not be a performance killer and rather quick. The alternative would be for me to synchronise the complete access to the method. WDYT? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48783) Build of docker-commons-plugin fails on macOS
Title: Message Title Jesse Glick updated JENKINS-48783 Jenkins / JENKINS-48783 Build of docker-commons-plugin fails on macOS Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51264) Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins
Title: Message Title Stephen Connolly updated JENKINS-51264 Released as 2.4 (but that version was a partial release, so you really want 2.5 to get this feature) Jenkins / JENKINS-51264 Add ability to override the Plugin-Version manifest entry of -SNAPSHOT plugins Change By: Stephen Connolly Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-i
[JIRA] (JENKINS-44305) Can't use credentials to upload file to s3
Title: Message Title alfredo cambera commented on JENKINS-44305 Re: Can't use credentials to upload file to s3 According to the documentation the plug-in works with AWS Credentials (https://github.com/jenkinsci/pipeline-aws-plugin#withaws) but it doesn't. This is quite confusing Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43299) Add support for aws-credentials-plugin
Title: Message Title alfredo cambera commented on JENKINS-43299 Re: Add support for aws-credentials-plugin According to the documentation https://github.com/jenkinsci/pipeline-aws-plugin#withaws the plug-in should work with AWS Credentials too: Use Jenkins AWS credentials information (AWS Access Key: AccessKeyId, AWS Secret Key: SecretAccessKey): Maintaining two sets of credentials is confusing and generates unnecessary complexity to the pipeline. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43299) Add support for aws-credentials-plugin
Title: Message Title Thorsten Hoeger closed an issue as Fixed Jenkins / JENKINS-43299 Add support for aws-credentials-plugin Change By: Thorsten Hoeger Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44305) Can't use credentials to upload file to s3
Title: Message Title alfredo cambera edited a comment on JENKINS-44305 Re: Can't use credentials to upload file to s3 According to the documentation the plug-in works with AWS Credentials ([https://github.com/jenkinsci/pipeline-aws-plugin#withaws)] but it doesn't. This is quite confusing ticket should not be closed as the reported bug refers to AWS Credentials not working. The provided answers offer a workaround. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44305) Can't use credentials to upload file to s3
Title: Message Title Thorsten Hoeger commented on JENKINS-44305 Re: Can't use credentials to upload file to s3 Can you elaborate what is not working? It was implemented in 1.26 and should work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51266) Statistics Gatherer plugin should be marked as dynamically loadable
Title: Message Title lucamilanesio closed an issue as Fixed Jenkins / JENKINS-51266 Statistics Gatherer plugin should be marked as dynamically loadable Change By: lucamilanesio Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51266) Statistics Gatherer plugin should be marked as dynamically loadable
Title: Message Title lucamilanesio resolved as Fixed Jenkins / JENKINS-51266 Statistics Gatherer plugin should be marked as dynamically loadable Change By: lucamilanesio Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47922) BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step)
Title: Message Title Andrew Cho commented on JENKINS-47922 Re: BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step) Thanks Sandeep for information. It seems like there is a bug in our web service API that does not return the correct number of defects. This is tracked in our internal issue tracking system. Once the bug is fixed, I will reply here. Thank you for your patience. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44305) Can't use credentials to upload file to s3
Title: Message Title alfredo cambera commented on JENKINS-44305 Re: Can't use credentials to upload file to s3 Thorsten Hoeger you are completely right. The plug-in works as expected on the referred version. I was using 1.25. Thanks a lot! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43299) Add support for aws-credentials-plugin
Title: Message Title Dan Bovey commented on JENKINS-43299 Re: Add support for aws-credentials-plugin Yep, a little more research and that line in the README was only added, along with the feature to support "AWS credential" credential type, 14 days ago (27 April 2018) https://github.com/jenkinsci/pipeline-aws-plugin/pull/82 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43299) Add support for aws-credentials-plugin
Title: Message Title
alfredo cambera updated an issue
Jenkins / JENKINS-43299
Add support for aws-credentials-plugin
Change By:
alfredo cambera
Comment:
According to the documentation [https://github.com/jenkinsci/pipeline-aws-plugin#withaws] the plug-in should work with AWS Credentials too:{quote}Use Jenkins AWS credentials information (AWS Access Key: AccessKeyId, AWS Secret Key: SecretAccessKey):{quote}Maintaining two sets of credentials is confusing and generates unnecessary complexity to the pipeline.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43299) Add support for aws-credentials-plugin
Title: Message Title Dan Bovey edited a comment on JENKINS-43299 Re: Add support for aws-credentials-plugin Yep , a this can be closed now. A little more research and that line in the README was only added, along with the feature to support "AWS credential" credential type, 14 days ago (27 April 2018) [ https://github.com/jenkinsci/pipeline-aws-plugin/pull/82 ] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jacob Keller commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields Yes, please. Additional testing would be a huge benefit. You can even use the one compiled by the pull request build tester found at https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgit-plugin/detail/PR-578/11/artifacts Specifically https://ci.jenkins.io/job/Plugins/job/git-plugin/job/PR-578/11/artifact/target/git.hpi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27621) Jenkins is not an Item
Title: Message Title James Nord updated an issue Jenkins / JENKINS-27621 Jenkins is not an Item Change By: James Nord Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27621) Jenkins is not an Item
Title: Message Title James Nord commented on JENKINS-27621 Re: Jenkins is not an Item came up again today. We want a permission X to be able to define something at an abitrary level in Jenkins (be it at the root, or at the folder). AFAICT this today (without abusing the system) requires 2 permissions, one scoped to Item and one scoped to Jenkins. in reality it should be the same permission just granted on a different thing... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27621) Jenkins is not an Item
Title: Message Title James Nord edited a comment on JENKINS-27621 Re: Jenkins is not an Item came up again today.We want a permission X to be able to define something at an abitrary level in Jenkins (be it at the root, or at the folder).AFAICT this today (without abusing the system) requires 2 permissions, one scoped to Item and one scoped to Jenkins. in reality it should be the same permission just granted on a different thing... tem.getFullName() handling -> we already have that. delete() can be made to throw an error (access denied or the ilk)onCopiedFrom() should be a no op as you can never create a new JenkinsonLoad() whould be a no-opWhat may be the sticking point is that you may somehow be able to create a new job X from Jenkins (but I think that is disallowed anyway by virtue of the source job being a parent of the new job.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51267) Warnings polluted with unrelated Qt MSBuild warnings
Title: Message Title Łukasz Wojniłowicz created an issue Jenkins / JENKINS-51267 Warnings polluted with unrelated Qt MSBuild warnings Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-05-11 15:57 Environment: Jenkins ver. 2.121 Priority: Minor Reporter: Łukasz Wojniłowicz There is a issue with many unrelated warnings reported when compiling KMyMoney project on MSVC here. The MSBuild Warnings shows warning for e.g. Qt, while it should show warnings only for KMyMoney. Please read more about this issue here Add Comment
[JIRA] (JENKINS-51226) debian package must depend on *some* jre
Title: Message Title
vila commented on JENKINS-51226
Re: debian package must depend on *some* jre
diff --git a/deb/build/debian/control b/deb/build/debian/control index 2ea8ca2..8808fd3 100644 — a/deb/build/debian/control +++ b/deb/build/debian/control @@ -8,7 +8,7 @@ Homepage: @@HOMEPAGE@@ Package: @@ARTIFACTNAME@@ Architecture: all -Depends: ${misc:Depends}, daemon, adduser, procps, psmisc, net-tools -Conflicts: hudson +Depends: ${misc:Depends}, daemon, adduser, procps, psmisc, net-tools, default-jre-headless (>= 2:1.8) +Conflicts: hudson, default-jre-headless (>= 2:1.9) Replaces: hudson Description: @@DESCRIPTION_FILE@Kohsuke Kawaguchi With the patch above, 'apt-get install jenkins' works again (and installs with java8) but should fail with java9 I've tested it on bare ubuntu 16.04.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Code changed in jenkins User: Jesse Glick Path: pom.xml src/test/java/org/jenkinsci/plugins/docker/workflow/DockerDSLTest.java http://jenkins-ci.org/commit/docker-workflow-plugin/d56b6d232b56e8d59d6176697ae6a1b1ecd99455 Log: Merge pull request #137 from jglick/release-JENKINS-38018 JENKINS-38018 Preparing for release Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/cf80d9e2f628...d56b6d232b56 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38018) withDockerRegistry fails to authenticate with DockerHub
Title: Message Title Jesse Glick commented on JENKINS-38018 Re: withDockerRegistry fails to authenticate with DockerHub Fix released in docker-workflow 1.16. Probably I should file separate issues for the other two plugins, but I am too lazy. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51268) Passwords in forms are returned back to client
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51268 Passwords in forms are returned back to client Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-11 17:02 Environment: Jenkins 2.107.2 Priority: Minor Reporter: Maxim Titov Passwords in forms are stored in base64 and returned back to client. In case the internal attacker has the access to Jenkins` home directory, the attacker will be able to decrypt the passwords without any additional efforts using the secret key located in the same directory. Is there any option to return empty form keeping password stored elsewhere or encrypt form password with some random key? Add Comment
[JIRA] (JENKINS-51269) Do not return session id back to client
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51269 Do not return session id back to client Issue Type: Bug Assignee: Unassigned Attachments: Screenshot_1.png Components: core Created: 2018-05-11 17:16 Environment: Jenkins 2.107.2 Priority: Minor Reporter: Maxim Titov Do not return JSESSIONID in response headers back to client. Could be used by attacker to steal active session in case it's protected by 'httpOnly' flag. GET https:///whoAmI/ Add Comment
[JIRA] (JENKINS-51270) Anti-CSRF token exposed & static
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51270 Anti-CSRF token exposed & static Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-11 17:20 Environment: Jenkins 2.107.2 Priority: Minor Reporter: Maxim Titov In some cases the Jenkins-crumb-token, utilized as countermeasure against CSRF attacks, is sent via URI parameters. Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the “Referer” header when any off-site links are followed. Placing tokens into the URL increases the risk that they will be captured by an attacker. Also the anti-CSRF token is constant for each user and did not change from session to session. Thus, in case an attacker steals victim`s token, he will be able to perform CSRF attacks against him. Add Comment
[JIRA] (JENKINS-49392) Violations plugin freezes project settings screen
Title: Message Title Petr H commented on JENKINS-49392 Re: Violations plugin freezes project settings screen I encountered a very similar issue during the Jenkins startup after it's been updated from 2.107.2 to 2.107.3. Downgraded to 2.107.2 for now and will look into the possibility to remove the Violations plugin. During the startup jenkins.log ends up at: May 11, 2018 6:45:12 PM jenkins.InitReactorRunner$1 onAttained INFO: Prepared all plugins And one thread can be seen utilizing 100% CPU and doing the following: "Initializing plugin sonar" #34 daemon prio=5 os_prio=0 tid=0x7fc6e400e800 nid=0x4700 runnable [0x7fc7129cb000] java.lang.Thread.State: RUNNABLE at org.kxml2.io.KXmlParser.next(Unknown Source) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor$ParseMessages.toTag(FindBugsDescriptor.java:141) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor$ParseMessages.doIt(FindBugsDescriptor.java:123) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor$ParseMessages.execute(FindBugsDescriptor.java:115) at hudson.plugins.violations.parse.ParseXML.parse(ParseXML.java:44) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor.parseMessages(FindBugsDescriptor.java:102) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor.parseMessages(FindBugsDescriptor.java:93) at hudson.plugins.violations.types.findbugs.FindBugsDescriptor.(FindBugsDescriptor.java:88) at hudson.plugins.violations.TypeDescriptor.(TypeDescriptor.java:95) at org.jenkinsci.plugins.jvcts.config.ViolationsToBitbucketServerConfigHelper.createNewConfig(ViolationsToBitbucketServerConfigHelper.java:38) at org.jenkinsci.plugins.jvcts.ViolationsToBitbucketServerDescriptor.(ViolationsToBitbucketServerDescriptor.java:31) at org.jenkinsci.plugins.jvcts.ViolationsToBitbucketServerRecorder.(ViolationsToBitbucketServerRecorder.java:23) at sun.misc.Unsafe.ensureClassInitialized(Native Method) at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43) at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:142) at java.lang.reflect.Field.acquireFieldAccessor(Field.java:1088) at java.lang.reflect.Field.getFieldAccessor(Field.java:1069) at java.lang.reflect.Field.get(Field.java:393) at net.java.sezpoz.IndexItem.instance(IndexItem.java:185) at hudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:353) at hudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:232) at hudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:526) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAd
[JIRA] (JENKINS-51271) Refresh token is not invalidated
Title: Message Title Maxim Titov created an issue Jenkins / JENKINS-51271 Refresh token is not invalidated Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-05-11 17:32 Environment: Jenkins 2.107.2 Priority: Major Reporter: Maxim Titov The refresh token (ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE cookie) is not invalidated on the server side after user logout. A user could still use the token in tailored requests in case he has logged out from the application. If a potential malefactor can steal the refresh token, he will have the large window (around two weeks) of time for malicious activity. Additionally, it should be noted that the lifetime of the token is set to two weeks period that provides to the attacker a wide time range for malicious activities on behalf of the victim. Add Comment
[JIRA] (JENKINS-51272) Restore pusher service as a socket.io service with basic ping command support
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-51272 Restore pusher service as a socket.io service with basic ping command support Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-05-11 17:52 Priority: Minor Reporter: R. Tyler Croy I had previously removed the pusher service when we switched to Node.js, and it's time to bring it back. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51273) Inconsistent Declarative Behavior in Yaml File vs legacy podTemplate
Title: Message Title Matthew Ludlum created an issue Jenkins / JENKINS-51273 Inconsistent Declarative Behavior in Yaml File vs legacy podTemplate Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-05-11 18:05 Priority: Major Reporter: Matthew Ludlum Depending on the type of declarative pipeline, you can experience inconsistent behavior and inheritance of variables. Using the SSH Agent example, you can see that the container and sshAgent wrappers do not always play nice. https://github.com/MattLud/kubernetes-plugin/commit/3488e1ff1e7d5195616883a9a18dcd593ba29397 The take away is that using the legacy pod template WITH declarative pipeline is the only one that works. The rest, declarative and fromYaml with declarative and declarative pipeline, fail to work inside the sshAgent block. Add Comment
[JIRA] (JENKINS-51274) Blue Ocean "Create Pipeline" does not accept "ext:..." URLs for git repositories
Title: Message Title E H created an issue Jenkins / JENKINS-51274 Blue Ocean "Create Pipeline" does not accept "ext:..." URLs for git repositories Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-05-11 18:06 Environment: macOS 10.12.6, java 1.8.0_172-b11 Priority: Minor Reporter: E H I installed the Blue Ocean plugin in a new jenkins instance to try it out. It asks me to create a pipeline (since there are none yet). However, it will not accept "ext::..." style URLs for the git repository, says "Repository URL - Please enter a valid URL." Steps to Reproduce: Install Jenkins, Blue Ocean. Open Blue Ocean Create a pipeline Select "Git" for "Where do you store your code?" Enter an "ext:..." url like "ext::/usr/local/bin/script.sh user@host.domain %S REPONAME". Click the "Create Pipeline" button. Expected Results: Blue Ocean continues to the next step. Actual Results: Blue Ocean does not continue on and a " Repository URL - Please enter a valid URL." message is shown. A
[JIRA] (JENKINS-51274) Blue Ocean "Create Pipeline" does not accept "ext:..." URLs for git repositories
Title: Message Title E H updated an issue Jenkins / JENKINS-51274 Blue Ocean "Create Pipeline" does not accept "ext:..." URLs for git repositories Change By: E H Environment: macOS 10.12.6, java 1.8.0_172-b11 , Jenkins 2.107.3, Blue Ocean 1.5.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title
Christian Höltje commented on JENKINS-51057
Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM
I finally got VirtualVM working reasonably well (using lots of RAM and a RAM Disk for temp files). I found that there are 0 instances of org.jenkinsci.plugins.ssegateway.EventHistoryStore and 0 instances of org.jenkinsci.plugins.ssegateway.sse.EventDispatcher. Is it possible that the Retry objects are not being reclaimed by GC? When I look at the objects in VirtualVM the Retry object has a reference (item) to a ConcurrentLinkedQueue$Node object. The Node object has a reference (item) to the Retry object plus a reference to the next {{Node} in the queue.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51046) Tool to incrementalify POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51046 Re: Tool to incrementalify POM Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/dd139d3d04ccf830383c81f72759c62903f7974f Log: JENKINS-51046 Ready POMs for incrementals:incrementalify. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-51057 EventDispatcher and ConcurrentLinkedQueue ate my JVM Change By: Christian Höltje Labels: leak memory memory-leak Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51247 Re: Move flattened POM into target directory Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/753d0856d9fdef5aa526d8ed154aa242bd7a8144 Log: Merge pull request #105 from jglick/flatten JENKINS-51247 Simplified usage of flatten-maven-plugin Compare: https://github.com/jenkinsci/plugin-pom/compare/f8a5e377fe2d...753d0856d9fd *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51247 Re: Move flattened POM into target directory Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/plugin-pom/e4689b8d5f6e76a755f09adbdb7b3fc8c301f8ea Log: JENKINS-51247 source:jar, not source:jar-no-fork Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51247 Re: Move flattened POM into target directory Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/pom/3770b93a9478e56584a02a792f8929ccf44e Log: Merge pull request #24 from jglick/flatten JENKINS-51247 Simplified usage of flatten-maven-plugin Compare: https://github.com/jenkinsci/pom/compare/54d67630d3e7...3770b93a9478 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51247) Move flattened POM into target directory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51247 Re: Move flattened POM into target directory Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/pom/e940c43f7ddc29ae44503bb58a1d8df82ce8d2f2 Log: JENKINS-51247 source:jar, not source:jar-no-fork Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
