date:20150509

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Basil Peace created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28318 
 
 
 
  Twitter plugin stores token secret in plain text  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kenichi Maehashi 
 
 
 

Components:
 

 twitter-plugin 
 
 
 

Created:
 

 09/May/15 9:40 AM 
 
 
 

Environment:
 

 Twitter plugin 0.7 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Basil Peace 
 
 
 
 
 
 
 
 
 
 
I believe that passwords and secrets should be encrypted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [github-oauth-plugin] (JENKINS-28319) Client secret is stored in config as plain text

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Basil Peace created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28319 
 
 
 
  Client secret is stored in config as plain text  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Sam Kottler 
 
 
 

Components:
 

 github-oauth-plugin 
 
 
 

Created:
 

 09/May/15 10:29 AM 
 
 
 

Environment:
 

 Github Authentication plugin 0.20 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Basil Peace 
 
 
 
 
 
 
 
 
 
 
Client secret is stored in config as plain text. I'm sure that it should be encrypted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [github-plugin] (JENKINS-28320) GitHub plugins store access tokens in config files as plain text

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Basil Peace created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28320 
 
 
 
  GitHub plugins store access tokens in config files as plain text  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kanstantsin Shautsou 
 
 
 

Components:
 

 github-plugin, github-pullrequest-plugin 
 
 
 

Created:
 

 09/May/15 11:04 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Basil Peace 
 
 
 
 
 
 
 
 
 
 
Access tokens in config files should be encrypted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [github-oauth-plugin] (JENKINS-28319) GitHub OAuth client secret is stored in config as plain text

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Basil Peace updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28319 
 
 
 
  GitHub OAuth client secret is stored in config as plain text  
 
 
 
 
 
 
 
 
 

Change By:
 
 Basil Peace 
 
 
 

Summary:
 
 Client GitHub OAuth client  secret is stored in config as plain text 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25977) Make publishers of analysis-core a SimpleBuildStep

2015-05-09 Thread a...@andne.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andy Neebel commented on  JENKINS-25977 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make publishers of analysis-core a SimpleBuildStep  
 
 
 
 
 
 
 
 
 
 
I took a little look at the code of analysis-core-plugin and think I see which class needs to be modified (HealthAwareRecorder), but there is quite the hierarchy of classes involved that all pass AbstractBuild through them and that is the extension point that the findbugs-plugin and warnings-plugin and others use. So yes, it appears that some major refactoring is needed unless there is a reliable way to convert a Run into an AbstractBuild. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jim jaeger commented on  JENKINS-28212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 
 
The issue also occurs on Jenkins 1.612 + Plugin Version 2.40.1.  Steps to recreate: 1) Open a config of a project and add the email section to the post build options 2) Click save --> Exception  
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher from {"project_disabled":false,"project_recipient_list":"$DEFAULT_RECIPIENTS","project_replyto":"$DEFAULT_REPLYTO","project_content_type":"default","project_default_subject":"$DEFAULT_SUBJECT","project_default_content":"$DEFAULT_CONTENT","project_attachments":"","project_attach_buildlog":"0","project_presend_script":"$DEFAULT_PRESEND_SCRIPT","project_save_output":false,"project_triggers": {"stapler-class":"","$class":""} 
,"stapler-class":"hudson.plugins.emailext.ExtendedEmailPublisher","$class":"hudson.plugins.emailext.ExtendedEmailPublisher"} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegise

[JIRA] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jim jaeger updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28212 
 
 
 
  Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 

Change By:
 
 jim jaeger 
 
 
 

Priority:
 
 Major Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

2015-05-09 Thread slide.o....@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-28212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 
 
I don't get this exception. I ran Jenkins 1.612 + Email-ext 2.40.1 and I don't get this exception when I add email-ext to the post-build steps. So, something else is at play.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [plot-plugin] (JENKINS-25849) remove unneccessary stack traces in jenkins log

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25849 
 
 
 
  remove unneccessary stack traces in jenkins log  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [plot-plugin] (JENKINS-25849) remove unneccessary stack traces in jenkins log

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25849 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: remove unneccessary stack traces in jenkins log  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Sebastian Schuberth Path: src/main/java/hudson/plugins/plot/Plot.java http://jenkins-ci.org/commit/plot-plugin/e7bab51199f96a929609eb98db2ff959a13636af Log: [FIXED JENKINS-25849] Do not log if parsing a blank string to int fails 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jim jaeger commented on  JENKINS-28212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 
 
Additonal system information: SUSE Linux Enterprise Server 11 x86_64 GNU/Linux with Jenkins on Tomcat 7. Which more system information do you need? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

2015-05-09 Thread dan...@beckweb.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-28212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 
 
Job type and installed plugins may help. 
Are you able to reproduce this issue on a newly set up instance e.g. on your desktop machine? java -jar jenkins.war and installing the plugin is a 5 minute job  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jim jaeger commented on  JENKINS-28212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 
 
Job Type: Freestyle Installed Plugins:  analysis-collector 1.43  analysis-core 1.71  ant 1.2  antisamy-markup-formatter 1.3  artifactdeployer 0.33  artifactory 2.3.0  build-name-setter 1.3  build-pipeline-plugin 1.4.7  buildresult-trigger 0.17  checkstyle 3.42  copyartifact 1.35  credentials 1.22  cvs 2.12  dashboard-view 2.9.4  dependencyanalyzer 0.7  deploy 1.10  discard-old-build 1.05  email-ext 2.40.1  email-ext-recipients-column 1.0  external-monitor-job 1.4  git 2.3.5  git-client 1.17.0  html-audio-notifier 0.4  html5-notifier-plugin 1.5  htmlpublisher 1.3  http_request 1.8.8  ibm-ucdeploy-publisher 1.2.0  javadoc 1.3  jquery 1.11.2-0  jshint-checkstyle 3.36  jslint-checkstyle 3.35  junit 1.6  ldap 1.11  ldapemail 0.8  m2release 0.14.0  mailer 1.15  mapdb-api 1.0.6.0  matrix-auth 1.2  matrix-project 1.4.1  maven-info 0.2.0  maven-invoker-plugin 1.2  maven-metadata-plugin 1.2.0  maven-plugin 2.9  maven-repo-cleaner 1.2  pam-auth 1.2  parameterized-trigger 2.26  postbuild-task 1.8  progress-bar-column-plugin 1.0  repository 1.2  sametime 0.4  scm-api 0.2  scp 1.8  script-security 1.14  scripttrigger 0.31  ssh 2.4  ssh-credentials 1.11  ssh-slaves 1.9  subversion 2.5  teamconcert 1.1.9.1  token-macro 1.10  translation 1.12  versionnumber 1.5  windows-slaves 1.0  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-18989) Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"

2015-05-09 Thread j...@jyng.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 joel Young commented on  JENKINS-18989 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot get Plugin to honor Java Jar added via "Additional groovy classpath"  
 
 
 
 
 
 
 
 
 
 
I've been having the same problem. I'm using v2.2 of the plugin. I've tried using the "Additional Classpath" fields, gone into the Jenkins file in /etc/sysconfig and added a "-cp" options to the JENKINS_JAVA_OPTIONS setting, and tried using the classload in the form: manager.hudson.class.classLoader.addURL(new URL("file:///" + filePath)) 
None of it seemed to work. In the end I had to create a "Trigger parameterized build on other project" then specify my script in a Build step. The classpath variables appeared to work there. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25977) Make publishers of analysis-core a SimpleBuildStep

2015-05-09 Thread ullrich.haf...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ulli Hafner commented on  JENKINS-25977 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make publishers of analysis-core a SimpleBuildStep  
 
 
 
 
 
 
 
 
 
 
Yes, all depending plug-ins need to be changed. I don't think that this could be done in a backward compatible way.  
Additionally, the publishers use BuildStepMonitor#STEP as return value for BuildStepMonitor getRequiredMonitorService(). This seems to be a bad choice for the workflow plug-in according to the JavaDoc. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [crx-content-package-deployer-plugin] (JENKINS-25032) Credentials metadata leak in GraniteCredentialsListBoxModel

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25032 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Credentials metadata leak in GraniteCredentialsListBoxModel  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mark Adamcin Path: src/main/java/org/jenkinsci/plugins/graniteclient/BuildPackageBuilder.java src/main/java/org/jenkinsci/plugins/graniteclient/DeployPackagesBuilder.java src/main/java/org/jenkinsci/plugins/graniteclient/DownloadPackagesBuilder.java src/main/java/org/jenkinsci/plugins/graniteclient/GraniteAHCFactory.java src/main/java/org/jenkinsci/plugins/graniteclient/GraniteCredentialsListBoxModel.java src/main/java/org/jenkinsci/plugins/graniteclient/PackageChoiceParameterDefinition.java src/main/java/org/jenkinsci/plugins/graniteclient/ReplicatePackagesBuilder.java http://jenkins-ci.org/commit/crx-content-package-deployer-plugin/9210b8b5e8bc11cc2e5cd6e8fd7f9a4e8b16ec0b Log: (JENKINS-25032) Close Credentials metadata leak in GraniteCredentialsListBoxModel 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [crx-content-package-deployer-plugin] (JENKINS-25032) Credentials metadata leak in GraniteCredentialsListBoxModel

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25032 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Credentials metadata leak in GraniteCredentialsListBoxModel  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mark Adamcin Path: src/main/java/org/jenkinsci/plugins/graniteclient/BuildPackageBuilder.java src/main/java/org/jenkinsci/plugins/graniteclient/DeployPackagesBuilder.java src/main/java/org/jenkinsci/plugins/graniteclient/DownloadPackagesBuilder.java src/main/java/org/jenkinsci/plugins/graniteclient/GraniteAHCFactory.java src/main/java/org/jenkinsci/plugins/graniteclient/GraniteCredentialsListBoxModel.java src/main/java/org/jenkinsci/plugins/graniteclient/PackageChoiceParameterDefinition.java src/main/java/org/jenkinsci/plugins/graniteclient/ReplicatePackagesBuilder.java http://jenkins-ci.org/commit/crx-content-package-deployer-plugin/5089ad5f9803c55a6e0f46eaebb0bbd79f802228 Log: Merge pull request #1 from jenkinsci/bugfix/JENKINS-25032 
(JENKINS-25032) Close Credentials metadata leak in GraniteCredentialsListBoxModel 
Compare: https://github.com/jenkinsci/crx-content-package-deployer-plugin/compare/bb9b876b7ced...5089ad5f9803 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28320) GitHub plugins store access tokens in config files as plain text

2015-05-09 Thread gentoo.inte...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28320 
 
 
 
  GitHub plugins store access tokens in config files as plain text  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Component/s:
 
 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] [github-plugin] (JENKINS-28320) GitHub plugins store access tokens in config files as plain text

2015-05-09 Thread gentoo.inte...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-28320 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: GitHub plugins store access tokens in config files as plain text  
 
 
 
 
 
 
 
 
 
 
github-pullrequest-plugin is experimental atm and i don't care about this problem.  Keeping github-plugin component for verification. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28320) GitHub plugins store access tokens in config files as plain text

2015-05-09 Thread gentoo.inte...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28320 
 
 
 
  GitHub plugins store access tokens in config files as plain text  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Assignee:
 
 Kanstantsin Shautsou 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

2015-05-09 Thread slide.o....@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-28212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 
 
Can you post the config.xml for your job? Scrub any username/passwords first. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jim jaeger commented on  JENKINS-28212 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 
 
config.xml attached. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [email-ext-plugin] (JENKINS-28212) Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jim jaeger updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28212 
 
 
 
  Failed to instantiate class hudson.plugins.emailext.ExtendedEmailPublisher  
 
 
 
 
 
 
 
 
 

Change By:
 
 jim jaeger 
 
 
 

Attachment:
 
 config.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-18938) COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Davidson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-18938 
 
 
 
  COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Davidson 
 
 
 

Priority:
 
 Major Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-18938) COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Davidson commented on  JENKINS-18938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names  
 
 
 
 
 
 
 
 
 
 
I'm assuming the numbers are removed because on some systems, environment variables cannot start with a number. However, the implementation creates difficult to workaround aliasing problems where job names like my_build_win32 and my_build_win64 resolve to same variable (my_build_win_). 
A better implementation that only removes numbers from the start of the variable would be: 

 

projectName.toUpperCase().replaceAll("^[^A-Z]+", "_").replaceAll("[^A-Z0-9]+", "_") // Variables must begin with a letter (or underscore) and consist of letters, numbers, and _
 

 
This prevents invalid variables and should avoid aliasing for 99.5% of job names. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in copyartifact-1.35.1. It will be available in a day. 
This is a problem only in Jenkins 1.610 and I highly recommend you to upgrade your Jenkins to the latest one or use a LTS version. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28011 
 
 
 
  Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28096) Copyartifact doesn't work with Workflow's snippet generator.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in copyartifact-1.35.1. It will be available in a day. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28096 
 
 
 
  Copyartifact doesn't work with Workflow's snippet generator.  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28094) Get rid of ca:selectorList (fix problem with Jenkins-1.610)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in copyartifact-1.35.1. It will be available in a day. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28094 
 
 
 
  Get rid of ca:selectorList (fix problem with Jenkins-1.610)  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27475) NPE when renaming a job while a Copy Artifact step has incomplete config

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in copyartifact-1.35.1. It will be available in a day. 
You also need to upgrade your Jenkins to 1.580.1 or later. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27475 
 
 
 
  NPE when renaming a job while a Copy Artifact step has incomplete config  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [parameterized-trigger-plugin] (JENKINS-17176) The "Restrict matrix execution to subset" Groovy filter is not evaluate

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam updated  JENKINS-17176 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-17176 
 
 
 
  The "Restrict matrix execution to subset" Groovy filter is not evaluate  
 
 
 
 
 
 
 
 
 

Change By:
 
 ikedam 
 
 
 

Status:
 
 Reopened Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [parameterized-trigger-plugin] (JENKINS-17176) The "Restrict matrix execution to subset" Groovy filter is not evaluate

2015-05-09 Thread achit...@mercenarytechnology.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Could not reproduce with Jenkins 1.596.2, parameterized-trigger 2.26. Reopen the issue with detailed instructions to reproduce the problem. 
Steps I tested: 
 

Create a multi-configuration project "downstream" 
 

Add axes 
 

User-defined Axis 
 

Name: axis1
 

Values: value1 value2
 
 
 

User-defined Axis 
 

Name: axis2
 

Values: value1 value2
 
 
 
 
 

Set "Combination Filter" 
 

axis1 != axis2
 
 
 
 
 

Run "downstream" 
 

"axis1=value1,axis2=value2" and "axis1=value2, axis2=value1" will be run.
 
 
 

Create a freestyle project "upstream" 
 

Add "Trigger parameterized build on other projects" in "Post-build Actions"

[JIRA] [workflow-plugin] (JENKINS-28321) Method pointer operator (.&) broken

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 A C created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28321 
 
 
 
  Method pointer operator (.&) broken  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 10/May/15 1:32 AM 
 
 
 

Environment:
 

 Jenkins 1.6.11  Workflow 1.6 
 
 
 

Labels:
 

 groovy 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 A C 
 
 
 
 
 
 
 
 
 
 
The method pointer operator (.&) is entirely broken. The following test: 
def bar = 'foo'.&toUpperCase 
Results in: startup failed: General error during canonicalization: java.lang.UnsupportedOperationException 
Plus a giant call stack. 
The workaround is to instead explicitly create a closure which calls the method, which is syntactically cumbersome and reduces semantic readability.

[JIRA] [authorize-project-plugin] (JENKINS-28298) Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-28298 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1  
 
 
 
 
 
 
 
 
 
 
Instructions to reproduce the problem are written in 

JENKINS-22469
. 
REST API 
 

Returns HTTP status code 200.
 

No exceptions are logged in the system log.
 

The updated configuration is not loaded into the memory (authorization configuration gets empty in the configuration page).
 

But the new configuration is saved to the disk.
 

When restarting Jenkins you can active the new configuration.
 
 
CLI 
 

The command exits with 0.
 

No exceptions are logged in the system log.
 

The updated configuration is not loaded into the memory (authorization configuration gets empty in the configuration page).
 

But the new configuration is saved to the disk.
 

When restarting Jenkins you can active the new configuration.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [authorize-project-plugin] (JENKINS-28298) Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-28298 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1  
 
 
 
 
 
 
 
 
 
 
Might be broken for 

JENKINS-21024
. It is also ported to Jenkins-1.532.3. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [authorize-project-plugin] (JENKINS-28298) Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-28298 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1  
 
 
 
 
 
 
 
 
 
 

 
 

 Jenkins version 
 

 Test result 
 
 
 

 1.532 
 

 Success 
 
 
 

 1.543 
 

 Success 
 
 
 

 1.544 
 

 Success 
 
 
 

 1.545 
 

 Faulure 
 
 
 

 1.548 
 

 Failure 
 
 
 

 1.554 
 

 Failure

[JIRA] [copyartifact-plugin] (JENKINS-18938) COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names

2015-05-09 Thread jacek.tom...@hexagongeospatial.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Davidson commented on  JENKINS-18938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names  
 
 
 
 
 
 
 
 
 
 
Scratch that. The only time project name is added to an environment variable is when it's appended to a fixed string (COPYARTIFACT_BUILD_NUMBER_), which avoids the problem of starting with a number altogether. So I agree with Johanns, there's no reason to replace numbers. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [project-inheritance-plugin] (JENKINS-28322) New version not saved when only Promoted builds plugin configuration is saved

Title: Message Title

Jacek Tomaka created an issue

Jenkins / JENKINS-28322

New version not saved when only Promoted builds plugin configuration is saved

Issue Type:

Bug

Assignee:

Jacek Tomaka

Components:

project-inheritance-plugin, promoted-builds-plugin

Created:

10/May/15 4:55 AM

Priority:

Major

Reporter:

Jacek Tomaka

When inheritance project contains promoted build configuration, i.e Promoted build plugin is installed and "Promote builds when..." is configured on a project, then subsequent modifications to "Promote builds when..." subsection is not immediately visible and no new version is saved.
This is because promoted builds plugin stores only references to promotion processes in the config files, i.e. :
zupa
And the configuration of promotions processes themselves are stored under "promotions" subdirectory.
Because VersionedObjectStore.areIdentical 's implementation compares configuration strings: Jenkins.XSTREAM2.toXMLUTF8(o1, os1); Jenkins.XSTREAM2.toXMLUTF8(o2, os2); It will not detect changes and store a new version.
The way promoted builds plugin stores configuration breaks versioning in inheritance plugin.
This bug consists of two parts: 1. Provide short term workaround to get Promoted builds configuration working, even sacrificing versioning, i.e. always the latest version of promoted builds configuration is used. 2. Create bug to solve problem completely, i.e. COS: versioning is working even with changes made only to t

[JIRA] [multijob-plugin] (JENKINS-25675) Provide environment variables like Parameterized Trigger Plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Davidson commented on  JENKINS-25675 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provide environment variables like Parameterized Trigger Plugin  
 
 
 
 
 
 
 
 
 
 
I also am in need of this functionality. My situation is similar. I have a top level job that kicks off "product" builds for various platforms. Currently, I'm kicking these off via the parameterized trigger plugin and blocking. Once all of the product builds are complete, there are a series of cross-platform test/checkout jobs that run against the product. In order to ensure the jobs run against the exact product built by the top-level job, the build number is passed in via parameter. 
I attempted to convert the top-level job to a mutljob project this afternoon and ran into issues after discovering that there appears to be no way to gather the build numbers of jobs kicked off in a phase.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [prioritysorter-plugin] (JENKINS-28280) Wrong Job Group is shown in the selector