[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed

2017-02-24 Thread stefan.wal...@lisec.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stefan Walter commented on  JENKINS-9104  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed   
 

  
 
 
 
 

 
 Is there any workaround to this issue, because it completely breaks our usage of Jenkins?  
 

  
 
 
 
 

 
 
 

 
 
 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-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker commented on  JENKINS-42312  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
 James Dumay Blue Ocean 1.0.0-b24  
 

  
 
 
 
 

 
 
 

 
 
 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-34168) please delete

2017-02-24 Thread jho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Slinkyton updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34168  
 
 
  please delete   
 

  
 
 
 
 

 
Change By: 
 Tom Slinkyton  
 
 
Summary: 
 TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server please delete  
 

  
 
 
 
 

 
 
 

 
 
 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-34168) TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server

2017-02-24 Thread jho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Slinkyton edited a comment on  JENKINS-34168  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server   
 

  
 
 
 
 

 
 Please delete  post  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-41722) Job folder loading performance is worse when folder contains fewer items

2017-02-24 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu commented on  JENKINS-41722  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job folder loading performance is worse when folder contains fewer items   
 

  
 
 
 
 

 
 And if the total number items (job) is critical to the overall Jenkins performance, it'd be good if Jenkins could suggest an upper bound limit number.  
 

  
 
 
 
 

 
 
 

 
 
 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-41722) Job folder loading performance is worse when folder contains fewer items

2017-02-24 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu commented on  JENKINS-41722  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job folder loading performance is worse when folder contains fewer items   
 

  
 
 
 
 

 
 Refer to jenkins_open_AC_folder_Current_Thread.log file. The Thread "Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 (133)" was process item "Projects/AC" at beginning correctly. Until Thread "Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 View/index.jelly View/sidepanel.jelly AbstractFolder/tasks-bottom.jelly (133)" starts to process item "Build_Steps", which is totally outside of current view context: INFO: OUT: RoleBasedAuthorizationStrategy.getACL(AbstractItem project=com.cloudbees.hudson.plugins.folder.Folder@2e820a2b[Build_Steps]): start Feb 24, 2017 6:06:21 PM com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy getACL INFO: OUT: RoleBasedAuthorizationStrategy.getACL(AbstractItem project=com.cloudbees.hudson.plugins.folder.Folder@2e820a2b[Build_Steps]): Thread.getAllStackTraces()= Current Thread: Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 View/index.jelly View/sidepanel.jelly AbstractFolder/tasks-bottom.jelly (133) Thread Handling GET /view/All/job/Projects/job/AC/ from 172.18.25.141 : RequestHandlerThread9 View/index.jelly View/sidepanel.jelly AbstractFolder/tasks-bottom.jelly at java.lang.Thread.dumpThreads(Native Method) at java.lang.Thread.getAllStackTraces(Thread.java:1607) at com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy.printAllStackTraces(RoleBasedAuthorizationStrategy.java:94) at com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy.getACL(RoleBasedAuthorizationStrategy.java:176) at hudson.model.AbstractItem.getACL(AbstractItem.java:498) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:512) at jenkins.model.Jenkins.getItems(Jenkins.java:1719) at jenkins.model.Jenkins.getItems(Jenkins.java:325) at hudson.model.Items.getAllItems(Items.java:363) at hudson.model.Items.getAllItems(Items.java:359) at jenkins.model.Jenkins.getAllItems(Jenkins.java:1753) at jenkins.model.Jenkins.getAllItems(Jenkins.java:1762) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.validDestinations(StandardHandler.java:85) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.applicability(StandardHandler.java:54) at com.cloudbees.hudson.plugins.folder.relocate.DefaultRelocationUI.isAvailable(DefaultRelocationUI.java:67) at com.cloudbees.hudson.plugins.folder.relocate.RelocationAction.getIconClassName(RelocationAction.java:99) If the caller function can filter out the un-needed items based upon the path first, this could save the time to process hasPermission()/getACL for the un-needed items.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items

2017-02-24 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41722  
 
 
  Job folder loading performance is worse when folder contains fewer items   
 

  
 
 
 
 

 
Change By: 
 Rick Liu  
 
 
Attachment: 
 jenkins_open_AC_folder_Current_Thread.log  
 

  
 
 
 
 

 
 
 

 
 
 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-41722) Job folder loading performance is worse when folder contains fewer items

2017-02-24 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41722  
 
 
  Job folder loading performance is worse when folder contains fewer items   
 

  
 
 
 
 

 
Change By: 
 Rick Liu  
 
 
Attachment: 
 jenkins_open_AC_folder.log.tgz  
 

  
 
 
 
 

 
 
 

 
 
 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-41722) Job folder loading performance is worse when folder contains fewer items

2017-02-24 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu commented on  JENKINS-41722  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job folder loading performance is worse when folder contains fewer items   
 

  
 
 
 
 

 
 The whole point here is it shouldn't always call getAllItems(). Back in old days when there is no Folder-plugin, every item is at root level. It probably makes no difference if you call getAllItems() or getItems(). With folder structure, Jenkins would need an API similar to getItems() but with the ability to get items at a specified path, and to return only the immediate children items.  
 

  
 
 
 
 

 
 
 

 
 
 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-42318) REGRESSION: UI Not Refreshing When Starting a Build

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Thorsten Scherler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42318  
 
 
  REGRESSION: UI Not Refreshing When Starting a Build   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Thorsten Scherler  
 

  
 
 
 
 

 
 
 

 
 
 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-42291) Clicking on the cog icon in blue ocean takes you to an invalid page.

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42291  
 
 
  Clicking on the cog icon in blue ocean takes you to an invalid page.   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
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-42301) BlueOcean link is wrong when on PluginManager's page

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Tom FENNELLY  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42301  
 
 
  BlueOcean link is wrong when on PluginManager's page   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Tom FENNELLY  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42291) Clicking on the cog icon in blue ocean takes you to an invalid page.

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Tom FENNELLY  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42291  
 
 
  Clicking on the cog icon in blue ocean takes you to an invalid page.   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Tom FENNELLY  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42120) Revisit Git repository creation flow credential setup

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay stopped work on  JENKINS-42120  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
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-42291) Clicking on the cog icon in blue ocean takes you to an invalid page.

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42291  
 
 
  Clicking on the cog icon in blue ocean takes you to an invalid page.   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-42312  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
 Sounds like a karaoke 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-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Thorsten Scherler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Assignee: 
 Thorsten Scherler  
 

  
 
 
 
 

 
 
 

 
 
 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-42301) BlueOcean link is wrong when on PluginManager's page

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42301  
 
 
  BlueOcean link is wrong when on PluginManager's page   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42318) REGRESSION: UI Not Refreshing When Starting a Build

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42318  
 
 
  REGRESSION: UI Not Refreshing When Starting a Build   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Summary: 
 Blue Ocean Bug - REGRESSION:  UI Not Refreshing When Starting a Build  
 
 
Priority: 
 Major Critical  
 
 
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-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay commented on  JENKINS-42312  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
 austin stoker thanks for filing this issue. What version of Blue Ocean are you running?  
 

  
 
 
 
 

 
 
 

 
 
 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-42318) Blue Ocean Bug - UI Not Refreshing When Starting a Build

2017-02-24 Thread jdu...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Dumay updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42318  
 
 
  Blue Ocean Bug - UI Not Refreshing When Starting a Build   
 

  
 
 
 
 

 
Change By: 
 James Dumay  
 
 
Sprint: 
 1.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42318) Blue Ocean Bug - UI Not Refreshing When Starting a Build

2017-02-24 Thread jaxel...@oceanx.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Axelman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42318  
 
 
  Blue Ocean Bug - UI Not Refreshing When Starting a Build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ivan Meredith  
 
 
Components: 
 blueocean-display-url-plugin  
 
 
Created: 
 2017/Feb/25 1:52 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Josh Axelman  
 

  
 
 
 
 

 
 I am on the latest Jenkins and latest Blue Ocean plugins (fresh install) on CentOS 7. I am using the latest Chrome on MacOS Sierra.  When I run a build I get the waiting for build to start screen. If I refresh the pipeline has started and is halfway finished. Here is JS error I see in the console: [ERROR - io.jenkins.blueocean.dashboard.harmonizeTimes] not found any startTime, seems that a component should not have called this me error @ blueocean.js:17977  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
   

[JIRA] (JENKINS-38268) Parallel step and closure scope

2017-02-24 Thread m...@tknerr.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Knerr edited a comment on  JENKINS-38268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel step and closure scope   
 

  
 
 
 
 

 
 I believe [~nvgoldin]'s example is not representative for this issue, since `get_dummy_params` is a method. If it were closure instead (which is totally not needed in this case, so it would be quite artificial) it would fail again, I suspect.Here is another example which suffers from the issue, and I have totally no clue how to work around it:{code:groovy}def onEachSlave(doStuff) {  def  slaves  doStuffClosures  = [ :]  for (slave in [ 'slavelnx1', 'slavelnx2', 'slavelnx3']   def doStuffClosures = [:]  for (slave in slaves ) {def s = slavedoStuffClosures[s] = { echo "running on ${s}..."; doStuff(s); echo "...done on ${s}!" }  }  return doStuffClosures}parallel(onEachSlave { slave ->echo "do stuff on ${slave}..."}){code}The output is:{noformat}[Pipeline] parallel[Pipeline] [slavelnx1] { (Branch: slavelnx1)[Pipeline] [slavelnx2] { (Branch: slavelnx2)[Pipeline] [slavelnx3] { (Branch: slavelnx3)[Pipeline] [slavelnx1] echo[slavelnx1] running on slavelnx1...[Pipeline] [slavelnx2] echo[slavelnx2] running on slavelnx2...[Pipeline] [slavelnx3] echo[slavelnx3] running on slavelnx3...[Pipeline] [slavelnx1] echo[slavelnx1] doing stuff on slavelnx3[Pipeline] [slavelnx1] echo[slavelnx1] ...done on slavelnx1![Pipeline] [slavelnx1] }[Pipeline] [slavelnx2] echo[slavelnx2] doing stuff on slavelnx3[Pipeline] [slavelnx2] echo[slavelnx2] ...done on slavelnx2![Pipeline] [slavelnx2] }[Pipeline] [slavelnx3] echo[slavelnx3] doing stuff on slavelnx3[Pipeline] [slavelnx3] echo[slavelnx3] ...done on slavelnx3![Pipeline] [slavelnx3] }[Pipeline] // parallel[Pipeline] End of Pipeline{noformat}This is Jenkins 2.32.1 and workflow-cps 2.23[~jglick] can you confirm this is the issue, or is it just my missing groovy foo?Would also be happy to hear if someone can come up with a workaround for this  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 

[JIRA] (JENKINS-38268) Parallel step and closure scope

2017-02-24 Thread m...@tknerr.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Knerr edited a comment on  JENKINS-38268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel step and closure scope   
 

  
 
 
 
 

 
 I believe [~nvgoldin]'s example is not representative for this issue, since `get_dummy_params` is a method. If it were closure instead (which is totally not needed in this case, so it would be quite artificial) it would fail again, I suspect. [~jglick] here Here  is another example which suffers from the issue, and I have totally no clue how to work around it:{code:groovy}def onEachSlave(doStuff) {  def slaves = ['slavelnx1', 'slavelnx2', 'slavelnx3']  def doStuffClosures = [:]  for (slave in slaves) {def s = slavedoStuffClosures[s] = { echo "running on ${s}..."; doStuff(s); echo "...done on ${s}!" }  }  return doStuffClosures}parallel(onEachSlave { slave ->echo "do stuff on ${slave}..."}){code}The output is:{noformat}[Pipeline] parallel[Pipeline] [slavelnx1] { (Branch: slavelnx1)[Pipeline] [slavelnx2] { (Branch: slavelnx2)[Pipeline] [slavelnx3] { (Branch: slavelnx3)[Pipeline] [slavelnx1] echo[slavelnx1] running on slavelnx1...[Pipeline] [slavelnx2] echo[slavelnx2] running on slavelnx2...[Pipeline] [slavelnx3] echo[slavelnx3] running on slavelnx3...[Pipeline] [slavelnx1] echo[slavelnx1] doing stuff on slavelnx3[Pipeline] [slavelnx1] echo[slavelnx1] ...done on slavelnx1![Pipeline] [slavelnx1] }[Pipeline] [slavelnx2] echo[slavelnx2] doing stuff on slavelnx3[Pipeline] [slavelnx2] echo[slavelnx2] ...done on slavelnx2![Pipeline] [slavelnx2] }[Pipeline] [slavelnx3] echo[slavelnx3] doing stuff on slavelnx3[Pipeline] [slavelnx3] echo[slavelnx3] ...done on slavelnx3![Pipeline] [slavelnx3] }[Pipeline] // parallel[Pipeline] End of Pipeline{noformat}This is Jenkins 2.32.1 and workflow-cps 2.23 [~jglick] can you confirm this is the issue, or is it just my missing groovy foo?Would also be happy to hear if someone can come up with a workaround for this  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 

[JIRA] (JENKINS-38268) Parallel step and closure scope

2017-02-24 Thread m...@tknerr.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Knerr commented on  JENKINS-38268  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parallel step and closure scope   
 

  
 
 
 
 

 
 I believe Nadav Goldin's example is not representative for this issue, since `get_dummy_params` is a method. If it were closure instead (which is totally not needed in this case, so it would be quite artificial) it would fail again, I suspect. Jesse Glick here is another example which suffers from the issue, and I have totally no clue how to work around it: 

 

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


def onEachSlave(doStuff) {
  def slaves = ['slavelnx1', 'slavelnx2', 'slavelnx3']
  def doStuffClosures = [:]
  for (slave in slaves) {
def s = slave
doStuffClosures[s] = { echo "running on ${s}..."; doStuff(s); echo "...done on ${s}!" }
  }
  return doStuffClosures
}

parallel(onEachSlave { slave ->
echo "do stuff on ${slave}..."
})
 

 The output is: 

 
[Pipeline] parallel
[Pipeline] [slavelnx1] { (Branch: slavelnx1)
[Pipeline] [slavelnx2] { (Branch: slavelnx2)
[Pipeline] [slavelnx3] { (Branch: slavelnx3)
[Pipeline] [slavelnx1] echo
[slavelnx1] running on slavelnx1...
[Pipeline] [slavelnx2] echo
[slavelnx2] running on slavelnx2...
[Pipeline] [slavelnx3] echo
[slavelnx3] running on slavelnx3...
[Pipeline] [slavelnx1] echo
[slavelnx1] doing stuff on slavelnx3
[Pipeline] [slavelnx1] echo
[slavelnx1] ...done on slavelnx1!
[Pipeline] [slavelnx1] }
[Pipeline] [slavelnx2] echo
[slavelnx2] doing stuff on slavelnx3
[Pipeline] [slavelnx2] echo
[slavelnx2] ...done on slavelnx2!
[Pipeline] [slavelnx2] }
[Pipeline] [slavelnx3] echo
[slavelnx3] doing stuff on slavelnx3
[Pipeline] [slavelnx3] echo
[slavelnx3] ...done on slavelnx3!
[Pipeline] [slavelnx3] }
[Pipeline] // parallel
[Pipeline] End of Pipeline
 

 This is Jenkins 2.32.1 and workflow-cps 2.23  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
 

[JIRA] (JENKINS-39515) Failed to install Go 1.7.3

2017-02-24 Thread speedy.carr+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Micah Lapping-Carr commented on  JENKINS-39515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to install Go 1.7.3
 

  
 
 
 
 

 
 Per the issue link from Tiernan's comment, this has been fixed going forward (and I can confirm that go 1.8 on linux worked), but there are no plans to go back and update previous installers, as other folks might have dependencies on the hashes from them. One possible fix for this issue for this plugin would be to find somewhere to host updated installers (or find where someone else trustworthy has hosted them) and reference those, rather than the official ones, if a user of the plugin requests it. Not clean by any means, but would fix the issues.  
 

  
 
 
 
 

 
 
 

 
 
 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-39515) Failed to install Go 1.7.3

2017-02-24 Thread speedy.carr+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Micah Lapping-Carr edited a comment on  JENKINS-39515  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to install Go 1.7.3
 

  
 
 
 
 

 
 Per the issue link from Tiernan's comment  (a few comments above mine) , this has been fixed going forward (and I can confirm that go 1.8 on linux worked), but there are no plans to go back and update previous installers, as other folks might have dependencies on the hashes from them. One possible fix for this issue for this plugin would be to find somewhere to host updated installers (or find where someone else trustworthy has hosted them) and reference those, rather than the official ones, if a user of the plugin requests it. Not clean by any means, but would fix the issues.  
 

  
 
 
 
 

 
 
 

 
 
 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-42189) Groovy 2.4.8 interoperability issues

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-42189  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Groovy 2.4.8 interoperability issues   
 

  
 
 
 
 

 
 Thanks for tip. As noted in GROOVY-8092 I see no problem with that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40874) Missing ErrorAction after Jenkins restart

2017-02-24 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Works as expected with workflow-api 2.7 and workflow-basic-steps-2.3 bundled with blueocean. Closing it as no more work needed on it.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40874  
 
 
  Missing ErrorAction after Jenkins restart   
 

  
 
 
 
 

 
Change By: 
 Vivek Pandey  
 
 
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.

[JIRA] (JENKINS-40874) Missing ErrorAction after Jenkins restart

2017-02-24 Thread vivek.pan...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vivek Pandey commented on  JENKINS-40874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing ErrorAction after Jenkins restart   
 

  
 
 
 
 

 
 Ryan Campbell Works as expected with bundled workflow-api 2.7 and workflow-basic-steps-2.3 with blueocean! Looks like got fixed along the way.  
 

  
 
 
 
 

 
 
 

 
 
 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-42317) Scanning branches for freestyle project deletes all build history

2017-02-24 Thread frank.ra...@cerner.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Frank Racis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42317  
 
 
  Scanning branches for freestyle project deletes all build history   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Matthew DeTullio  
 
 
Components: 
 multi-branch-project-plugin  
 
 
Created: 
 2017/Feb/24 11:09 PM  
 
 
Environment: 
 Jenkins on Windows, Latest releases as of 24-FEB-2016  Jenkins 2.47  Multibranch 0.6  Folders 5.18  Branch API 2.0.7  GitHub Branch 2.0.3  GitHub API 1.84  Git 3.0.5  Git Client 2.2.1  Artifactory 2.9.1  (and many more)  
 
 
Labels: 
 multibranch regression  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Frank Racis  
 

  
 
 
 
 

 
 A section "com.github.mjdetullio.jenkins.plugins.multibranch.BranchProjectProperty" can appear in the template config.xml file after certain configuration operations. When this section is present, running branch indexing will delete the job execution history under all branches. This section doesn't always exist. One way to create it is to enable "Ant/ivy Artifactory integration", which will create the section. Disabling the "Ant/ivy Artifactory integration" doesn't help - the section will still be present and will still cause the error. This wast not happening with Multibranch 0.5.2, BranchApi 1.11.1, and SCM 1.3. After upgrading, existing jobs had their jobs deleted when reindexed. I was able to come up with a repro case with a new project: Repro steps: 
 
Create a new freestyle multibranch project 
Add a GitHub source and save (my source had

[JIRA] (JENKINS-42316) Log report corrupted content in durable-*/pid

2017-02-24 Thread plapo...@nuglif.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pascal Laporte created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42316  
 
 
  Log report corrupted content in durable-*/pid   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 durable-task-plugin, kubernetes-plugin  
 
 
Created: 
 2017/Feb/24 11:06 PM  
 
 
Environment: 
 jenkins 2.47  kubernetes-plugin 0.11  durable-task-plugin 1.13  
 
 
Labels: 
 kubernetes pipeline container  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Pascal Laporte  
 

  
 
 
 
 

 
 Within a container, generated with kubernetes (using kubernetes-plugin), a simple process invocation will generate multiple time this log: 

 

...
Cannot contact kubernetes-c4df03a7122e48a5a094643522eca149-2f29e02b2bb2: java.io.IOException: corrupted content in /home/jenkins/workspace/POPOPOPO@tmp/durable-a2a574cd/pid: java.lang.NumberFormatException: For input string: ""
...
 

 Here is a simple pipeline to easily reproduce: 

 

podTemplate(label: 'mypod', containers: [])
{
  stage("Test"){
  node("mypod"){
container("jnlp"){
  sh '''
  echo "#!/bin/sh
sleep 10" > popo.sh
   chmod a+x popo.sh
   ./popo.sh
  '''
}
  }
  }
}
 
 

[JIRA] (JENKINS-42314) Timing reported for branches is 1ms

2017-02-24 Thread svano...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Van Oort assigned an issue to Sam Van Oort  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42314  
 
 
  Timing reported for branches is 1ms   
 

  
 
 
 
 

 
Change By: 
 Sam Van Oort  
 
 
Assignee: 
 Sam Van Oort  
 

  
 
 
 
 

 
 
 

 
 
 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-42315) PodTemplate is now mandatory within pipeline

2017-02-24 Thread plapo...@nuglif.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pascal Laporte created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42315  
 
 
  PodTemplate is now mandatory within pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Carlos Sanchez  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2017/Feb/24 10:46 PM  
 
 
Environment: 
 jenkins 2.47  kubernetes-plugin 0.11   
 
 
Labels: 
 pipeline kubernetes  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Pascal Laporte  
 

  
 
 
 
 

 
 Before version 0.11 We were able to declare in the global jenkins configuration a PodTemplate with containers. Here an simple pipeline example that was working with a global PodTemplate with 0.10 

 

stage("Example"){
  node("mypod"){
  container("golang"){
  sh '''
echo "something"
  '''
}
 }
}
 

 With 0.11 we get an error: 

 

org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class org.csanchez.jenkins.plugins.kubernetes.pipeline.PodTemplateStep is missing
 

 It is now (with 0.11) mandatory to have the PodTemplate and containers declare within the pipel

[JIRA] (JENKINS-42314) Timing reported for branches is 1ms

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42314  
 
 
  Timing reported for branches is 1ms   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 workflow-api-plugin  
 
 
Created: 
 2017/Feb/24 10:45 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jesse Glick  
 

  
 
 
 
 

 
 Observed in https://ci.jenkins.io/job/Plugins/job/workflow-support-plugin/job/PR-30/5/flowGraphTable/ that of the four branches, the first three are displayed as 

Branch: linux-8 - (1 ms in block)
 whereas only the last shows a real time: 

Branch: windows-8-2.32.2 - (17 min in block)
 Unfortunately I do not know what plugin versions are being run here so it is possible this no longer reproduces with current code, but it should be easy enough to check: just run a build with parallel that will sleep for a while in each of several branches.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
   

[JIRA] (JENKINS-42204) Scan of git pipeline fails with NPE due to recent GitSCMSource change

2017-02-24 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Confirmed fixed on the master branch. May still need further compatibility testing, since there is still not an automated test which shows the problem as reported here.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42204  
 
 
  Scan of git pipeline fails with NPE due to recent GitSCMSource change   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
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 email

[JIRA] (JENKINS-42204) Scan of git pipeline fails with NPE due to recent GitSCMSource change

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42204  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Scan of git pipeline fails with NPE due to recent GitSCMSource change   
 

  
 
 
 
 

 
 Code changed in jenkins User: Mark Waite Path: src/main/java/jenkins/plugins/git/GitSCMSource.java http://jenkins-ci.org/commit/git-plugin/608a378e37bfca1692d23751955de0a9e998f9b2 Log: Merge pull request #475 from jbq/scm_source_compat JENKINS-42204 GitSCMSource: Fix backwards compatibility for advanced options. Compare: https://github.com/jenkinsci/git-plugin/compare/d780f27fb1d2...608a378e37bf  
 

  
 
 
 
 

 
 
 

 
 
 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

2017-02-24 Thread randall.ra...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Randall Raboy commented on  JENKINS-37483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock caused by synchronized methods in EC2Cloud   
 

  
 
 
 
 

 
 I am seeing the same deadlock in our setup: (omitted jvm related classes) 

 
Handling POST /cloud/ec2-us-west-2/provision from 172.16.6.210 : RequestHandlerThread[#969] - threadId:76774 - state:WAITING
stackTrace:
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Native Method)
- waiting to lock  (a java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by "jenkins.util.Timer [#3]" t@36
...
at hudson.model.Queue._withLock(Queue.java:1307)
at hudson.model.Queue.withLock(Queue.java:1186)
at jenkins.model.Nodes.removeNode(Nodes.java:237)
at jenkins.model.Jenkins.removeNode(Jenkins.java:2084)
at hudson.plugins.ec2.EC2Cloud.countCurrentEC2Slaves(EC2Cloud.java:420)
at hudson.plugins.ec2.EC2Cloud.getPossibleNewSlavesCount(EC2Cloud.java:499)
at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:518)
- locked <65f5826a> (a hudson.plugins.ec2.AmazonEC2Cloud)
at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:340)
...
Locked ownable synchronizers:
- locked <112a6eb5> (a java.util.concurrent.ThreadPoolExecutor$Worker)

jenkins.util.Timer [#3] - threadId:36 - state:BLOCKED
stackTrace:
java.lang.Thread.State: BLOCKED
at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:634)
- waiting to lock <65f5826a> (a hudson.plugins.ec2.AmazonEC2Cloud) owned by "Handling POST /cloud/ec2-us-west-2/provision from 172.16.6.210 : RequestHandlerThread[#969]" t@76774
at hudson.plugins.ec2.EC2AbstractSlave.getInstance(EC2AbstractSlave.java:277)
at hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:429)
at hudson.plugins.ec2.EC2AbstractSlave.isAlive(EC2AbstractSlave.java:397)
at hudson.plugins.ec2.EC2SpotSlave.terminate(EC2SpotSlave.java:73)
at hudson.plugins.ec2.EC2AbstractSlave.idleTimeout(EC2AbstractSlave.java:344)
at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:136)
at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:85)
at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:43)
at hudson.slaves.ComputerRetentionWork$1.run(ComputerRetentionWork.java:72)
at hudson.model.Queue._withLock(Queue.java:1309)
at hudson.model.Queue.withLock(Queue.java:1186)
at hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:63)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)
...
Locked ownable synchronizers:
- locked  (a java.util.concurrent.locks.ReentrantLock$NonfairSync)
 

 I noticed this deadlock only happen if I switch from on-demand to a spot request. The on-demand works pretty well. Similarly, I noticed same deadlock when using the ec2 fleet plugin.  Jenkins version 2.32.2 EC2 plugin: 1.36  
 

  
 
 
 
 

 
 
 

   

[JIRA] (JENKINS-42313) Default Value no honoured

2017-02-24 Thread ebrahim.mosh...@cognitoiq.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ebrahim Moshaya created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42313  
 
 
  Default Value no honoured   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Boguslaw Klimas  
 
 
Attachments: 
 git-parameter.png, git-parameter2.png  
 
 
Components: 
 git-parameter-plugin  
 
 
Created: 
 2017/Feb/24 9:56 PM  
 
 
Environment: 
 Jenkins ver. 2.45  Git Parameter Plugin 0.8.0  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Ebrahim Moshaya  
 

  
 
 
 
 

 
 When I have origin/master as the default value as in the screenshot attached. This works perfectly until someone creates a branch called for example: master-blah-blah or master-test or anything else proceeding master. when I click on build with parameters. It defaults to the other branches and not origin/master.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

 

[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages {noformat}init ---|--Linux Release-|--Linux Debug-|--Windows Release-|--Windows Debug{noformat} during During  the build I try to click on a node in the parallel section other than Linux Release  the UI doesn't update  ( or Doesn't have to be Linux Release, it's  whatever the topmost node displayed in the parallel section is, I reordered the script to test this)  the UI doesn't update.   But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL).I put some break points into the _javascript_ and found that it's at least getting as far as this bit of code: {code:_javascript_} key: 'nodeClicked',value: function nodeClicked(node) {var stage = node.stage;var listener = this.props.onNodeClick;if (listener) {listener(stage.name, stage.id);}// Update selectionthis.setState({ selectedStage: stage }); {code:_javascript_}  If When  I manually append the stage.id of a node in the parallel section   to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.  ( which  I find  the node stage.id  by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id)  to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages {noformat}init ---|--Linux Release-|--Linux Debug-|--Windows Release-|--Windows Debug{noformat}During the build I try to click on a node in the parallel section other than Linux Release the UI doesn't update (Doesn't have to be Linux Release, it's whatever the topmost node displayed in the parallel section is, I reordered the script to test this)But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the _javascript_ and found that it's at least getting as far as this bit of code:{code:_javascript_}key: 'nodeClicked',value: function nodeClicked(node) {var stage = node.stage;var listener = this.props.onNodeClick;if (listener) {listener(stage.name, stage.id);}// Update selectionthis.setState({ selectedStage: stage });{code :_javascript_ }When I manually append the stage.id of a node in the parallel section  to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on. (I find the node stage.id by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id)    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
  

[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages  {noformat} init ---|--Linux Release-|--Linux Debug-|--Windows Release-|--Windows Debugduring the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the _javascript_ and found that it's at least getting as far as this bit of code:key: 'nodeClicked',value: function nodeClicked(node) {var stage = node.stage;var listener = this.props.onNodeClick;if (listener) {listener(stage.name, stage.id);}// Update selectionthis.setState({ selectedStage: stage });If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 Thi

[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages {noformat}init ---|--Linux Release-|--Linux Debug-|--Windows Release-|--Windows Debug {noformat} during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the _javascript_ and found that it's at least getting as far as this bit of code:key: 'nodeClicked',value: function nodeClicked(node) {var stage = node.stage;var listener = this.props.onNodeClick;if (listener) {listener(stage.name, stage.id);}// Update selectionthis.setState({ selectedStage: stage });If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
  

[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages  ``` init ---|--Linux Release-|--Linux Debug-|--Windows Release-|--Windows Debug ``` during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the _javascript_ and found that it's at least getting as far as this bit of code:key: 'nodeClicked',value: function nodeClicked(node) {var stage = node.stage;var listener = this.props.onNodeClick;if (listener) {listener(stage.name, stage.id);}// Update selectionthis.setState({ selectedStage: stage });If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages init -- - |--Linux Release - |--Linux Debug - |--Windows Release - |--Windows Debugduring the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the _javascript_ and found that it's at least getting as far as this bit of code:key: 'nodeClicked',value: function nodeClicked(node) {var stage = node.stage;var listener = this.props.onNodeClick;if (listener) {listener(stage.name, stage.id);}// Update selectionthis.setState({ selectedStage: stage });If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JobAssignedLabelCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/bb790ad2efb3b01d017afba95d6195f26701c625 Log: JENKINS-42310 Added Test cases for the JobAssignedLabel Lint 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-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Change By: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages  ``` init ---|--Linux Release-|--Linux Debug-|--Windows Release-|--Windows Debug ``` during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is already complete and outside the paralell section) it happily updates the UI (I noticed it basically just adds a number to the end of the URL). I put some break points into the _javascript_ and found that it's at least getting as far as this bit of code:key: 'nodeClicked',value: function nodeClicked(node) {var stage = node.stage;var listener = this.props.onNodeClick;if (listener) {listener(stage.name, stage.id);}// Update selectionthis.setState({ selectedStage: stage });If I manually append the stage.id of a node in the parallel section (which I find by clicking the node I want and hitting a breakpoint I set in the above code and then checking the value of the stage.id) to the URL and refresh the page then the view updates correctly and I can see the status of the node I had clicked on.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[JIRA] (JENKINS-42312) Can only select top node of parallel nodes while job is in progress.

2017-02-24 Thread austinsto...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 austin stoker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42312  
 
 
  Can only select top node of parallel nodes while job is in progress.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2017/Feb/24 9:50 PM  
 
 
Environment: 
 Firefox 51.0  Chrome Version 54.0.2840.99 m (64-bit)  Microsoft Edge 38.14393.0.0  Jenkins 2.17  Blue Ocean 1.0.0-b24  
 
 
Labels: 
 UI  
 
 
Priority: 
  Major  
 
 
Reporter: 
 austin stoker  
 

  
 
 
 
 

 
 During a build I have an init stage followed by a parallel section with 4 stages  init -|-Linux Release 
 

 
 
--Linux Debug 
 
 
--Windows Release 
 
 
--Windows Debug during the build I try to click on a node in the parallel section other than Linux Release (or whatever the topmost node displayed in the parallel section is, I reordered the script to test this) the UI doesn't update. But if I click the "init" node (which is a

[JIRA] (JENKINS-29914) Subversion working copy is slow (low resolution timestamps?)

2017-02-24 Thread kerrhome (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Shannon Kerr commented on  JENKINS-29914  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Subversion working copy is slow (low resolution timestamps?)   
 

  
 
 
 
 

 
 I watching a build right now and I'm at 41 minutes to clean and svn switch a workspace that on the command line would take less than a minute. The system's CPU is at 48% and there are several gigabytes of memory free. This is just crazy that it's taking this long for something so simple. If this is not going to be fixed, are there any suggestions on what we can do to work around this besides switching from SVN to something else?  
 

  
 
 
 
 

 
 
 

 
 
 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-42311) Lightbox Popup Fails in Build Pipeline View

2017-02-24 Thread cao...@aeshna.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Caolan O'Domhnaill created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42311  
 
 
  Lightbox Popup Fails in Build Pipeline View   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 pipelinebroken.png  
 
 
Components: 
 build-pipeline-plugin  
 
 
Created: 
 2017/Feb/24 9:46 PM  
 
 
Environment: 
 Jenkins 2.32.2  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Caolan O'Domhnaill  
 

  
 
 
 
 

 
 Pipeline View in Jenkins 2.32.2 fails to connect with the error: The connection was reset. See attached picture. For troubleshooting I did some google searches looking for the error and found nothing related to this. Also looked in /var/log/jenkins/jenkins.log and nothing comes up. If I change build pipeline settings to use one of the other options, the console info appears but that is not what we want.  Build pipeline Plugin: 1.5.6 jQuery Plugin: 1.11.2-0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
   

[JIRA] (JENKINS-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/CleanupWorkspaceChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/eaca2a7b473dc3d59b63496b82655a9fa54d341c Log: JENKINS-42310 CleanupWorkspace Lint defect support Maven and Matrix projects Compare: https://github.com/jenkinsci/jenkinslint-plugin/compare/a531774efd92^...eaca2a7b473d  
 

  
 
 
 
 

 
 
 

 
 
 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-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JobDescriptionChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/13f711c3349d3cea573e15e5522552183d74a0e2 Log: JENKINS-42310 JobDescription Lint defect support Maven and Matrix projects  
 

  
 
 
 
 

 
 
 

 
 
 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-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JobDescriptionCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/e3b1b5ac8799e156e3f3a831602e1e791a1bfdfd Log: JENKINS-42310 Added Test cases for the JobDescription Lint 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-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/JobDescriptionCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/a531774efd92254528171a345f3666113d638fdf Log: JENKINS-42310 Added Test cases for the JobDescription Lint 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-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Victor Martinez Path: src/test/java/org/jenkins/ci/plugins/jenkinslint/check/CleanupWorkspaceCheckerTestCase.java http://jenkins-ci.org/commit/jenkinslint-plugin/8aca94377879188dbbc3e39b5fa8b0a34e54e654 Log: JENKINS-42310 Added Test cases for the CleanupWorkspace Lint 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-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-42310  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
 Code changed in jenkins User: Victor Martinez Path: src/main/java/org/jenkins/ci/plugins/jenkinslint/check/JobAssignedLabelChecker.java http://jenkins-ci.org/commit/jenkinslint-plugin/71d0f8045ef14ade2a66cff50a22858c1df3b017 Log: JENKINS-42310 JobAssignedLabel Lint defect support Maven and Matrix projects  
 

  
 
 
 
 

 
 
 

 
 
 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-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread victormartinezru...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Martinez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42310  
 
 
  MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Victor Martinez  
 
 
Components: 
 jenkinslint-plugin  
 
 
Created: 
 2017/Feb/24 8:57 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Victor Martinez  
 

  
 
 
 
 

 
 
 

 
 
 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 G

[JIRA] (JENKINS-42310) MAVEN and MATRIX are not linted in some defects

2017-02-24 Thread victormartinezru...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Martinez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42310  
 
 
  MAVEN and MATRIX are not linted in some defects   
 

  
 
 
 
 

 
Change By: 
 Victor Martinez  
 

  
 
 
 
 

 
 Some lint defects are purely using Project rather than AbstractProject/AbstractItem or even switching between matrix and maven projects  
 

  
 
 
 
 

 
 
 

 
 
 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-42189) Groovy 2.4.8 interoperability issues

2017-02-24 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-42189  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Groovy 2.4.8 interoperability issues   
 

  
 
 
 
 

 
 FYI: the vote to release Groovy 2.4.9 has been started: http://mail-archives.apache.org/mod_mbox/groovy-dev/201702.mbox/browser  
 

  
 
 
 
 

 
 
 

 
 
 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-40456) First time builds are not reporting to Bitbucket

2017-02-24 Thread pszczekutow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Paweł Szczekutowicz commented on  JENKINS-40456  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: First time builds are not reporting to Bitbucket   
 

  
 
 
 
 

 
 Hi Antonio Mansilla  I have same issue. I'm using multibranch pipeline projects with latest plugins. Notifications are sent inside node block but not in any stage block. INPROGRESS is sent after checkout stage with checkout scm step. SUCCESSFUL and FAILED are sent inside node but outside stage blocks too. All notifications are sent with same buildKey. First build is not notified with any state, second and next ones are notified.  
 

  
 
 
 
 

 
 
 

 
 
 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-34779) configurable scm polling for github organization folder jobs

2017-02-24 Thread mcroo...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 mcrooney commented on  JENKINS-34779  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: configurable scm polling for github organization folder jobs   
 

  
 
 
 
 

 
 "I am inclined to suggest either using a service such as ngrok to allow tunnelling your GitHub webhook notification". I think this is a great solution for some organizations where this is allowed, but I've been involved in multiple companies trying to set this up where that's simply not allowed from a networking/security standpoint. Perhaps polling the Github events API (Jenkins-41072) is a cool alternative, though   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42103) Github creation flow doesn't handle revoked access token properly

2017-02-24 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers commented on  JENKINS-42103  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github creation flow doesn't handle revoked access token properly   
 

  
 
 
 
 

 
 James Dumay in this scenario where the saved token was revoked, I feel like there should be some copy that informs the user of such. Do you have any suggestions?  
 

  
 
 
 
 

 
 
 

 
 
 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-42103) Github creation flow doesn't handle revoked access token properly

2017-02-24 Thread cmey...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cliff Meyers updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42103  
 
 
  Github creation flow doesn't handle revoked access token properly   
 

  
 
 
 
 

 
Change By: 
 Cliff Meyers  
 

  
 
 
 
 

 
 If a user saves a Github personal access token in the creation flow and then re-enters after the token has been revoked, they  should  receive in appropriate error message.Repro Steps# Navigate to /create-pipeline# Select "Github"# Enter a valid Github access token# Navigate to Github and revoke the access token# Navigate to /create-pipeline again# Select "Github"Expected BehaviorUser should be prompted to enter a new access token. Ideally the user should get some feedback that it appears the credential is invalid.Actual Behavior"Loading" message displays forever. http://localhost:8080/jenkins/blue/rest/organizations/jenkins/scm/github/organizations/?credentialId=github 500 (Server Error){code}{  "message" : "Server returned HTTP response code: 401, message: 'Unauthorized' for URL: https://api.github.com/user",  "code" : 500,  "errors" : [ ]}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

 

[JIRA] (JENKINS-34168) TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server

2017-02-24 Thread jho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Hoppe closed an issue as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Please delete post  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-34168  
 
 
  TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server   
 

  
 
 
 
 

 
Change By: 
 Joseph Hoppe  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-42154) Triggering branch indexing on pull request creation

2017-02-24 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42154  
 
 
  Triggering branch indexing on pull request creation   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42154) Triggering branch indexing on pull request creation

2017-02-24 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-42154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Triggering branch indexing on pull request creation   
 

  
 
 
 
 

 
 That has nothing to do with multibranch which gets triggered by: https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/PushGHEventSubscriber.java and https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/PullRequestGHEventSubscriber.java  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-34168) TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server

2017-02-24 Thread jho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Hoppe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34168  
 
 
  TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server   
 

  
 
 
 
 

 
Change By: 
 Joseph Hoppe  
 

  
 
 
 
 

 
 I have a couple projects working in Jenkins with TFS, but a number that also do not. I.e., this one fails:* Configure the project. Re-enter my TFS credentials to confirm that they are correct.* Wipe out my project's entire existing workspace just to try to make a better test. * Click build now.* Build fails with message below. However, all of the files have been downloaded from TFS - I can see them in the workspace.E:\Tech Consulting Jenkins\Jenkins\jobs\SilverlightMultiFileUploader\workspace\readme.txtFATAL: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://.../ (authenticating as ...)java.lang.RuntimeException: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://.../ (authenticating as ...) at hudson.plugins.tfs.model.Server.execute(Server.java:157) at hudson.plugins.tfs.model.Project.getFiles(Project.java:256) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:57) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:270) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://.../ (authenticating as ...) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2666) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2527) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2515) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2491) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:60) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:17) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:153) ... 11 moreCaused by: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://.../ (authenticating as ...) at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java

[JIRA] (JENKINS-41831) Github Org folder Configuration changes not affecting children in the folder (Regression?)

2017-02-24 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-41831  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Github Org folder Configuration changes not affecting children in the folder (Regression?)   
 

  
 
 
 
 

 
 Morgan Goose I may create a secondary issue to investigate proactively applying configuration changes where those configuration changes have not changed the scm criteria (and hence will not need a scan)  
 

  
 
 
 
 

 
 
 

 
 
 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-34168) TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server

2017-02-24 Thread jho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Hoppe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34168  
 
 
  TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server   
 

  
 
 
 
 

 
Change By: 
 Joseph Hoppe  
 

  
 
 
 
 

 
 I have a couple projects working in Jenkins with TFS, but a number that also do not. I.e., this one fails:* Configure the project. Re-enter my TFS credentials to confirm that they are correct.* Wipe out my project's entire existing workspace just to try to make a better test. * Click build now.* Build fails with message below. However, all of the files have been downloaded from TFS - I can see them in the workspace.E:\Tech Consulting Jenkins\Jenkins\jobs\SilverlightMultiFileUploader\workspace\readme.txtFATAL: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http:// tfstta . int . [myemployer] . com:8080 / (authenticating as  ten\u[7 numbers]  ... )java.lang.RuntimeException: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http:// tfstta . int . [myemployer] . com:8080 / (authenticating as  ten\u[7 numbers]  ... ) at hudson.plugins.tfs.model.Server.execute(Server.java:157) at hudson.plugins.tfs.model.Project.getFiles(Project.java:256) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:57) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:270) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http:// tfstta . int . [myemployer] . com:8080 / (authenticating as  ten\u[7 numbers]  ... ) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2666) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2527) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2515) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2491) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:60) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:17) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:153) ... 11 moreCaused by: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: A

[JIRA] (JENKINS-42308) Command line parsing failed: Unclosed single-quoted string

2017-02-24 Thread jfl...@lexmark.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John Flynn commented on  JENKINS-42308  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Command line parsing failed: Unclosed single-quoted string   
 

  
 
 
 
 

 
 It appears that the 'useAdvancedParser' - "Use advanced parsing mechanism" is always true.  
 

  
 
 
 
 

 
 
 

 
 
 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-34168) TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server

2017-02-24 Thread jho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joseph Hoppe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34168  
 
 
  TFS plugin downloads source but then reports TFSUnauthorizedException: Access denied connecting to TFS server   
 

  
 
 
 
 

 
Change By: 
 Joseph Hoppe  
 

  
 
 
 
 

 
 I have a couple projects working in Jenkins with TFS, but a number that also do not. I.e., this one fails:* Configure the project. Re-enter my TFS credentials to confirm that they are correct.* Wipe out my project's entire existing workspace just to try to make a better test. * Click build now.* Build fails with message below. However, all of the files have been downloaded from TFS - I can see them in the workspace.E:\Tech Consulting Jenkins\Jenkins\jobs\SilverlightMultiFileUploader\workspace\readme.txtFATAL: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://tfstta.int.[myemployer].com:8080/ (authenticating as ten\u[7 numbers])java.lang.RuntimeException: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://tfstta.int.[myemployer].com:8080/ (authenticating as ten\u[7 numbers]) at hudson.plugins.tfs.model.Server.execute(Server.java:157) at hudson.plugins.tfs.model.Project.getFiles(Project.java:256) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:57) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:270) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://tfstta.int.[myemployer].com:8080/ (authenticating as ten\u[7 numbers]) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2666) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2527) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2515) at com.microsoft.tfs.core.clients.versioncontrol.soapextensions.Workspace.get(Workspace.java:2491) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:60) at hudson.plugins.tfs.commands.GetFilesToWorkFolderCommand.call(GetFilesToWorkFolderCommand.java:17) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:153) ... 11 moreCaused by: com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server http://

[JIRA] (JENKINS-36836) Git path polling ignores do not work in Pipeline jobs

2017-02-24 Thread ron.swan...@thomsonreuters.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ron Swanson commented on  JENKINS-36836  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git path polling ignores do not work in Pipeline jobs   
 

  
 
 
 
 

 
 Michael Andrews Good day. Can you please say more about how you got that working?  
 

  
 
 
 
 

 
 
 

 
 
 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-41226) Active choice reactive reference parameter has no value on rebuild

2017-02-24 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Expected behavior. Please, read the parameter documentation o the wiki page  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41226  
 
 
  Active choice reactive reference parameter has no value on rebuild   
 

  
 
 
 
 

 
Change By: 
 Ioannis Moutsatsos  
 
 
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...@goog

[JIRA] (JENKINS-41226) Active choice reactive reference parameter has no value on rebuild

2017-02-24 Thread imoutsat...@msn.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ioannis Moutsatsos commented on  JENKINS-41226  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Active choice reactive reference parameter has no value on rebuild   
 

  
 
 
 
 

 
 This is the expected behavior unless you have render the AC-Reference parameter as an input. See the wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Active+Choices+Plugin and focus on the section: 'Passing Reactive Reference Values to the build'  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick stopped work on  JENKINS-30206  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
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-34779) configurable scm polling for github organization folder jobs

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34779  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: configurable scm polling for github organization folder jobs   
 

  
 
 
 
 

 
 Well if we implement JENKINS-41072 than I suppose this should be deleted, not customizable?  
 

  
 
 
 
 

 
 
 

 
 
 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-36290) Intermitted failure with JenkinsRule and multi branch pipeline test

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 A bug in Blue Ocean code. If it is still failing, you will need to track it down there I suppose. Add logging?  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36290  
 
 
  Intermitted failure with JenkinsRule and multi branch pipeline test   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
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+unsubsc

[JIRA] (JENKINS-36290) Intermitted failure with JenkinsRule and multi branch pipeline test

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36290  
 
 
  Intermitted failure with JenkinsRule and multi branch pipeline test   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 blueocean  
 

  
 
 
 
 

 
 
 

 
 
 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-41048) Allow to not build commits of a PR

2017-02-24 Thread emanue...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 emanuelez commented on  JENKINS-41048  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow to not build commits of a PR   
 

  
 
 
 
 

 
 It would if it was possible to perform this check before the "build started" status was sent to Github. I'm not sure when such message is sent right now.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42227) StackOverFlowError starting Jenkins with Pipeline jobs

2017-02-24 Thread r...@akom.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov edited a comment on  JENKINS-42227  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StackOverFlowError starting Jenkins with Pipeline jobs   
 

  
 
 
 
 

 
 Adding another, slightly different  [^stacktrace2.txt]  with a StackOverFlowError, again preventing Jenkins (2.47 with latest plugins as of 2017/02/24) from starting.This time, I tried something else:# removed a few jobs I was suspecting# Jenkins starts# put the jobs back (I'm just moving folders while Jenkins is stopped)# Jenkins starts!I am getting the feeling that this has to do with recovering the previously running Pipeline execution state after restart.  Eg: * job 1 ran job 2 * Jenkins was stopped ( and maybe i killed job 2  while stopping it )* Jenkins starts and attempts to resume job 1, which seems to either forever wait for completion of job 2 which isn't even running, or Jenkins just doesn't start with the Stack Overflow.When I moved the offending jobs away, Jenkins cleared their saved state (I'm guessing).  
 

  
 
 
 
 

 
 
 

 
 
 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-42227) StackOverFlowError starting Jenkins with Pipeline jobs

2017-02-24 Thread r...@akom.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov edited a comment on  JENKINS-42227  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StackOverFlowError starting Jenkins with Pipeline jobs   
 

  
 
 
 
 

 
 Adding another, slightly different  [^stacktrace2.txt]  with a StackOverFlowError, again preventing Jenkins (2.47 with latest plugins as of 2017/02/24) from starting. This time, I tried something else:# removed a few jobs I was suspecting# Jenkins starts# put the jobs back (I'm just moving folders while Jenkins is stopped)# Jenkins starts!I am getting the feeling that this has to do with recovering the previously running Pipeline execution state after restart.  Eg: * job 1 ran job 2 * Jenkins was stopped (maybe i killed job 2)* Jenkins starts and attempts to resume job 1, which seems to either forever wait for completion of job 2 which isn't even running, or Jenkins just doesn't start with the Stack Overflow.When I moved the offending jobs away, Jenkins cleared their saved state (I'm guessing).  
 

  
 
 
 
 

 
 
 

 
 
 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-39171) NPE when using properties from @Field in multibranch-pipeline

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Steps to reproduce from scratch please?  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39171  
 
 
  NPE when using properties from @Field in multibranch-pipeline   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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

[JIRA] (JENKINS-39171) NPE when using properties from @Field in multibranch-pipeline

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39171  
 
 
  NPE when using properties from @Field in multibranch-pipeline   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Labels: 
 multibranch pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39171) NPE when using properties from @Field in multibranch-pipeline

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39171  
 
 
  NPE when using properties from @Field in multibranch-pipeline   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 workflow-cps-plugin  
 
 
Component/s: 
 workflow-multibranch-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-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The “workaround” is the correct approach. This Git plugin extension is only useful for freestyle projects. 

The loading of the Jenkinsfile happens before the checkout on the node
 Right—he is talking about loading of Jenkinsfile from the master …@script directory.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40267  
 
 
  Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
   

[JIRA] (JENKINS-40332) Useless context for snippet generator in MBPL folder

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40332  
 
 
  Useless context for snippet generator in MBPL folder   
 

  
 
 
 
 

 
 Indeed. At a minimum, PipelineTriggersJobProperty/config.jelly needs to ignore an it which is not in fact a Job, to avoid offering unusable properties. CC Andrew Bayer. Ideally from the folder, we would show triggers applicable to WorkflowJob. Unfortunately this is impossible using current core APIs: TriggerDescriptor.isApplicable takes an Item not a Class. We could inspect the type parameter of the Trigger (klazz), though this is less precise. If there is already at least one branch project, we could try to redirect to its pipeline-syntax/ page.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Component/s: 
 core  
 
 
Component/s: 
 workflow-job-plugin  
 
 
Component/s: 
 pipeline  
 
 
Labels: 
 multibranch api pipeline trigger  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
  

[JIRA] (JENKINS-42227) StackOverFlowError starting Jenkins with Pipeline jobs

2017-02-24 Thread r...@akom.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov commented on  JENKINS-42227  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: StackOverFlowError starting Jenkins with Pipeline jobs   
 

  
 
 
 
 

 
 Adding another, slightly different stacktrace2.txt with a StackOverFlowError, again preventing Jenkins (2.47 with latest plugins as of 2017/02/24) from starting.  
 

  
 
 
 
 

 
 
 

 
 
 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-42227) StackOverFlowError starting Jenkins with Pipeline jobs

2017-02-24 Thread r...@akom.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alexander Komarov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42227  
 
 
  StackOverFlowError starting Jenkins with Pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Alexander Komarov  
 
 
Attachment: 
 stacktrace2.txt  
 

  
 
 
 
 

 
 
 

 
 
 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-40968) Set individual jobs configurations and parameters

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-40968  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Set individual jobs configurations and parameters   
 

  
 
 
 
 

 
 

I need to pass parameters to jobs. But jobs created by multibranch pipeline plugin allows only to view configurations
 properties step. I am not really sure what the rest of this issue is referring to. Can probably be closed as a user list question.  
 

  
 
 
 
 

 
 
 

 
 
 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-42154) Triggering branch indexing on pull request creation

2017-02-24 Thread pg.mil...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre-Gildas MILLON reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42154  
 
 
  Triggering branch indexing on pull request creation   
 

  
 
 
 
 

 
Change By: 
 Pierre-Gildas MILLON  
 
 
Resolution: 
 Duplicate  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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-42154) Triggering branch indexing on pull request creation

2017-02-24 Thread pg.mil...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pierre-Gildas MILLON commented on  JENKINS-42154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Triggering branch indexing on pull request creation   
 

  
 
 
 
 

 
 Hello, This is not a hook configuration issue as the hook is correctly configured and works fine. This issue here is that Jenkins only trigger branch indexing on the Github push event and not on the pull_request event. That's the reason why I pointed at the DefaultPushGHEventSubscriber.java, where we can see L71 that it filters only on Push event. You can easily reproduce the case by creating a multibranch pipeline job configured ton only build PRs: when you create a PR from an existing branch and do not push any commit, the branch indexing will never happen until Jenkins receives a Push payload from any Jenkins-wide configured Github repository.  
 

  
 
 
 
 

 
 
 

 
 
 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-41118) Allow custom workspaces in declarative pipeline

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-41118  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow custom workspaces in declarative pipeline   
 

  
 
 
 
 

 
 

has a really long path where only a custom workspace will help get the path short enough to compile
 This is a general problem of workspace management in Jenkins, which is already filed. Specifying a custom workspace in a Jenkinsfile is not a great solution; it adds an implicit dependency on the file layout of the node being used for the build (making it harder to scale up with many agents). There should not be collisions between unrelated jobs, though (see JENKINS-36358 for the opposite request).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40874) Missing ErrorAction after Jenkins restart

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-40874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Missing ErrorAction after Jenkins restart   
 

  
 
 
 
 

 
 Working for me in CloudBees Jenkins Enterprise 2.32.2.1-rolling (for sake of concrete plugin versions). Looks the same in stage view after restart.  
 

  
 
 
 
 

 
 
 

 
 
 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-37369) Multibranch Pipeline: Last build information is not propagated to Jenkins View

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37369  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multibranch Pipeline: Last build information is not propagated to Jenkins View   
 

  
 
 
 
 

 
 Or any AbstractFolder. Better would be to have core define some kind of extension point for populating this view cell, or simply use ItemGroup.getAllJobs itself.  
 

  
 
 
 
 

 
 
 

 
 
 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-42080) API to write a single file to the repository

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-42080  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: API to write a single file to the repository
 

  
 
 
 
 

 
 As noted in JENKINS-39703, SCMFile may need to add some methods to define some new abstract type SCMFileContent which has contentAsBytes etc. but also a replace method—since GitHub does not let you overwrite a file without specifying what you are overwriting (presumably to avoid data loss with non-fast-forward merges).  
 

  
 
 
 
 

 
 
 

 
 
 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-42214) Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-42214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Field entries for hudson.scm.EditType fields in "jenkins-whitelist" must be static   
 

  
 
 
 
 

 
 Ah…I am already checking static in MethodSignature and StaticMethodSignature, but not FieldSignature or StaticFieldSignature.  
 

  
 
 
 
 

 
 
 

 
 
 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-40877) Display links to Github PR and Branch on Pipeline Result

2017-02-24 Thread tscher...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thorsten Scherler started work on  JENKINS-40877  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Thorsten Scherler  
 
 
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-41657) workflow-cps-global-lib not compatible with mercurial

2017-02-24 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-41657  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
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-41503) JSON Schema issue: mapArgumentValue not accepting null

2017-02-24 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated  JENKINS-41503  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41503  
 
 
  JSON Schema issue: mapArgumentValue not accepting null   
 

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


  1   2   3   4   >