[JIRA] (JENKINS-39770) PipelineRunGraph not rendered when there is more that 100 nodes

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-39770  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PipelineRunGraph not rendered when there is more that 100 nodes   
 

  
 
 
 
 

 
 hrm... so the problem is that we actively do not want to show that many things in parallel. there isn't a way to do that now that I can see though... so "fixing" it to show 100+ in parallel is not right though...   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39305) Adding pipeline support to hpe plugin

[ka...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 New feature in HPE plugin v5 -  https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools/#HPApplicationAutomationTools-SupportforPipelines  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39305  
 
 
  Adding pipeline support to hpe plugin   
 

  
 
 
 
 

 
Change By: 
 Yafim Kazak  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-39306) Adding pipeline support for runing LoadRunner scenarios

[ka...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 New feature in HPE plugin v5 -  https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools/#HPApplicationAutomationTools-SupportforPipelines  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39306  
 
 
  Adding pipeline support for runing LoadRunner scenarios   
 

  
 
 
 
 

 
Change By: 
 Yafim Kazak  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, 

[JIRA] (JENKINS-39308) Adding pipeline support for runing Performance Center

[ka...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 New feature in HPE plugin v5 -  https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools/#HPApplicationAutomationTools-SupportforPipelines  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39308  
 
 
  Adding pipeline support for runing Performance Center   
 

  
 
 
 
 

 
Change By: 
 Yafim Kazak  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, 

[JIRA] (JENKINS-39312) Adding pipeline support for Service virtualization

[ka...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 New feature in HPE plugin v5 -  https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools/#HPApplicationAutomationTools-SupportforPipelines  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39312  
 
 
  Adding pipeline support for Service virtualization   
 

  
 
 
 
 

 
Change By: 
 Yafim Kazak  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send 

[JIRA] (JENKINS-39313) Adding pipeline support for ALM lab management

[ka...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yafim Kazak closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 New feature in HPE plugin v5 -  https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools/#HPApplicationAutomationTools-SupportforPipelines  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39313  
 
 
  Adding pipeline support for ALM lab management   
 

  
 
 
 
 

 
Change By: 
 Yafim Kazak  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an 

[JIRA] (JENKINS-40587) API for submitting step input form

[jdu...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40587  
 
 
  API for submitting step input form   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Vivek Pandey  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Dec/21 6:47 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 James Dumay  
 

  
 
 
 
 

 
 Needed to complete JENKINS-38494  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

  

[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes

[mne...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Neale commented on  JENKINS-37491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes   
 

  
 
 
 
 

 
 It's also hard to describe all these options to people - the reality is "do you want lots of builds when you merge to master" - but most people would say "no".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40586) Colorize "Replayed" builds differently

[rus.cah...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramanathan M created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40586  
 
 
  Colorize "Replayed" builds differently   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Dec/21 3:52 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ramanathan M  
 

  
 
 
 
 

 
 With the option to do in-line editing of pipeline scripts, it's possible to iterate through changes without having to follow the cycle of committing in version control and then awaiting the build results in Jenkins. Like the different colors for failed and passed builds, it would be nice to indicate those builds that were triggered using the "Replay" option by highlighting or showing the icon in a different color.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 

[JIRA] (JENKINS-40585) Schedule a Build with another job as upstream

[bsrikanth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 srikanth reddy started work on  JENKINS-40585  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 srikanth reddy  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40585) Schedule a Build with another job as upstream

[bsrikanth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 srikanth reddy stopped work on  JENKINS-40585  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 srikanth reddy  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40585) Schedule a Build with another job as upstream

[bsrikanth...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 srikanth reddy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40585  
 
 
  Schedule a Build with another job as upstream   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Maurice W.  
 
 
Components: 
 parameterized-remote-trigger-plugin, pipeline, plugin-usage-plugin  
 
 
Created: 
 2016/Dec/21 3:06 AM  
 
 
Labels: 
 plugin pipeline, job  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 srikanth reddy  
 

  
 
 
 
 

 
 Production Approval job (Let’s Say A) This job is to create email notification to the manager and schedule a Production Job to schedule at a particular time. Say 4:00 pm Need to build as a pipeline with A and B A has a parameter CRQ Number (Ticketing system), B has to catch that parameter value  and build at the scheduled time. Production Job (Let’s Say B). A is upstream to B . Is it possible to Build a Pipeline like this.  If yes Please suggest some plugins and possibilities When I build job A with a parameter and it should block the Job B and it should only trigger at schedule time.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-40584) Choosing "Build origin branches" does not add "Push" webhook

[kway...@shapesecurity.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kyle Wayman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40584  
 
 
  Choosing "Build origin branches" does not add "Push" webhook   
 

  
 
 
 
 

 
Change By: 
 Kyle Wayman  
 

  
 
 
 
 

 
 * Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master our case) is  branched  built . But a push to master does not trigger a build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40584) Choosing "Build origin branches" does not add "Push" webhook

[kway...@shapesecurity.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kyle Wayman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40584  
 
 
  Choosing "Build origin branches" does not add "Push" webhook   
 

  
 
 
 
 

 
Change By: 
 Kyle Wayman  
 

  
 
 
 
 

 
 * Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master  in  our case) is built. But a push to master does not trigger a build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40584) Choosing "Build origin branches" does not add "Push" webhook

[kway...@shapesecurity.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kyle Wayman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40584  
 
 
  Choosing "Build origin branches" does not add "Push" webhook   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 github-organization-folder-plugin  
 
 
Created: 
 2016/Dec/21 12:01 AM  
 
 
Environment: 
 Cloudbees Jenkins Enterprise 2.19.3.1, GitHub Enterprise  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kyle Wayman  
 

  
 
 
 
 

 
 Adding an Organization Folder and scanning for repos that contain Jenkinsfiles created webhooks in Github Enterprise, but the webhook was created for "pull_request and repository" but not "push". What this means is that PRs are automatically built, and when a PR is merged, the base branch (master our case) is branched. But a push to master does not trigger a build.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-40583) Anchore build step will fail if there is more than a single whitespace separating a container image (name/id) from the dockerfile path, in anchore_images input file

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40583  
 
 
  Anchore build step will fail if there is more than a single whitespace separating a container image (name/id) from the dockerfile path, in anchore_images input file   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40583) Anchore build step will fail if there is more than a single whitespace separating a container image (name/id) from the dockerfile path, in anchore_images input file

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40583  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore build step will fail if there is more than a single whitespace separating a container image (name/id) from the dockerfile path, in anchore_images input file   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Nurmi Path: src/main/java/com/anchore/jenkins/plugins/anchore/AnchoreBuilder.java http://jenkins-ci.org/commit/anchore-container-scanner-plugin/614a9d1cf35c3d4c06d54c0e736d5bef204e5cad Log: [FIXED JENKINS-40583] adding more checking and better tokenizing for handling the parse of anchore_images input file Signed-off-by: Daniel Nurmi   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40583) Anchore build step will fail if there is more than a single whitespace separating a container image (name/id) from the dockerfile path, in anchore_images input file

[nu...@anchore.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Nurmi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40583  
 
 
  Anchore build step will fail if there is more than a single whitespace separating a container image (name/id) from the dockerfile path, in anchore_images input file   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Nurmi  
 
 
Components: 
 anchore-container-scanner-plugin  
 
 
Created: 
 2016/Dec/20 11:58 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Daniel Nurmi  
 

  
 
 
 
 

 
 Affects anchore plugin <= 1.0.4. The workaround until the fix is released is to ensure that, when creating the anchore_images input file, that there is only a single regular 'space' separating the image from the dockerfile path, in each line.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 

[JIRA] (JENKINS-39844) Unable to execute inside container: 500 Internal Server Error from Kubernetes

[cj...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 cjyar commented on  JENKINS-39844  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to execute inside container: 500 Internal Server Error from Kubernetes   
 

  
 
 
 
 

 
 I figured out the cause of the error: The Jenkins master was running in a different namespace from the slave pods. I didn't see any documentation saying that they had to be in the same namespace. It's a reasonable restriction, but it would be great to have a better error message.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40581) Blue Ocean Pull Request Enable Tab Does nothing

[marky.r.jack...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40581  
 
 
  Blue Ocean Pull Request Enable Tab Does nothing   
 

  
 
 
 
 

 
Change By: 
 Marky Jackson  
 
 
Priority: 
 Minor Blocker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40582) Unable to use ${I,G} in a path string

[hand_e_f...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Richardson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40582  
 
 
  Unable to use ${I,G} in a path string   
 

  
 
 
 
 

 
Change By: 
 Mark Richardson  
 

  
 
 
 
 

 
 To match this  lien  line :{noformat}stderr: fatal: Unable to create 'E:/Jenkins/workspace/builds/repo/project/component/.git/shallow.lock': File exists.{noformat}I have the indicator:{noformat}stderr: fatal: Unable to create 'E:\/Jenkins\/workspace\/builds\/([^\/]+)\/([^\/]+)\/([^\/]+)\/\.git\/shallow\.lock': File exists\.{noformat}And description:{noformat}Run the following command to delete the lock file from the Jenkins server and start the build again.del Jenkins\\E\$\\Jenkins\\workspace\\builds\\${1,1}\\${1,2}\\${1,3}\\.git\\shallow.lock{noformat}Which generates the following output:{noformat}Run the following command to delete the lock file from the Jenkins server and start the build again.del \\Jenkins\E$\Jenkins\workspace\builds${1,1}${1,2}${1,3}\.git\shallow.lock{noformat}But I expect:{noformat}Run the following command to delete the lock file from the Jenkins server and start the build again.del \\Jenkins\E$\Jenkins\workspace\builds\repo\project\component\.git\shallow.lock{noformat}It appears to be using the escaped `\` to escape the `$`.  How do I get around this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 

[JIRA] (JENKINS-40582) Unable to use ${I,G} in a path string

[hand_e_f...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Richardson updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40582  
 
 
  Unable to use ${I,G} in a path string   
 

  
 
 
 
 

 
Change By: 
 Mark Richardson  
 

  
 
 
 
 

 
 To match this line:{noformat}stderr: fatal: Unable to create 'E:/Jenkins/workspace/builds/repo/project/component/.git/shallow.lock': File exists.{noformat}I have the indicator:{noformat}stderr: fatal: Unable to create 'E:\/Jenkins\/workspace\/builds\/([^\/]+)\/([^\/]+)\/([^\/]+)\/\.git\/shallow\.lock': File exists\.{noformat}And description:{noformat}Run the following command to delete the lock file from the Jenkins server and start the build again.del Jenkins\\E\$\\Jenkins\\workspace\\builds\\${1,1}\\${1,2}\\${1,3}\\.git\\shallow.lock{noformat}Which generates the following output:{noformat}Run the following command to delete the lock file from the Jenkins server and start the build again.  del \\Jenkins\E$\Jenkins\workspace\builds${1,1}${1,2}${1,3}\.git\shallow.lock{noformat}But I expect:{noformat}Run the following command to delete the lock file from the Jenkins server and start the build again.  del \\Jenkins\E$\Jenkins\workspace\builds\repo\project\component\.git\shallow.lock{noformat}It appears to be using the escaped `\` to escape the `$`.  How do I get around this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 

[JIRA] (JENKINS-40582) Unable to use ${I,G} in a path string

[hand_e_f...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Richardson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40582  
 
 
  Unable to use ${I,G} in a path string   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Tomas Westling  
 
 
Components: 
 build-failure-analyzer-plugin  
 
 
Created: 
 2016/Dec/20 10:44 PM  
 
 
Environment: 
 Jenkins ver. 2.19.3  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mark Richardson  
 

  
 
 
 
 

 
 To match this lien: 

 
stderr: fatal: Unable to create 'E:/Jenkins/workspace/builds/repo/project/component/.git/shallow.lock': File exists.
 

 I have the indicator: 

 
stderr: fatal: Unable to create 'E:\/Jenkins\/workspace\/builds\/([^\/]+)\/([^\/]+)\/([^\/]+)\/\.git\/shallow\.lock': File exists\.
 

 And description: 

 
Run the following command to delete the lock file from the Jenkins server and start the build again.
del Jenkins\\E\$\\Jenkins\\workspace\\builds\\${1,1}\\${1,2}\\${1,3}\\.git\\shallow.lock
 

 Which generates the following output: 

[JIRA] (JENKINS-40581) Blue Ocean Pull Request Enable Tab Does nothing

[marky.r.jack...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marky Jackson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40581  
 
 
  Blue Ocean Pull Request Enable Tab Does nothing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 BO1.jpeg, BO2.jpeg  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2016/Dec/20 10:27 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marky Jackson  
 

  
 
 
 
 

 
 Jenkins version 2.37 Blue Ocean Plugin version 1.0.0-b14  Problem: I have a multi-branch pipeline and I can see the branches but I cannot enable the Pull Request. I am successful in doing a freestyle build and using the Github Pull Request Builder. The Enable button does nothing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
   

[JIRA] (JENKINS-38825) MultiJob does not build Pipeline jobs

[si...@simonmweber.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Simon Weber commented on  JENKINS-38825  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MultiJob does not build Pipeline jobs   
 

  
 
 
 
 

 
 Alright, I've got things largely working. I'll clean things up and post some code tomorrow. I'll probably stop short of creating a PR, since my changes cut a lot of corners (eg removing some features around scm changes) in the interest of resolving the blocker.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40580) Non-identifier characters in parallel names unquoted

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40580  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Non-identifier characters in parallel names unquoted   
 

  
 
 
 
 

 
 Yup, needed to quote at least parallel branch names that aren't valid identifiers in Groovy. I decided to just quote all of them on toGroovy() serialization, 'cos why not. PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/79  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40580) Non-identifier characters in parallel names unquoted

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-40580  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40580  
 
 
  Non-identifier characters in parallel names unquoted   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40580) Non-identifier characters in parallel names unquoted

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer started work on  JENKINS-40580  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40577) Job Import Plugin - Error on Import - java.lang.NoClassDefFoundError: com/google/inject/internal/guava/base/$Preconditions

[rowanjoh...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ahrr Jay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40577  
 
 
  Job Import Plugin - Error on Import - java.lang.NoClassDefFoundError: com/google/inject/internal/guava/base/$Preconditions   
 

  
 
 
 
 

 
Change By: 
 Ahrr Jay  
 

  
 
 
 
 

 
 Looking to import Jobs from a server running an older version of jenkins (1.651.1) to the new server.1. Entered the URL & selected the saved credentials (a user on the old server with access to manage jenkins) from the drop down.2. Clicked query and got the stack trace below.*+Stack Trace:+*  { { code:java} javax.servlet.ServletException: java.lang.NoClassDefFoundError: com/google/inject/internal/guava/base/$Preconditions at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 

[JIRA] (JENKINS-40580) Non-identifier characters in parallel names unquoted

[kzan...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40580  
 
 
  Non-identifier characters in parallel names unquoted   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2016/Dec/20 8:32 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Keith Zantow  
 

  
 
 
 
 

 
 Converting JSON to Jenkinsfile where parallel branch names contain non-identifier characters, the Jenkinsfile is invalid, the names are not quoted. E.g. this JSON: 

 

{"pipeline":{"agent":{"isLiteral":true,"value":"any"},"stages":[{"name":"parallel","branches":[{"name":"parallel 1","steps":[{"name":"echo","arguments":[{"key":"message","value":{"isLiteral":true,"value":"1"}}]}]},{"name":"parallel 2","steps":[{"name":"echo","arguments":[{"key":"message","value":{"isLiteral":true,"value":"2"}}]}]}]}]}}
 

 Generates this invalid Jenkinsfile: 

 

pipeline {
  agent any
  
  stages {
stage('parallel') {
  steps {
parallel(
  parallel 1: {
echo(message: '1')

  },
  parallel 2: {
echo(message: '2')

  }
)
  }
}

  }
  
}
 

 Sorry for the ugly formatting.  
 

  
 
 
 

[JIRA] (JENKINS-40579) Email Extension Plugin not allowing to change job configuration

[yashwanth1...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 yashwanth kandepaneni created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40579  
 
 
  Email Extension Plugin not allowing to change job configuration   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David van Laatum  
 
 
Attachments: 
 Jenkins_1.PNG, Jenkins_2.PNG  
 
 
Components: 
 email-ext-plugin  
 
 
Created: 
 2016/Dec/20 8:26 PM  
 
 
Environment: 
 Jenkins version - 1.651.3  Email Extension Plugin - 2.52  Operatins system - Red Hat Enterprise Linux Server release 7.2  java version - 1.7.0_111  Tomcat version -7.0.54.0  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Major  
 
 
Reporter: 
 yashwanth kandepaneni  
 

  
 
 
 
 

 
 Hi After configuring Email notification for job, I 'm not able to make any changes to job. If i'm trying to do,its logging out from Jenkins and if i try to re-login its not submitting my changes. Can you please let me know did i miss configured anything in job. PFA   
 

  
 
 
 
 

 
 
 

  

[JIRA] (JENKINS-40578) Matrix flyweight job crashes with NPE if it's triggered jobs are in the queue for a long time

[gabriel....@silabs.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gabriel Ash created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40578  
 
 
  Matrix flyweight job crashes with NPE if it's triggered jobs are in the queue for a long time   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 matrix-project-plugin  
 
 
Created: 
 2016/Dec/20 8:24 PM  
 
 
Environment: 
 Jenkins 2.36  Matrix Project Plugin 1.7.1   
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Gabriel Ash  
 

  
 
 
 
 

 
 I have a Matrix project with 50 configurations that run against a label supported by 25 machines. So, when this job runs, it immediately creates a build queue. This job has "execute concurrent builds if necessary" enabled, although I believe I have seen this issue occur when only one instance of this job running as well. The build queue on this server can sometimes grow very large, preventing these jobs from running for a long time. After some time with its matrix configuration jobs in the queue, I see the flyweight job fail with the following null pointer (causing Jenkins to interrupt all of the configurations in the job to fail): Interrupting #1003 FATAL: null java.lang.NullPointerException at hudson.matrix.DefaultMatrixExecutionStrategyImpl.waitForCompletion(DefaultMatrixExecutionStrategyImpl.java:288) at hudson.matrix.DefaultMatrixExecutionStrategyImpl.run(DefaultMatrixExecutionStrategyImpl.java:162) at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:364) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1729) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:313) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Finished: FAILURE looking at the source in 

[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step

[k...@koomie.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karl Schulz commented on  JENKINS-34268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Lock multiple resources using the Pipeline lock step   
 

  
 
 
 
 

 
 I'm also unable to successfully use the MY_VAR option. It's awesome to be able to lock multiple resources now, but can't recreate the capability of a Freestyle job without being able to query the results.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27869) entered SCM password should be masked in output

[andreas.man...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Mandel commented on  JENKINS-27869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: entered SCM password should be masked in output   
 

  
 
 
 
 

 
 Why not store the password parameter as PasswordParameterValue so that it can be handled as such? Anders Hammar Sorry I did not get this before, you can use the Password Mask functionality of the EnvInject or the Mask Passwords Plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40556) remove "script" reference from Pipeline-examples readme

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40556  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: remove "script" reference from Pipeline-examples readme   
 

  
 
 
 
 

 
 Code changed in jenkins User: R. Tyler Croy Path: docs/BEST_PRACTICES.md http://jenkins-ci.org/commit/pipeline-examples/c88982acec122ef92be3b71d4ab9cf4ea8719b8d Log: Merge pull request #62 from HRMPW/patch-2 JENKINS-40556 - update best_practices.md Compare: https://github.com/jenkinsci/pipeline-examples/compare/6543e341d89e...c88982acec12  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40577) Job Import Plugin - Error on Import - java.lang.NoClassDefFoundError: com/google/inject/internal/guava/base/$Preconditions

[rowanjoh...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ahrr Jay created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40577  
 
 
  Job Import Plugin - Error on Import - java.lang.NoClassDefFoundError: com/google/inject/internal/guava/base/$Preconditions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 job-import-plugin  
 
 
Created: 
 2016/Dec/20 7:40 PM  
 
 
Environment: 
 Jenkins - 2.36  OS - CentOS 7  Browser - Chrome  Java - java-1.7.0-openjdk-1.7.0.111-2.6.7.2.el7_2.x86_64  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ahrr Jay  
 

  
 
 
 
 

 
 Looking to import Jobs from a server running an older version of jenkins (1.651.1) to the new server. 1. Entered the URL & selected the saved credentials (a user on the old server with access to manage jenkins) from the drop down. 2. Clicked query and got the stack trace below. Stack Trace: {{javax.servlet.ServletException: java.lang.NoClassDefFoundError: com/google/inject/internal/guava/base/$Preconditions at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at 

[JIRA] (JENKINS-40550) Remove "script" from Pipeline references in Jenkins UI

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40550  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove "script" from Pipeline references in Jenkins UI   
 

  
 
 
 
 

 
 Code changed in jenkins User: R. Tyler Croy Path: content/doc/book/pipeline/getting-started.adoc content/doc/book/pipeline/jenkinsfile.adoc content/doc/book/pipeline/shared-libraries.adoc http://jenkins-ci.org/commit/jenkins.io/8adf7b8e0d6d208580b776fa27e4b8976ab882af Log: Correct or remove references to Pipeline Script where possible There is still some outstanding work which needs to be done in JENKINS-40550 to update web UI elements to reflect the appropriate "Scripted Pipeline" phrasing. References WEBSITE-273  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40340) Option to suppress changelong when getting Pipeline Jenkinsfile from GitHub SCM

[cagrubb...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Cory Grubbs commented on  JENKINS-40340  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option to suppress changelong when getting Pipeline Jenkinsfile from GitHub SCM   
 

  
 
 
 
 

 
 Can somebody provide an update/eta on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40457) java.lang.ArrayStoreException when a image pull secret is defined

[jenkins...@carlossanchez.eu (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40457  
 
 
  java.lang.ArrayStoreException when a image pull secret is defined   
 

  
 
 
 
 

 
Change By: 
 Carlos Sanchez  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37759) Usage of @Initializer(after = InitMilestone.COMPLETED) in plugins breaks the initialization logic

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The fix has not been released by the maintainer yet, but I think my work is done here  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37759  
 
 
  Usage of @Initializer(after = InitMilestone.COMPLETED) in plugins breaks the initialization logic   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-40576) Declarative Pipeline Content for Pipeline Syntax page in Jenkins

[pw...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Wolf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40576  
 
 
  Declarative Pipeline Content for Pipeline Syntax page in Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Patrick O'Hannigan  
 
 
Attachments: 
 Screen Shot 2016-12-20 at 11.03.33 AM.png  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Dec/20 7:07 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Patrick Wolf  
 

  
 
 
 
 

 
 We need to create a Declarative Pipeline content page for the Pipeline Syntax Page within Jenkins. This page should be similar to the Global Variables page and have static content such as that found in the current declarative syntax page.  See the screenshot below for an example of what this can look like  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
   

[JIRA] (JENKINS-40575) Allow custom tabs in github-organization-folder

[tomtheengin...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Hughes created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40575  
 
 
  Allow custom tabs in github-organization-folder   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 github-organization-folder-plugin  
 
 
Created: 
 2016/Dec/20 6:05 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tom Hughes  
 

  
 
 
 
 

 
 It's possible to have lots of branches in a repository, at which point the GitHub Organization Folder view starts to become pretty cluttered. It would be nice to be able to specify a regex to organize the branches into different tabs. For example, if you are using "git-flow", there could be a regex to separate out branches that start for release/ into a separate tab.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[JIRA] (JENKINS-40370) Run stage when branch name matches

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Run stage when branch name matches   
 

  
 
 
 
 

 
 Code changed in jenkins User: rsandell Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/AbstractModelASTCodeBlock.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWhen.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTWhenExpression.java pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/StageConditionals.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/DeclarativeStageConditional.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/DeclarativeStageConditionalDescriptor.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/impl/BranchConditional.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/when/impl/EnvironmentConditional.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ClosureModelTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/StageConditionalTranslator.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/d28a97cfce8b8c611f174a1827d86f4138e53857 Log: JENKINS-40370 Make stage.when more declarative  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
  

[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible

[pw...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Wolf commented on  JENKINS-40524  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rework agent syntax to be more extensible   
 

  
 
 
 
 

 
 Then the second option is confusing and misleading.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40524  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rework agent syntax to be more extensible   
 

  
 
 
 
 

 
 Patrick Wolf - no, the second would not be possible. label inside docker or dockerfile would be equivalent to label 'foo' - i.e., which agent to run on in the first place.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40351  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: README.md src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure.jelly src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_es.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_fr.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_pt.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_pt_BR.properties src/main/resources/org/jvnet/hudson/test/JenkinsComputerConnectorTester/configure_zh_TW.properties http://jenkins-ci.org/commit/jenkins-test-harness/68bdc598cb970da0fc89ebe48de64626280c80b8 Log: Merge pull request #44 from jenkinsci/JENKINS-40351 [FIXED JENKINS-40351] provide missing config page Compare: https://github.com/jenkinsci/jenkins-test-harness/compare/6b20f9ffb88d...68bdc598cb97  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40351) JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40351  
 
 
  JenikinsRule.configRoundTrip(ComputerConnector c) throws error whilst loading config page   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible

[pw...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Wolf commented on  JENKINS-40524  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rework agent syntax to be more extensible   
 

  
 
 
 
 

 
 question Andrew Bayer the second example in the second option 

 

agent {
  // Also would work with 'docker "httpd:2.4.12"' if the image is the only desired argument
  docker {
image "httpd:2.4.12"
args "-v /tmp:/tmp -p 80:80"
label "foo"
// the below would be for things like private registry, kubernetes pod config, whatever
someComplicatedOption {
  optA "banana"
  optB "monkey"
  }
}
 

 What does label refer to? Is that the agent label or the container label? Would this be supported? 

 

agent {
  label "nodename"
  docker {
image "httpd:2.4.12"
args "-v /tmp:/tmp -p 80:80"
label "foo"
// the below would be for things like private registry, kubernetes pod config, whatever
someComplicatedOption {
  optA "banana"
  optB "monkey"
  }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible

[lglickfi...@circleup.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Logan Glickfield commented on  JENKINS-40524  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rework agent syntax to be more extensible   
 

  
 
 
 
 

 
 I'm a fan of option 2. The first option leaves some confusion as to what exactly label means. It's unclear to me whether it will prefer an existing labeled node and fall back to docker, or whether it will always create a new docker node and just apply that label. The second provides some clarity that the label is just an attribute of the docker/dockerfile nodes.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37839) Many users are getting error while opening jenkins

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing as incomplete. The requester did not provide details required for investigation after the ping  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37839  
 
 
  Many users are getting error while opening jenkins   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-37839) Many users are getting error while opening jenkins

[janario.olive...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37839  
 
 
  Many users are getting error while opening jenkins   
 

  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Assignee: 
 Janario Oliveira  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37839) Many users are getting error while opening jenkins

[janario.olive...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37839  
 
 
  Many users are getting error while opening jenkins   
 

  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Component/s: 
 core  
 
 
Component/s: 
 http-request-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37839) Many users are getting error while opening jenkins

[janario.olive...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Janario Oliveira stopped work on  JENKINS-37839  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Janario Oliveira  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27869) entered SCM password should be masked in output

[ryan.campb...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27869  
 
 
  entered SCM password should be masked in output   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27869) entered SCM password should be masked in output

[ryan.campb...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 recampbell commented on  JENKINS-27869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: entered SCM password should be masked in output   
 

  
 
 
 
 

 
 It looks like the upstream bug in maven-release-plugin is fixed. https://issues.apache.org/jira/browse/SCM-811 Since the fix is from May of this year, I'm closing this as Invalid/Won't Fix.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40370) Run stage when branch name matches

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Run stage when branch name matches   
 

  
 
 
 
 

 
 Dominik Bartholdi Strangely enough, rsandell and I are thinking pretty much exactly on those lines. =) Think of the elements inside when (i.e. branch or _expression_ currently) as implementations of an extension point analogous to Run Condition. Since, well, they will be implementations of an extension point. =) That said, contributing from outside may end up being hairy depending on how complex they are, given parsing challenges, but we'll see what we can do.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40524  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Rework agent syntax to be more extensible   
 

  
 
 
 
 

 
 So I'd really like to get some feedback on two possible syntax approaches - I'm fine with either one, so I need input. =) First, which is what's currently in the PR: 

 

agent {
  label "foo"
}

agent {
  docker "httpd:2.4.12"
  dockerArgs "-v /tmp:/tmp -p 80:80"
  label "foo"
  // the below would be for things like private registry, kubernetes pod config, whatever
  someComplicatedOption {
optA "banana"
optB "monkey"
  }
}

agent {
  dockerfile "true"
  dockerArgs "-v /tmp:/tmp -p 80:80"
  label "foo"
}
 

 Second: 

 

agent {
  // i.e., DeclarativeAgent types with only one required argument and only one specified argument don't need the nested block
  label  "foo"
}

agent {
  // Also would work with 'docker "httpd:2.4.12"' if the image is the only desired argument
  docker {
image "httpd:2.4.12"
args "-v /tmp:/tmp -p 80:80"
label "foo"
// the below would be for things like private registry, kubernetes pod config, whatever
someComplicatedOption {
  optA "banana"
  optB "monkey"
  }
}

agent {
  // Also would work with 'dockerfile true' as above
  dockerfile {
args "-v /tmp:/tmp -p 80:80"
label "foo"
  }
}
 

 And of course, agent any and agent none will still be working. Thoughts, Patrick Wolf, Michael Neale, James Dumay, rsandell, aurelien leboulanger, Dominik Bartholdi, Logan Glickfield, Peter Leibiger?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 

[JIRA] (JENKINS-18439) Ability to modify the login page

[jessica.we...@servicenow.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jessica Welch commented on  JENKINS-18439  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to modify the login page   
 

  
 
 
 
 

 
 yay! glad to help   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40188) Unable to use build step with boolean parameterized parameter

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-40188  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to use build step with boolean parameterized parameter   
 

  
 
 
 
 

 
 You should be able to use params.PARAM now if you've got workflow-job 2.8 or later installed, yeah.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-32573) Cobertura misconfiguration destroys 'publishers' node

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32573  
 
 
  Cobertura misconfiguration destroys 'publishers' node   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 robustness  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes

[bill.hamil...@autodesk.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bill Hamilton commented on  JENKINS-37491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes   
 

  
 
 
 
 

 
 Sorry I meant to say that I liked Kurt Madel's solution (branch protection). Stephens solution could still result in build storms.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-27869) entered SCM password should be masked in output

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-27869  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: entered SCM password should be masked in output   
 

  
 
 
 
 

 
 I think this is rather a bug in maven-release-plugin. It should be forking a child process in a way that does not involve printing the password to stdout.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes

[bill.hamil...@autodesk.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bill Hamilton commented on  JENKINS-37491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes   
 

  
 
 
 
 

 
 Stephen Connolly, yes that sounds like a good solution. We are considering changing our PR build support recommendation to be:  If you want Jenkins PR build support, choose the option to build the PR at head (not merge). Any changes to your task branch and PR will result in the PR being built at head. To insure that your merge doesn’t destabilize master, choose the Git “branch protection” option on Master.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40551) environmental variables are not set in Pre Build in maven project

[yu.shao...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yu Shao resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I figured out a way to pass all the listener environmental variables to the new shell environment, so not a defect.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40551  
 
 
  environmental variables are not set in Pre Build in maven project   
 

  
 
 
 
 

 
Change By: 
 Yu Shao  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-40129) Extend GitChangeSet to get the repository name

[phil.mcar...@cloudgine.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil McArdle commented on  JENKINS-40129  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extend GitChangeSet to get the repository name   
 

  
 
 
 
 

 
 This would be a boon for us too. I don't mind having the changes, but I'd like to be able to filter them.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36089) Pipeline support for Promoted Builds Plugin

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-36089  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline support for Promoted Builds Plugin   
 

  
 
 
 
 

 
 

Get rid of the built-in promotion job, use standalone one
 Yes this is the key. The number of the upstream build being “promoted” should simply be passed as a build parameter to the downstream build. Of course you can do this today without the UI. I do not think other concepts of the existing plugin are particularly problematic (though, as mentioned, certain common use cases are done more simply in a single Pipeline job).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40239) Add descriptions for build conditions and expose them in the editor metadata

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-40239  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40239  
 
 
  Add descriptions for build conditions and expose them in the editor metadata   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40239) Add descriptions for build conditions and expose them in the editor metadata

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40239  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add descriptions for build conditions and expose them in the editor metadata   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pom.xml src/main/java/io/blueocean/rest/pipeline/editor/ExportedBuildCondition.java src/main/java/io/blueocean/rest/pipeline/editor/PipelineMetadataService.java http://jenkins-ci.org/commit/blueocean-pipeline-editor-plugin/60123c707cd80b332d8a1bb599d2e34b93339539 Log: [FIXED JENKINS-40239] Add build condition descriptions to metadata  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-18317) Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity

[douglas....@teledynelecroy.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Douglas Lee commented on  JENKINS-18317  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Coverity - Default Defect Filter selects no defects when non-default component map is associated with a stream in Coverity   
 

  
 
 
 
 

 
 I have Jenkins 2.27, plugin 1.7.3, and Coverity 8.5.0, and I see this exact issue: 0 defects matched. I tried setting my stream to use the Default Component Map, but that didn't seem to help. Are there any updates or other known workarounds for this issue?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40460) Null Pointer Exception when polling P4

[pal...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated  JENKINS-40460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40460  
 
 
  Null Pointer Exception when polling P4   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40460) Null Pointer Exception when polling P4

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Null Pointer Exception when polling P4   
 

  
 
 
 
 

 
 Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/build/P4EnvironmentContributor.java src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java src/main/java/org/jenkinsci/plugins/p4/workspace/Expand.java src/main/java/org/jenkinsci/plugins/p4/workspace/Workspace.java src/test/java/org/jenkinsci/plugins/p4/client/WorkflowTest.java http://jenkins-ci.org/commit/p4-plugin/abdc93a40764693d5f30c7cfac651b137648fe62 Log: Support custom SyncID. Exclude BUILD_NUMBER from SyncID. Pushed logging to higher level, so it is not reporting TagActions when building the Environment. JENKINS-40460  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40460) Null Pointer Exception when polling P4

[pal...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen started work on  JENKINS-40460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40460) Null Pointer Exception when polling P4

[pal...@perforce.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Paul Allen updated  JENKINS-40460  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Ready for release.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40460  
 
 
  Null Pointer Exception when polling P4   
 

  
 
 
 
 

 
Change By: 
 Paul Allen  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40574) Pipeline build parameters are null in first build

[suzanne.m.hamil...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Suzanne Hamilton commented on  JENKINS-40574  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline build parameters are null in first build   
 

  
 
 
 
 

 
 This StackOverflow question seems to be referring to the same issue: http://stackoverflow.com/questions/40782302/jenkinsfile-parameter-properties-not-configured-in-jenkins-server-at-initial-bra  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-24402) jsch version

[emim...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Emiliano m commented on  JENKINS-24402  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jsch version   
 

  
 
 
 
 

 
 As far I can see this is because jenkins use plugins deprecated or not maintained and those plugins not update the jsch library, I try add a pull request in plugins with the fix but nobody answer.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40574) Pipeline build parameters are null in first build

[suzanne.m.hamil...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Suzanne Hamilton updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40574  
 
 
  Pipeline build parameters are null in first build   
 

  
 
 
 
 

 
Change By: 
 Suzanne Hamilton  
 

  
 
 
 
 

 
 Parameters which are set in {{properties}} in a pipeline build are null the first time the build is run, even if they are given default values. On subsequent builds, the parameters have values as expected.Example: create a new Pipeline job and define the pipeline script like this in the build config:{code}properties([  [$class: 'ParametersDefinitionProperty',parameterDefinitions: [  [$class: 'StringParameterDefinition',name: 'SOME_PARAMETER',defaultValue: 'some value',description: 'A test parameter']]  ]])echo "Value of parameter:"echo env.SOME_PARAMETER{code}Run the build by clicking "Build" (note that this says "Build" rather than "Build with Parameters"  unless the build has been run at least once ). The console output is:{code}[Pipeline] echoValue of parameter:[Pipeline] echonull{code}Run the build a second time by clicking "Build with Parameters" and then confirming the default value. The console output is now:{code}[Pipeline] echoValue of parameter:[Pipeline] echosome value{code}If you refer to the parameter directly using {{SOME_PARAMETER}} rather than {{env.SOME_PARAMETER}}, the first build fails with a {{groovy.lang.MissingPropertyException}} instead.This isn't so bad when you're configuring a single new job, but it becomes a real problem for multibranch pipeline jobs, because the first build of every branch always fails unless the pipeline script does extra work to handle the missing parameter.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[JIRA] (JENKINS-40574) Pipeline build parameters are null in first build

[suzanne.m.hamil...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Suzanne Hamilton created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40574  
 
 
  Pipeline build parameters are null in first build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2016/Dec/20 4:06 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Suzanne Hamilton  
 

  
 
 
 
 

 
 Parameters which are set in properties in a pipeline build are null the first time the build is run, even if they are given default values. On subsequent builds, the parameters have values as expected. Example: create a new Pipeline job and define the pipeline script like this in the build config: 

 

properties([
  [$class: 'ParametersDefinitionProperty',
parameterDefinitions: [
  [$class: 'StringParameterDefinition',
name: 'SOME_PARAMETER',
defaultValue: 'some value',
description: 'A test parameter']]
  ]
])

echo "Value of parameter:"
echo env.SOME_PARAMETER
 

 Run the build by clicking "Build" (note that this says "Build" rather than "Build with Parameters"). The console output is: 

 

[Pipeline] echo
Value of parameter:
[Pipeline] echo
null
 

 Run the build a second time by clicking "Build with Parameters" and then confirming the default value. The console output is now: 

 

[Pipeline] echo
Value of parameter:

[JIRA] (JENKINS-40573) JSON representation should only use named arguments

[kzan...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Zantow created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40573  
 
 
  JSON representation should only use named arguments   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2016/Dec/20 3:48 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Keith Zantow  
 

  
 
 
 
 

 
 Currently, the JSON format has 2 different representations of step parameters, e.g.: 

 

"steps": [{
"name": "bat",
"arguments": {
"isLiteral": true,
"value": "someBatScript"
}
}]
 

 vs. 

 

"steps": [{
"name": "bat",
"arguments": [{
"key": "script",
"value": {
"isLiteral": true,
"value": "someBatScript"
},
}]
}]
 

 Since JSON is intended only to support tools, this should be consolidated to only use named arguments and the conversion to/from the Jenkinsfile should handle converting to/from these "single required parameter" forms, giving the most idiomatic Jenkinsfile from a JSON representation wherever possible. I think this should be fairly straightforward to implement by checking if the step has a single required parameter, to use that for conversion from a Jenkinsfile and if that is the only parameter supplied by the JSON, convert it back to the idiomatic form.  
 

  

[JIRA] (JENKINS-40370) Run stage when branch name matches

[pw...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Patrick Wolf commented on  JENKINS-40370  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Run stage when branch name matches   
 

  
 
 
 
 

 
 rsandell For some reason when I read your comment I read it as:  

 

branch "*/master"
when {
  _expression_ {
"foo" == "boo"
  }
}
 

 Not sure why I saw it like that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40572) Job DSL Support

[tomasno...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomas Norre Mikkelsen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40572  
 
 
  Job DSL Support   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 extensible-choice-parameter-plugin  
 
 
Created: 
 2016/Dec/20 3:40 PM  
 
 
Labels: 
 plugin jenkins  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tomas Norre Mikkelsen  
 

  
 
 
 
 

 
 Are the any planned support for the Job DSL?  I know i can by-pass this by using configure block, i'm just curios if anything planned? as i prefer Job DSL without configure blocks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

 

[JIRA] (JENKINS-40239) Add descriptions for build conditions and expose them in the editor metadata

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40239  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add descriptions for build conditions and expose them in the editor metadata   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Aborted.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Always.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Changed.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Failure.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Success.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Unstable.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/model/BuildCondition.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Messages.properties http://jenkins-ci.org/commit/pipeline-model-definition-plugin/a1963cdf49d71f1d81e6b668122138a0e4c90d99 Log: Merge pull request #76 from abayer/jenkins-40239 JENKINS-40239 Add descriptions for build conditions Compare: https://github.com/jenkinsci/pipeline-model-definition-plugin/compare/b7ad371b24ff...a1963cdf49d7  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40239) Add descriptions for build conditions and expose them in the editor metadata

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40239  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add descriptions for build conditions and expose them in the editor metadata   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Aborted.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Always.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Changed.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Failure.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Success.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Unstable.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/model/BuildCondition.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/model/conditions/Messages.properties http://jenkins-ci.org/commit/pipeline-model-definition-plugin/e047542af22d24c4a5fe427436df95f29a20aa40 Log: JENKINS-40239 Add descriptions for build conditions  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-31262) BZ 95459 - Really long wait to display a build page if there is more than 50 matching defect

[kwil...@synopsys.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Shami Willms updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31262  
 
 
  BZ 95459 - Really long wait to display a build page if there is more than 50 matching defect   
 

  
 
 
 
 

 
 We are looking at options to fix this soon.  
 

  
 
 
 
 

 
Change By: 
 Shami Willms  
 
 
Summary: 
 BZ 95459 - Really long wait to display a build page if there is more than 50 matching defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates

[g.a.st...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Glen Stark commented on  JENKINS-6334  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for displaying changesets in submodule updates   
 

  
 
 
 
 

 
 This is also a problem for us. Is anyone paying attention to this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40046) Add option to disable internal shared library

[phil.mcar...@cloudgine.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil McArdle commented on  JENKINS-40046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to disable internal shared library   
 

  
 
 
 
 

 
 Yep, sorry, meant to clarify. Totally in support of your request   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40393) Internationalize all the error messages in Declarative

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-40393  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40393  
 
 
  Internationalize all the error messages in Declarative   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40393) Internationalize all the error messages in Declarative

[scm_issue_l...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40393  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Internationalize all the error messages in Declarative   
 

  
 
 
 
 

 
 Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTMethodCall.java pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStep.java pipeline-model-api/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ast/Messages.properties pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Parser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DeclarativeLinterCommandTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WhenStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterActionTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/GroovyShellDecoratorImplTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParserTest.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/165db74375e95b484825b41f6631b2c966c7a8ed Log: [FIXED JENKINS-40393] i18n for validation messages  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
  

[JIRA] (JENKINS-40046) Add option to disable internal shared library

[i...@torstenreinhard.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Torsten Reinhard commented on  JENKINS-40046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to disable internal shared library   
 

  
 
 
 
 

 
 I´ve also deleted it - but in any case someone will push content back to this internal repo it´ll take some time to figure this out.  So for me with the option to configure external hosted repositories there´s no need at all for this internal one - so an option to switch it off would be nice.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40352) Duplicate changesets in pipeline jobs

[ra...@java.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Krzysztof Malinowski commented on  JENKINS-40352  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Duplicate changesets in pipeline jobs   
 

  
 
 
 
 

 
 I had this case when pipeline explicitly configured 'checkout git ...' instead of using 'checkout scm'. One changelog came from Git configuration in job (which is used to get Jenkinsfile) and the other came from explicitly configured scm in Jenkinsfile. Replacing 'checkout git ...' with 'checkout scm' in Jenkinsfile fixed the issue for me.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40481) Certificate error from time to time

[yassenvladimi...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasen Vladimirov closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40481  
 
 
  Certificate error from time to time   
 

  
 
 
 
 

 
Change By: 
 Yasen Vladimirov  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40569) @Grab does not override already loaded classes

[hans.sch...@sap.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hans Schulz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40569  
 
 
  @Grab does not override already loaded classes   
 

  
 
 
 
 

 
Change By: 
 Hans Schulz  
 

  
 
 
 
 

 
 When using @Grab annotation in Pipeline scripts or global libs, classes which are already in the jenkins classloader do not get overridden.Example:Trying to grab com.bettercloud:vault-java-driver:1.2.0 while havinghttps:// github wiki . com/jenkinsci/hashicorp jenkins - vault-plugin ci.org / blob display / master JENKINS / pom.xml HashiCorp+Vault+Plugin  (depends on com.bettercloud:vault-java-driver:1.1.0) installed gives you classes in version 1.1.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40569) @Grab does not override already loaded classes

[hans.sch...@sap.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hans Schulz commented on  JENKINS-40569  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: @Grab does not override already loaded classes   
 

  
 
 
 
 

 
 Actually I just copied the Component of JENKINS-16361; I've changed it to pipeline.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40569) @Grab does not override already loaded classes

[hans.sch...@sap.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hans Schulz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40569  
 
 
  @Grab does not override already loaded classes   
 

  
 
 
 
 

 
Change By: 
 Hans Schulz  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 job-dsl-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40569) @Grab does not override already loaded classes

[m...@daniel-spilker.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-40569  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: @Grab does not override already loaded classes   
 

  
 
 
 
 

 
 The description mentions Pipeline, but you assigned the jdb-dsl-plugin component. Pipeline and Job DSL are different things. Which did you mean?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40571) Jira: Create new version

[yassenvladimi...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yasen Vladimirov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40571  
 
 
  Jira: Create new version   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2016-12-20-16-47-23-195.png  
 
 
Components: 
 jira-plugin  
 
 
Created: 
 2016/Dec/20 2:49 PM  
 
 
Environment: 
 JIRA plugin 2.3  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Yasen Vladimirov  
 

  
 
 
 
 

 
 Hi, saw in 2.3 you can create the version in jira in Build. But filed has no boxes. Where in Post-Build you can. 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
   

[JIRA] (JENKINS-40479) WithCredentials annotation flaky behaviour

[mfra...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Manuel Franco resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40479  
 
 
  WithCredentials annotation flaky behaviour   
 

  
 
 
 
 

 
Change By: 
 Manuel Franco  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-35656) Inconsistent timezone display

[aubert...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandre Aubert commented on  JENKINS-35656  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistent timezone display   
 

  
 
 
 
 

 
 It's now ok after upgrading to 1.37.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-35656) Inconsistent timezone display

[aubert...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexandre Aubert commented on  JENKINS-35656  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Inconsistent timezone display   
 

  
 
 
 
 

 
 Hi, I have the same problem but the problem is in the left part showing UTC time although user.timezone is well set to 'Europe/Paris' (in my context). This information is not considered in the build history panel. And also at the bottom 'page generated at : UTC time' instead of local time. This seems to be a regression in a recent version of Jenkins (i'm using 1.36). Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40046) Add option to disable internal shared library

[phil.mcar...@cloudgine.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Phil McArdle commented on  JENKINS-40046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to disable internal shared library   
 

  
 
 
 
 

 
 I just hit this. I don't know why or when it chooses to use the internal library, in my case. It was almost as if some files were from the new library, and some from the old, given my errors. I've deleted the contents of the internal library now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-40126) Add tests for jgit

[rarabaol...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Raul Arabaolaza updated  JENKINS-40126  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40126  
 
 
  Add tests for jgit   
 

  
 
 
 
 

 
Change By: 
 Raul Arabaolaza  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





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