date:20170328

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Unfortunately this is a sharp corner that didn't make the release. We will be starting work on it next week and will have a release that contains it out shortly after that. Closing as duplicate of JENKINS-41960.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-43172  
 
 
  Cannot change Stage name after adding parallel branch in Blue Ocean editor
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
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"

[JIRA] (JENKINS-41960) Developer can change the stage level configuration

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41960  
 
 
  Developer can change the stage level configuration   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 

  
 
 
 
 

 
 *Scope** Hovering over a stage column reveals the stage handle* Clicking anywhere on the stage name or stage handle changes the sheet changes to show the config for the selected stage*  Change the stage name*  Developer can see settings for:** Agent** Environment  
 

  
 
 
 
 

 
 
 

 
 
 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-43180) Multi Axis name "-" validation

2017-03-28 Thread danielahcard...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Alejandro Hernández created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43180  
 
 
  Multi Axis name "-" validation   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Attachments: 
 invalid.PNG, invalidError.PNG  
 
 
Components: 
 matrix-project-plugin  
 
 
Created: 
 2017/Mar/29 3:53 AM  
 
 
Environment: 
 Jenkins 2.19.4 Plugin version: 1.9  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Alejandro Hernández  
 

  
 
 
 
 

 
 When creating a Multi configuration job, you can create an axis with name including "-", for example: axi-name and there is no error validation warning that is invalid. Create a "Combination filter" : (axi_name.toString().contains('1') || axi_name.toString().contains('2'))    When you try to save it you get:    Besides that, if you use underscore you can solve the problem, for example: axi_name And the combination filter:  (axi_name.toString().contains('1') || axi_name.toString().contains('2'))

[JIRA] (JENKINS-43179) Configuration Empty droplist when adding workspace cleanup include/exclude patterns

2017-03-28 Thread w...@csie.org (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chen-Yu Tsai created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43179  
 
 
  Configuration Empty droplist when adding workspace cleanup include/exclude patterns   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oliver Gondža  
 
 
Attachments: 
 delete_workspace_empty_dropdown_select.png  
 
 
Components: 
 ws-cleanup-plugin  
 
 
Created: 
 2017/Mar/29 2:54 AM  
 
 
Environment: 
 Jenkins 2.52  Workspace Cleanup Plugin 0.32  Chrome 57.0.2987.110 (64-bit) on Windows 10  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Chen-Yu Tsai  
 

  
 
 
 
 

 
 Recently while trying to add new jobs, I found that I cannot add include/exclude patterns to  the workspace cleanup step. The dropdown select box is empty, where it used to have INCLUDE/EXCLUDE options. For existing jobs, existing pattern entries continue to work, but one cannot add new entries, as shown in the attached screenshot. There are also 4 _javascript_ errors in the page (domain name obfuscated): select.js:8 Uncaught TypeError: Cannot read property 'firstChild' of undefined {{ at updateListBox (https://ci.xxx.xxx/adjuncts/e62d70f0/lib/form/select/select.js:8:67)}} {{ at https://ci.xxx.xxx/adjuncts/e62d70f0/lib/form/select/select.js:79:13}} {{ at h (https://ci.xxx.xxx/static/e62d70f0/scripts/hudson-behavior.js:1294:9)}} {{ at refillOnChange (https://ci.xxx.xxx/static/e62d70f0/scripts/hudson-behavior.js:1309:5)}} {{ at https://ci.xxx.xxx/adjuncts/e62d70f0/lib/form/select/select.js:77:9}} {{ at Array.forEach (native)}} {{ at https://ci.xxx.xxx/static/e62d70f0/scripts/behavior.js:111:30}} {{ at Array.forEach (native)}} {{ at https://ci.xxx.xxx/static/e62d70f0/scripts/behavior.js:107:27}} {{ at Array.forEach

[JIRA] (JENKINS-42667) Job fails due to timeout when destroying docker container

2017-03-28 Thread b...@mathews2000.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Mathews updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42667  
 
 
  Job fails due to timeout when destroying docker container   
 

  
 
 
 
 

 
Change By: 
 Ben Mathews  
 

  
 
 
 
 

 
 Since the last update (version 1.10, which included a timeout for docker operations - commit 3f8a83fbacdce1e3d286cf1790182a89d9f6cd11), our pipelines began to fail at the end of a stage, when removing the temporary container.The steps run inside the container are executed without a problem (and take several minutes), but when the plugin stops and removes the container created to run commands inside, the 10s timeout ends the build as failure.My suggestion would be to remove the timeout for this operation, or not to fail the build when it happens (it is just removing a temporary container, after what really matters was executed successfully). PS: when rolled back to Docker Pipeline 1.9.1, everything worked back as it should. Below are the related log entries of one job that represent this problem:[Pipeline] }[Pipeline] // stage[Pipeline] }$ docker stop --time=1 033ff889f75dad2e4d59fdc7e31a604bb352da84eda43e7c3f4803bbfc3bf338$ docker rm -f 033ff889f75dad2e4d59fdc7e31a604bb352da84eda43e7c3f4803bbfc3bf338ERROR: Timeout after 10 seconds[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Failed to rm container '033ff889f75dad2e4d59fdc7e31a604bb352da84eda43e7c3f4803bbfc3bf338'. at org.jenkinsci.plugins.docker.workflow.client.DockerClient.rm(DockerClient.java:158) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.stop(DockerClient.java:145) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.destroy(WithContainerStep.java:107) at org.jenkinsci.plugins.docker.workflow.WithContainerStep.access$400(WithContainerStep.java:74) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Callback.finished(WithContainerStep.java:302) at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:362) at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:146) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at

[JIRA] (JENKINS-40355) P4 hangs on reconcile call

2017-03-28 Thread collumbr...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Collum commented on  JENKINS-40355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4 hangs on reconcile call   
 

  
 
 
 
 

 
 Hey Matthew Smith, no we never resolved it per se. But we have not actually run into this since I entered this 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-43147) Support Request Body for HTTP DELETE

2017-03-28 Thread janario.olive...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43147  
 
 
  Support Request Body for HTTP DELETE   
 

  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
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-43178) Can't send email to unknown email address

2017-03-28 Thread da...@vanlaatum.id.au (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43178  
 
 
  Can't send email to unknown email address   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 

  
 
 
 
 

 
 Security patch broke it.  If configured email is not attached to a know user fails to send email with   Not sending mail to unregistered user x...@example.com    
 

  
 
 
 
 

 
 
 

 
 
 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-43178) Can't send email to unknown email address

2017-03-28 Thread da...@vanlaatum.id.au (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43178  
 
 
  Can't send email to unknown email address   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David van Laatum  
 
 
Components: 
 email-ext-plugin  
 
 
Created: 
 2017/Mar/29 1:40 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 David van Laatum  
 

  
 
 
 
 

 
 Security patch broke it.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-43147) Support Request Body for HTTP DELETE

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-43147  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support Request Body for HTTP DELETE   
 

  
 
 
 
 

 
 Code changed in jenkins User: Janario Oliveira Path: src/main/java/jenkins/plugins/http_request/util/HttpBodyDelete.java src/main/java/jenkins/plugins/http_request/util/HttpClientUtil.java http://jenkins-ci.org/commit/http-request-plugin/670eefcf988afd1788da3ccd5429246422f367b7 Log: JENKINS-43147 - Added support to send body in delete method  
 

  
 
 
 
 

 
 
 

 
 
 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-42131) JDL Dropdowns in wrong place on Firefox

2017-03-28 Thread jmcdon...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald commented on  JENKINS-42131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDL Dropdowns in wrong place on Firefox   
 

  
 
 
 
 

 
 This may hold the key to our solution: https://github.com/tajo/react-portal  
 

  
 
 
 
 

 
 
 

 
 
 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-42785) Parameterized Pipeline Projects have their Build Triggers unset after each build

2017-03-28 Thread keit...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zubot-Gephart commented on  JENKINS-42785  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Pipeline Projects have their Build Triggers unset after each build   
 

  
 
 
 
 

 
 Fair enough! Well for my part at least, I can confirm adding a triggers{} section solved the problem, so many thanks   
 

  
 
 
 
 

 
 
 

 
 
 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-32167) ISVNAuthentication provider did not provide credentials

2017-03-28 Thread stephen.mcca...@hcs.us.com (JIRA)

Title: Message Title

Stephen McCants commented on JENKINS-32167

Re: ISVNAuthentication provider did not provide credentials

Jesse Glick, playing some with the unit test you created, I realized it is a different use case then the one I'm using in my production Jenkins environment. I have externals that point to the same SVN server and can use the same user id/password to get data from the externals and the main project. I've refactored your unit test into that situation with only one SVN server, but still two repositories - one using the other as an external. It almost passes without additionalCredentials. That resulted in a couple of thoughts:

The reason it almost passes is because it is lucky enough to find the defaultCredentials in RemotableSVNAuthenticationBuilderProvider.getBuilder(String realm) every step of the way until SubversionSCM.checkout(...) calls the BuildRevisionMapTask constructor, which always builds the defaultAuthProvider with a null location value. The null location means it won't have default credentials and must have additionalCredentials to succeed.

Should you ever be allowed to have no default credentials?
Should the code warn/error if there are no default credentials and no additional credentials? Maybe in the CredentialsSVNAuthenticationProviderImpl constructor?
Does it make sense to cache credentials against realms where they have previously worked? That would work around this problem without providing additional credentials that are duplicates of the default.

Would you be interested in my unit test (I'd polish it a little more before sending it along)?
I was tripped up in my production environment because of a difference in realms between a full qualified host name and an unqualfied hostname. That I provided additional credentials for the realm " Subversion repository", but it was looking for " Subversion repository" based on the way the external had been configured. It would be preferable if the final solution was smart enough to handle fully qualified host names, IP addresses and unqualified host names.

Add Comment

[JIRA] (JENKINS-43177) env.WHATEVER not considered for environment variable cross reference resolution in Declarative

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-43177  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: env.WHATEVER not considered for environment variable cross reference resolution in Declarative   
 

  
 
 
 
 

 
 One risk of a fix I've got almost done is that it could turn 

 

environment {
  FOO = "foo"
  BAR = "${env.FOO} and env.Should not change"
} 

 into BAR == "foo and Should not change" - so I'm poking around to make sure I can do that replacement solely in the curlies.  
 

  
 
 
 
 

 
 
 

 
 
 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-43102) Add support for arm platform

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-43102  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add support for arm platform   
 

  
 
 
 
 

 
 Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/CPU.java src/main/java/jenkins/plugins/nodejs/tools/pathresolvers/LatestInstallerPathResolver.java src/test/java/jenkins/plugins/nodejs/tools/ArchitectureCallableTest.java src/test/java/jenkins/plugins/nodejs/tools/InstallerPathResolversTest.java src/test/resources/jenkins/plugins/nodejs/tools/expectedURLs.txt http://jenkins-ci.org/commit/nodejs-plugin/ba9eb55c88f4c521cb5004c6566f79ac370e7a05 Log: JENKINS-43102 Add a tentative support for ARM CPUs (armv7l, armv6l, arm64)  
 

  
 
 
 
 

 
 
 

 
 
 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-43177) env.WHATEVER not considered for environment variable cross reference resolution in Declarative

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43177  
 
 
  env.WHATEVER not considered for environment variable cross reference resolution in Declarative   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2017/Mar/28 11:57 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Andrew Bayer  
 

  
 
 
 
 

 
 With an environment section like this: 

 

environment {
  FOO = "something"
  BAR = "${env.FOO} else"
} 

 The EnvVars-driven environment variable resolution/expansion doesn't know that env.FOO means that it needs to resolve FOO before resolving BAR, so there's no guarantee that'll actually happen in that order, and you may well get BAR as null else.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-43177) env.WHATEVER not considered for environment variable cross reference resolution in Declarative

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-43177  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-41275) Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41275  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)   
 

  
 
 
 
 

 
 Incorporated this into the fix for JENKINS-42521 at https://github.com/jenkinsci/workflow-support-plugin/pull/31  
 

  
 
 
 
 

 
 
 

 
 
 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-41275) Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-41275  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41275  
 
 
  Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-41275) Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-41275  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-41275) Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41275  
 
 
  Add way to easily test currentBuild result is better/worse than some value (isBetterOrEqualTo)   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 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-41708) StackOverFlowError thrown when launching a PipelineJob, PogoMetaClassSite

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41708  
 
 
  StackOverFlowError thrown when launching a PipelineJob, PogoMetaClassSite   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Issue Type: 
 Patch Bug  
 
 
Component/s: 
 workflow-cps-plugin  
 
 
Component/s: 
 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-41998) 'bat' step fails if configured agent overrides system path

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41998  
 
 
  'bat' step fails if configured agent overrides system path   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 workflow-durable-task-step-plugin  
 
 
Component/s: 
 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-41045) Support ExtendedChoiceParameterDefinition plugin

2017-03-28 Thread kuber.k...@dowjones.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kuber Kaul commented on  JENKINS-41045  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support ExtendedChoiceParameterDefinition plugin   
 

  
 
 
 
 

 
 James Dumay - thanks  
 

  
 
 
 
 

 
 
 

 
 
 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-43176) MercurialChangeLogParser fails in parallel checkouts

2017-03-28 Thread sociallya...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Yap updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43176  
 
 
  MercurialChangeLogParser fails in parallel checkouts   
 

  
 
 
 
 

 
Change By: 
 Victor Yap  
 

  
 
 
 
 

 
 Using parallel nodes and checkout sometimes causes the following error:{code:java}hudson.util.IOException2: Failed to parse /var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml: '  ' at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:55) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:26) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:746) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1500(WorkflowRun.java:125) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:936) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:123) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Suppressed: hudson.util.IOException2: Failed to parse /var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml: '  ' ... 16 more Caused by: org.xml.sax.SAXParseException; systemId: file:/var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml; lineNumber: 3; columnNumber: 1; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1239) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at org.apache.commons.digester.Digester.parse(Digester.java:1871) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:51) ... 15 more Caused by: org.xml.sax.SAXParseException; systemId: file:/var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml; lineNumber: 3; columnNumber: 1; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1239) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at org.apache.commons.digester.Digester.parse(Digester.java:1871) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:51) ... 15 more

[JIRA] (JENKINS-41999) Multiple nested closures and withEnv in CPS Global seem to nullify the env singleton

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-41999  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multiple nested closures and withEnv in CPS Global seem to nullify the env singleton   
 

  
 
 
 
 

 
 Yeah, looks like you need the closure test - i.e., Closure test = config.test, to get its delegate set.   
 

  
 
 
 
 

 
 
 

 
 
 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-43176) MercurialChangeLogParser fails in parallel checkouts

2017-03-28 Thread sociallya...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Yap updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43176  
 
 
  MercurialChangeLogParser fails in parallel checkouts   
 

  
 
 
 
 

 
Change By: 
 Victor Yap  
 

  
 
 
 
 

 
 Using parallel nodes and checkout sometimes causes the following error: {code:java} hudson.util.IOException2: Failed to parse /var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml: '' at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:55) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:26) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:746) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1500(WorkflowRun.java:125) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:936) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:123) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Suppressed: hudson.util.IOException2: Failed to parse /var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml: ''  ... 16 more Caused by: org.xml.sax.SAXParseException; systemId: file:/var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml; lineNumber: 3; columnNumber: 1; XML document structures must start and end within the same entity.  at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1239)  at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643)  at org.apache.commons.digester.Digester.parse(Digester.java:1871)  at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:51)  ... 15 moreCaused by: org.xml.sax.SAXParseException; systemId: file:/var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml; lineNumber: 3; columnNumber: 1; XML document structures must start and end within the same entity. at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1239) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:643) at org.apache.commons.digester.Digester.parse(Digester.java:1871) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:51) ... 15

[JIRA] (JENKINS-43176) MercurialChangeLogParser fails in parallel checkouts

2017-03-28 Thread sociallya...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Yap created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43176  
 
 
  MercurialChangeLogParser fails in parallel checkouts   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 parallel-test-fail.png, parallel-test-pass.png  
 
 
Components: 
 mercurial-plugin  
 
 
Created: 
 2017/Mar/28 10:49 PM  
 
 
Environment: 
 Operating System: Centos 7.2, 64-bit  JDK: 1.8.0  Jenkins: 2.48  Mercurial Plugin: 1.59  Running Jenkins directly  No reverse proxy  installed via yum  issue occurs on the master node  
 
 
Labels: 
 mercurial checkout  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Victor Yap  
 

  
 
 
 
 

 
 Using parallel nodes and checkout sometimes causes the following error: hudson.util.IOException2: Failed to parse /var/lib/jenkins/jobs/parallel-test/builds/28/changelog0.xml: '  ' at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:55) at hudson.plugins.mercurial.MercurialChangeLogParser.parse(MercurialChangeLogParser.java:26) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:746) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1500(WorkflowRun.java:125) at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:936) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:123) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83) at

[JIRA] (JENKINS-42620) java.lang.NoSuchMethodError: No such DSL method 'pipeline' found error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-42620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.NoSuchMethodError: No such DSL method 'pipeline' found error   
 

  
 
 
 
 

 
 Looks like you don't have the Pipeline: Model Definition plugin installed.  
 

  
 
 
 
 

 
 
 

 
 
 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-42620) java.lang.NoSuchMethodError: No such DSL method 'pipeline' found error

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42620  
 
 
  java.lang.NoSuchMethodError: No such DSL method 'pipeline' found error   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42635) Passing Closures to NonCPS Library Function give strange results

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Like I said over on JENKINS-42769, this is our old hated friend JENKINS-26481 in yet another form. Quoting from what I said there in case people stumble across this: 

In the end, this (and the issue you linked to) is a symptom of JENKINS-26481 - when you call a CPS-transformed method within (or pass a CPS-transformed closure to) non-CPS-transformed code, it gets...weird. As you saw, what you end up getting is often the return value from the first closure to "complete" in that scope. Basically, @NonCPS code can't call functions defined in CPS-transformed code and can't do anything with a Closure from CPS-transformed code. You'll need to find another way to pass the data you need into the @NonCPS function as parameters, rather than it calling a CPS-transformed function.
  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42635  
 
 
  Passing Closures to NonCPS Library Function give strange results   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-42667) Job fails due to timeout when destroying docker container

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42667  
 
 
  Job fails due to timeout when destroying docker container   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 docker-workflow-plugin  
 
 
Component/s: 
 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-42769) NonCPS function returns wrong results!

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 In the end, this (and the issue you linked to) is a symptom of JENKINS-26481 - when you call a CPS-transformed method within (or pass a CPS-transformed closure to) non-CPS-transformed code, it gets...weird. As you saw, what you end up getting is often the return value from the first closure to "complete" in that scope. Basically, @NonCPS code can't call functions defined in CPS-transformed code and can't do anything with a Closure from CPS-transformed code. You'll need to find another way to pass the data you need into the @NonCPS function as parameters, rather than it calling a CPS-transformed function.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42769  
 
 
  NonCPS function returns wrong results!   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-42779) groovy.lang.MissingFieldException: No such field: binding for class: WorkflowScript

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-42779  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: groovy.lang.MissingFieldException: No such field: binding for class: WorkflowScript   
 

  
 
 
 
 

 
 I'll defer to Kohsuke Kawaguchi or Jesse Glick, but I don't think binding is supposed to be available at the user level here.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42785) Parameterized Pipeline Projects have their Build Triggers unset after each build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-42785  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameterized Pipeline Projects have their Build Triggers unset after each build   
 

  
 
 
 
 

 
 So...this brings up a good question! The root cause here is that job parameters, triggers and other misc job properties are all set in Pipeline (including Declarative, albeit behind the scenes) with the properties step...which overwrites whatever was previously in the job properties/triggers/parameters. So if you have parameters in your Declarative Pipeline but not triggers, your triggers are always going to get wiped out. The quiet period and remote trigger bit are technically not part of the triggers which is why they stay set. Is weird, I know. So a workaround for this for you would be to use this as your Jenkinsfile: 

 

pipeline {
    agent any
    parameters {
       string(name: 'requested', defaultValue: 'all', description: 'Which stages should be run?')
    }
triggers {
cron('@daily')
pollSCM('@hourly')
githubPush()
upstream(threshold: hudson.model.Result.SUCCESS, upstreamProjects: "some-project,some-other-project")
}
    stages {
       stage('stage1') {
          steps {
             echo 'Running stage 1'
          }
       }
    }
 } 

 I'm not 100% sure upstream will work right - it should but I honestly can't remember for sure. But the other three certainly will. The question this all raises is whether Declarative should allow the UI-configured job properties/parameters/triggers to persist if they're not explicitly overridden. I'm not sure yet, which is why I'm leaving this open. =)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-42785) Parameterized Pipeline Projects have their Build Triggers unset after each build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42785  
 
 
  Parameterized Pipeline Projects have their Build Triggers unset after each build   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 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-42785) Parameterized Pipeline Projects have their Build Triggers unset after each build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42785  
 
 
  Parameterized Pipeline Projects have their Build Triggers unset after each build   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Issue Type: 
 Bug Story  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42785) Parameterized Pipeline Projects have their Build Triggers unset after each build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42785  
 
 
  Parameterized Pipeline Projects have their Build Triggers unset after each build   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-40355) P4 hangs on reconcile call

2017-03-28 Thread matthew.k.sm...@viasat.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Smith commented on  JENKINS-40355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: P4 hangs on reconcile call   
 

  
 
 
 
 

 
 Hi Brian, did you ever resolve this issue? We are seeing the same 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-42807) Shared-Library Import without def causes MultipleCompilationErrorsException

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 So you need to follow @Library('shared-lib@master') with _ - yes, an underscore. It's annoying, but the annotation needs to be on something, and a method call doesn't count. Sorry for the inconvenience!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42807  
 
 
  Shared-Library Import without def causes MultipleCompilationErrorsException   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues"

[JIRA] (JENKINS-42785) Parameterized Pipeline Projects have their Build Triggers unset after each build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42785  
 
 
  Parameterized Pipeline Projects have their Build Triggers unset after each build   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 pipeline-model-definition-plugin  
 
 
Component/s: 
 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-42836) Build parameter not expanded in script path

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42836  
 
 
  Build parameter not expanded in script path   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42860  
 
 
  RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 github-branch-source-plugin  
 
 
Component/s: 
 github-oauth-plugin  
 
 
Component/s: 
 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-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42860  
 
 
  RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Sam Gleske Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42988) Batch command hang upon completion

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42988  
 
 
  Batch command hang upon completion   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42988) Batch command hang upon completion

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42988  
 
 
  Batch command hang upon completion   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 workflow-durable-task-step-plugin  
 
 
Component/s: 
 batch-task-plugin  
 
 
Component/s: 
 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-43033) Suppress Sleep Step Output

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43033  
 
 
  Suppress Sleep Step Output   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 workflow-basic-steps-plugin  
 
 
Component/s: 
 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-42988) Batch command hang upon completion

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42988  
 
 
  Batch command hang upon completion   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 windows-slaves-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43104) Declarative pipeline branch condition not working

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-43104  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Declarative pipeline branch condition not working   
 

  
 
 
 
 

 
 Try just 

 

branch "master" 

 maybe? If that doesn't work either, could you try this instead of branch to see what its output is? 

 

_expression_ {
  echo "BRANCH_NAME is ${env.BRANCH_NAME}"
  return env.BRANCH_NAME == "master"
} 

 Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 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-43106) pipeline job hangs sporadically at checkout GitSCM

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43106  
 
 
  pipeline job hangs sporadically at checkout GitSCM   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 git-plugin  
 
 
Component/s: 
 github-branch-source-plugin  
 
 
Component/s: 
 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-43104) Declarative pipeline branch condition not working

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43104  
 
 
  Declarative pipeline branch condition not working   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 pipeline-model-definition-plugin  
 
 
Component/s: 
 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-43104) Declarative pipeline branch condition not working

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43104  
 
 
  Declarative pipeline branch condition not working   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38005  
 
 
  Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
 Not sure about the step result aspect - I can never remember how that actually gets set. But at a minimum, this will definitely log an error. If it turns out to still not cause the step in Blue Ocean to know it failed, we can revisit.  
 

  
 
 
 
 

 
 
 

 
 
 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

2017-03-28 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38005  
 
 
  Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
Change By: 
 Michael Neale  
 
 
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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

2017-03-28 Thread mne...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
 gosh that is terrible. The step result isn't failure, and there is no log message.   
 

  
 
 
 
 

 
 
 

 
 
 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-43175) java.lang.NullPointerException at hudson.plugins.cmake.CmakeBuilder.perform(CmakeBuilder.java:265)

2017-03-28 Thread fzbass...@yahoo.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eric Wallengren created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43175  
 
 
  java.lang.NullPointerException at hudson.plugins.cmake.CmakeBuilder.perform(CmakeBuilder.java:265)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 cmakebuilder-plugin  
 
 
Created: 
 2017/Mar/28 10:17 PM  
 
 
Environment: 
 Windows 7  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Eric Wallengren  
 

  
 
 
 
 

 
 After creating a DSL job using the following closure:  cmake  { cmakeInstallation('InSearchPath') generator('Visual Studio 14 2015') sourceDir('control4') cleanBuild() buildDir('control4/build') } The resulting xml looks like so:   InSearchPath Visual Studio 14 2015 true control4 control4/build -DIGNORE_UNIT_TESTS=1  When I run the job in that configuration the exception reported is thrown. After changing the job (just saving it in the UI) the XML looks like so:   InSearchPath control4/build -DIGNORE_UNIT_TESTS=1 Visual Studio 14 2015 control4 true   And the job runs without complaint. I have no toolSteps defined, nor do I want any (it appears optional anyway). The empty toolSteps element must be set. I am now using the configure closure to work around the issue:  configure { it / builders << 'hudson.plugins.cmake.CmakeBuilder' (plugin: 'cmakebuilder')  { installationName('InSearchPath') workingDir('control4/build') generator('Visual Studio 14 2015') sourceDir('control4') cleanBuild('true') toolSteps() }  } Here's the full stacktrace: 00:00:20.364 java.lang.NullPointerException 00:00:20.364 at hudson.plugins.cmake.CmakeBuilder.perform(CmakeBuilder.java:265) 00:00:20.364 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 00:00:20.364 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 00:00:20.364 at hudson.model.Build$BuildExecution.build(Build.java:205) 00:00:20.364 at

[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
 PR up at https://github.com/jenkinsci/jenkins/pull/2823 with Jesse's suggested patch and a change to the error message.  
 

  
 
 
 
 

 
 
 

 
 
 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-38005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38005  
 
 
  Using archiveArtifacts with a non-matching pattern silently fails the build   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Assignee: 
 Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43060) No success notification is being send

2017-03-28 Thread ford.arnett...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ford Arnett commented on  JENKINS-43060  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No success notification is being send   
 

  
 
 
 
 

 
 I am also experiencing this issue. I thought this was originally a project issue but I have created a new project from scratch and still have the problem. In my case there seems to be a patter to it. If the last run was successful the notification will fire. However, if the last run was a failure the next success will not fire.   
 

  
 
 
 
 

 
 
 

 
 
 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-6748) Analysis of Checkstyle Warnings per User

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-6748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Analysis of Checkstyle Warnings per User   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ulli Hafner Path: analysis-core.iml pom.xml src/main/java/hudson/plugins/analysis/core/AbstractProjectAction.java src/main/java/hudson/plugins/analysis/core/HealthAwarePublisher.java src/main/java/hudson/plugins/analysis/graph/AnnotationsByUserGraph.java src/main/java/hudson/plugins/analysis/graph/BuildResultGraph.java src/main/java/hudson/plugins/analysis/graph/CategoryBuildResultGraph.java src/main/java/hudson/plugins/analysis/graph/UserBuildResultGraph.java src/main/java/hudson/plugins/analysis/util/AbstractBlamer.java src/main/java/hudson/plugins/analysis/util/BlameFactory.java src/main/java/hudson/plugins/analysis/util/BlameInterface.java src/main/java/hudson/plugins/analysis/util/GitBlamer.java src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java src/main/java/hudson/plugins/analysis/util/model/AnnotationContainer.java src/main/java/hudson/plugins/analysis/util/model/Author.java src/main/java/hudson/plugins/analysis/util/model/FileAnnotation.java src/main/java/hudson/plugins/analysis/views/AuthorDetail.java src/main/java/hudson/plugins/analysis/views/DetailFactory.java src/main/java/hudson/plugins/analysis/views/TabDetail.java src/main/resources/hudson/plugins/analysis/views/AuthorDetail/index.jelly src/main/resources/hudson/plugins/analysis/views/TabDetail/authors.jelly src/main/resources/hudson/plugins/analysis/views/TabDetail/warnings.jelly src/main/resources/result/main.jelly http://jenkins-ci.org/commit/analysis-core-plugin/64e45dc705970bac9bdb3cd1fdbe94516bccf61f Log: JENKINS-6748 Integrated the work of Lukas Krose/John Gibson: show culprint of warnings (for git). Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/a3d48bf5f198^...64e45dc70597  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-41045) Support ExtendedChoiceParameterDefinition plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-41045  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support ExtendedChoiceParameterDefinition plugin   
 

  
 
 
 
 

 
 Kuber Kaul not that this stage. We need to do some more work on our extensibility framework in order to have plugins like Extended Choice plugin be able to add their own elements to Blue Ocean.  
 

  
 
 
 
 

 
 
 

 
 
 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-41045) Support ExtendedChoiceParameterDefinition plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41045  
 
 
  Support ExtendedChoiceParameterDefinition plugin   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Summary: 
 Support  PARAMETER_TYPE_SINGLE_SELECT type  ExtendedChoiceParameterDefinition plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42820) Regression in analysis-core:1.82 when browsing warnings

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42820  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Regression in analysis-core:1.82 when browsing warnings   
 

  
 
 
 
 

 
 Code changed in jenkins User: Ulli Hafner Path: analysis-core http://jenkins-ci.org/commit/analysis-suite-plugin/8563f9d921d4c3a691c310dabc3525990cb0549c Log: [FIXED JENKINS-42820] Fixed navigation into warnings by type.  
 

  
 
 
 
 

 
 
 

 
 
 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-41908) Improve Diagnostics: Unable to Assign Groups to Roles

Title: Message Title


 
 
 
 

 
 
 

 
   
 Trent Dailey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41908  
 
 
  Improve Diagnostics: Unable to Assign Groups to Roles   
 

  
 
 
 
 

 
Change By: 
 Trent Dailey  
 
 
Issue Type: 
 Improvement 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-42515) User education empty state updates

2017-03-28 Thread cmey...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-42515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User education empty state updates   
 

  
 
 
 
 

 
 I should note this PR covers all the remaining Pipeline empty states on the Activity, Branches and PR tabs. If we are happy with this and decide to land it before release, I will cut a new ticket that covers the "Run" empty states for Pipeline, Tests, Changes, etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43065) Task Scanner Plugin - Ignore case broken

2017-03-28 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43065  
 
 
  Task Scanner Plugin - Ignore case broken   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-43155) Multiple links and graphics when there are several branches

2017-03-28 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43155  
 
 
  Multiple links and graphics when there are several branches   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 

  
 
 
 
 

 
 When we have several branches in one project  within the Pipeline Multibranch Plugin , task scanner shows multiple links to open tasks (same link), as well as the same number of graphics (the same graphics).See the attached screenshots.  
 

  
 
 
 
 

 
 
 

 
 
 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-43155) Multiple links and graphics when there are several branches

2017-03-28 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43155  
 
 
  Multiple links and graphics when there are several branches   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Component/s: 
 workflow-multibranch-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41908) Improve Diagnostics: Unable to Assign Groups to Roles

Title: Message Title


 
 
 
 

 
 
 

 
   
 Trent Dailey commented on  JENKINS-41908  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Improve Diagnostics: Unable to Assign Groups to Roles   
 

  
 
 
 
 

 
 Hi Oleg, I am having this same issue again and it appears to be tied to the total number of roles I have.  I can add as many roles as I want, but once I get to a certain number of roles it will not allow me to assign a group or user to the roles.  I get the "This page expects a form submission but had only {}" error.  Once I remove a role, I can then got back in and add as many groups as I want to the roles. The new request body has been attached to the 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-41908) Improve Diagnostics: Unable to Assign Groups to Roles

Title: Message Title


 
 
 
 

 
 
 

 
   
 Trent Dailey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41908  
 
 
  Improve Diagnostics: Unable to Assign Groups to Roles   
 

  
 
 
 
 

 
Change By: 
 Trent Dailey  
 
 
Priority: 
 Minor Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-41908) Improve Diagnostics: Unable to Assign Groups to Roles

Title: Message Title


 
 
 
 

 
 
 

 
   
 Trent Dailey updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41908  
 
 
  Improve Diagnostics: Unable to Assign Groups to Roles   
 

  
 
 
 
 

 
Change By: 
 Trent Dailey  
 
 
Attachment: 
 body.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-42048) Cannot Connect, PID NumberFormatException

2017-03-28 Thread jwhitcr...@sugarcrm.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Whitcraft updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42048  
 
 
  Cannot Connect, PID NumberFormatException   
 

  
 
 
 
 

 
Change By: 
 Jon Whitcraft  
 
 
Attachment: 
 Screenshot 2017-03-28 17.05.18.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42515) User education empty state updates

2017-03-28 Thread cmey...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers updated  JENKINS-42515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42515  
 
 
  User education empty state updates   
 

  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 
 
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-42515) User education empty state updates

2017-03-28 Thread cmey...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-42515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User education empty state updates   
 

  
 
 
 
 

 
 PR: https://github.com/jenkinsci/blueocean-plugin/pull/929  
 

  
 
 
 
 

 
 
 

 
 
 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-43170) No credentials injected into managed settings.xml with Pipeline Maven Plugin

2017-03-28 Thread reck...@yatta.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 creckord closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing as invalid. Sorry for the noise, I got it working somehow. I dug around in the sources a bit and noticed that this should work. So I recreated the whole config file setup, credentials and domains, and suddenly it works, although I have no clue why now and not before...  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-43170  
 
 
  No credentials injected into managed settings.xml with Pipeline Maven Plugin   
 

  
 
 
 
 

 
Change By: 
 creckord  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this

[JIRA] (JENKINS-43174) Embed iframe/panel into Jenkins

2017-03-28 Thread radin...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Radinsky created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43174  
 
 
  Embed iframe/panel into Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 FebWG.png  
 
 
Components: 
 core, plugin-proposals  
 
 
Created: 
 2017/Mar/28 8:07 PM  
 
 
Environment: 
 N/A  
 
 
Labels: 
 jenkins plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alex Radinsky  
 

  
 
 
 
 

 
 I have some external web service running (actually it just several web pages) and I'm looking for a way how to embed this system as a panel inside Jenkins (probably as iframe). Checked thru Jenkins plugins but found nothing. Attached example view of what I look for..  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37324) We would like a more meaningful description of a step

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-37324  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: We would like a more meaningful description of a step   
 

  
 
 
 
 

 
 This ticket is still 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-27299) Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility

2017-03-28 Thread mmit...@microsoft.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Mitchell commented on  JENKINS-27299  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Refactor Disable Build feature out of AbstractProject for Pipeline Compatibility   
 

  
 
 
 
 

 
 I feel like this should be a higher priority. This makes using pipeline in conjunction with job dsl difficult.  
 

  
 
 
 
 

 
 
 

 
 
 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-38460) Move toasts from bottom left to bottom right

2017-03-28 Thread adrien.lecharpent...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38460  
 
 
  Move toasts from bottom left to bottom right   
 

  
 
 
 
 

 
Change By: 
 Adrien Lecharpentier  
 

  
 
 
 
 

 
 On [~brody]'s advice the toasts should be on the bottom left of the screen rather than the bottom  left  right .  
 

  
 
 
 
 

 
 
 

 
 
 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-41236) SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"

2017-03-28 Thread bitwise...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41236  
 
 
  SauceConnect step fails in Declarative pipeline: Missing required parameter: "sauceConnectPath"   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 Resolved Closed  
 
 
Assignee: 
 Gavin Mogan  
 

  
 
 
 
 

 
 
 

 
 
 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-43173) Jenkins Job template

2017-03-28 Thread eldo.jos...@thehartford.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eldo Joseph created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43173  
 
 
  Jenkins Job template   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2017/Mar/28 7:38 PM  
 
 
Environment: 
 DEV  
 
 
Labels: 
 pipeline-input pipeline pipeline-properties  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Eldo Joseph  
 

  
 
 
 
 

 
 I have create job template at Jenkins and created jobs based out of template. But when I added properties: Set Job properties -> Build Triggers -> Build periodically code to schedule jenkins job execution, the relation of job with template is removing after first execution and job became stand alone job. Whatever change I made to template is not picking by the job after that. Is there a option to schedule jobs while using job template?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-43072) jenkinsci/jnlp not connecting to master

2017-03-28 Thread zmeggy...@skawa.hu (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Zalan Meggyesi edited a comment on  JENKINS-43072  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jenkinsci/jnlp not connecting to master   
 

  
 
 
 
 

 
 Kenneth, do you have a possible workaround, perhaps?  I just ran into this and it rendered my cluster unusable.   For me, both parameters are doubled up, not just the MAC. For anyone else who comes looking, deleting the start command arguments did the trick for me. Still, I'd like to know why it broke near the end of my day, without an upgrade being done at any time today, so Carlos, if you have anything to share on how this change came about, it would be most welcome as an opportunity to learn.  
 

  
 
 
 
 

 
 
 

 
 
 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-43172) Cannot change Stage name after adding parallel branch in Blue Ocean editor

2017-03-28 Thread bitwise...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43172  
 
 
  Cannot change Stage name after adding parallel branch in Blue Ocean editor
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-pipeline-editor-plugin  
 
 
Created: 
 2017/Mar/28 7:01 PM  
 
 
Environment: 
 rc3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Liam Newman  
 

  
 
 
 
 

 
 Steps to reproduce: 
 
Open blue Ocean Pipeline editor 
Create a stage named "Test" 
Rename the stage to "Platform 1" 
Add a parallel branch to that stage name it "Platform 2" 
Click first first branch of parallel again 
 Expected: Option to change the name of the stage to "Test" Actual:  Changing displayed name will change the name of the parallel branch, but not the name of stage.  There is no way in the editor to change the name of the stage without deleting all parallel branches first.

[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user

2017-03-28 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-38698  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM Changelog: Commits, made via github, displayed with "noreply" user   
 

  
 
 
 
 

 
 I'm not clear which type of pipeline job you're using, since you say that GitHub is the only branch source available. If you're using a GitHub Organization Folders job, then the customization of checkout technique will need to be performed either in a pipeline global library shared with all jobs, or in each job.If you're using a pipeline multi-branch job, then the customization of checkout technique can be performed at job definition, and may then be adjusted or modified in either a pipeline global library shared with all jobs, or in the Jenkinsfile for each branch. 
 

  
 
 
 
 

 
 
 

 
 
 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-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user

2017-03-28 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38698  
 
 
  SCM Changelog: Commits, made via github, displayed with "noreply" user   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Attachment: 
 Pipeline-Multi-Branch.png  
 
 
Attachment: 
 GitHub-Org-Folders.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging

2017-03-28 Thread jbro...@snapapp.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Brooks commented on  JENKINS-42152  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging   
 

  
 
 
 
 

 
 Wojciech Duda, I'm assuming that to test this we need to build a plugin from your fork, correct? (Sorry, still really cutting my teeth on Jenkins.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user

2017-03-28 Thread roch.dev...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roch Devost commented on  JENKINS-38698  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM Changelog: Commits, made via github, displayed with "noreply" user   
 

  
 
 
 
 

 
 According to this article: https://support.cloudbees.com/hc/en-us/articles/226122247-How-to-Customize-Checkout-for-Pipeline-Multibranch the "Additional Behaviours" should appear in Branch Source -> Git, but in branch source I only have GitHub available, which doesn't have this option. Additionally, I want to change the behaviour for all projects if possible and not have to redo this setup on each one (especially since they are created automatically from pushes to the organizations repos). I understand the need for backward compatibility, but since pretty much all commits in GitHub are made by "noreply", there should at least be a way to change the behaviour globally (JAVA_OPTS?)  
 

  
 
 
 
 

 
 
 

 
 
 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-42749) Polling configuration is not updated until next successful build

2017-03-28 Thread pw...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Wolf commented on  JENKINS-42749  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Polling configuration is not updated until next successful build   
 

  
 
 
 
 

 
 Emilio Escobar this isn't related to Pipeline is it? This should be true for any polling on an ephemeral node. In Pipeline you could check the author directly in the Pipeline and skip sections or the entire Pipeline based on the author rather than relying on workspace polling.  
 

  
 
 
 
 

 
 
 

 
 
 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-43168) Performance publisher throws NPE when publishing jmeter results

2017-03-28 Thread sahar.jaz...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sahar commented on  JENKINS-43168  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance publisher throws NPE when publishing jmeter results   
 

  
 
 
 
 

 
 Issue got resolved after I updated jenkins and performance plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user

2017-03-28 Thread roch.dev...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Roch Devost edited a comment on  JENKINS-38698  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM Changelog: Commits, made via github, displayed with "noreply" user   
 

  
 
 
 
 

 
 Where exactly is this option? I have looked everywhere and cannot seem to find it.   I am using the `checkout scm` step in Blue Ocean rc3 if that helps.  
 

  
 
 
 
 

 
 
 

 
 
 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-43171) Correct Pom for build-monitor-plugin

2017-03-28 Thread cr...@cars.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chaz Ruhl created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43171  
 
 
  Correct Pom for build-monitor-plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 build-monitor-plugin, job-dsl-plugin  
 
 
Created: 
 2017/Mar/28 5:53 PM  
 
 
Environment: 
 Jenkins-2.32.3  gradle - 2.12  build-monitor-plugin-1.11+build.201701152243  job-dsl-plugin - 1.58  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Chaz Ruhl  
 

  
 
 
 
 

 
 We run tests against our job-dsl code using gradle before kicking off the dsl processing job. For dsl code referencing various plugins, we include the dependancies via build.gradle dependancies {    testPlugins 'org.jenkins-ci.main:maven-plugin:2.3' } when including build-monitor-plugin: testPlugins 'org.jenkins-ci.plugins:build-monitor-plugin:1.11+build.201701152243' I get an error saying: > Could not resolve org.jenkins-ci.plugins:build-monitor-plugin:1.11+build.201701152243. > Could not parse POM http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/1.11+build.201701152243/build-monitor-plugin-1.11+build.201701152243.pom > Could not find org.jenkins-ci.plugins:build-monitor:1.11+build.201701152243. After a little digging, it appears the pom is not set-up per https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-pom.xml I was able to add the pom & hpi to our local repository and successfully got the tests running by making the following changes:  org.jenkins-ci.plugins plugin 1.609.3   This was set to build-monitor - which doesn't seem to exist. With the required jenkins version in the correct place (the parent), a separate verison tag needs to be added: 1.11+build.201701152243 A version for the hamcrest dependancy was needed for it to be correctly found  org.hamcrest hamcrest-all 3.1 test

[JIRA] (JENKINS-43170) No credentials injected into managed settings.xml with Pipeline Maven Plugin

2017-03-28 Thread reck...@yatta.de (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 creckord created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43170  
 
 
  No credentials injected into managed settings.xml with Pipeline Maven Plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Dominik Bartholdi  
 
 
Components: 
 config-file-provider-plugin, pipeline-maven-plugin  
 
 
Created: 
 2017/Mar/28 5:33 PM  
 
 
Environment: 
 Jenkins 2.32.3  Config File Provider Plugin 2.15.7  Pipeline Maven Integration Plugin 2.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 creckord  
 

  
 
 
 
 

 
 I have a settings.xml that is managed by the Config File Provider Plugin and uses the option to inject stored credentials from the Jenkins credentials stores instead of having them directly in the settings.xml. I'm using this settings.xml in a withMaven block like this: 

 

withMaven(maven: 'Maven', mavenSettingsConfig: 'default-settings', mavenLocalRepo: '.repo') {
   sh 'mvn help:effective-settings'
} 

 I would have expected that the effective settings would contain  sections for the configured credentials, but they don't. All static content from the managed settings.xml is present though. I've marked this as Improvement instead of Bug, since https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin indicates that this might be expected: 

The file types 'Global Maven settings.xml' and 'Maven settings.xml' have built-in support for the Credentials Plugin. When the plugin serves the settings.xml to the maven execution, the

[JIRA] (JENKINS-38698) SCM Changelog: Commits, made via github, displayed with "noreply" user

2017-03-28 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-38698  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: SCM Changelog: Commits, made via github, displayed with "noreply" user   
 

  
 
 
 
 

 
 The "pipeline syntax" link on most pipeline job definition pages will let you choose the "checkout" step. That will then guide you through the web page to select various git plugin options. Look for "Additional Behaviours" and you'll find a drop-down list which includes "Use commit author in changelog". We were tempted some years ago to make "Use commit author in changelog" the default, but any change to default behavior tends to result in a loud outcry from users who don't expect defaults to change from one release to the next.  
 

  
 
 
 
 

 
 
 

 
 
 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-43143) [Regression] Parameters no longer available in credentials for environment