[JIRA] (JENKINS-50739) Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50739  
 
 
  Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Labels: 
 active-choices  jenkins pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-50739) Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50739  
 
 
  Active Choices - The variables jenkinsProject and jenkinsBuild are NOT available in pipeline projects   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Environment: 
 Active Choices 2.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-55271) Jenkinsfile Active Choice Parameter

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated  JENKINS-55271  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55271  
 
 
  Jenkinsfile Active Choice Parameter   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-55271) Jenkinsfile Active Choice Parameter

2019-01-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55271  
 
 
  Jenkinsfile Active Choice Parameter   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Issue Type: 
 Bug Task  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-47063) Support checkout of Jenkinsfile for multibranch & organization pipeline jobs

2018-12-21 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Sam Gleske  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47063  
 
 
  Support checkout of Jenkinsfile for multibranch & organization pipeline jobs   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Denis Saponenko Sam Gleske  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-41108) Posibility to specify the name of jenkinsfile

2018-12-21 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41108  
 
 
  Posibility to specify the name of jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-54552) code analyzer tool exe to analyze the code and generate the excel file

2018-11-09 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54552  
 
 
  code analyzer tool exe to analyze the code and generate the excel file   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-54552) code analyzer tool exe to analyze the code and generate the excel file

2018-11-09 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-54552  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: code analyzer tool exe to analyze the code and generate the excel file   
 

  
 
 
 
 

 
 hi praveen kumar You can ask questions about using Jenkins in the user forum. Jira is for reporting bugs. https://groups.google.com/forum/#!forum/jenkinsci-users  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-54552) code analyzer tool exe to analyze the code and generate the excel file

2018-11-09 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54552  
 
 
  code analyzer tool exe to analyze the code and generate the excel file   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Component/s: 
 core  
 
 
Component/s: 
 windows-exe-runner-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-26948) Workflow compatibility for MsBuildBuilder

2018-10-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler edited a comment on  JENKINS-26948  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Workflow compatibility for MsBuildBuilder   
 

  
 
 
 
 

 
 I have a PR open here:  [ https:// issues github . jenkins-ci.org com / login.jsp?os_destination=%2Fbrowse%2FJENKINS jenkinsci/msbuild - 26948] plugin/pull/36  to add pipeline support.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-26948) Workflow compatibility for MsBuildBuilder

2018-10-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-26948  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Workflow compatibility for MsBuildBuilder   
 

  
 
 
 
 

 
 I have a PR open here: https://issues.jenkins-ci.org/login.jsp?os_destination=%2Fbrowse%2FJENKINS-26948 to add pipeline support.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-26948) Workflow compatibility for MsBuildBuilder

2018-10-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Michael Fowler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26948  
 
 
  Workflow compatibility for MsBuildBuilder   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 kdsweeney Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-26948) Workflow compatibility for MsBuildBuilder

2018-10-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-26948  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





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


[JIRA] (JENKINS-53026) Snippitizer should use double quotes around strings containing variables

2018-08-13 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53026  
 
 
  Snippitizer should use double quotes around strings containing variables   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Attachments: 
 image-2018-08-13-21-02-59-197.png  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2018-08-14 01:06  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 In the example below, the user would expect ${WORKSPACE} to be substitutes for the workspace path. The snippitzer returns the parameter surrounded in single quotes so the replace does not happen. In this scenario, the snippitezer should return the parameter in double quotes and either convert the exiting double quotes to single, or properly escape them.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

 

[JIRA] (JENKINS-41759) Add possibilities to read environment from trusted properties file

2018-08-13 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-41759  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add possibilities to read environment from trusted properties file   
 

  
 
 
 
 

 
 rsandell This is a neat feature, did it ever get integrated?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





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


[JIRA] (JENKINS-51090) Emails no longer sent to developers on build failure

2018-05-02 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51090  
 
 
  Emails no longer sent to developers on build failure   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 After updating both the git and email-ext plugins, a project that had been working for years no longer sends emails to developers on a build failure.{code:java}Email was triggered for: Failure - AnySending email for trigger: Failure - AnyAn attempt to send an e-mail to empty list of recipients, ignored.{code}A simplified configuration to recreate the issue is shown below:!image-2018-05-02-15-28-53-400.png!!image-2018-05-02-15-29-47-973.png! !image-2018-05-02-15-34-10-012.png!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51090) Emails no longer sent to developers on build failure

2018-05-02 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51090  
 
 
  Emails no longer sent to developers on build failure   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Attachment: 
 image-2018-05-02-15-34-10-012.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-51090) Emails no longer sent to developers on build failure

2018-05-02 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51090  
 
 
  Emails no longer sent to developers on build failure   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David van Laatum  
 
 
Attachments: 
 image-2018-05-02-15-28-53-400.png, image-2018-05-02-15-29-47-973.png  
 
 
Components: 
 email-ext-plugin, git-plugin  
 
 
Created: 
 2018-05-02 19:30  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 After updating both the git and email-ext plugins, a project that had been working for years no longer sends emails to developers on a build failure. 

 

Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
An attempt to send an e-mail to empty list of recipients, ignored.
 

 A simplified configuration to recreate the issue is shown below:
 

  
 
 
 
 

 
 
 

 
 
  

[JIRA] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34581  
 
 
  Please add support for Pipelines to the Powershell plugin   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Component/s: 
 powershell-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49973) Windows EXE runner should spport pipeline

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49973  
 
 
  Windows EXE runner should spport pipeline   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Labels: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49973) Windows EXE runner should spport pipeline

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-49973  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-49973) Windows EXE runner should spport pipeline

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49973  
 
 
  Windows EXE runner should spport pipeline   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Michael Fowler  
 
 
Components: 
 windows-exe-runner-plugin  
 
 
Created: 
 2018-03-07 06:50  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Googl

[JIRA] (JENKINS-20878) Windows Command timing out running Gulp Script.

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-20878  
 
 
  Windows Command timing out running Gulp Script.
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Component/s: 
 batch-task-plugin  
 
 
Component/s: 
 windows-exe-runner-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38214) Windows EXE runner should handle token macros

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-38214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-41822) msbuild warning parser with NullPointerExcetpion

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41822  
 
 
  msbuild warning parser with NullPointerExcetpion   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Component/s: 
 warnings-plugin  
 
 
Component/s: 
 msbuild-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-43356) MSBuild command fails in Jenkinsfile

2018-03-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43356  
 
 
  MSBuild command fails in Jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Labels: 
 msbuild  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37900) Support Assembly Informational Version

2017-03-04 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-37900  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37901) Assembly Version should be optional

2017-03-04 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-37901  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37900) Support Assembly Informational Version

2017-03-04 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Michael Fowler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37900  
 
 
  Support Assembly Informational Version   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Sanketh PB Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37901) Assembly Version should be optional

2017-03-04 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Michael Fowler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37901  
 
 
  Assembly Version should be optional   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Sanketh PB Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-42331) Column sort doesn't do anything

2017-02-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42331  
 
 
  Column sort doesn't do anything   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Victor Martinez  
 
 
Components: 
 jenkinslint-plugin  
 
 
Created: 
 2017/Feb/27 1:50 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 When clicking on the column header to sort, the arrow is displayed, by the jobs are still not sorted.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-41451) git-plugin: user accounts are looked up by their name

2017-02-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41451  
 
 
  git-plugin: user accounts are looked up by their name   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-39279) Add ability to add/remove/verify USB device connections

2017-01-10 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to pjdarton  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39279  
 
 
  Add ability to add/remove/verify USB device connections   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 pjdarton  
 

  
 
 
 
 

 
 
 

 
 
 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-22827) Parameters entered into the "Tunnel connection through" section of "Launch slave agents via Java Web Start" are not writen into the JNLP file

2017-01-10 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to pjdarton  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-22827  
 
 
  Parameters entered into the "Tunnel connection through" section of "Launch slave agents via Java Web Start" are not writen into the JNLP file   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 pjdarton  
 

  
 
 
 
 

 
 
 

 
 
 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-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.

2016-12-21 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-22679  
 
 
  Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-22070) I want to be able to use the Promoted_user_name variable but it's not displayed when i'm executing the set command.

2016-12-21 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler resolved as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 tested working in 2.27  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-22070  
 
 
  I want to be able to use the Promoted_user_name variable but it's not displayed when i'm executing the set command.
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-16663) Consider injected env variables in promotion

2016-12-21 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-16663  
 
 
  Consider injected env variables in promotion   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-40115) Ability to specify feed to use for poling

2016-11-29 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40115  
 
 
  Ability to specify feed to use for poling   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 nuget-plugin  
 
 
Created: 
 2016/Nov/30 4:31 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 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 "Jenk

[JIRA] (JENKINS-32237) Exception when trying to add Build Promotion process

2016-11-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I still get a warning saying adding a promotion to a multi branch project is not supported and it references this ticket. Was the fix ever merged? I don't a commit tagged with Jenkins-32237 in github.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32237  
 
 
  Exception when trying to add Build Promotion process   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved 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 gro

[JIRA] (JENKINS-18005) Git Publisher plugin does not use token macro expressions for tag name

2016-11-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-18005  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git Publisher plugin does not use token macro expressions for tag name   
 

  
 
 
 
 

 
 Fixed in Pull Request: https://github.com/jenkinsci/git-plugin/pull/448  
 

  
 
 
 
 

 
 
 

 
 
 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-26315) Git plugin can't handle property references in repository URLs when polling

2016-11-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-26315  
 
 
  Git plugin can't handle property references in repository URLs when polling   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37533) Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL

2016-11-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37533  
 
 
  Git notifyCommit polling not triggered with Parameterized Build variable in Repository URL   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)

2016-09-21 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-37599  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)   
 

  
 
 
 
 

 
 Jesse Glick Thanks for looking into this. Your proposed work around didn't work for me. Even if the class path was not shown in the UI, it was saved into config.xml thus causing the build to fail.  
 

  
 
 
 
 

 
 
 

 
 
 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-38214) Windows EXE runner should handle token macros

2016-09-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-38214  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows EXE runner should handle token macros   
 

  
 
 
 
 

 
 fixed in PR https://github.com/jenkinsci/windows-exe-runner-plugin/pull/1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-38214) Windows EXE runner should handle token macros

2016-09-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38214  
 
 
  Windows EXE runner should handle token macros   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Michael Fowler  
 
 
Components: 
 windows-exe-runner-plugin  
 
 
Created: 
 2016/Sep/14 8:14 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to th

[JIRA] (JENKINS-38213) PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion

2016-09-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38213  
 
 
  PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
  {code:java}${PROMOTION_ENV, var="BUILD_DISPLAY_NAME"}${ENV, var="BUILD_DISPLAY_NAME"}{code}Both return the Build  nameset  name set  in the promotion process ,  not the build name of the job containing the promotion procecss  
 

  
 
 
 
 

 
 
 

 
 
 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-38213) PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion

2016-09-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38213  
 
 
  PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 {code:java} ${PROMOTION_ENV, var="BUILD_DISPLAY_NAME"}${ENV, var="BUILD_DISPLAY_NAME"} {code}   Both return the Build  name of  nameset in  the promotion process not the build name of the job containing the promotion procecss  
 

  
 
 
 
 

 
 
 

 
 
 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-38213) PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion

2016-09-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38213  
 
 
  PROMOTION_ENV return env vars for the promotion environment not from the source of the promotion   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Components: 
 promoted-builds-plugin  
 
 
Created: 
 2016/Sep/14 7:42 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 $ {PROMOTION_ENV, var="BUILD_DISPLAY_NAME"} $ {ENV, var="BUILD_DISPLAY_NAME"} Both return the Build name of the promotion process not the build name of the job containing the promotion procecss  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-30411) Add the PROMOTION_ENV token macro

2016-09-07 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-30411  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add the PROMOTION_ENV token macro   
 

  
 
 
 
 

 
 Oleg Nenashev Thanks. It's only working for the variables set prior to the jobs run for me. Should I open a separate ticket?  
 

  
 
 
 
 

 
 
 

 
 
 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-30411) Add the PROMOTION_ENV token macro

2016-09-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-30411  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add the PROMOTION_ENV token macro   
 

  
 
 
 
 

 
 Is it expected that PROMOTION_ENV should be able to retrieve env vars added or changed by the env_inject 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-29956) Wipe out repository & force clone ignore's Windows directory junctions

2016-09-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-29956  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Wipe out repository & force clone ignore's Windows directory junctions   
 

  
 
 
 
 

 
 Oleg Nenashev Could this be backported to an LTS release?  
 

  
 
 
 
 

 
 
 

 
 
 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-32267) Allow replacement based on parameters at creation time

2016-09-06 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32267  
 
 
  Allow replacement based on parameters at creation time   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Resolution: 
 Not A Defect  
 
 
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-27630) AssemblyInfo.cs not being changed

2016-08-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27630  
 
 
  AssemblyInfo.cs not being changed   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 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-33316) Can't use environment variables

2016-08-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-33316  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
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-33316) Can't use environment variables

2016-08-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Michael Fowler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33316  
 
 
  Can't use environment variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Leonardo Kobus Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 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-37599) Custom groovy script for promoted builds not working on windows

2016-08-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37599  
 
 
  Custom groovy script for promoted builds not working on windows   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Oleg Nenashev  
 
 
Attachments: 
 image-2016-08-22-17-26-00-659.png  
 
 
Components: 
 promoted-builds-plugin, script-security-plugin  
 
 
Created: 
 2016/Aug/22 9:27 PM  
 
 
Environment: 
 Windows  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 When trying to add a custom groovy script to a promotion process on windows, an invalid classpath is set preventing the script from running. If you delete the classpath, it returns on the next save of the project.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[JIRA] (JENKINS-36896) Stack Trace on startup

2016-08-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36896  
 
 
  Stack Trace on startup   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Component/s: 
 core  
 

  
 
 
 
 

 
 
 

 
 
 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-36896) Stack Trace on startup

2016-08-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-36896  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Stack Trace on startup   
 

  
 
 
 
 

 
 Christoph Obexer There are tow issues: 1) the plugin dies when it hits the invalid symlink 2) Jenkins creates invalid symlinks. This has been an issue with Jenkins in windows since symlinks were added a few years ago. Cloudbees does not test on Windows. Half the time Jenkins creates a file instead of symlink, and when it does create an actual symlink, the link is broken anyway.  The fast solution is to have a try catch so that the plugin doesn't die on the invalid links. Getting cloud bees to fix the symlink issue seems unlike given how long it has existed.  
 

  
 
 
 
 

 
 
 

 
 
 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-36859) EZ-Templates not compatible with jobs created with the MultiBranch plugin

2016-08-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-36859  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EZ-Templates not compatible with jobs created with the MultiBranch plugin   
 

  
 
 
 
 

 
 Hi Marc, There's no stack trace, the plugin creates projects with no configuration, just the parameters. It looks like it copies the config.xml that defines the branching strategy in the root of the project, but not the config.xml in the Templates folder of the project that contains the actual configuration. I am using version 1.1.1 . I have not tried with previous versions. Let me know if I can provide additional info. -Michael  
 

  
 
 
 
 

 
 
 

 
 
 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-15371) Displayed Build version does not interpret parameters

2016-08-16 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Deniz Bahadir  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-15371  
 
 
  Displayed Build version does not interpret parameters   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Deniz Bahadir  
 

  
 
 
 
 

 
 
 

 
 
 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-37451) versionNumber should be exposed to API

2016-08-16 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37451  
 
 
  versionNumber should be exposed to API   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Summary: 
 VersionNumber versionNumber  should be exposed to API  
 

  
 
 
 
 

 
 
 

 
 
 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-37451) versionNumber should be exposed to API

2016-08-16 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37451  
 
 
  versionNumber should be exposed to API   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 It would be nice if the  VersionNumber  versionNumber  were exposed in the API  
 

  
 
 
 
 

 
 
 

 
 
 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-37451) VersionNumber should be exposed to API

2016-08-16 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37451  
 
 
  VersionNumber should be exposed to API   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Michael Fowler  
 
 
Components: 
 versionnumber-plugin  
 
 
Created: 
 2016/Aug/16 7:38 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 It would be nice if the VersionNumber were exposed in the API  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-22424) versionnumber/displayName not working

2016-08-16 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Deniz Bahadir  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-22424  
 
 
  versionnumber/displayName not working   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Deniz Bahadir  
 

  
 
 
 
 

 
 
 

 
 
 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-33119) Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file

2016-07-28 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-33119  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to set the assembly copyright value in the AssemblyVersionInfo.cs file   
 

  
 
 
 
 

 
 Rami Abughazaleh have you tried: https://wiki.jenkins-ci.org/display/JENKINS/Change+Assembly+Version ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-37004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use token macro variables   
 

  
 
 
 
 

 
 Fixed in PR https://github.com/jenkinsci/change-assembly-version-plugin/pull/9  
 

  
 
 
 
 

 
 
 

 
 
 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-33316) Can't use environment variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-33316  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use environment variables   
 

  
 
 
 
 

 
 Fixed in PR https://github.com/jenkinsci/change-assembly-version-plugin/pull/9  
 

  
 
 
 
 

 
 
 

 
 
 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-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37004  
 
 
  Can't use token macro variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Environment: 
 Jenkins 1. 651change-assembly-version-plugin 1.5.1 625  
 

  
 
 
 
 

 
 
 

 
 
 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-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Michael Fowler  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37004  
 
 
  Can't use token macro variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Leonardo Kobus Michael Fowler  
 

  
 
 
 
 

 
 
 

 
 
 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-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-37004  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
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-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37004  
 
 
  Can't use token macro variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 I would like to use token macros for the assembly version as follows: {noformat} ${PROPFILE,file="gitversion.properties",property="GitVersion_NuGetVersionV2"}b${BUILD_NUMBER} {noformat}  
 

  
 
 
 
 

 
 
 

 
 
 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-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37004  
 
 
  Can't use token macro variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 Can't use environment variables in the FileName box. This force me to change this line in every project.For example  I would like to  change all AssemblyInfo.cs in a directory called like $JOB_NAME. So I want to write  use token macros for the assembly version as follows :  $ JOB_NAME\**\Properties\AssemblyInfo {PROPFILE,file="gitversion . csbut that's not working. properties",property="GitVersion_NuGetVersionV2"}b${BUILD_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-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37004  
 
 
  Can't use token macro variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Priority: 
 Critical 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-37004) Can't use token macro variables

2016-07-27 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37004  
 
 
  Can't use token macro variables   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Leonardo Kobus  
 
 
Components: 
 change-assembly-version-plugin  
 
 
Created: 
 2016/Jul/27 6:46 PM  
 
 
Environment: 
 Jenkins 1.651  change-assembly-version-plugin 1.5.1  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 Can't use environment variables in the FileName box. This force me to change this line in every project. For example I would like to change all AssemblyInfo.cs in a directory called like $JOB_NAME. So I want to write: $JOB_NAME**\Properties\AssemblyInfo.cs but that's not working.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 


[JIRA] (JENKINS-33316) Can't use environment variables

2016-07-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-33316  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can't use environment variables   
 

  
 
 
 
 

 
 I tried building the plugin and got 2 test failures: testResolveEnvironmentVariables_recursively_excludingSvn(org.jenkinsci.plugins.changeassemblyversion.ReplacementsTest): -1 testResolveEnvironmentVariables(org.jenkinsci.plugins.changeassemblyversion.ReplacementsTest): second instance  
 

  
 
 
 
 

 
 
 

 
 
 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-33316) Can't use environment variables

2016-07-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Leonardo Kobus  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33316  
 
 
  Can't use environment variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 leonardo kobus Leonardo Kobus  
 

  
 
 
 
 

 
 
 

 
 
 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-33316) Can't use environment variables

2016-07-26 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to leonardo kobus  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-33316  
 
 
  Can't use environment variables   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 leonardo kobus  
 

  
 
 
 
 

 
 
 

 
 
 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-36896) Stack Trace on startup

2016-07-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36896  
 
 
  Stack Trace on startup   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Environment: 
 Windows  
 

  
 
 
 
 

 
 
 

 
 
 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-36896) Stack Trace on startup

2016-07-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36896  
 
 
  Stack Trace on startup   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Matthew DeTullio  
 
 
Components: 
 multi-branch-project-plugin  
 
 
Created: 
 2016/Jul/23 6:00 AM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 Multi-branch plugin causes jenkins to crash on startup when it searches for config files in symbolic links: 

 

hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
	at hudson.WebAppMain$3.run(WebAppMain.java:237)
Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
	at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269)
	at jenkins.InitReactorRunner.run(InitReactorRunner.java:44)
	at jenkins.model.Jenkins.executeReactor(Jenkins.java:916)
	at jenkins.model.Jenkins.(Jenkins.java:815)
	at hudson.model.Hudson.(Hudson.java:85)
	at hudson.model.Hudson.(Hudson.java:81)
	at hudson.WebAppMain$3.run(WebAppMain.java:225)
Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110)
	at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:905)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflec

[JIRA] (JENKINS-35157) Allow conditional build step to be used in promotion process

2016-07-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-35157  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow conditional build step to be used in promotion process   
 

  
 
 
 
 

 
 I'm using the Promoted Builds 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-35157) Allow conditional build step to be used in promotion process

2016-07-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler edited a comment on  JENKINS-35157  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow conditional build step to be used in promotion process   
 

  
 
 
 
 

 
 [~ legoleg oleg_nenashev ] Can you comment on this?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35157) Allow conditional build step to be used in promotion process

2016-07-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-35157  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow conditional build step to be used in promotion process   
 

  
 
 
 
 

 
 Oleg N Can you comment on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-35157) Allow conditional build step to be used in promotion process

2016-07-22 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35157  
 
 
  Allow conditional build step to be used in promotion process   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Component/s: 
 promoted-builds-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-36859) EZ-Templates not compatible with jobs created with the MultiBranch plugin

2016-07-21 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36859  
 
 
  EZ-Templates not compatible with jobs created with the MultiBranch plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Marc Carter  
 
 
Components: 
 ez-templates-plugin  
 
 
Created: 
 2016/Jul/21 9:30 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 When you try to use a template based of a multi branch job type, the resulting project has parameters and nothing else is populated. https://wiki.jenkins-ci.org/display/JENKINS/Branch+API+Plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-3367) Building process output coloring

2016-07-20 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-3367  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Building process output coloring   
 

  
 
 
 
 

 
 I've installed the 1.26 release, but am still not getting color in the 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-36727) NullPointerException when using GitPublisher in post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Nicolas De Loof  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36727  
 
 
  NullPointerException when using GitPublisher in post build actions   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Nicolas De Loof  
 

  
 
 
 
 

 
 
 

 
 
 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-31678) NullPointerException when using GitPublisher in release post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31678  
 
 
  NullPointerException when using GitPublisher in release post build actions   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Comment: 
 On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project when trying to add the git publisher in the config screen:{code:java}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegise

[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36727  
 
 
  NullPointerException when using GitPublisher in post build actions   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Environment: 
 On Jenkins 1. 638 625.1  with git - plugin 2. 4 5 . 0. 2  
 

  
 
 
 
 

 
 
 

 
 
 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-36727) NullPointerException when using GitPublisher in post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36727  
 
 
  NullPointerException when using GitPublisher in post build actions   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project when trying to add the git publisher in the config screen:{code:java}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.j

[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36727  
 
 
  NullPointerException when using GitPublisher in post build actions   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Environment: 
 Debian Wheezy running  Jenkins 1.638 with git-plugin 2.4.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-36727) NullPointerException when using GitPublisher in post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36727  
 
 
  NullPointerException when using GitPublisher in post build actions   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 

  
 
 
 
 

 
 Configure a job to use the Jenkins release plugin and use the Git publisher as release step after a successful release build. Tick the checkbox "Push only If Build Succeeds". Then a release build failes with the following NullPointerException:FATAL: nulljava.lang.NullPointerException at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:203) at hudson.plugins.release.ReleaseWrapper.executeBuildSteps(ReleaseWrapper.java:423) at hudson.plugins.release.ReleaseWrapper.access$300(ReleaseWrapper.java:99) at hudson.plugins.release.ReleaseWrapper$4.tearDown(ReleaseWrapper.java:370) at hudson.model.Build$BuildExecution.doRun(Build.java:173) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 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)This is caused by the null derefenced buildResult of AbstractBuild.getResult().  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
  

[JIRA] (JENKINS-36727) NullPointerException when using GitPublisher in post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36727  
 
 
  NullPointerException when using GitPublisher in post build actions   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Labels: 
 exception git plugin  publisher  
 

  
 
 
 
 

 
 
 

 
 
 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-36727) NullPointerException when using GitPublisher in post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36727  
 
 
  NullPointerException when using GitPublisher in post build actions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2016/Jul/15 8:31 PM  
 
 
Environment: 
 Debian Wheezy running Jenkins 1.638 with git-plugin 2.4.0.  
 
 
Labels: 
 exception git plugin  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Michael Fowler  
 

  
 
 
 
 

 
 Configure a job to use the Jenkins release plugin and use the Git publisher as release step after a successful release build. Tick the checkbox "Push only If Build Succeeds". Then a release build failes with the following NullPointerException: FATAL: null java.lang.NullPointerException at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:203) at hudson.plugins.release.ReleaseWrapper.executeBuildSteps(ReleaseWrapper.java:423) at hudson.plugins.release.ReleaseWrapper.access$300(ReleaseWrapper.java:99) at hudson.plugins.release.ReleaseWrapper$4.tearDown(ReleaseWrapper.java:370) at hudson.model.Build$BuildExecution.doRun(Build.java:173) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 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) This is caused by the null derefenced buildResult of AbstractBuild.getResult().  
 

  
 
 

[JIRA] (JENKINS-31678) NullPointerException when using GitPublisher in release post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler edited a comment on  JENKINS-31678  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when using GitPublisher in release post build actions   
 

  
 
 
 
 

 
 On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project  when trying to add the git publisher in the config screen :{code:java}javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87){code}  
 

  
 
 
 

[JIRA] (JENKINS-31678) NullPointerException when using GitPublisher in release post build actions

2016-07-15 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-31678  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when using GitPublisher in release post build actions   
 

  
 
 
 
 

 
 On Jenkins 1.625.1 with git plugin 2.5.2 on a multi branch project: 

 

javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
 

  
  

[JIRA] (JENKINS-32245) Git publisher support

2016-07-12 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-32245  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Git publisher support   
 

  
 
 
 
 

 
 It looks like this was fixed in 0.5. Can you confirm?  
 

  
 
 
 
 

 
 
 

 
 
 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-36029) multibranch-job deleted when bitbucket communication fails

2016-07-11 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36029  
 
 
  multibranch-job deleted when bitbucket communication fails   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-35316) nuget plugin succeeds when nupkg doesn't exist

2016-06-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler assigned an issue to Arnaud TAMAILLON  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35316  
 
 
  nuget plugin succeeds when nupkg doesn't exist   
 

  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
Assignee: 
 Arnaud TAMAILLON  
 

  
 
 
 
 

 
 
 

 
 
 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-34422) Allow using archived artifact as source for publication

2016-06-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler started work on  JENKINS-34422  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Fowler  
 
 
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-34422) Allow using archived artifact as source for publication

2016-06-14 Thread michaeldkfow...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Fowler commented on  JENKINS-34422  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow using archived artifact as source for publication   
 

  
 
 
 
 

 
 Pull Request submitted: https://github.com/jenkinsci/nuget-plugin/pull/5   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


  1   2   >