[JIRA] [ssh-plugin] (JENKINS-24402) jsch version

2016-01-28 Thread tobias.l...@trevotrend.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tobias Lang commented on  JENKINS-24402 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: jsch version  
 
 
 
 
 
 
 
 
 
 
We also suffer from this in a production environment and would be happy if it could get fixed. Thanks in advance. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32639) Github commit status doesn't work

2016-01-28 Thread a.belayt...@smart-crowd.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexey Belaytzev resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32639 
 
 
 
  Github commit status doesn't work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alexey Belaytzev 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32639) Github commit status doesn't work

2016-01-28 Thread a.belayt...@smart-crowd.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexey Belaytzev edited a comment on  JENKINS-32639 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github commit status doesn't work  
 
 
 
 
 
 
 
 
 
 I don`t  now  what happend, must be GH repair bug, but all works fine today. I never change in build jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32639) Github commit status doesn't work

2016-01-28 Thread a.belayt...@smart-crowd.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexey Belaytzev commented on  JENKINS-32639 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github commit status doesn't work  
 
 
 
 
 
 
 
 
 
 
I don`t what happend, must be GH repair bug, but all works fine today. I never change in build jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-16871) Inconsistent use of XML escaping in config.xml when uploading through API

2016-01-28 Thread dtho...@osrfoundation.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dirk Thomas edited a comment on  JENKINS-16871 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inconsistent use of XML escaping in config.xml when uploading through API  
 
 
 
 
 
 
 
 
 
 When using tool like the Jenkins plugin JobConfigHistory to look at the diffs the workaround only generates more noise. It would be really great if this could be addressed at some point.    Btw. the behavior is still the same in the current LTS release 1.642.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-16871) Inconsistent use of XML escaping in config.xml when uploading through API

2016-01-28 Thread dtho...@osrfoundation.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dirk Thomas commented on  JENKINS-16871 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inconsistent use of XML escaping in config.xml when uploading through API  
 
 
 
 
 
 
 
 
 
 
When using tool like the Jenkins plugin JobConfigHistory to look at the diffs the workaround only generates more noise. It would be really great if this could be addressed at some point.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [customtools-plugin] (JENKINS-32682) Unable to use VERSION environment variable

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence commented on  JENKINS-32682 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use VERSION environment variable  
 
 
 
 
 
 
 
 
 
 
Here is a job definition which doesn't seem to work: 
```false PHP_VERSION Version of PHP to be installed phpenv  true false false false  false   phpenvfalse  false``` 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [customtools-plugin] (JENKINS-32682) Unable to use VERSION environment variable

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32682 
 
 
 
  Unable to use VERSION environment variable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Joshua Spence 
 
 
 

Attachment:
 
 phpenv.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [customtools-plugin] (JENKINS-32682) Unable to use VERSION environment variable

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence commented on  JENKINS-32682 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use VERSION environment variable  
 
 
 
 
 
 
 
 
 
 
Yeah, I had tried `$ {PHP_VERSION} 
` previously but that didn't work either. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [customtools-plugin] (JENKINS-32682) Unable to use VERSION environment variable

2016-01-28 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-32682 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use VERSION environment variable  
 
 
 
 
 
 
 
 
 
 
Please try $ {PHP_VERSION} 
 . Custom tools resolves only parameters in brackets 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [customtools-plugin] (JENKINS-32682) Unable to use VERSION environment variable

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32682 
 
 
 
  Unable to use VERSION environment variable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Joshua Spence 
 
 
 

Environment:
 
 Jenkins 1.646Custom Tools Plugin 0.4.4Extended Choice Parameter Plug-In 0.28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [customtools-plugin] (JENKINS-32662) Extended Choice Parameter Plugin Incompatibility

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32662 
 
 
 
  Extended Choice Parameter Plugin Incompatibility  
 
 
 
 
 
 
 
 
 

Change By:
 
 Joshua Spence 
 
 
 

Summary:
 
 Unable to use versions with custom tool Extended Choice Parameter Plugin Incompatibility 
 
 
 
 
 
 
 
 
 
 I am unable to use versioning for a custom tool.  It seems that the Custom Tools plugin is not compatible with the latest version of the Extended Choice Parameter plugin. ```javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class com.cloudbees.jenkins.plugins.customtools.CustomTool from {"name":"phpenv","exportedPaths":"phpenv/bin,phpenv/shims","home":"","additionalVariables":"","toolVersion":{"versionsListSource":{"name":"PHP_VERSION","description":"The PHP version to use.","parameterGroup":{"value":"0","type":"PT_SINGLE_SELECT","visibleItemCount":"5","multiSelectDelimiter":",","quoteValue":false,"propertySource":{"value":"0","propertyValue":"5.3.29"},"defaultPropertySource":{"value":"0","defaultPropertyValue":"5.3.29","properties":{"stapler-class-bag":"true","hudson-tools-InstallSourceProperty":{"installers":{"label":"","command":"export PHPENV_ROOT=$(pwd)/phpenv\nexport PATH=\"$PATH:$(pwd)/phpenv/bin\"\n\nif test -d $PHPENV_ROOT; then\n$PHPENV_ROOT/bin/phpenv update\nelse\n(curl -L http://git.io/phpenv-installer | bash)\nfi\n\nif ! test -d $PHPENV_ROOT/shims; then\nmkdir $PHPENV_ROOT/shims\nfi","toolHome":".","stapler-class":"hudson.tools.CommandInstaller","$class":"hudson.tools.CommandInstaller" at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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 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.acegisec

[JIRA] [customtools-plugin] (JENKINS-32682) Unable to use VERSION environment variable

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32682 
 
 
 
  Unable to use VERSION environment variable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 customtools-plugin 
 
 
 

Created:
 

 29/Jan/16 1:47 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Joshua Spence 
 
 
 
 
 
 
 
 
 
 
I have defined a `phpenv` custom tool which has a `PHP_VERSION` parameter which allows the requested PHP version to be specified. The installation script for this custom tool is roughly as follows: 
``` export PHPENV_ROOT=$(pwd)/phpenv export PATH="$PATH:$(pwd)/phpenv/bin" 
if test -d $PHPENV_ROOT; then $PHPENV_ROOT/bin/phpenv update else (curl -L http://git.io/phpenv-installer | bash) fi 
phpenv install $PHP_VERSION phpenv global $PHP_VERSION ``` 
It seems, however, that the `$PHP_VERSION` environment variable is not set. Am I correct in thinking that the version parameter is exposed through an environment variable? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 

[JIRA] [customtools-plugin] (JENKINS-32662) Unable to use versions with custom tool

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence commented on  JENKINS-32662 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use versions with custom tool  
 
 
 
 
 
 
 
 
 
 
OK, v0.28 seems to work. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [customtools-plugin] (JENKINS-32662) Unable to use versions with custom tool

2016-01-28 Thread j...@freelancer.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joshua Spence commented on  JENKINS-32662 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to use versions with custom tool  
 
 
 
 
 
 
 
 
 
 
We tried downgrading the Extended Choice plugin to v0.33 but it still doesn't seem to work. 

JENKINS-31458
 might be related? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [jobconfighistory-plugin] (JENKINS-21600) Enable paging to improve performance

2016-01-28 Thread dtho...@osrfoundation.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dirk Thomas commented on  JENKINS-21600 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable paging to improve performance  
 
 
 
 
 
 
 
 
 
 
For a specific job the history seems to be limited based on the config value. But the global page (e.g. "Show job configs only") is not restricted at all. It would be great if pagination (or at least a configurable limit) could be added for that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [groovy-postbuild-plugin] (JENKINS-32681) Option to disable script security approval

2016-01-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-32681 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Option to disable script security approval  
 
 
 
 
 
 
 
 
 
 
What's the rationale for this? 
When you have Overall/RunScripts, there's no sandbox/approval (or is there on Groovy Postbuild?). If you don't, there must be. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-32493) New Parent POM for Jenkins Plugins

2016-01-28 Thread rodr...@freebsd.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Rodrigues commented on  JENKINS-32493 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New Parent POM for Jenkins Plugins  
 
 
 
 
 
 
 
 
 
 
I followed the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-CreatingaNewPlugin 
and generated a pom.xml file which still has: 
 org.jenkins-ci.plugins plugin  1.580.1   
Can you change things so that your new parent POM changes are reflected in this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [credentials-plugin] (JENKINS-29646) Rebuild plugin mangles Credentials parameters

2016-01-28 Thread will.sa...@greenwayhealth.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Will Saxon commented on  JENKINS-29646 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Rebuild plugin mangles Credentials parameters  
 
 
 
 
 
 
 
 
 
 
FYI this is fixed by this PR 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [credentials-plugin] (JENKINS-29646) Rebuild plugin mangles Credentials parameters

2016-01-28 Thread will.sa...@greenwayhealth.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Will Saxon updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29646 
 
 
 
  Rebuild plugin mangles Credentials parameters  
 
 
 
 
 
 
 
 
 

Change By:
 
 Will Saxon 
 
 
 

Component/s:
 
 rebuild-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [groovy-postbuild-plugin] (JENKINS-32681) Option to disable script security approval

2016-01-28 Thread schristo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Christou created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32681 
 
 
 
  Option to disable script security approval  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 wolfs 
 
 
 

Components:
 

 groovy-postbuild-plugin, script-security-plugin 
 
 
 

Created:
 

 28/Jan/16 10:51 PM 
 
 
 

Priority:
 
  Trivial 
 
 
 

Reporter:
 
 Steven Christou 
 
 
 
 
 
 
 
 
 
 
It would be nice to have an option in Manage Jenkins -> Configure Security to disable the need for approval process for the groovy-postbuild plugin. By default the script security plugin is enabled and with no method for disabling, or ignoring an entire project. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 

[JIRA] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List

2016-01-28 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32676 
 
 
 
  Workflow scripts can't modify a List  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 script-security 1.18{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods push java.util.List java.lang.Object}} also{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods join java.lang.Object[] java.lang.String}} eg:node() {  def list = []  list.push( "asdf" )   def str = list.join('-') } 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [active-choices-plugin] (JENKINS-32680) Review variables expansion in Groovy scripts for active-choices parameters

2016-01-28 Thread brunodepau...@yahoo.com.br (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bruno P. Kinoshita created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32680 
 
 
 
  Review variables expansion in Groovy scripts for active-choices parameters  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Bruno P. Kinoshita 
 
 
 

Components:
 

 active-choices-plugin 
 
 
 

Created:
 

 28/Jan/16 9:36 PM 
 
 
 

Labels:
 

 envinronment-variables 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Bruno P. Kinoshita 
 
 
 
 
 
 
 
 
 
 
We have had issues reported about it in the past, and while it looks like we fixed the issue related to using env vars in scripts, we haven't fixed the variable expansion as reported here  
https://github.com/jenkinsci/active-choices-plugin/commit/2ee4d3412da98bb132990bb1d790f8dd5bdf453c 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 

[JIRA] [scm-sync-configuration-plugin] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs

2016-01-28 Thread bria...@bellsouth.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian Wilson commented on  JENKINS-15898 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion back-end cannot handle renaming of jobs  
 
 
 
 
 
 
 
 
 
 
Unfortunately the 0.0.9 revision of SCM Sync also introduces a serious bug. When you restart Jenkins, the web UI is just blank screen. Revision 0.0.9 is seriously flawed and should not be used. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32639) Github commit status doesn't work

2016-01-28 Thread lan...@yandex.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev commented on  JENKINS-32639 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github commit status doesn't work  
 
 
 
 
 
 
 
 
 
 
All your logs provided is about hooks, not the status. You can check that GH set status on commit with GH status api with something like curl or directly in the browser. 
Can't help with current info provided.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-18952) Option to change "Last Successful Artifacts" for a project to "Latest Artifacts"

2016-01-28 Thread rsi...@gracenote.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 robsimon updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-18952 
 
 
 
  Option to change "Last Successful Artifacts" for a project to "Latest Artifacts"  
 
 
 
 
 
 
 
 
 

Change By:
 
 robsimon 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 project-stats-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cmakebuilder-plugin] (JENKINS-32657) cmakebuilder should allow cmake scripting

2016-01-28 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber commented on  JENKINS-32657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 
 
For the new build-step which just invokes cmake, I would suggest users should be able to configure the following 
 

Which cmake installation should be used
 

Arbitrary arguments, in a text field. One argument per line, so users will not have to worry about quotation.
 

Working directory for cmake?
 

An option to ignore the exit status of cmake?
 
 
Both arguments and working dir should handle $VARIABLE expansion. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [audit-trail-plugin] (JENKINS-32679) Audit Trail plugin fails to track queue item api calls

2016-01-28 Thread sami.salo...@nokia.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sami Salonen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32679 
 
 
 
  Audit Trail plugin fails to track queue item api calls  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 audit-trail-plugin 
 
 
 

Created:
 

 28/Jan/16 7:21 PM 
 
 
 

Environment:
 

 Audit Trail plugin version: 2.2  Jenkins version: 1.609.3 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Sami Salonen 
 
 
 
 
 
 
 
 
 
 
Steps to reproduce using the Jenkins GUI: 
1. Change Audit Trail configuration URL Patterns to Log in Jenkins global configuration from its default value: .*/(?:configSubmit|..|safeExit) to include also api calls: .*/(?:configSubmit|..|safeExit|api.*) 
2. Trigger a build and check its queueId from JENKINS_HOST/job/project_name/lastBuild/api/xml 3. Query queue item using JENKINS_HOST/queue/item/queue-id-from-previous-step/api/xml 4. Jenkins should say "Oops!" with a devilish grin and dump a stack trace containing this: 

 

Caused by: java.lang.NoSuchMethodError: hudson.model.Queue.getItem(I)Lhudson/model/Queue$Item;
	at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:84)
 


[JIRA] [cmakebuilder-plugin] (JENKINS-32657) cmakebuilder should allow cmake scripting

2016-01-28 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber edited a comment on  JENKINS-32657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 
 ??'existing cmake auto-installer'?? : The plugin is able to download  and install  cmake from cmake.org  and install it , if configured so. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cmakebuilder-plugin] (JENKINS-32657) cmakebuilder should allow cmake scripting

2016-01-28 Thread fifteenknots...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber commented on  JENKINS-32657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 
 
'existing cmake auto-installer' : The plugin is able to download and install cmake from cmake.org, if configured so. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-32678) Add support for workflow Pipeline script from SCM

2016-01-28 Thread phi...@gmx.ch (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philipp Meier started work on  JENKINS-32678 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Philipp Meier 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-32678) Add support for workflow Pipeline script from SCM

2016-01-28 Thread phi...@gmx.ch (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philipp Meier assigned an issue to Philipp Meier 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32678 
 
 
 
  Add support for workflow Pipeline script from SCM  
 
 
 
 
 
 
 
 
 

Change By:
 
 Philipp Meier 
 
 
 

Assignee:
 
 Daniel Spilker Philipp Meier 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [job-dsl-plugin] (JENKINS-32678) Add support for workflow Pipeline script from SCM

2016-01-28 Thread phi...@gmx.ch (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philipp Meier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32678 
 
 
 
  Add support for workflow Pipeline script from SCM  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 Daniel Spilker 
 
 
 

Components:
 

 job-dsl-plugin 
 
 
 

Created:
 

 28/Jan/16 7:01 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Philipp Meier 
 
 
 
 
 
 
 
 
 
 
Add DSL for the workflow multibranch plugin(https://github.com/jenkinsci/workflow-plugin/tree/master/multibranch) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-

[JIRA] [scriptler-plugin] (JENKINS-31973) When using the scriptler plugin the server is responding very slow

2016-01-28 Thread r...@samorai.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ran S commented on  JENKINS-31973 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: When using the scriptler plugin the server is responding very slow  
 
 
 
 
 
 
 
 
 
 
Thanks for the update! 
is there any chance to get a fix for that soon? my jobs are already dependent on these versions and i cannot downgrade. 
Thanks, Ran 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [_unsorted] (JENKINS-32677) Don't see labels applied to the codebase

2016-01-28 Thread hmagna...@fieldglass.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hector Magnanao created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32677 
 
 
 
  Don't see labels applied to the codebase  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 _unsorted 
 
 
 

Created:
 

 28/Jan/16 5:34 PM 
 
 
 

Environment:
 

 Jenkins 1.625  Windows  PTC Integrity CM plugin 1.36 
 
 
 

Labels:
 

 configuration 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Hector Magnanao 
 
 
 
 
 
 
 
 
 
 
I'm trying to apply a label to the codebase after a good build in Integrity. I have the checkpoint option checked. I see the label on the last build but I don't see the label in the members. Is there something that's I'm missing ? I would like to apply the label to the all the members atter a good successful build. 
 
 
 
 
 
 
 
 
 
 
 

[JIRA] [branch-api-plugin] (JENKINS-31381) Create default view for organization folder with no children

2016-01-28 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31381 
 
 
 
  Create default view for organization folder with no children  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [multijob-plugin] (JENKINS-18768) Multijob plugin doesn't aggregate test results from downstream projects

2016-01-28 Thread mariusz.ku...@sabre.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mariusz Kuras commented on  JENKINS-18768 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multijob plugin doesn't aggregate test results from downstream projects   
 
 
 
 
 
 
 
 
 
 
Hello, 
Is there anybody who will take this ticket?  
Thanks, Mariusz 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-32493) New Parent POM for Jenkins Plugins

2016-01-28 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32493 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New Parent POM for Jenkins Plugins  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Andres Rodriguez Path: hpi-archetype/pom.xml http://jenkins-ci.org/commit/maven-hpi-plugin/b4584801fd964cb4a95ec9edd287c53498226ad1 Log: 

JENKINS-32493
 Adapt to new plugin parent POM 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-32493) New Parent POM for Jenkins Plugins

2016-01-28 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32493 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New Parent POM for Jenkins Plugins  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: hpi-archetype/pom.xml http://jenkins-ci.org/commit/maven-hpi-plugin/c3a868625ed0c2b71482ed0b4f4a5276325ee3fc Log: Merge pull request #27 from andresrc/newParentPOM 


JENKINS-32493
 Adapt to new plugin parent POM 
Compare: https://github.com/jenkinsci/maven-hpi-plugin/compare/5d26cc0cfc18...c3a868625ed0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-32493) New Parent POM for Jenkins Plugins

2016-01-28 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32493 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New Parent POM for Jenkins Plugins  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Andres Rodriguez Path: hpi-archetype/pom.xml http://jenkins-ci.org/commit/maven-hpi-plugin/4c18b5ced71ae8fcb363b1d5f5118775f9af19c7 Log: 

JENKINS-32493
 Adapt to new plugin parent POM (v2.2) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-32493) New Parent POM for Jenkins Plugins

2016-01-28 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32493 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: New Parent POM for Jenkins Plugins  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Andres Rodriguez Path: hpi-archetype/pom.xml http://jenkins-ci.org/commit/maven-hpi-plugin/bc6559d1cdd28619686efaba357812bd4d031ea5 Log: 

JENKINS-32493
 Adapt to parent POM 2.3 and JTH 2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-32018) Multibranch workflow project tracking multiple repositories

2016-01-28 Thread te...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 James Nord commented on  JENKINS-32018 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multibranch workflow project tracking multiple repositories  
 
 
 
 
 
 
 
 
 
 
 
Why would you need to refer anything of the CI environment? URLs? I don't follow.
 
Tools (you need a specific one to build!) : (maven / JDK etc) may have different names Credentials (maybe for deploying you deploy as you - I deploy as me): IDs may not match Labels (where to build it): you may say linux - I may say RedHat 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32498) Bitbucket notify on start failed: String index out of range: -10

2016-01-28 Thread antonio.mansi...@flagbit.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Mansilla commented on  JENKINS-32498 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket notify on start failed: String index out of range: -10  
 
 
 
 
 
 
 
 
 
 
 I'm newbee as well, so I don't know but I've already marked it as "Resolved" as the bug is fixed and I'd wait to close it until the Bugfix is published on the next version of the plugin. Then you or anyone can close it I think. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-28790) Sonar database credentials in build console output not masked since LTS version 1.596.3

2016-01-28 Thread esc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Emilio Escobar  commented on  JENKINS-28790 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Sonar database credentials in build console output not masked since LTS version 1.596.3  
 
 
 
 
 
 
 
 
 
 
Hi Daniel Beck before that https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/tasks/Maven.java#L327 the ArgumentListBuilder has the masked arguments properly set, but by the execution of args = args.toWindowsCommand(); we are instantiating a new one with three args and none of them masked as you can see https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/ArgumentListBuilder.java#L352 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32498) Bitbucket notify on start failed: String index out of range: -10

2016-01-28 Thread e...@sourcloud.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Woitschig commented on  JENKINS-32498 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket notify on start failed: String index out of range: -10  
 
 
 
 
 
 
 
 
 
 
Is is my part to close this issue? (newbee ) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32498) Bitbucket notify on start failed: String index out of range: -10

2016-01-28 Thread antonio.mansi...@flagbit.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Mansilla resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32498 
 
 
 
  Bitbucket notify on start failed: String index out of range: -10  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonio Mansilla 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32498) Bitbucket notify on start failed: String index out of range: -10

2016-01-28 Thread e...@sourcloud.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Woitschig commented on  JENKINS-32498 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket notify on start failed: String index out of range: -10  
 
 
 
 
 
 
 
 
 
 
Thank you Antonio Mansilla! 
I have tested it, its working! Great!   
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List

2016-01-28 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32676 
 
 
 
  Workflow scripts can't modify a List  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 script-security 1.18{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods push java.util.List java.lang.Object}}eg: {{ node() {  def list = []  list.push( "asdf" )} }}  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List

2016-01-28 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32676 
 
 
 
  Workflow scripts can't modify a List  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 script-security 1.18{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods push java.util.List java.lang.Object}}eg:    {{  node() {  def list = []  list.push( "asdf" )}  }}  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List

2016-01-28 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32676 
 
 
 
  Workflow scripts can't modify a List  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List

2016-01-28 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32676 
 
 
 
  Workflow scripts can't modify a List  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 script-security 1.18{{org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use  method  staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods push  java. util.List java. lang. String substring int Object }}eg:  {{ someString.substring node (  10  ) ;}}  {    def list = []  workaround: {{someString   list . substring push (  10, someString.length(  "asdf" )  );  }  } }  which is slightly annoying and makes the Jenkinsfile more verbose than necessary.Related to: https://issues.jenkins-ci.org/browse/JENKINS-29541 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [script-security-plugin] (JENKINS-32676) Workflow scripts can't modify a List

2016-01-28 Thread michael.sch...@fmr.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Scharp created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32676 
 
 
 
  Workflow scripts can't modify a List  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 script-security-plugin 
 
 
 

Created:
 

 28/Jan/16 4:31 PM 
 
 
 

Labels:
 

 workflow 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Michael Scharp 
 
 
 
 
 
 
 
 
 
 
script-security 1.18 
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String substring int 
eg: someString.substring( 10 ); 
workaround: someString.substring( 10, someString.length() ); 
which is slightly annoying and makes the Jenkinsfile more verbose than necessary. 
Related to: https://issues.jenkins-ci.org/browse/JENKINS-29541 
 
 
 
 
 
 
 
 
 
 
 
 

   

[JIRA] [git-client-plugin] (JENKINS-30045) Git client plugin does not work with new Git for Windows 2.5.0

2016-01-28 Thread neomonk...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Neo Monkeus commented on  JENKINS-30045 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git client plugin does not work with new Git for Windows 2.5.0  
 
 
 
 
 
 
 
 
 
 
Sorry Mark Waite, haven't had time to follow on this. With a clean install of win_2012 server, I manually installed git into a non-default location. It added the location of git to the path, set %GIT_HOME% and was seeing the issue. I resolved the issue by setting %GIT_SSH% 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-18649) Renaming jobs should be a separate permission from configuring

2016-01-28 Thread scott.rah...@dowjones.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Rahner commented on  JENKINS-18649 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Renaming jobs should be a separate permission from configuring  
 
 
 
 
 
 
 
 
 
 
This is a big issue for us at Dow Jones where central teams create and manage jobs, folders, etc but the app teams own the jobs content. When they rename jobs it causes all sort of havok with plugins, apis, reports, etc 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-32675) Pipeline Plugin: Adjusting the Visualization of Pipeline Steps

2016-01-28 Thread chahine.a...@invensity.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Leon updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32675 
 
 
 
  Pipeline Plugin: Adjusting the Visualization of Pipeline Steps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Leon Leon 
 
 
 
 
 
 
 
 
 
 Hello everyone,We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:.i.e: showing nodes like: - stages- running batch- parallel stepsBut not showing other steps like:- Allocate node : StartAllocate node : Body : StartChange Directory : Start My question:  Is such an operation possible  or will at affect the workflow functionality  ?I tried to made the changes by starting with the class FlowGraphTable.Thank you in advance.Any help would be greatly appreciated 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-32675) Pipeline Plugin: Adjusting the Visualization of Pipeline Steps

2016-01-28 Thread chahine.a...@invensity.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Leon Leon created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32675 
 
 
 
  Pipeline Plugin: Adjusting the Visualization of Pipeline Steps  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 28/Jan/16 3:24 PM 
 
 
 

Environment:
 

 Workflow Plugin 1.10  Pipeline Plugin 1.13 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Leon Leon 
 
 
 
 
 
 
 
 
 
 
Hello everyone, 
We are trying to change the visualization of the pipeline steps to make it more understandable for Jenkins users (developers or managers) and make it only show relevant steps:. 
i.e: showing nodes like: 
 

stages
 

running batch
 

parallel steps
 
 
But not showing other steps like: 
 

  

[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32498) Bitbucket notify on start failed: String index out of range: -10

2016-01-28 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32498 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket notify on start failed: String index out of range: -10  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Antonio Mansilla Path: src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/6358b8b0f0f1967dcfb0edf52ed67903c7681a80 Log: [Fix JENKINS-32498] Fix problem fetching repo name from URI 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32498) Bitbucket notify on start failed: String index out of range: -10

2016-01-28 Thread antonio.mansi...@flagbit.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Mansilla commented on  JENKINS-32498 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket notify on start failed: String index out of range: -10  
 
 
 
 
 
 
 
 
 
 
Hi Erik Woitschig good news, finally I have found and fixed the problem and will be published on next plugin release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-32133) Polish and expose auto-generated Workflow step documentation

2016-01-28 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Polish and expose auto-generated Workflow step documentation  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: gusreiber Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/css/workflow.css cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslHelp.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReference.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/js/workflow.js cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.css cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.js http://jenkins-ci.org/commit/workflow-plugin/7d1fdbdff78fd55bff325051617b3457f5629dad Log: 

JENKINS-32133
 styling issues for DSL reference help 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-32133) Polish and expose auto-generated Workflow step documentation

2016-01-28 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-32133 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Polish and expose auto-generated Workflow step documentation  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslHelp.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReference.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.css cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.js http://jenkins-ci.org/commit/workflow-plugin/71559f35cb73ecf7cfa880045b58a4317693b347 Log: 

JENKINS-32133
 Merged #320. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [naginator-plugin] (JENKINS-32625) Naginator plugin does not keep node information

2016-01-28 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-32625 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Naginator plugin does not keep node information  
 
 
 
 
 
 
 
 
 
 
It's caused for naginator-plugin replays only build parameters, and it doesn't replay the node-specifying feature provided by parameterized-trigger-plugin. (It is called a "parameter" in UI, but actually is not a build parameter.) 
Node Label Parameter plugin may help you, as it implements the node-specifying feature as a build parameter, and can be replayed with naginator-plugin. Would you see whether it helps you? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cli] (JENKINS-32535) Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'

2016-01-28 Thread pjano...@redhat.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Janoušek updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32535 
 
 
 
  Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pavel Janoušek 
 
 
 

Issue Type:
 
 Bug Improvement 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cli] (JENKINS-32535) Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'

2016-01-28 Thread pjano...@redhat.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Janoušek edited a comment on  JENKINS-32535 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'  
 
 
 
 
 
 
 
 
 
 [Branch|https://github.com/pjanouse/jenkins/tree/JENKINS-32535] ready, final impl.  depend  depends  on  final version of  resolved  JENKINS-32273. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cli] (JENKINS-32535) Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'

2016-01-28 Thread pjano...@redhat.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Janoušek commented on  JENKINS-32535 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Improve test coverage of CLI commands 'add-job-to-view' and 'remove-job-from-view'  
 
 
 
 
 
 
 
 
 
 
Branch ready, final impl. depend on final version of JENKINS-32273. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [naginator-plugin] (JENKINS-32625) Naginator plugin does not keep node information

2016-01-28 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam assigned an issue to ikedam 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32625 
 
 
 
  Naginator plugin does not keep node information  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Assignee:
 
 Nicolas De Loof ikedam 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [copyartifact-plugin] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception

2016-01-28 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-32664 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Copy Artifact plugin parameter passing via curl throws exception  
 
 
 
 
 
 
 
 
 
 
Unsupported usage. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32519) Bitbucket notify on start failed: No change set to send to Bitbucket!

2016-01-28 Thread antonio.mansi...@flagbit.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Mansilla resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32519 
 
 
 
  Bitbucket notify on start failed: No change set to send to Bitbucket!  
 
 
 
 
 
 
 
 
 

Change By:
 
 Antonio Mansilla 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32519) Bitbucket notify on start failed: No change set to send to Bitbucket!

2016-01-28 Thread antonio.mansi...@flagbit.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Mansilla commented on  JENKINS-32519 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket notify on start failed: No change set to send to Bitbucket!  
 
 
 
 
 
 
 
 
 
 
jake bishop That's fine. If the status doesn't appear in bitbucket is because it seems to not be supported by Bitbucket, I already created an issue at Bitbucket with following response: 

I've checked with our Developers and build status simply isn't supported on PRs from repo forks right now. This is the reason you are not seeing the status on the PR. However, that should works fine if you are not working with forks. Please let us know if there's anything else we can do for you. 
All the best,  Renato Rudnicki Atlassian Support
 
I'll resolve this issue since the problem was solved. If anyone face new problems with this, please create a new issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-01-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-9104 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed  
 
 
 
 
 
 
 
 
 
 
Antony Bartlett Forwarding the praise to my (first)namesake Daniel Weber who did all the work  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32574) Support for Jenkins credential storage

2016-01-28 Thread antonio.mansi...@flagbit.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Mansilla commented on  JENKINS-32574 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support for Jenkins credential storage  
 
 
 
 
 
 
 
 
 
 
Hi again Evan Powell finally I got Jenkins credentials to be supported and it will be released in next plugin version, see pull request. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [build-failure-analyzer-plugin] (JENKINS-32615) com.sonyericsson.jenkins.plugins.bfa.model.dbf.ParameterizedTriggerDBF uses wrong ClassLoader to detect hudson.plugins.parameterizedtrigger.Build

2016-01-28 Thread tomas.westl...@sonymobile.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Westling commented on  JENKINS-32615 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: com.sonyericsson.jenkins.plugins.bfa.model.dbf.ParameterizedTriggerDBF uses wrong ClassLoader to detect hudson.plugins.parameterizedtrigger.BuildInfoExporterAction  
 
 
 
 
 
 
 
 
 
 
Good find! I think the best solution is just to remove the test from the dependency in the pom since there is already a test dependency set as optional for parameterized-trigger. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [build-failure-analyzer-plugin] (JENKINS-32615) com.sonyericsson.jenkins.plugins.bfa.model.dbf.ParameterizedTriggerDBF uses wrong ClassLoader to detect hudson.plugins.parameterizedtrigger.Build

2016-01-28 Thread tomas.westl...@sonymobile.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Westling edited a comment on  JENKINS-32615 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: com.sonyericsson.jenkins.plugins.bfa.model.dbf.ParameterizedTriggerDBF uses wrong ClassLoader to detect hudson.plugins.parameterizedtrigger.BuildInfoExporterAction  
 
 
 
 
 
 
 
 
 
 Good find!I think the best solution is just to remove the test from the dependency in the pomsince there is already a test dependency set as optional for parameterized-trigger. Since there is a test dependency, this would hint at why this issue didn't cause any tests to fail. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart

2016-01-28 Thread d...@baltrinic.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Baltrinic edited a comment on  JENKINS-26761 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart  
 
 
 
 
 
 
 
 
 
 For what its worth we just got bit by this again on a machine w/an older version for workflow.  As we now have Cloudbees support I opened an internal ticket (ironically failing to recognize the problem as being this one :-)  ) , and that ticket has an attached support bundle in case it helps run down the problem.  See  Cloudbees ZenDesk ticket #32944. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart

2016-01-28 Thread d...@baltrinic.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenneth Baltrinic commented on  JENKINS-26761 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart  
 
 
 
 
 
 
 
 
 
 
For what its worth we just got bit by this again on a machine w/an older version for workflow. As we now have Cloudbees support I opened an internal ticket (ironically failing to recognize the problem as being this one , and that ticket has an attached support bundle in case it helps run down the problem. See Cloudbees ZenDesk ticket #32944. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-01-28 Thread a...@akb.me.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antony Bartlett commented on  JENKINS-9104 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed  
 
 
 
 
 
 
 
 
 
 
That's great - thank you very much for clarifying this, and for your efforts to fix the wider issue - I'm looking forward to having more projects and configurations built automatically in a timely fashion through judicious use of parallelization  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [build-failure-analyzer-plugin] (JENKINS-32644) Unable to add indications

2016-01-28 Thread manjias...@googlemail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ashok Manji closed an issue as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
After kicking (restarting) Jenkins a number of times, this is now working as expected. 
Thanks for checking Tomas. Appreciate it. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32644 
 
 
 
  Unable to add indications   
 
 
 
 
 
 
 
 
 

Change By:
 
 Ashok Manji 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-32674) Pipeline Snippet generator does not create valid snippet

2016-01-28 Thread asotobu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32674 
 
 
 
  Pipeline Snippet generator does not create valid snippet  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Soto 
 
 
 
 
 
 
 
 
 
 In case you want to use Workflow (Pipeline plugin) with Docker integration, version 1.2, and you want to push something to a docker registry, you can generate the snippet using the snippet generator. The problem is that snippet generator creates an snippet using _withDockerRegistry_ method. When you execute it you get next exception:{code}hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.docker.workflow.Docker.withDockerRegistry() is applicable for argument types: {code}But if you change to use _withRegistry_ instead of _withDockerRegistry_ then it works. It also works if you do:{code}withDockerRegistry(registry: [url: 'https://index.docker.io/v1/', credentialsId:'0bb7a6bc-5ae5-4d4b-a7d3-dc4893d747a6']) {{code}Adding registry with an array. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-01-28 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-9104 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed  
 
 
 
 
 
 
 
 
 
 
Antony Bartlett The proposed MSBuild Plugin change only requires the plugin to be installed to be effective (assuming mspdbsrv.exe is what you don't want killed). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [workflow-plugin] (JENKINS-32674) Pipeline Snippet generator does not create valid snippet

2016-01-28 Thread asotobu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Soto created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32674 
 
 
 
  Pipeline Snippet generator does not create valid snippet  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 28/Jan/16 12:05 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alex Soto 
 
 
 
 
 
 
 
 
 
 
In case you want to use Workflow (Pipeline plugin) with Docker integration, version 1.2, and you want to push something to a docker registry, you can generate the snippet using the snippet generator. The problem is that snippet generator creates an snippet using withDockerRegistry method. When you execute it you get next exception: 

 

hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.docker.workflow.Docker.withDockerRegistry() is applicable for argument types: 
 

 
But if you change to use withRegistry instead of withDockerRegistry then it works. 
 
 
 
 
 
 
 
 
 
 
 
 

 
   

[JIRA] [cmakebuilder-plugin] (JENKINS-32657) cmakebuilder should allow cmake scripting

2016-01-28 Thread jorg.zieg...@fotonic.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jörg Ziegler commented on  JENKINS-32657 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cmakebuilder should allow cmake scripting  
 
 
 
 
 
 
 
 
 
 
absolutely. Actually the idea to having a new kind of build step sounds brilliant as an idea of how to implement it practically. 
In my mind there are two ways that cmake could be invoked: 
 

in script mode: -P 
 

in command mode (-E) where a series of commands are executed. The commands could be specified in the jenkins project.
 
 
I don't understand your reference to the 'existing cmake auto-installer' - could you please elaborate? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


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

2016-01-28 Thread a...@akb.me.uk (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antony Bartlett commented on  JENKINS-9104 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed  
 
 
 
 
 
 
 
 
 
 
Is there a plan for Visual Studio builds not started by the msbuild-plugin, please? 
I'm asking because our job configurations use a "Execute Windows batch command" build step rather than "Build a Visual Studio project or solution using MSBuild" build step (and our batch process is non-trivial). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [analysis-core-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config

2016-01-28 Thread croesusk...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Croesus Kall commented on  JENKINS-27548 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Sporadic IOException: Failed to persist config  
 
 
 
 
 
 
 
 
 
 
Pretty much the same problem here, except I only get the problem when creating a new issue via the Jenkins rest api. Clearing the org.xml.sax.driver property does not work. 
After restarting Jenkins, things work fine, but after a while it stops working. I have tried at length to reproduce this from a clean install but have not managed to  
Jenkins version 1.644 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [coverity-plugin] (JENKINS-32672) Jenkins integration with Coverity caught Execption

2016-01-28 Thread vineel.nir...@techmahindra.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vineel nirogi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32672 
 
 
 
  Jenkins integration with Coverity caught Execption  
 
 
 
 
 
 
 
 
 
 
Configure page is not loading after adding the coverity step in post build actions. 
 
 
 
 
 
 
 
 
 

Change By:
 
 vineel nirogi 
 
 
 

Attachment:
 
 errorCoverity.jpg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [coverity-plugin] (JENKINS-32672) Jenkins integration with Coverity caught Execption

2016-01-28 Thread vineel.nir...@techmahindra.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vineel nirogi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32672 
 
 
 
  Jenkins integration with Coverity caught Execption  
 
 
 
 
 
 
 
 
 

Change By:
 
 vineel nirogi 
 
 
 

Attachment:
 
 errorCoverity.jpg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [build-pipeline-plugin] (JENKINS-32673) Build Pipeline - Ability to Disable Retry option on a Job

2016-01-28 Thread migalski_pie...@hotmail.fr (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pierre Mig created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32673 
 
 
 
  Build Pipeline - Ability to Disable Retry option on a Job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 build-pipeline-plugin 
 
 
 

Created:
 

 28/Jan/16 11:24 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.580.3 
 
 
 

Labels:
 

 configuration 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Pierre Mig 
 
 
 
 
 
 
 
 
 
 
Hi,  In my use case i don't want somebody to be able to rerun or retry the job that someone else have initiate.  In a general context if some sensitive information are related to the build job (ex. parameters with identification, login,password, tokens) another person will be able to reuse them with the retry option. If the option Retry button can be disabled this will suite my need. Any more sophisticated solution are welcomed 
 
 
 
 
 
 
 
 
 

[JIRA] [build-failure-analyzer-plugin] (JENKINS-20900) Integrate with Git Pull Request

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-20900 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Integrate with Git Pull Request  
 
 
 
 
 
 
 
 
 
 
I think it should be possible with https://github.com/jenkinsci/github-integration-plugin/wiki/Features see "Publishers" section. You need prepare text in any possible way and then set in any PR related plugin (ghprb or github-pullrequest-plugin). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [build-failure-analyzer-plugin] (JENKINS-20900) Integrate with Git Pull Request

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-20900 
 
 
 
  Integrate with Git Pull Request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-24421) Github webhook throwing "Form too large"

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Also think that it servlet issue. If it still reproducible, feel free to reopen. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-24421 
 
 
 
  Github webhook throwing "Form too large"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-26886) Variables not being substituted in github URLs for $JOB_NAME

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
No replies - closing. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26886 
 
 
 
  Variables not being substituted in github URLs for $JOB_NAME  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-28104) Keyword expansion does not appear to work when registering the github web hook

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Incomplete 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28104 
 
 
 
  Keyword expansion does not appear to work when registering the github web hook  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Incomplete 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-28104) Keyword expansion does not appear to work when registering the github web hook

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-28104 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Keyword expansion does not appear to work when registering the github web hook  
 
 
 
 
 
 
 
 
 
 
No replies, closing. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-30980) Github polls fails when the Branches to build is different from empty for private repositories

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou edited a comment on  JENKINS-30980 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github polls fails when the Branches to build is different from empty for private repositories  
 
 
 
 
 
 
 
 
 
 Please disable GitHub  pustrigger  pushtrigger , enable "Poll SCM" and ensure that build triggering/checkout works.GitHub push trigger is just a simple kicker for git polling algorithm. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [copyartifact-plugin] (JENKINS-32664) Copy Artifact plugin parameter passing via curl throws exception

2016-01-28 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev assigned an issue to Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32664 
 
 
 
  Copy Artifact plugin parameter passing via curl throws exception  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [coverity-plugin] (JENKINS-32672) Jenkins integration with Coverity caught Execption

2016-01-28 Thread vineel.nir...@techmahindra.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vineel nirogi created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32672 
 
 
 
  Jenkins integration with Coverity caught Execption  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ken Dang 
 
 
 

Attachments:
 

 errorCoverity.jpg 
 
 
 

Components:
 

 coverity-plugin 
 
 
 

Created:
 

 28/Jan/16 10:47 AM 
 
 
 

Environment:
 

 linux 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 vineel nirogi 
 
 
 
 
 
 
 
 
 
 
I am working with Jenkins 1.615 and Coverity Plugin 1.6.0 I have installed the Coverity 7.7.0 in same server where I have Jenkins 1.615 
I have configured the Coverity with Jenkins by updating 1. Jenkins-

>Manage Jenkins


>Configure System
->Coverity Static Analysis location and checked connection. 2. Jenkins-

>Manage Jenkins
   

[JIRA] [github-plugin] (JENKINS-30980) Github polls fails when the Branches to build is different from empty for private repositories

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-30980 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github polls fails when the Branches to build is different from empty for private repositories  
 
 
 
 
 
 
 
 
 
 
Please disable GitHub pustrigger, enable "Poll SCM" and ensure that build triggering/checkout works. GitHub push trigger is just a simple kicker for git polling algorithm. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32666) Inject the Payload into the build

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32666 
 
 
 
  Inject the Payload into the build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

URL:
 
 https://github.com/jenkinsci/github-plugin/pull/108 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32666) Inject the Payload into the build

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou closed an issue as Postponed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closing according to GH comments. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32666 
 
 
 
  Inject the Payload into the build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 In Progress Closed 
 
 
 

Resolution:
 
 Postponed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32666) Inject the Payload into the build

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou resolved as Postponed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32666 
 
 
 
  Inject the Payload into the build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Status:
 
 Reopened Resolved 
 
 
 

Resolution:
 
 Postponed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [github-plugin] (JENKINS-32666) Inject the Payload into the build

2016-01-28 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32666 
 
 
 
  Inject the Payload into the build  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Resolution:
 
 Postponed 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [core] (JENKINS-32357) Better config page navigation - phase 1

2016-01-28 Thread tom.fenne...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY edited a comment on  JENKINS-32357 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Better config page navigation - phase 1  
 
 
 
 
 
 
 
 
 
 [We have a WiP Pull request here|https://github.com/ tfennelly jenkinsci /jenkins/pull/ 1 2006 ].[Dev list conversation|https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/tXursfAKz7M] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and 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   >