[JIRA] (JENKINS-37493) Cannot connect charts repostory

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Leon Huang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37493  
 
 
  Cannot connect charts repostory   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Guillermo Sanchez Urien  
 
 
Components: 
 kubernetes-ci-plugin  
 
 
Created: 
 2016/Aug/18 5:25 AM  
 
 
Environment: 
 Jenkins ver 2.7.1  kubernetes-ci-plugin ver 1.1  Jenkins running in a docker image pulled from "https://hub.docker.com/_/jenkins/"  
 
 
Labels: 
 plugin jenkins  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Leon Huang  
 

  
 
 
 
 

 
 The container running in the intranet with the HTTP proxy to access internet. When configure the 'Charts Repository Configurations' with the URL 'https://github.com/helm/charts' as the plugin readme instruct, 'connection timeout' showed. The Jenkins Manage Plugins has the advanced option with HTTP proxy set properly and plugins can be downloaded through that proxy. Stack trace javax.servlet.ServletException: rx.exceptions.OnErrorNotImplementedException: connect timed out at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at 

[JIRA] (JENKINS-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum assigned an issue to Paul Allen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Assignee: 
 Paul Allen  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 token-macro-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Assignee: 
 Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 p4-plugin  
 
 
Component/s: 
 email-ext-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum assigned an issue to Alex Earl  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Assignee: 
 David van Laatum Alex Earl  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 email-ext-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 email-ext-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[rob.pe...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Petti assigned an issue to David van Laatum  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 Rob Petti  
 
 
Assignee: 
 Rob Petti David van Laatum  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[rob.pe...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Petti commented on  JENKINS-36572  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
 You said you are using the p4-plugin, not the perforce-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-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ edited a comment on  JENKINS-34563  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine   
 

  
 
 
 
 

 
 The reason seems to be that REPOSITORY_EVENT is ignored by Jenkins when the repository was not forked: see https://github.com/jenkinsci/github-organization-folder-plugin/blob/master/src/main/java/org/jenkinsci/plugins/orgfolder/github/RepositoryGHEventSubscriber.java#L90 My understanding is that when a new repository is created, the REPOSITORY_EVENT is ignored because the repository is not a fork. When the `Jenkinsfile` is added, the PUSH_EVENT does not match any repository because it hasn't been created by Folder computation.  
 

  
 
 
 
 

 
 
 

 
 
 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-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ commented on  JENKINS-34563  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine   
 

  
 
 
 
 

 
 The reason seems to be that REPOSITORY_EVENT is ignored by Jenkins when the repository was not forked: see https://github.com/jenkinsci/github-organization-folder-plugin/blob/master/src/main/java/org/jenkinsci/plugins/orgfolder/github/RepositoryGHEventSubscriber.java#L90  
 

  
 
 
 
 

 
 
 

 
 
 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-36773) Pipeline name does not have spaces between slashes

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-36773  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline name does not have spaces between slashes   
 

  
 
 
 
 

 
 Thorsten Scherler can it be made to display the full folder path?  
 

  
 
 
 
 

 
 
 

 
 
 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-37492) Propose adding `diff` utility step

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Wood created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37492  
 
 
  Propose adding `diff` utility step   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 rsandell  
 
 
Components: 
 pipeline-utility-steps-plugin  
 
 
Created: 
 2016/Aug/18 3:52 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Owen Wood  
 

  
 
 
 
 

 
 Currently, diffing files requires using OS specific implementations (sh, bat).  This has the potential of triggering security approval, which can be an inconvenience. Proposing add new `diff` utility step, to allow OS agnostic use in PIpeline jobs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
  

[JIRA] (JENKINS-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum assigned an issue to Rob Petti  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It only does it with perforce plugin which suggests perforce is doing something different to every other scm plugin. If you can point out what, I may be able to fix but I can not do anything with this without something  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Assignee: 
 David van Laatum Rob Petti  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[rob.pe...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Petti commented on  JENKINS-36572  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
 Not related to 'perforce-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[rob.pe...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Petti assigned an issue to David van Laatum  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 Rob Petti  
 
 
Assignee: 
 Rob Petti David van Laatum  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[rob.pe...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Petti updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 Rob Petti  
 
 
Component/s: 
 perforce-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-37104) Ensure matrix projects do not break blue ocean

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-37104  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37104  
 
 
  Ensure matrix projects do not break blue ocean   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
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-37478) OWASP does not release files from scan

[steve.spring...@owasp.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett stopped work on  JENKINS-37478  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
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-37478) OWASP does not release files from scan

[steve.spring...@owasp.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett commented on  JENKINS-37478  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: OWASP does not release files from scan   
 

  
 
 
 
 

 
 I've seen this behavior on Windows occasionally as well. Best practice is to 
 
setup a shared data directory outside the workspace 
create a job which blocks all other DC jobs which performs an Update Only against the shared data directory 
disable auto update on individual jobs and specify the shared data directory 
 This will allow multiple DC jobs to run simultaneously without the possibility of database corruption or locking issues, and the analysys will be a bit faster on each job because it doesn't have to update all the time. I'd recommend to perform the Update Only job once a day. Not only will this provide best practice but should eliminate the issue on Windows as well.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37478) OWASP does not release files from scan

[steve.spring...@owasp.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett started work on  JENKINS-37478  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
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-37478) OWASP does not release files from scan

[steve.spring...@owasp.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett assigned an issue to Steve Springett  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37478  
 
 
  OWASP does not release files from scan   
 

  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
Assignee: 
 Steve Springett  
 

  
 
 
 
 

 
 
 

 
 
 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-37437) Pipeline integration for OWASP checker

[steve.spring...@owasp.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett commented on  JENKINS-37437  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline integration for OWASP checker   
 

  
 
 
 
 

 
 Support for workflow was added by CloudBees. https://github.com/jenkinsci/dependency-check-plugin/pull/3 If for some reason it doesn't work, perhaps getting the original committers involved may 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-37467) OWASP Dependency-Check Plugin with default options fails

[steve.spring...@owasp.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing as duplicate  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37467  
 
 
  OWASP Dependency-Check Plugin with default options fails   
 

  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
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-37467) OWASP Dependency-Check Plugin with default options fails

[steve.spring...@owasp.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Springett resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37467  
 
 
  OWASP Dependency-Check Plugin with default options fails   
 

  
 
 
 
 

 
Change By: 
 Steve Springett  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lee Webb created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37491  
 
 
  Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 github-branch-source-plugin  
 
 
Created: 
 2016/Aug/18 1:59 AM  
 
 
Environment: 
 github-branch-source 1.8.1  jenkins 2.18  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Lee Webb  
 

  
 
 
 
 

 
 When 'Build Origin PRs (merge with base branch)' is selected any PR's which are filed against a base branch are re-triggered when the base branch changes. While this is all fine if you have a small # of PR's & the builds are quick, if you have a large team & backlog of PR's then any merge to the base branch will automatically trigger every PR which is using the same baseline. When you then end up with is a Jenkins that has a massive queue to process & github often complaining that you've exceeded the API rate limit. The concept of building the merge branch is great, however at the moment I really can't use it because of the previously stated behaviour & causes massive issues for our builds. Previous versions of the plugin didn't exhibit this behaviour at all, nor do other systems like travis which build PR's using the merge branch, nor did the github pull request builder plugin. As a workaround I'm forced to use the 'Build Origin PRs (unmerged HEAD)' and then conduct the merge or checkout of the GH merge branch itself within the pipeline which is less than ideal. Can we have an option to inhibit a re-trigger when the baseline changes for PRs with merge? btw I like where this plugin is going  
 

  
 
 
   

[JIRA] (JENKINS-37335) github webhooks not working after changing repository URL with .ssh/config

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37335  
 
 
  github webhooks not working after changing repository URL with .ssh/config   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Summary: 
 github webhooks not working after changing  to deploy keys  repository URL with .ssh/config  
 

  
 
 
 
 

 
 
 

 
 
 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-37490) Add option to remove developer from default recipient list in EmailExtStep

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37490  
 
 
  Add option to remove developer from default recipient list in EmailExtStep   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 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-37490) Add option to remove developer from default recipient list in EmailExtStep

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum edited a comment on  JENKINS-37490  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to remove developer from default recipient list in EmailExtStep   
 

  
 
 
 
 

 
 check https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/EmailExtStep.java#L155I fixed this recently are you using the most recent version . ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-36846) request to have a contribution guildeline to build email-ext-plugin from source

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36846  
 
 
  request to have a contribution guildeline to build email-ext-plugin from source   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Status: 
 Open 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-37038) Jenkins can't send mail

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37038  
 
 
  Jenkins can't send mail
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
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-37333) EMail Extension Plugin - New Option for developers, that not sending mails to developers from merges

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum closed an issue as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37333  
 
 
  EMail Extension Plugin - New Option for developers, that not sending mails to developers from merges   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Won't 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum assigned an issue to Rob Petti  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Assignee: 
 David van Laatum Rob Petti  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 email-ext-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 email-ext-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 email-ext-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-37482) AbstractGitSCMSource.retrieve fails due to nonexistent cache directory

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-37482  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: AbstractGitSCMSource.retrieve fails due to nonexistent cache directory   
 

  
 
 
 
 

 
 Thanks for the pull request to resolve this. The JGit implementation in git-client will create the directory if it does not already exist. That's why this condition was not detected previously by those using the multi-branch pipeline plugins. They previously only used the JGit implementation. The command line implementation in git client does not create the directory if it does not already exist. PR424 detected that same condition and has a change pending in the git client command line implementation to create the directory if it does not already exist.  
 

  
 
 
 
 

 
 
 

 
 
 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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 email-ext-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-36572) Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36572  
 
 
  Email Extension Plugin - implement an option to only show last changelist (corresponding to the build) and not all changelist since last successful build   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Component/s: 
 perforce-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-37466) Jenkins -API Automation -Blocker

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37466  
 
 
  Jenkins -API Automation -Blocker   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
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-37466) Jenkins -API Automation -Blocker

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-37466  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins -API Automation -Blocker   
 

  
 
 
 
 

 
It is ant style pattern sytax  
 

  
 
 
 
 

 
 
 

 
 
 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-37466) Jenkins -API Automation -Blocker

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37466  
 
 
  Jenkins -API Automation -Blocker   
 

  
 
 
 
 

 
Change By: 
 David van Laatum  
 
 
Attachment: 
 Screen Shot 2016-08-18 at 11.07.51 AM.png  
 

  
 
 
 
 

 
 
 

 
 
 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-37490) Add option to remove developer from default recipient list in EmailExtStep

[da...@vanlaatum.id.au (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David van Laatum commented on  JENKINS-37490  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add option to remove developer from default recipient list in EmailExtStep   
 

  
 
 
 
 

 
 check https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/EmailExtStep.java#L155 I fixed this recently are you using the most recent version.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37427) Handle Matrix project in UI

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Ivan Meredith  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37427  
 
 
  Handle Matrix project in UI   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Ivan Meredith  
 

  
 
 
 
 

 
 
 

 
 
 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-37471) Build Pipeline Plugin Maunal Trigger not working in Folders

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Bidewell updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37471  
 
 
  Build Pipeline Plugin Maunal Trigger not working in Folders   
 

  
 
 
 
 

 
Change By: 
 Mark Bidewell  
 

  
 
 
 
 

 
 I am trying to organize jobs in jenkins using the folders plugin.  When trying to manually trigger a build in the pipeline between two jobs in the folder I receive an exception similar to the following: Aug 16, 2016 4:52:51 PM au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView triggerBuild SEVERE: No upstream trigger found for this projectAccelerated Client Experience » service-ace-tracker-api-devacetrack01-deployAug 16, 2016 4: 50 52 : 17 51  PM  se  org . diabol kohsuke . jenkins stapler . pipeline.DeliveryPipelineView triggerManual HttpResponseRenderer$Default handleJavaScriptProxyMethodCall WARNING:  Could not trigger manual build ACE  call to / service-ace-tracker-api-devacetrack01-deploy for upstream ACE $stapler / service bound/6c2ef2bd - ace 4b56 - tracker 4307 - api 9b6b - ci id: 5 8407f34bfbf1/triggerManualBuild failedjava .  Did you mean to specify lang.IllegalStateException: No upstream trigger found for this projectAccelerated Client Experience »  service-ace-tracker-api-devacetrack01-deploy ?  se.diabol.jenkins.pipeline.trigger.TriggerException: Could not trigger  at  se  au . diabol com . jenkins centrumsystems . pipeline hudson . trigger plugin . BPPManualTrigger buildpipeline . triggerManual BuildPipelineView.triggerBuild ( BPPManualTrigger BuildPipelineView .java: 38 496 ) at  se  au . diabol com . jenkins centrumsystems . pipeline hudson . DeliveryPipelineView plugin . triggerManual buildpipeline.BuildPipelineView.triggerManualBuild ( DeliveryPipelineView BuildPipelineView .java: 419 405 ) at  se  sun . diabol reflect . jenkins NativeMethodAccessorImpl . pipeline.PipelineApi.doManualStep invoke0 ( PipelineApi.java:50 Native Method ) at sun.reflect. GeneratedMethodAccessor2261 NativeMethodAccessorImpl .invoke( Unknown Source NativeMethodAccessorImpl.java:62 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$ 1 _javascript_ProxyMethodDispatcher .doDispatch(MetaClass.java: 124 474 ) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$ 3 11 . doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher. dispatch( NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler. MetaClass $5 . doDispatch(MetaClass. java: 233 380 ) at org.kohsuke.stapler. 

[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37323  
 
 
  Ensure that Pipeline Graph can handle stage blocks   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0- pre- beta-1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-37490) Add option to remove developer from default recipient list in EmailExtStep

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Owen Wood created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37490  
 
 
  Add option to remove developer from default recipient list in EmailExtStep   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 David van Laatum  
 
 
Components: 
 email-ext-plugin  
 
 
Created: 
 2016/Aug/18 1:21 AM  
 
 
Labels: 
 pipeline  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Owen Wood  
 

  
 
 
 
 

 
 Currently, for the pipeline step (emailext) it seems that developers add added by default to recipient list.  https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/EmailExtStep.java#L153 https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/plugins/trigger/AlwaysTrigger.java#L41 Dont see any options available to remove this if needed (without resorting to hacking with groovy init script) Proposing making this a configurable option.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
  

[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey started work on  JENKINS-37323  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
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-37293) ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks

[e...@borgstrom.ca (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Evan Borgstrom commented on  JENKINS-37293  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks   
 

  
 
 
 
 

 
 Just upgraded from 1.4 to 1.5. The issue persists.  
 

  
 
 
 
 

 
 
 

 
 
 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-37293) ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks

[e...@borgstrom.ca (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Evan Borgstrom updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37293  
 
 
  ECS Agents are not deleted because Jenkins is unable to delete logs due to NFS locks   
 

  
 
 
 
 

 
Change By: 
 Evan Borgstrom  
 
 
Environment: 
 jenkins 2.7.2amazon-ecs 1. 4 5  
 

  
 
 
 
 

 
 
 

 
 
 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-37332) java.io.IOException: Failed to rename during Plugin Update

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Or maybe not. Trying to locate/fix the issue wasn't all that successful. Oleg Nenashev told me he'll look into this tomorrow, so for record keeping, assigning to him for now.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37332  
 
 
  java.io.IOException: Failed to rename during Plugin Update   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 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-37489) Jenkins UI slow page load (big TTFB) - possible LDAP issue

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrii Melnyk updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37489  
 
 
  Jenkins UI slow page load (big TTFB) - possible LDAP issue   
 

  
 
 
 
 

 
Change By: 
 Andrii Melnyk  
 

  
 
 
 
 

 
 h5. Symptoms:periodically Jenkins UI becomes very slow, sometimes returns 504, restart Jenkins service helps, but just for a short period of time. The periodicity of problems depends on a number of users, which use UI. No strange logs, just Jenkins web UI respond time becomes critical (nginx errors: "upstream timed out (110: Connection timed out) while reading response header from upstream")Average CPU load < 10%, Memory usage ~ 500Mb (heap size ~ 2.5Gb), Active Threads has critical values (max=38) and it matches with the time of UI problemsGraphs (from [Monitoring plugin|https://wiki.jenkins-ci.org/display/JENKINS/Monitoring]) in attachmentsMonitoring plugin also has "Current requests" view, and there I find reason of this problem: lots of pending requests for same URLs, something like _"/job/MY-JOB/changes GET"_, _"/job/MY-JOB/BUILD-ID/wfapi/changesets?_=1471452733792 ajax GET"_I tried to kill this requests (to free threads) using "Kill" button in Monitoring plugin, and after that I find [helpful log records|https://gist.github.com/gips0n/94dec48afcc61c1960f8db2a8e60a43e].Second record points on that Jenkins tries to *loadUserByUsername* and it's strange, because I configured Jenkins search query to search users by uid (login) (according to [official configuration guide|https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin#LDAPPlugin-Configuration]), but not "FirstName LastName". Than I checked ldap server logs and discovered high CPU usage, high LA, and tons of incorrect search queries from Jenkins in slapd.log:{noformat}Aug 17 17:36:14 ldap-server slapd[1183]: conn=249907 fd=26 ACCEPT from IP=5.2.1.1:43078 (IP=0.0.0.0:636)Aug 17 17:36:15 ldap-server slapd[1183]: conn=249907 fd=26 TLS established tls_ssf=256 ssf=256Aug 17 17:36:15 ldap-server slapd[1183]: conn=249907 op=0 BIND dn="cn=jenkins-user,ou=system,dc=example,dc=com" method=128Aug 17 17:36:15 ldap-server slapd[1183]: conn=249907 op=0 BIND dn="cn=jenkins-user,ou=system,dc=example,dc=com" mech=SIMPLE ssf=0Aug 17 17:36:15 ldap-server slapd[1183]: conn=249907 op=0 RESULT tag=97 err=0 text=Aug 17 17:36:15 ldap-server slapd[1183]: conn=249907 op=1 SRCH base="ou=people,dc=example,dc=com" scope=2 deref=3 filter="(uid=firstname lastname)"Aug 17 17:36:15 ldap-server slapd[1183]: conn=249907 op=1 SEARCH RESULT tag=101 err=0 nentries=0 text=Aug 17 17:36:15 ldap-server slapd[1183]: conn=249907 op=2 UNBINDAug 17 17:36:15 ldap-server slapd[1183]: conn=249907 fd=26 closedAug 17 17:36:15 ldap-server slapd[1183]: conn=249911 fd=25 ACCEPT from IP=5.2.1.1:43132 (IP=0.0.0.0:636)Aug 17 17:36:16 ldap-server slapd[1183]: conn=249911 fd=25 TLS established tls_ssf=256 ssf=256Aug 17 17:36:16 ldap-server slapd[1183]: conn=249911 op=0 BIND dn="cn=jenkins-user,ou=system,dc=example,dc=com" method=128Aug 17 17:36:16 ldap-server slapd[1183]: conn=249911 op=0 BIND 

[JIRA] (JENKINS-37489) Jenkins UI slow page load (big TTFB) - possible LDAP issue

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrii Melnyk updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37489  
 
 
  Jenkins UI slow page load (big TTFB) - possible LDAP issue   
 

  
 
 
 
 

 
Change By: 
 Andrii Melnyk  
 
 
Environment: 
 jenkins 2.7.2  from http://pkg.jenkins-ci.org/debian-stable jenkins LDAP plugin 1.12 Ubuntu 16.04  
 

  
 
 
 
 

 
 
 

 
 
 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-37489) Jenkins UI slow page load (big TTFB) - possible LDAP issue

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrii Melnyk created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37489  
 
 
  Jenkins UI slow page load (big TTFB) - possible LDAP issue   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Attachments: 
 activeThreads.png, cpu.png, usedMemory.png  
 
 
Components: 
 core, ldap-plugin  
 
 
Created: 
 2016/Aug/17 10:10 PM  
 
 
Environment: 
 jenkins 2.7.2  jenkins LDAP plugin 1.12  
 
 
Labels: 
 slow UI ldap  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Andrii Melnyk  
 

  
 
 
 
 

 
 Symptoms: periodically Jenkins UI becomes very slow, sometimes returns 504, restart Jenkins service helps, but just for a short period of time. The periodicity of problems depends on a number of users, which use UI. No strange logs, just Jenkins web UI respond time becomes critical (nginx errors: "upstream timed out (110: Connection timed out) while reading response header from upstream") Average CPU load < 10%, Memory usage ~ 500Mb (heap size ~ 2.5Gb), Active Threads has critical values (max=38) and it matches with the time of UI problems Graphs (from Monitoring plugin) in attachments Monitoring plugin also has "Current requests" view, and there I find reason of this problem: lots of pending requests for same URLs, something like "/job/MY-JOB/changes GET", "/job/MY-JOB/BUILD-ID/wfapi/changesets?=1471452733792 ajax GET"_ I tried to kill this requests (to free threads) using "Kill" button in Monitoring plugin, and after that I find helpful log records. 

[JIRA] (JENKINS-37489) Jenkins UI slow page load (big TTFB) - possible LDAP issue

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrii Melnyk commented on  JENKINS-37489  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins UI slow page load (big TTFB) - possible LDAP issue   
 

  
 
 
 
 

 
 https://issues.jenkins-ci.org/browse/JENKINS-20051 can be related?  
 

  
 
 
 
 

 
 
 

 
 
 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-17116) gracefull job termination

[mbells.w...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matthew Bells commented on  JENKINS-17116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: gracefull job termination   
 

  
 
 
 
 

 
 I'm also have problems with this. In particular, our nodes are running Ubuntu 14.04. We are using Jenkins to run some tests as part of the build. There are a few steps where interruption will cause communication failures, leaked temporary files gigabytes in size, and locks that are not undone. Orphaned process is very bad as well, since this could lead to a new build starting communication on the same channel prior to the previous one terminating. Like Martin d'Anjou indicated, we would need a timeout parameter, since the allowed timeout for SIGTERM may be about 300sec, which is probably a lot longer than someone implementing this fix may anticipate.  
 

  
 
 
 
 

 
 
 

 
 
 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-33632) docker.inside broken

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Danny Waite commented on  JENKINS-33632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: docker.inside broken   
 

  
 
 
 
 

 
 Guys, I'm also seeing this issue when running on Kubernetes as outlined in the following article https://cloud.google.com/solutions/configuring-jenkins-container-engine Any help appreciated, as Christopher mentioned this is a blocking 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-37488) Deprecated workflowJob should mention to use pipelineJob instead

[m...@interunion.ca (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marc Tardif created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37488  
 
 
  Deprecated workflowJob should mention to use pipelineJob instead   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2016/Aug/17 10:00 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marc Tardif  
 

  
 
 
 
 

 
 When using `workflowJob`, I get this warning in the console:  workflowJob is deprecated When looking at the docs [here](https://jenkinsci.github.io/job-dsl-plugin/), I read the comment:  // Create or updates a workflow job. Deprecated.  The warning, or the comment, or both should mention to use `pipelineJob` instead.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
   

[JIRA] (JENKINS-30232) p4-plugin creates p4 connection on both master and slave during checkout

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 stuart rowe closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30232  
 
 
  p4-plugin creates p4 connection on both master and slave during checkout   
 

  
 
 
 
 

 
Change By: 
 stuart rowe  
 
 
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-37219) Option to suppress automatic SCM trigger from Jenkinsfile

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-37219  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option to suppress automatic SCM trigger from Jenkinsfile   
 

  
 
 
 
 

 
 New PR - https://github.com/jenkinsci/branch-api-plugin/pull/48 - moving this up to branch-api and allowing for both disabling branch indexing triggers and enabling them when they're otherwise suppressed by branch or folder properties.  
 

  
 
 
 
 

 
 
 

 
 
 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-37487) Aborted P4 syncs can leave files locked

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 stuart rowe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37487  
 
 
  Aborted P4 syncs can leave files locked   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2016/Aug/17 9:34 PM  
 
 
Environment: 
 OS: Windows 7  P4Server: Server version: P4D/LINUX26X86_64/2015.2/1394499 (2016/05/28)  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 stuart rowe  
 

  
 
 
 
 

 
 Users have reported that files have been left locked by the p4 process after an in progress sync was aborted.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  

[JIRA] (JENKINS-37486) NPE: Failed to abort at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167)

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37486  
 
 
  NPE: Failed to abort at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167)   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Priority: 
 Blocker Major  
 

  
 
 
 
 

 
 Pipeline jobs could not be cancelled.The pipeline thread dump showed  {code:none} java.lang.NullPointerExceptionat org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.stop(DurableTaskStep.java:211) {code}   suggesting a problem akin to JENKINS-34021 but for launcher rather than listener. This is blocking [https://issues.jenkins-ci.org/browse/JENKINS-34021].  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

  

[JIRA] (JENKINS-35567) multibranch project and ssh+git broken

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-35567  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: multibranch project and ssh+git broken   
 

  
 
 
 
 

 
 I believe this is covered by git client plugin PR424  
 

  
 
 
 
 

 
 
 

 
 
 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-37486) NPE: Failed to abort at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167)

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 James Sweet created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37486  
 
 
  NPE: Failed to abort at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 workflow-plugin  
 
 
Created: 
 2016/Aug/17 9:25 PM  
 
 
Environment: 
 Jenkins v1.642.18.3   pipeline-build-step:2.2 'Pipeline: Build Step'  pipeline-input-step:2.1 'Pipeline: Input Step'  pipeline-rest-api:1.7 'Pipeline: REST API Plugin'  pipeline-stage-step:2.1 'Pipeline: Stage Step'  pipeline-stage-view:1.7 'Pipeline: Stage View Plugin'  pipeline-utility-steps:1.1.6 'Pipeline Utility Steps'   workflow-aggregator:2.2 'Pipeline'  workflow-api:2.1 'Pipeline: API'  workflow-basic-steps:2.1 'Pipeline: Basic Steps'  workflow-cps:2.12 'Pipeline: Groovy'  workflow-cps-checkpoint:2.2 'CloudBees Pipeline: Groovy Checkpoint Plugin'  workflow-cps-global-lib:2.2 'Pipeline: Shared Groovy Libraries'  workflow-durable-task-step:2.4 'Pipeline: Nodes and Processes'  workflow-job:2.5 'Pipeline: Job'  workflow-multibranch:2.8 'Pipeline: Multibranch'  workflow-remote-loader:1.2 'Jenkins Pipeline Remote Loader Plugin'  workflow-scm-step:2.2 'Pipeline: SCM Step'  workflow-step-api:2.3 'Pipeline: Step API'  workflow-support:2.2 'Pipeline: Supporting APIs'  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 James Sweet  
 

  
 
 
 
 

 
 Pipeline jobs could not be cancelled. The pipeline thread dump showed  java.lang.NullPointerException at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:167) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.stop(DurableTaskStep.java:211) suggesting a problem akin to JENKINS-34021 but for launcher rather than listener. This is blocking 

[JIRA] (JENKINS-36958) Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-36958  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code   
 

  
 
 
 
 

 
 @jgl...@cloudbees.com I think PR424 die the git client plugin handles 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-37484) Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Sobral commented on  JENKINS-37484  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/pipeline-build-step-plugin/pull/6  
 

  
 
 
 
 

 
 
 

 
 
 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-37457) Create Task for executing Groovy Script

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 stuart rowe assigned an issue to stuart rowe  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37457  
 
 
  Create Task for executing Groovy Script   
 

  
 
 
 
 

 
Change By: 
 stuart rowe  
 
 
Assignee: 
 stuart rowe  
 

  
 
 
 
 

 
 
 

 
 
 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-37485) Propagate Job params to script does nothing

[imoutsat...@msn.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37485  
 
 
  Propagate Job params to script does nothing   
 

  
 
 
 
 

 
Change By: 
 Ioannis Moutsatsos  
 

  
 
 
 
 

 
 I have a script executed through the scriptler plugin and I would like to use in the script job environment variables such as BUILD_URL. At the beginnig of the script  I read the environment variables with {code: groovy java }def env = System.getenv() //also get the environment//then print to confirmenv.each{  println "${it.key} :${it.value}" }{code}Independent of whether I check the 'Propagate Job params to script' checkbox the parameters are the same and only related to the OS. I do not see any of the JOB related environement variables. See example screen shot attached  
 

  
 
 
 
 

 
 
 

 
 
 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-37485) Propagate Job params to script does nothing

[imoutsat...@msn.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37485  
 
 
  Propagate Job params to script does nothing   
 

  
 
 
 
 

 
Change By: 
 Ioannis Moutsatsos  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 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-37485) Propagate Job params to script does nothing

[imoutsat...@msn.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37485  
 
 
  Propagate Job params to script does nothing   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Dominik Bartholdi  
 
 
Attachments: 
 Untitled_Clipping_081716_051936_PM.jpg  
 
 
Components: 
 scriptler-plugin  
 
 
Created: 
 2016/Aug/17 9:19 PM  
 
 
Environment: 
 Scriptler v2.9 Jenkins v1.596.2  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ioannis Moutsatsos  
 

  
 
 
 
 

 
 I have a script executed through the scriptler plugin and I would like to use in the script job environment variables such as BUILD_URL. At the beginnig of the script I read the environment variables with  

 

Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


def env = System.getenv() //also get the environment
//then print to confirm
env.each{
  println "${it.key} :${it.value}" 
}
 

 Independent of whether I check the 'Propagate Job params to script' checkbox the parameters are the same and only related to the OS. I do not see any of the JOB related environement variables. See example screen shot attached  

[JIRA] (JENKINS-37484) Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Sobral created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37484  
 
 
  Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 workflow-plugin  
 
 
Created: 
 2016/Aug/17 9:12 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Sobral  
 

  
 
 
 
 

 
 The documentation for the Build step presently states this: 

 

result
typically SUCCESS, UNSTABLE, or FAILED (may be null for an ongoing build)
 

 However, the actual state is FAILURE, not FAILED.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-37483) Deadlock caused by synchronized methods in EC2Cloud

[todd.r...@urjanet.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Todd Rose commented on  JENKINS-37483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock caused by synchronized methods in EC2Cloud   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/ec2-plugin/pull/214  
 

  
 
 
 
 

 
 
 

 
 
 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-37332) java.io.IOException: Failed to rename during Plugin Update

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-37332  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.io.IOException: Failed to rename during Plugin Update   
 

  
 
 
 
 

 
 Responsible commit through git bisect (on OS X, with lsof, and running using java -jar jenkins.war): https://github.com/jenkinsci/jenkins/pull/2489/commits/2a450e5ac2ecd83a54f05c83729852073601816e 

 
$ git bisect good
2a450e5ac2ecd83a54f05c83729852073601816e is the first bad commit
commit 2a450e5ac2ecd83a54f05c83729852073601816e
Author: Stephen Connolly 
Date:   Thu Jul 28 16:09:21 2016 +0100

[FIXED JENKINS-37041] Ensure that detached plugins are always at least their minimum version

:04 04 fdfb36c7fafa895b74c030135405fe2920cfc96f d0ead1a29141a585923651e2593c826ce0fdd893 M  core

$ git bisect log
git bisect start
# bad: [e02419c61a562d991d8a068a34f357b2342747ca] [maven-release-plugin] prepare release jenkins-2.16
git bisect bad e02419c61a562d991d8a068a34f357b2342747ca
# good: [ae59dde643367c90ec4427490b841db9570e32ad] [maven-release-plugin] prepare release jenkins-2.15
git bisect good ae59dde643367c90ec4427490b841db9570e32ad
# good: [d7f62a29a6ead4ad35a64a3fcf764d9e25cb6185] Merge pull request #2480 from stephenc/jenkins-36871-prep
git bisect good d7f62a29a6ead4ad35a64a3fcf764d9e25cb6185
# bad: [65adca296d42c8038bad27eb1a10b40d71a163f0] Noting merge of JENKINS-37041
git bisect bad 65adca296d42c8038bad27eb1a10b40d71a163f0
# bad: [d92fd4cc63e19c60e374e45e045dcdce2d91e951] [JENKINS-37041] Address Code review comments
git bisect bad d92fd4cc63e19c60e374e45e045dcdce2d91e951
# good: [e7b39efff80ebdd50ddd8ab20ab2adee1d5b1dcc] Merge pull request #2485 from stephenc/jenkins-36996
git bisect good e7b39efff80ebdd50ddd8ab20ab2adee1d5b1dcc
# bad: [2a450e5ac2ecd83a54f05c83729852073601816e] [FIXED JENKINS-37041] Ensure that detached plugins are always at least their minimum version
git bisect bad 2a450e5ac2ecd83a54f05c83729852073601816e
# good: [8e536513e8d7b08cda63201ba14ee6e30289d713] [JENKINS-36996] Noting merge
git bisect good 8e536513e8d7b08cda63201ba14ee6e30289d713
# first bad commit: [2a450e5ac2ecd83a54f05c83729852073601816e] [FIXED JENKINS-37041] Ensure that detached plugins are always at least their minimum version
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[JIRA] (JENKINS-37483) Deadlock caused by synchronized methods in EC2Cloud

[todd.r...@urjanet.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Todd Rose commented on  JENKINS-37483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock caused by synchronized methods in EC2Cloud   
 

  
 
 
 
 

 
 I think the quickest fix for this is to make the non-static connect() method synchronize on the class object. connect() is really the only thing that I can see that can be invoked from a lot of different contexts and threads.  
 

  
 
 
 
 

 
 
 

 
 
 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-37481) Upgrading from 1.20.0 to 1.21.0 causes github org webhooks not to work

[sa...@virtoway.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Siniouguine updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37481  
 
 
  Upgrading from 1.20.0 to 1.21.0 causes github org webhooks not to work   
 

  
 
 
 
 

 
Change By: 
 Alexander Siniouguine  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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-37450) Cannot create nestedView with job-dsl 1.49

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37450  
 
 
  Cannot create nestedView with job-dsl 1.49   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
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-37483) Deadlock caused by synchronized methods in EC2Cloud

[todd.r...@urjanet.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Todd Rose created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37483  
 
 
  Deadlock caused by synchronized methods in EC2Cloud   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Francis Upton  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2016/Aug/17 8:02 PM  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Todd Rose  
 

  
 
 
 
 

 
 This is against 1.35 EC2Cloud.java has several synchronized methods that can be called from various timers. getNewOrExistingAvailableSlave() and connect() are the problematic ones in this case. Our installation heavily utilizes the spot market and we have a high number of nodes in our fleet. Under load you can easily get into a situation where one thread is terminating an instance and at the same time another is trying to provision a new one. The liberal use of synchronized methods in EC2Cloud is not safe. A finer-grained locking strategy, or moving to a lockless strategy is advisable. {{ T1 "Handling POST /view/Adhoc/job/admin_FailedSourceReplayRunner/build from xxx.xx.xxx.xx : RequestHandlerThread2247" – parking to wait for <0x00060090c078> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) which is held by T2 "EC2 alive slaves monitor thread"  "Handling POST /view/Adhoc/job/admin_FailedSourceReplayRunner/build from xxx.xx.xxx.xx : RequestHandlerThread2247": at sun.misc.Unsafe.park(Native Method) 
 
parking to wait for <0x00060090c078> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) 

[JIRA] (JENKINS-26107) Labeled block

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26107  
 
 
  Labeled block   
 

  
 
 
 
 

 
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-26107) Labeled block

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-26107  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Labeled block   
 

  
 
 
 
 

 
 Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/support/steps/StageStep.java src/main/java/org/jenkinsci/plugins/workflow/support/steps/StageStepExecution.java src/main/resources/org/jenkinsci/plugins/workflow/support/steps/StageStep/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/support/steps/StageStep/help-concurrency.html src/main/resources/org/jenkinsci/plugins/workflow/support/steps/StageStep/help.html src/main/resources/org/jenkinsci/plugins/workflow/support/steps/stage/Messages.properties src/test/java/org/jenkinsci/plugins/workflow/support/steps/StageStepConfigTest.java src/test/java/org/jenkinsci/plugins/workflow/support/steps/StageStepTest.java http://jenkins-ci.org/commit/pipeline-stage-step-plugin/114b000eb50d39e132b6493fed207321ef49a5bc Log: [FIXED JENKINS-26107] stage may now take a block; the original mode is deprecated.  
 

  
 
 
 
 

 
 
 

 
 
 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-37482) AbstractGitSCMSource.retrieve fails due to nonexistent cache directory

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-37482  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-37482) AbstractGitSCMSource.retrieve fails due to nonexistent cache directory

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-37482  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37482  
 
 
  AbstractGitSCMSource.retrieve fails due to nonexistent cache directory   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas started work on  JENKINS-34876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
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-37482) AbstractGitSCMSource.retrieve fails due to nonexistent cache directory

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37482  
 
 
  AbstractGitSCMSource.retrieve fails due to nonexistent cache directory   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2016/Aug/17 7:24 PM  
 
 
Labels: 
 multibranch  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 Not sure if this affects production systems, or indeed why it is not reported by everyone, but anyway I was unable to make AbstractGitSCMSource.retrieve(SCMHeadObserver, TaskListener) work in a test without this fix. (And there was no test for it.) Doing so failed with: 

 

hudson.plugins.git.GitException: Could not init $JENKINS_HOME/caches/git-4ab...
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:656)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(CliGitAPIImpl.java:181)
	at hudson.plugins.git.GitAPI.init(GitAPI.java:217)
	at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:275)
	at jenkins.scm.api.SCMSource.fetch(SCMSource.java:147)
	at jenkins.scm.api.SCMSource.retrieve(SCMSource.java:231)
	at jenkins.scm.api.SCMSource.fetch(SCMSource.java:176)
	at jenkins.plugins.git.AbstractGitSCMSourceTest.retrieveHeads(AbstractGitSCMSourceTest.java:74)
	at ...
Caused by: hudson.plugins.git.GitException: Error performing command: git init $JENKINS_HOME/caches/git-4ab...
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1726)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1695)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1691)
	at 

[JIRA] (JENKINS-36958) Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36958  
 
 
  Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code   
 

  
 
 
 
 

 
 Wrong component.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 git-client-plugin  
 
 
Component/s: 
 gitlab-plugin  
 
 
Component/s: 
 multi-branch-project-plugin  
 
 
Labels: 
 jenkins plugin multibranch  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 
  

[JIRA] (JENKINS-35567) multibranch project and ssh+git broken

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35567  
 
 
  multibranch project and ssh+git broken   
 

  
 
 
 
 

 
 Wrong component.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 multi-branch-project-plugin  
 
 
Labels: 
 multibranch  
 

  
 
 
 
 

 
 
 

 
 
 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-35565) multibranch project and git broken

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong component.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-35565  
 
 
  multibranch project and git broken   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 branch-api-plugin  
 
 
Component/s: 
 multi-branch-project-plugin  
 
 
Labels: 
 multibranch  
 
 
Assignee: 
 stephenconnolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

   

[JIRA] (JENKINS-37481) Upgrading from 1.20.0 to 1.21.0 causes github org webhooks not to work

[sa...@virtoway.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Siniouguine created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37481  
 
 
  Upgrading from 1.20.0 to 1.21.0 causes github org webhooks not to work   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Kirill Merkushev  
 
 
Components: 
 github-plugin  
 
 
Created: 
 2016/Aug/17 7:09 PM  
 
 
Environment: 
 Windows  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Alexander Siniouguine  
 

  
 
 
 
 

 
 When upgrading to the latest 1.21.0 version having 1.20.0 installed, webhooks from github are stop working with an error trace below (500 error reported by github). Downgrading back to the 1.20 solves the problem so must be something with a new version. java.lang.NullPointerException: Secret should be defined to compute sign at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:204) at org.jenkinsci.plugins.github.webhook.GHWebhookSignature.webhookSignature(GHWebhookSignature.java:41) at org.jenkinsci.plugins.github.webhook.RequirePostWithGHHookPayload$Processor.shouldProvideValidSignature(RequirePostWithGHHookPayload.java:149) at org.jenkinsci.plugins.github.webhook.RequirePostWithGHHookPayload$Processor.invoke(RequirePostWithGHHookPayload.java:74) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:26) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at 

[JIRA] (JENKINS-36229) API for UI to honour permissions

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey updated  JENKINS-36229  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36229  
 
 
  API for UI to honour permissions   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Austin commented on  JENKINS-34876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM   
 

  
 
 
 
 

 
 I observed the same behavior, but I came up with a hacky workaround... I wrote a shell script that will dump git tags into a sorted list that can be ingested as a property file when using the the Extended Choice Parameter plugin. 1) Run this script in the root of your git checkout dir: 


genVers.sh

 

git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > /tmp/versions.properties
 

 2) Install the Extended Choice Parameter plugin and add it to your job https://wiki.jenkins-ci.org/display/JENKINS/Extended+Choice+Parameter+plugin 3) Point the config to the property file you generated and set the key. See my attached example:   4) Test it
 

  
 
 
 
 

 
 
 

 
 
 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Austin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34876  
 
 
  Git Parameters not working for Pipeline projects and Jenkinsfile from SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Austin  
 
 
Attachment: 
 Screenshot_20160817_145625.png  
 

  
 
 
 
 

 
 
 

 
 
 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-36574) Add option to choose static notification context

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-36574  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36574  
 
 
  Add option to choose static notification context   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Austin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34876  
 
 
  Git Parameters not working for Pipeline projects and Jenkinsfile from SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Austin  
 
 
Attachment: 
 Screenshot_20160817_145201.png  
 

  
 
 
 
 

 
 
 

 
 
 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Austin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34876  
 
 
  Git Parameters not working for Pipeline projects and Jenkinsfile from SCM   
 

  
 
 
 
 

 
Change By: 
 Mark Austin  
 
 
Comment: 
 I observed the same problem.I came up with a workaround, note that you need git 2.0 in order to do this...1) I wrote a script that is executed inside of the git checkout root:[code]git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > versions.properties[code]  
 

  
 
 
 
 

 
 
 

 
 
 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-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Austin commented on  JENKINS-34876  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM   
 

  
 
 
 
 

 
 I observed the same problem. I came up with a workaround, note that you need git 2.0 in order to do this... 1) I wrote a script that is executed inside of the git checkout root: [code] git tag -l --sort=version:refname | sort -r | xargs echo -n | sed 's/ /,/g' | sed '1s/^/key=/' > versions.properties [code]  
 

  
 
 
 
 

 
 
 

 
 
 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-37450) Cannot create nestedView with job-dsl 1.49

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37450  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot create nestedView with job-dsl 1.49   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-plugin/build.gradle job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/d329f4540aafef9d13b411dc171090add2e78c39 Log: decode element name before mapping to class [FIXES JENKINS-37450]  
 

  
 
 
 
 

 
 
 

 
 
 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-37450) Cannot create nestedView with job-dsl 1.49

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-37450  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot create nestedView with job-dsl 1.49   
 

  
 
 
 
 

 
 Code changed in jenkins User: Daniel Spilker Path: build.gradle docs/Home.md job-dsl-plugin/build.gradle job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/JenkinsJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/da51e53eed31df6452ba711d1bbb11259cb1c312 Log: Merge pull request #898 from daspilker/JENKINS-37450 JENKINS-37450 fix regression Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/9edd3c953372...da51e53eed31  
 

  
 
 
 
 

 
 
 

 
 
 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-37450) Cannot create nestedView with job-dsl 1.49

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37450  
 
 
  Cannot create nestedView with job-dsl 1.49   
 

  
 
 
 
 

 
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-36574) Add option to choose static notification context

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-36574  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-27629) The "Repository browser" option was not save

[s...@avr-vr.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Samuel Delisle commented on  JENKINS-27629  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: The "Repository browser" option was not save   
 

  
 
 
 
 

 
 I'm having the same issue with 1.54 + Jenkins 1.580.3 on Windows 7 x64. No matter what I set as repository browser, it's not saved to config.xml and it reverts back to (Auto) when I reload the job config page. All other settings are saved properly. According to Chrome's development tools, the submitted form seems to include the url I set: 

 
[...] 
scm:3
installation:(Default)
_.source:${REPO_URL}
_.credentialsId:
revisionType:BRANCH
_.revision:$Changeset
_.modules:
_.subdir:
stapler-class:hudson.plugins.mercurial.browser.BitBucket
stapler-class:hudson.plugins.mercurial.browser.FishEye
stapler-class:hudson.plugins.mercurial.browser.GoogleCode
stapler-class:hudson.plugins.mercurial.browser.HgWeb
stapler-class:hudson.plugins.mercurial.browser.Kallithea
_.url:http://myhost:5000/myrepogroup/myrepo/
stapler-class:hudson.plugins.mercurial.browser.KilnHG
stapler-class:hudson.plugins.mercurial.browser.RhodeCode
stapler-class:hudson.plugins.mercurial.browser.RhodeCodeLegacy
[...] 
 

 There's also this in a "json" section of the form: 

 
"scm": {"value": "3", "installation": "(Default)", "source": "${REPO_URL}", "credentialsId": "", "revisionType": "BRANCH", "revision": "$Changeset", "modules": "", "clean": false, "subdir": "", "disableChangeLog": false, "": "4", "browser": {"stapler-class": "hudson.plugins.mercurial.browser.Kallithea", "url": "http://myhost:5000/myrepogroup/myrepo/"}}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA