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

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

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

 
 
 
 
 
 
 
  Re: GitHub OAuth client secret is stored in config as plain text  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Sam Gleske Path: src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java src/test/java/org/jenkinsci/plugins/GithubSecurityRealmTest.java http://jenkins-ci.org/commit/github-oauth-plugin/1821a0c184db116b13b62a335b389541542c171d Log: Merge PR #51 JENKINS-28319 encrypt the client secret 
Compare: https://github.com/jenkinsci/github-oauth-plugin/compare/586af554db38...1821a0c184db 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-oauth-plugin] (JENKINS-28319) GitHub OAuth client secret is stored in config as plain text

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

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

 
 
 
 
 
 
 
  Re: GitHub OAuth client secret is stored in config as plain text  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: John P. Neumann Path: src/main/java/org/jenkinsci/plugins/GithubSecurityRealm.java src/test/java/org/jenkinsci/plugins/GithubSecurityRealmTest.java http://jenkins-ci.org/commit/github-oauth-plugin/72fd51a3966a104c7d03b0299fc902194f23cecb Log: JENKINS-28319 encrypt the client secret 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32565) workflowLibs.git: Unable to clone empty repository via ssh using msys-git

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lionel Orellana commented on  JENKINS-32565 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: workflowLibs.git: Unable to clone empty repository via ssh using msys-git  
 
 
 
 
 
 
 
 
 
 
More of an issue when you get a fatal error instead of a warning. 
fatal: could not fetch refs from ssh://**@**:***/workflowLibs.git 
Easy way around it is to create an empty repo locally and push it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34501) Steps that accept closure overwrite parallel branch context logs

[nick.sonnev...@smartward.com.au (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Sonneveld created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34501 
 
 
 
  Steps that accept closure overwrite parallel branch context logs  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Attachments:
 

 jenkins-step-closure-loses-parallel-log.groovy, jenkins-step-closure-loses-parallel-log.log 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Apr/29 2:09 AM 
 
 
 

Environment:
 

 Jenkins 2.0, Pipeline plugins 2.0, Linux master, Windows slaves 
 
 
 

Labels:
 

 workflow pipeline 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Nick Sonneveld 
 
 
 
 
 
 
 
 
 
 
When within a parallel branch and using steps that accept a closure (such as 'withEnv', 'dir' or 'timeout') the parallel context prepended in log is lost after the step has completed. This doesn't happen if a closure is called directly. 
  

[JIRA] [git-plugin] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory

[jacob.kel...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Keller edited a comment on  JENKINS-32479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: multiple git repositories sometimes fail to checkout some of them into subdirectory  
 
 
 
 
 
 
 
 
 
 I  found  believe  the root cause  of the issue  is due to  using MultiSCM to checkout submodules that exist within  how  the  repository. This causes the git commands to fail if it happens to handle the parent project first. I believe this is an issue that should be fixed from within git.An alternative work-around would be to extend the submodule support in  Git plugin  to enable  handles clones, via  " git init" + "git fetch" + "git checkout  submodule to specific sha1sum "  which causes it to accidentally remove the other repositories .  I am  asking on the git mailing list if  investigating  this  is expected behavior and how best to fix it  now . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [extended-choice-parameter-plugin] (JENKINS-34478) JSON-editor with File-Upload causes "Argument list too long" fatal error

[totoroliu1...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu commented on  JENKINS-34478 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JSON-editor with File-Upload causes "Argument list too long" fatal error  
 
 
 
 
 
 
 
 
 
 
By the way, 
I have another question regarding to JSON's File option: 
 
"File": { "type": "string", "propertyOrder": 3, 
 

"media": 

Unknown macro: { "binaryEncoding"} 
 
,* "options": 

Unknown macro: { "include_filename"} 
 
}
 
 
 
Do I have to predefine "binaryEncoding" and "type"? If I want to allow user to upload either text files, or tarball files, or image files, then how do I make it to dynamically use different binaryEncoding and type? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory

[jacob.kel...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Keller commented on  JENKINS-32479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: multiple git repositories sometimes fail to checkout some of them into subdirectory  
 
 
 
 
 
 
 
 
 
 
I found the root cause of the issue is due to using MultiSCM to checkout submodules that exist within the repository. This causes the git commands to fail if it happens to handle the parent project first. I believe this is an issue that should be fixed from within git. 
An alternative work-around would be to extend the submodule support in Git plugin to enable "checkout submodule to specific sha1sum". 
I am asking on the git mailing list if this is expected behavior and how best to fix it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [extended-choice-parameter-plugin] (JENKINS-34440) JSON-editor File upload is not working and is blocking the whole display

[totoroliu1...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34440 
 
 
 
  JSON-editor File upload is not working and is blocking the whole display  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rick Liu 
 
 
 

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] [extended-choice-parameter-plugin] (JENKINS-34478) JSON-editor with File-Upload causes "Argument list too long" fatal error

[totoroliu1...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rick Liu commented on  JENKINS-34478 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JSON-editor with File-Upload causes "Argument list too long" fatal error  
 
 
 
 
 
 
 
 
 
 
That'd be awesome~ Thank you very much vimil.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [support-core-plugin] (JENKINS-34462) Support core plugin needs to obtain the status of whether CSRF protection is enabled

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Wood resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34462 
 
 
 
  Support core plugin needs to obtain the status of whether CSRF protection is enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Wood 
 
 
 

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] [support-core-plugin] (JENKINS-34462) Support core plugin needs to obtain the status of whether CSRF protection is enabled

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

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

 
 
 
 
 
 
 
  Re: Support core plugin needs to obtain the status of whether CSRF protection is enabled  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Owen Wood Path: src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java http://jenkins-ci.org/commit/support-core-plugin/1b0969fede6c441d093577b21d9a69badae0fd7a Log: JENKINS-34462 - Code review changes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [support-core-plugin] (JENKINS-34462) Support core plugin needs to obtain the status of whether CSRF protection is enabled

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

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

 
 
 
 
 
 
 
  Re: Support core plugin needs to obtain the status of whether CSRF protection is enabled  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Owen Wood Path: src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java http://jenkins-ci.org/commit/support-core-plugin/e394d97c24b7c3be12edc1588e04c8437fdf4996 Log: JENKINS-34462 - Support core plugin needs to obtain the status of whether CSRF protection is enabled 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [support-core-plugin] (JENKINS-34462) Support core plugin needs to obtain the status of whether CSRF protection is enabled

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

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

 
 
 
 
 
 
 
  Re: Support core plugin needs to obtain the status of whether CSRF protection is enabled  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Steven Christou Path: src/main/java/com/cloudbees/jenkins/support/impl/AboutJenkins.java http://jenkins-ci.org/commit/support-core-plugin/054936abbe2a8a7a838cba131cd1b86abc3c78bb Log: Merge pull request #59 from Evildethow/feature/JENKINS-34462 
JENKINS-34462 - Support core plugin needs to obtain the status of whether CSRF protection is enabled 
Compare: https://github.com/jenkinsci/support-core-plugin/compare/f231a0c3f728...054936abbe2a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [delivery-pipeline-plugin] (JENKINS-34500) Pipeline Plugin - pipeline-stage-step

[mev...@parchment.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Evans created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34500 
 
 
 
  Pipeline Plugin - pipeline-stage-step   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Patrik Boström 
 
 
 

Attachments:
 

 first build always running.png 
 
 
 

Components:
 

 delivery-pipeline-plugin 
 
 
 

Created:
 

 2016/Apr/28 9:03 PM 
 
 
 

Environment:
 

 docker run --rm -p : -p 8080:8080 -p 8081:8081 -p 9418:9418 -ti jenkinsci/workflow-demo 
 
 
 

Labels:
 

 jenkins pipeline 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Matt Evans 
 
 
 
 
 
 
 
 
 
 
I'm trying to create 'deployment' stages in a JENKINSFILE. 
I set concurrency to 1 for the deployment stage. From reading pipeline-stage step documentation it is said that: 
" Newer builds are always given priority when 

[JIRA] [core] (JENKINS-33546) Regression with build parameters in XML API

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vivek Pandey commented on  JENKINS-33546 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression with build parameters in XML API  
 
 
 
 
 
 
 
 
 
 
Astro Ashtar Not yet. Its intended to go in 2.2 - that will be in coupe weeks. See https://github.com/jenkinsci/jenkins/pull/2265. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ghprb-plugin] (JENKINS-34499) Nullpointer for ghprbhook URL for GitHub Pull Request Builder

[ty...@monkeypox.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34499 
 
 
 
  Nullpointer for ghprbhook URL for GitHub Pull Request Builder  
 
 
 
 
 
 
 
 
 

Change By:
 
 R. Tyler Croy 
 
 
 

Project:
 
 Infrastructure Jenkins 
 
 
 

Key:
 
 INFRA JENKINS - 675 34499 
 
 
 

Workflow:
 
 classic default workflow JNJira 
 
 
 

Component/s:
 
 ghprb-plugin 
 
 
 

Component/s:
 
 github 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [ghprb-plugin] (JENKINS-34499) Nullpointer for ghprbhook URL for GitHub Pull Request Builder

[ty...@monkeypox.org (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R. Tyler Croy assigned an issue to Honza Brázdil 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34499 
 
 
 
  Nullpointer for ghprbhook URL for GitHub Pull Request Builder  
 
 
 
 
 
 
 
 
 

Change By:
 
 R. Tyler Croy 
 
 
 

Priority:
 
 Blocker Minor 
 
 
 

Assignee:
 
 R. Tyler Croy Honza Brázdil 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [extended-choice-parameter-plugin] (JENKINS-34478) JSON-editor with File-Upload causes "Argument list too long" fatal error

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 vimil commented on  JENKINS-34478 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JSON-editor with File-Upload causes "Argument list too long" fatal error  
 
 
 
 
 
 
 
 
 
 
Rick, I can make an enhancement to store the file in the job's work-space folder. So if the job runs on the slave then it will be available in the workspace folder which is on the slave machine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33546) Regression with build parameters in XML API

[locopelo...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Astro Ashtar commented on  JENKINS-33546 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression with build parameters in XML API  
 
 
 
 
 
 
 
 
 
 
Vivek Panday - do you know if it's been migrated into jenkins 2.x yet? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-token-root-plugin] (JENKINS-25637) Add CrumbExclusion for buildByToken URL

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

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

 
 
 
 
 
 
 
  Re: Add CrumbExclusion for buildByToken URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java src/test/java/org/jenkinsci/plugins/build_token_root/BuildRootActionTest.java http://jenkins-ci.org/commit/build-token-root-plugin/b55500bb117dcd872a03ca2f90aa78b2a085075d Log: Merge pull request #10 from ydubreuil/

JENKINS-25637
 
[FIXED JENKINS-25637] don't require a crumb to trigger a build 
Compare: https://github.com/jenkinsci/build-token-root-plugin/compare/1bfbfda0f451...b55500bb117d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-token-root-plugin] (JENKINS-25637) Add CrumbExclusion for buildByToken URL

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

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

 
 
 
 
 
 
 
  Re: Add CrumbExclusion for buildByToken URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Pedro Algarvio Path: src/main/java/org/jenkinsci/plugins/build_token_root/BuildRootAction.java http://jenkins-ci.org/commit/build-token-root-plugin/a0b99f948fcb5cd12cd8781a81f3d18bd387d131 Log: Exclude the plugin rooth path from requiring crumb 
Refs https://issues.jenkins-ci.org/browse/JENKINS-25637 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-token-root-plugin] (JENKINS-25637) Add CrumbExclusion for buildByToken URL

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

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25637 
 
 
 
  Add CrumbExclusion for buildByToken URL  
 
 
 
 
 
 
 
 
 

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] [build-token-root-plugin] (JENKINS-25637) Add CrumbExclusion for buildByToken URL

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

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

 
 
 
 
 
 
 
  Re: Add CrumbExclusion for buildByToken URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Yoann Dubreuil Path: src/test/java/org/jenkinsci/plugins/build_token_root/BuildRootActionTest.java http://jenkins-ci.org/commit/build-token-root-plugin/a1a621da89fff2a3f2174345bb0aaa1348781f4a Log: 

JENKINS-25637
 test that a crumb is not required 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34494 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 
 
Sam Van Oort confirmed after some investigation that it appears that multiple reports about Jenkins failing to start are all caused by plugins being disabled, and possibly users not properly deleting the *.disabled files. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34494 
 
 
 
  Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Assignee:
 
 Sam Van Oort 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34498) Jenkins 2.0 "out of the box" plugins failed to install

[igor_koyf...@agilent.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Igor Koyfman created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34498 
 
 
 
  Jenkins 2.0 "out of the box" plugins failed to install  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/28 7:03 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Igor Koyfman 
 
 
 
 
 
 
 
 
 
 
This is kind of ridiculous, but I think it's still a bug and I do need help. So I updated to Jenkins 1.656 to 2.0, and after the main war file got installed and restarted there was a nice button, I don't remember what it said, that in effect triggered installation of the basic package of plugins, or whatever you call it, the "out of the box" stuff. But due to high demand on the website most of them failed to install, and there seems to be no way to try again. How do I get that button back, or, short of that, just a direct link or script to get all those plugins at once? I have no idea what they were because I tried rolling back and reinstalling but the button is still gone. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 

[JIRA] [jira-issue-updater-plugin] (JENKINS-31755) Jenkins "Jira Issue Updater Plugin" pasrsing error when "Affects Version/s" is not empty

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Julia Mril commented on  JENKINS-31755 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins "Jira Issue Updater Plugin" pasrsing error when "Affects Version/s" is not empty  
 
 
 
 
 
 
 
 
 
 
Ian Sparkes, do you know who should review and merge your PR https://github.com/jenkinsci/jira-issue-updater-plugin/pull/13 ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34497) Frozen builds

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 thomas jacques created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34497 
 
 
 
  Frozen builds  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Magnus Sandberg 
 
 
 

Components:
 

 core, prioritysorter-plugin 
 
 
 

Created:
 

 2016/Apr/28 6:37 PM 
 
 
 

Environment:
 

 Jenkins : 1.642.1  --   OS : red hat 6  --   Java  --    - Vendor: Oracle Corporation    - Version: 1.7.0_55Active Plugins  --    * active-directory:1.41 *(update available)* 'Jenkins Active Directory plugin'    * ant:1.2 'Ant Plugin'    * antisamy-markup-formatter:1.3 'OWASP Markup Formatter Plugin'    * audit-trail:2.2 'Audit Trail'    * authorize-project:1.1.0 *(update available)* 'Authorize Project'    * build-monitor-plugin:1.7+build.172 *(update available)* 'Build Monitor View'    * build-pipeline-plugin:1.4.9 *(update available)* 'Build Pipeline Plugin'    * build-view-column:0.2 'Build View Column Plugin'    * categorized-view:1.8 'categorized-view'    * conditional-buildstep:1.3.3 'conditional-buildstep'    * configurationslicing:1.44 *(update available)* 'Configuration Slicing plugin'    * configure-job-column-plugin:1.0 'Configure Job Column Plugin'    * copy-to-slave:1.4.4 'Copy To Slave Plugin'    * copyartifact:1.37 *(update available)* 'Copy Artifact Plugin'    * credentials:1.24 *(update available)* 'Credentials Plugin'    * credentials-binding:1.6 *(update available)* 'Credentials Binding Plugin'    * cvs:2.12 'Jenkins CVS Plug-in'    * dashboard-view:2.9.6 *(update available)* 'Dashboard View'    * delivery-pipeline-plugin:0.9.7 *(update available)* 'Delivery Pipeline Plugin'    * dependencyanalyzer:0.7 'Jenkins Dependency Analyzer Plugin'    * discard-old-build:1.05 'Discard Old Build plugin'    * downstream-buildview:1.9 'Downstream build view'    * dynamicparameter:0.2.0 'Jenkins Dynamic Parameter Plug-in'    * envfile:1.2 'Jenkins Environment File Plugin'    * envinject:1.92.1 'Environment Injector Plugin'    * extended-choice-parameter:0.55 *(update available)* 'Extended Choice Parameter Plug-In'    * extensible-choice-parameter:1.3.2 'Extensible Choice Parameter plugin'    * external-monitor-job:1.4 'External Monitor Job Type Plugin'    * filesystem-list-parameter-plugin:0.0.3 'Jenkins Filesystem List Parameter Plug-in'    * git:2.4.0 *(update available)* 'Jenkins GIT plugin'    * git-client:1.19.0 *(update available)* 'Jenkins 

[JIRA] [git-plugin] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory

[jacob.kel...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Keller commented on  JENKINS-32479 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: multiple git repositories sometimes fail to checkout some of them into subdirectory  
 
 
 
 
 
 
 
 
 
 
Any chance you happen to have a smaller recreation we could use for testing? I'd like to try and sort out exactly what's happening here, as it recently happened again. I believe it may only occur when a fresh clone is initiated. 
What version of Git command line are you using, and what version of Git and Multi SCM are you using? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34496) maven-hpi-plugin injecting test for non hpi packaged projects

[tom.fenne...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY started work on  JENKINS-34496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Tom FENNELLY 
 
 
 

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] [core] (JENKINS-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to Sam Van Oort 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34494 
 
 
 
  Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Assignee:
 
 Sam Van Oort 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34496) maven-hpi-plugin injecting test for non hpi packaged projects

[tom.fenne...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY commented on  JENKINS-34496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: maven-hpi-plugin injecting test for non hpi packaged projects  
 
 
 
 
 
 
 
 
 
 
PR: https://github.com/jenkinsci/maven-hpi-plugin/pull/32 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34496) maven-hpi-plugin injecting test for non hpi packaged projects

[tom.fenne...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tom FENNELLY created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34496 
 
 
 
  maven-hpi-plugin injecting test for non hpi packaged projects  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Tom FENNELLY 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/28 4:58 PM 
 
 
 

Labels:
 

 maven-hpi maven 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Tom FENNELLY 
 
 
 
 
 
 
 
 
 
 
E.g. if building a jenkins-module packaged artifact, the InjectedTest will be generated but will fail the build. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 
  

[JIRA] [xunit-plugin] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed

[bernard.ladent...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernard Ladenthin edited a comment on  JENKINS-14117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The plugin hasn't been performed correctly: remote file operation failed  
 
 
 
 
 
 
 
 
 
 Same here , .First it looks from an  upgrade from  to The slave is a Windows 7 x64 Machine.{code:none}[xUnit] [INFO] - Starting to record.[xUnit] [INFO] - Processing JUnit[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'surefire-reports/TEST-*.xml' relative to 'J:\JenkinsSlave\workspace\S970 STester STest' for the testing framework 'JUnit'.[xUnit] [ERROR] - The plugin hasn't been performed correctly: remote file operation failed: J:\JenkinsSlave\workspace\S970 STester STest at hudson.remoting.Channel@ea9617:ST-SikuliTester: java.io.IOException: java.io.IOException: Failed to read J:\JenkinsSlave\workspace\S970 STester STest\generatedJUnitFiles\JUnit\TEST--346453655.xmlBuild step 'Process xUnit test result report' changed build result to FAILURE{code} A deeper analysis:After i've deleted the local repository, now the Test-*.xml files contain in the second line a comma in the xml.The 2,052.575 produces the error. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-24207) Use Perforce Jobs attached to changelist to track JIRA issues

[jacek.tom...@hexagongeospatial.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacek Tomaka assigned an issue to Jacek Tomaka 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-24207 
 
 
 
  Use Perforce Jobs attached to changelist to track JIRA issues  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jacek Tomaka 
 
 
 

Assignee:
 
 Jacek Tomaka 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34494 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 
 

if plugin installations are not run, will detached plugins will get installed
 
That code exists, executed during startup. It compares old Jenkins version with new Jenkins version, and installs all plugins in the "bundled" version if they've been detached between these versions. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34495 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin fails to resolve image ID  
 
 
 
 
 
 
 
 
 
 
That means you ware right. The fix should be 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] [core] (JENKINS-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Keith Zantow commented on  JENKINS-34494 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 
 
Similarly, if plugin installations are not run, will detached plugins will get installed? I just thought of this as I'm looking to detach some code into a plugin for another ticket... this would leave Jenkins in a similarly bad state. As part of this PR, I think we should ensure during an upgrade, at least: 
*) required dependencies are installed *) required dependencies are enabled 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jaap Coomans commented on  JENKINS-34495 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin fails to resolve image ID  
 
 
 
 
 
 
 
 
 
 
Thank you for the quick response Oliver Gondža. I tried to run the script for both ACTIVE and active and the result is as I expected based on my earlier findings: 
 

ACTIVE: Returns Result: []
 

active: Returns a list of all 6 available images
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34329) Should not be possible to update a domain to have a null name

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Armando Fernandez resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34329 
 
 
 
  Should not be possible to update a domain to have a null name  
 
 
 
 
 
 
 
 
 

Change By:
 
 Armando Fernandez 
 
 
 

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] [testng-plugin] (JENKINS-34404) testng-plugin: 502 Bad Gateway when using custom Home directory

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Jones closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34404 
 
 
 
  testng-plugin: 502 Bad Gateway when using custom Home directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mike Jones 
 
 
 

Status:
 
 Open Closed 
 
 
 

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] [testng-plugin] (JENKINS-34404) testng-plugin: 502 Bad Gateway when using custom Home directory

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mike Jones commented on  JENKINS-34404 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: testng-plugin: 502 Bad Gateway when using custom Home directory  
 
 
 
 
 
 
 
 
 
 
I wasn't the person that configured Jenkins on the server, changing the jenkinsURL in the jenkins.model.JenkinsLocationConfiguration.xml file (located in the JENKINS_HOME directory) fixed this issue. Sorry for reporting 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] [xunit-plugin] (JENKINS-22268) Boost C++ unit tests and the xUnit plugin - Not working

[jeanluc.bounth...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jean-Luc Bounthong commented on  JENKINS-22268 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Boost C++ unit tests and the xUnit plugin - Not working  
 
 
 
 
 
 
 
 
 
 
Hi, 
Got the same error after updating Boost to 1.59, is there any work in progress concerning this issue ? 
Best, 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža commented on  JENKINS-34495 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin fails to resolve image ID  
 
 
 
 
 
 
 
 
 
 
Thanks for reporting this. It is strange but my openstack does not eliminate the images because of case mismatch in status field. Can you run Jenkins.instance.clouds[0].openstack.@client.images().listAll(['status':'active']) (vs. ACTIVE) from JENKINS_URL/script to verify? 
You are right that there si a lot to catch up in case a mandatory field is left null. Plugin should at least report (if not abort the provisioning) in case some of the required fields is not configured (or resolved as in this case). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [remoting] (JENKINS-22722) Master doesn't show connected slave

[sta...@fit.vutbr.cz (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Starka commented on  JENKINS-22722 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Master doesn't show connected slave  
 
 
 
 
 
 
 
 
 
 
Same here. Master is running on some SoC Arm with Debian Wheezy and slave is on win 7 started as java headless from commandline. Jenkins version is 2.0 rc-1. I think this bug is quite serious and prevents me to actualy use many plugins since I need to stay on 1.559. or to look for another CI software. 
Here is slave's log from cmd: 

 

C:\jenkins2_slave>java -jar "C:\jenkins2_slave\slave.jar" -jnlpUrl http://local.pc:8082/computer/windows_slave/slave-agent.jnlp -secret ef9469
b438646d065d61d86577dc3ebfd7b0bc6ee2f8dc563661a8d209062002
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main createEngine
INFO: Setting up slave: windows_slave
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener 
INFO: Jenkins agent is running in headless mode.
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://local.pc:8082/]
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to local.pc:39916
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP3-connect
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Server didn't accept the handshake: Unknown protocol:Protocol:JNLP3-connec
t
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to local.pc:39916
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP2-connect
Dub 28, 2016 1:35:31 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Dub 28, 2016 2:20:19 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Terminated
Dub 28, 2016 2:20:29 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://local.pc:8082/]
Dub 28, 2016 2:20:29 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Dub 28, 2016 2:20:29 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to local.pc:39916
Dub 28, 2016 2:20:29 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP3-connect
Dub 28, 2016 2:20:30 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Server didn't accept the handshake: Unknown protocol:Protocol:JNLP3-connec
t
Dub 28, 2016 2:20:30 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to local.pc:39916
Dub 28, 2016 2:20:30 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP2-connect
Dub 28, 2016 2:20:30 ODP. hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Dub 28, 2016 2:20:55 ODP. hudson.util.ProcessTree get
WARNING: Failed to load winp. Reverting to the default
java.lang.UnsatisfiedLinkError: Native Library C:\Users\pc\.jenkins\cache\jars\4
A\winp.x64.22D9AB310A3FA2D96B6E03A836A47724.dll already loaded in another classl
oader
at java.lang.ClassLoader.loadLibrary0(Unknown Source)
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.load0(Unknown Source)
at java.lang.System.load(Unknown Source)
at org.jvnet.winp.Native.loadDll(Native.java:190)
at org.jvnet.winp.Native.load(Native.java:122)
at org.jvnet.winp.Native.(Native.java:56)
at org.jvnet.winp.WinProcess.enableDebugPrivilege(WinProcess.java:212)
at hudson.util.ProcessTree$Windows.(ProcessTree.java:494)
at hudson.util.ProcessTree.get(ProcessTree.java:345)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:965)
at 

[JIRA] [credentials-plugin] (JENKINS-34329) Should not be possible to update a domain to have a null name

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

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

 
 
 
 
 
 
 
  Re: Should not be possible to update a domain to have a null name  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Armando Fernandez Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsStoreAction.java src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/DomainWrapper/configure.jelly http://jenkins-ci.org/commit/credentials-plugin/3a743bc29cd5b42e79fef4d1fdbc193ee748e66a Log: JENKINS-34329 Stop allowing to update domains to have blank 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] [credentials-plugin] (JENKINS-34329) Should not be possible to update a domain to have a null name

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

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

 
 
 
 
 
 
 
  Re: Should not be possible to update a domain to have a null name  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Armando Fernandez Path: src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/DomainWrapper/configure.jelly src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/newDomain.jelly http://jenkins-ci.org/commit/credentials-plugin/1ac82bc1046ae410f42161e4fe862ed4c96b310a Log: JENKINS-34329 Use value and type comparator 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34329) Should not be possible to update a domain to have a null name

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

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

 
 
 
 
 
 
 
  Re: Should not be possible to update a domain to have a null name  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsStoreAction.java src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/DomainWrapper/configure.jelly src/main/resources/com/cloudbees/plugins/credentials/CredentialsStoreAction/newDomain.jelly http://jenkins-ci.org/commit/credentials-plugin/49a06e8c166a4e899dcdf5dece313f26701e176b Log: Merge pull request #47 from armfergom/JENKINS-34329 
JENKINS-34329 Stop allowing to update domains to have blank names 
Compare: https://github.com/jenkinsci/credentials-plugin/compare/7a916eecc0df...49a06e8c166a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34494 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 
 
https://twitter.com/alexsotob/status/725425301522661376 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34495 
 
 
 
  Plugin fails to resolve image ID  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oliver Gondža 
 
 
 
 
 
 
 
 
 
 I've set up and configured the OpenStack Cloud plugin with one template. When I try to launch a slave based on that template (via Manage nodes) all I get is: "Error. Boot failed".After studying the logs and the network traffic I found the cause. The plugin tries to resolve the image ID based on the Image name that I configured. (See {{jenkins.plugins.openstack.compute.internal.OpenStack.getImageIdFor(String name)} } ).This results is an API call to the images API:{{HTTP/1.1 GET v1/images?status=ACTIVE=My_Image}}The API however expects a lowercase status instead of uppercase (see also http://developer.openstack.org/api-ref-image-v1.html). So the response body is:{{\{"images": []}\}}.The result of this is that the plugin tries to provision an instance via the API without providing an imageRef. So there are essentially two issues:1. The plugin makes the wrong API call2. The plugin doesn't handle the situation where no images are returned correctly. This bug was introduced with commit 50dd47d798bcd79a99ebfb62e51cb2c2d05f. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [openstack-cloud-plugin] (JENKINS-34495) Plugin fails to resolve image ID

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jaap Coomans created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34495 
 
 
 
  Plugin fails to resolve image ID  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 openstack-cloud-plugin 
 
 
 

Created:
 

 2016/Apr/28 12:45 PM 
 
 
 

Environment:
 

 Jenkins v1.609.1  OpenStack Cloud plugin v2.3  OS: SLES 11 SP3 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Jaap Coomans 
 
 
 
 
 
 
 
 
 
 
I've set up and configured the OpenStack Cloud plugin with one template. When I try to launch a slave based on that template (via Manage nodes) all I get is: "Error. Boot failed". 
After studying the logs and the network traffic I found the cause. The plugin tries to resolve the image ID based on the Image name that I configured. (See {{jenkins.plugins.openstack.compute.internal.OpenStack.getImageIdFor(String name)}). 
This results is an API call to the images API: HTTP/1.1 GET v1/images?status=ACTIVE=My_Image The API however expects a lowercase status instead of uppercase (see also http://developer.openstack.org/api-ref-image-v1.html). So the response body is: {"images": []}. 
The result of this is that the plugin tries to provision an instance via the API without providing an imageRef.  
So there are essentially two issues: 1. The plugin makes the wrong API call 2. The plugin doesn't 

[JIRA] [core] (JENKINS-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-34494 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 
 
References: 
https://issues.jenkins-ci.org/browse/JENKINS-34434 https://groups.google.com/forum/#!msg/jenkinsci-users/4mAzgV_HvCk/XRk-uLdUNAAJ https://www.reddit.com/r/programming/comments/4gl6cd/jenkins_20_is_here/d2ip3cy https://www.reddit.com/r/programming/comments/4gl6cd/jenkins_20_is_here/d2jpm52 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34494) Enable disabled (transitive) dependencies when installing a new plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34494 
 
 
 
  Enable disabled (transitive) dependencies when installing a new plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Apr/28 12:29 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Daniel Beck 
 
 
 
 
 
 
 
 
 
 
When installing a new plugin, Jenkins automatically also installs dependencies that are not installed. 
Unfortunately, it's possible to disable plugins, whose effect to the Jenkins runtime is effectively the same as if the plugin was missing – except that there's currently no process to enable plugins that are disabled. 
Similar to DownloadJobs added for missing dependencies, there should be EnableJobs that enable disabled dependencies (or another approach, but this would nicely mirror the existing DownloadJob one). 
We received multiple reports from users affected by this when upgrading to 2.0 and installing the pipeline plugins, so this is critical. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 

[JIRA] [core] (JENKINS-34448) Slave's offlineCause is rewritten during a rare condition

[pjano...@redhat.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Janoušek resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Merged. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-34448 
 
 
 
  Slave's offlineCause is rewritten during a rare condition  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pavel Janoušek 
 
 
 

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] [core] (JENKINS-34448) Slave's offlineCause is rewritten during a rare condition

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

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

 
 
 
 
 
 
 
  Re: Slave's offlineCause is rewritten during a rare condition  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ing. Pavel Janousek Path: core/src/main/java/hudson/slaves/SlaveComputer.java http://jenkins-ci.org/commit/jenkins/822cec62dba4f31aac03afed26b575091f774342 Log: JENKINS-34448 Fixed offlineCause race condition 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34448) Slave's offlineCause is rewritten during a rare condition

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

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

 
 
 
 
 
 
 
  Re: Slave's offlineCause is rewritten during a rare condition  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/slaves/SlaveComputer.java http://jenkins-ci.org/commit/jenkins/b8f983bceb598c10263580ffc331e6ba52d0c853 Log: Merge pull request #2290 from pjanouse/JENKINS-34448 
JENKINS-34448 Fixed offlineCause race condition 
Compare: https://github.com/jenkinsci/jenkins/compare/67597a7c91ea...b8f983bceb59 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [delivery-pipeline-plugin] (JENKINS-34493) Delivery pipeline view shows even when the user doesn't have permissions on underlying projects

[elindo...@iprofs.nl (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ernst Lindoorn created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34493 
 
 
 
  Delivery pipeline view shows even when the user doesn't have permissions on underlying projects  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Patrik Boström 
 
 
 

Components:
 

 delivery-pipeline-plugin 
 
 
 

Created:
 

 2016/Apr/28 12:13 PM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Ernst Lindoorn 
 
 
 
 
 
 
 
 
 
 
When a restricted user is configured to only have permissions on a select number of projects he can still see delivery pipeline views (although empty) for other projects. 
Broken in Jenkins 1.656, delivery-pipeline-plugin 0.9.9 This behavior broke somewhere after 0.9.5 of the delivery-pipeline-plugin. 
To reproduce: 
 

In global security configure project-based matrix authorization 
 

Remove all permissions on the anonymous role
 

Add a test user and give him overall -> read permission and no other permissions
 
 
 

Configure a delivery pipeline with one or two projects 

[JIRA] [xunit-plugin] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed

[bernard.ladent...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernard Ladenthin edited a comment on  JENKINS-14117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The plugin hasn't been performed correctly: remote file operation failed  
 
 
 
 
 
 
 
 
 
 Same here, upgrade from  to  The slave is a Windows 7 x64 Machine.   {code:none}[xUnit] [INFO] - Starting to record.[xUnit] [INFO] - Processing JUnit[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'surefire-reports/TEST-*.xml' relative to 'J:\JenkinsSlave\workspace\S970 STester STest' for the testing framework 'JUnit'.[xUnit] [ERROR] - The plugin hasn't been performed correctly: remote file operation failed: J:\JenkinsSlave\workspace\S970 STester STest at hudson.remoting.Channel@ea9617:ST-SikuliTester: java.io.IOException: java.io.IOException: Failed to read J:\JenkinsSlave\workspace\S970 STester STest\generatedJUnitFiles\JUnit\TEST--346453655.xmlBuild step 'Process xUnit test result report' changed build result to FAILURE{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philip Cheong commented on  JENKINS-33185 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Visualize parallel steps within a Pipeline Stage  
 
 
 
 
 
 
 
 
 
 
I would be happy with something more simple such as this: 
https://wiki.jenkins-ci.org/download/attachments/69764097/screenshot2.png?version=1=1400172472000 
...where the box indicating the stage simply displays the number of parallel steps that it will run. Bonus points for each step having it's own progress bar! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xunit-plugin] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed

[bernard.ladent...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernard Ladenthin edited a comment on  JENKINS-14117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The plugin hasn't been performed correctly: remote file operation failed  
 
 
 
 
 
 
 
 
 
 Same here, upgrade from  to {code: bash none }[xUnit] [INFO] - Starting to record.[xUnit] [INFO] - Processing JUnit[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'surefire-reports/TEST-*.xml' relative to 'J:\JenkinsSlave\workspace\S970 STester STest' for the testing framework 'JUnit'.[xUnit] [ERROR] - The plugin hasn't been performed correctly: remote file operation failed: J:\JenkinsSlave\workspace\S970 STester STest at hudson.remoting.Channel@ea9617:ST-SikuliTester: java.io.IOException: java.io.IOException: Failed to read J:\JenkinsSlave\workspace\S970 STester STest\generatedJUnitFiles\JUnit\TEST--346453655.xmlBuild step 'Process xUnit test result report' changed build result to FAILURE{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xunit-plugin] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed

[bernard.ladent...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernard Ladenthin edited a comment on  JENKINS-14117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The plugin hasn't been performed correctly: remote file operation failed  
 
 
 
 
 
 
 
 
 
 Same here, upgrade from  to  {code:bash}[xUnit] [INFO] - Starting to record.[xUnit] [INFO] - Processing JUnit[xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'surefire-reports/TEST-*.xml' relative to 'J:\JenkinsSlave\workspace\S970 STester STest' for the testing framework 'JUnit'.[xUnit] [ERROR] - The plugin hasn't been performed correctly: remote file operation failed: J:\JenkinsSlave\workspace\S970 STester STest at hudson.remoting.Channel@ea9617:ST-SikuliTester: java.io.IOException: java.io.IOException: Failed to read J:\JenkinsSlave\workspace\S970 STester STest\generatedJUnitFiles\JUnit\TEST--346453655.xmlBuild step 'Process xUnit test result report' changed build result to FAILURE{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

[rea...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rens hoskens edited a comment on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 Have the same issue on Windows Server 2008 R2. Hope it will get fixed soon (or a plain maven command would be usefull as well){code: groovy none }node {mvn 'clean package -DskipTests=true'}def mvn(args) {bat "${tool 'Maven 3.3.9'}/bin/mvn ${args}"}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

[rea...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rens hoskens edited a comment on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 Have the same issue on Windows Server 2008 R2. Hope it will get fixed soon (or a plain maven command would be usefull as well) {code:groovy}node {mvn 'clean package -DskipTests=true'}def mvn(args) {bat "${tool 'Maven 3.3.9'}/bin/mvn ${args}"}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xunit-plugin] (JENKINS-14117) The plugin hasn't been performed correctly: remote file operation failed

[bernard.ladent...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Bernard Ladenthin commented on  JENKINS-14117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The plugin hasn't been performed correctly: remote file operation failed  
 
 
 
 
 
 
 
 
 
 
Same here, upgrade from  to  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

[rea...@hotmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rens hoskens commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
Have the same issue on Windows Server 2008 R2. Hope it will get fixed soon (or a plain maven command would be usefull as well) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [pipeline-view-plugin] (JENKINS-34492) Jenkins 2.0 pipeline view, stage logs, closing steps

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Gabor V created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34492 
 
 
 
  Jenkins 2.0 pipeline view, stage logs, closing steps  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Sergei Egorov 
 
 
 

Components:
 

 pipeline-view-plugin 
 
 
 

Created:
 

 2016/Apr/28 11:38 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Gabor V 
 
 
 
 
 
 
 
 
 
 
If you open stage logs in pipeline view, you can click on the steps separately to open the logs, but you can not close these step logs by clicking on the small arrow. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 

[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz stopped work on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Antonio Muñiz 
 
 
 

Status:
 
 In Progress 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] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.

[ghebr...@gmx.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mengesteab Ghebreyesus commented on  JENKINS-25070 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion fails to update externals once after external is changed.  
 
 
 
 
 
 
 
 
 
 
We are also experiencing similar problem in many of our Projects during checking out from particular svn Project.. However, we get this error: 1. If we restart Jenkins and  2. In one of our Project from time to time in addition to restart Jenkins. 
OS : windows 7 Jenkins Version : 1656 Subversion Plugin 2.7 
Thank you all 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34224) Package not found

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ioannis Moutsatsos commented on  JENKINS-34224 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Package not found   
 
 
 
 
 
 
 
 
 
 
Do you have the scriptler plugin installed? It is required for active-choices. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30978) URLConnection.content.text hangs

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30978 
 
 
 
  URLConnection.content.text hangs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Summary:
 
 Groovy code throws exception only in plugin URLConnection.content.text hangs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30978) Groovy code throws exception only in plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30978 
 
 
 
  Groovy code throws exception only in plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 
 
 
 
 
 
 
 I have a script I can run via terminal, and via the envinject plugin ---  {code} import javax.net.ssl.HostnameVerifierimport javax.net.ssl.HttpsURLConnectionimport javax.net.ssl.SSLContextimport javax.net.ssl.TrustManagerimport javax.net.ssl.X509TrustManagerdef nullTrustManager = [checkClientTrusted: { chain, authType ->  },checkServerTrusted: { chain, authType ->  },getAcceptedIssuers: { null }]def nullHostnameVerifier = [verify: { hostname, session -> true }]SSLContext sc = SSLContext.getInstance("SSL")sc.init(null, [nullTrustManager as X509TrustManager] as TrustManager[], null)HttpsURLConnection.setDefaultSSLSocketFactory(sc.getSocketFactory())HttpsURLConnection.setDefaultHostnameVerifier(nullHostnameVerifier as HostnameVerifier)URL url = new URL('');URLConnection conn = url.openConnection();String basicAuth = "Basic " +  ;conn.setRequestProperty ("Authorization", basicAuth);svnPageContents = conn.content.textregexGroup = (svnPageContents =~ /svn - Revision (\d+):/)printf ("found: ${regexGroup[1][1]}") --- {code}   This just connects to svn to get the latest rev number, on a svn server with a self signed cert. On the console and in envinject this works fine. In the workflow plugin groovy script it exceptions out {code} java.lang.NullPointerException: Cannot get property 'text' on null object {code}   So my openConnection is returning null. I don't know why, but it's easy to reproduce 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [workflow-plugin] (JENKINS-33791) sh DSL is missing from the workflow plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Somehow you neglected to install the Pipeline: Durable Task Step plugin. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33791 
 
 
 
  sh DSL is missing from the workflow plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open 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] [workflow-plugin] (JENKINS-32766) groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32766 
 
 
 
  groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Summary:
 
 'Official' Groovy XML authoring doesn't work groovy.xml.MarkupBuilder fails  in  pipeline:  Pipeline with  NoSuchMethodError 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33349) Error after installing Pipeline/Workflow plugin

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Generally a user error of some kind, though Jenkins currently makes it hard to diagnose. (Fixes in progress.) 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33349 
 
 
 
  Error after installing Pipeline/Workflow plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

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] [bitbucket-pullrequest-builder-plugin] (JENKINS-31749) Bitbucket pullrequest builder plugin not compatible with Workflow

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-31749 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket pullrequest builder plugin not compatible with Workflow  
 
 
 
 
 
 
 
 
 
 
For most purposes you should instead use cloudbees-bitbucket-branch-source. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31687) Which node Groovy code actually executes on is not documented clearly

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Patrick O'Hannigan 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31687 
 
 
 
  Which node Groovy code actually executes on is not documented clearly  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Jesse Glick Patrick O'Hannigan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34147) localhost:8080/workflow-cps-snippetizer/dslReference is a fugly URL

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34147 
 
 
 
  localhost:8080/workflow-cps-snippetizer/dslReference is a fugly URL  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Duplicate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [metrics-plugin] (JENKINS-34491) Fix PCT against 2.0

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Rodriguez started work on  JENKINS-34491 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Andres Rodriguez 
 
 
 

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] [metrics-plugin] (JENKINS-34491) Fix PCT against 2.0

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Rodriguez created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34491 
 
 
 
  Fix PCT against 2.0  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Andres Rodriguez 
 
 
 

Components:
 

 metrics-plugin 
 
 
 

Created:
 

 2016/Apr/28 10:23 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andres Rodriguez 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christophe Carpentier commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
That would explain the iconsistent results during my tests. Weird. Anyway, I've encountered this both on failed and successful jobs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [delivery-pipeline-plugin] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin

[tommy.ty...@diabol.se (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tommy Tynjä assigned an issue to Tommy Tynjä 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34040 
 
 
 
  Add support for Pipeline plugin in the Delivery Pipeline plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tommy Tynjä 
 
 
 

Assignee:
 
 Patrik Boström Tommy Tynjä 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

[luebbe.opensou...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lübbe Onken edited a comment on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 Looks like I was too optimistic. The solution always worked with short running batch jobs, like dir, but it didn't with long running jobs, like a NAnt build.Is it possible that there is a race condition? Some state is checked very quickly after a task is started  and a . A  simple "dir" is quick enough to deliver the result in time and a slower task isn't? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

[luebbe.opensou...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lübbe Onken commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
Looks like I was too optimistic. The solution always worked with short running batch jobs, like dir, but it didn't with long running jobs, like a NAnt build. Is it possible that there is a race condition? Some state is checked very quickly after a task is started and a simple "dir" is quick enough to deliver the result in time and a slower task isn't? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-branch-source-plugin] (JENKINS-34259) Some links in multibranch projects are broken

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto edited a comment on  JENKINS-34259 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Some links in multibranch projects are broken  
 
 
 
 
 
 
 
 
 
 [~jglick] Do not work (when you reach the *Welcome* view, for example,  none  and there are not  branch sources  defined )# People link# Edit View link# Build History link 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31515) "/crumbIssuer" READ permissions

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Cannot Reproduce 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
No response to comment asking for additional information in several months. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31515 
 
 
 
  "/crumbIssuer" READ permissions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

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] [core] (JENKINS-34490) Jenkins credential change should require reauthentication

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck moved an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34490 
 
 
 
  Jenkins credential change should require reauthentication  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Project:
 
 Security Issues Jenkins 
 
 
 

Key:
 
 SECURITY JENKINS - 242 34490 
 
 
 

Workflow:
 
 Security v1.2 JNJira 
 
 
 

Status:
 
 Untriaged Open 
 
 
 

Component/s:
 
 core 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [github-branch-source-plugin] (JENKINS-34259) Some links in multibranch projects are broken

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34259 
 
 
 
  Some links in multibranch projects are broken  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Summary:
 
 "People" link Some links  in multibranch projects  is a bad link  are broken 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs

[luebbe.opensou...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lübbe Onken commented on  JENKINS-34150 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pipeline Batch hangs  
 
 
 
 
 
 
 
 
 
 
This hanging batch bug has bitten me heavily too. Failing batch jobs always terminated, successful jobs never did. A working solution for me is to explicitely return an exit code from any batch call. I'm on Windows 7 Professional. 
So: {{ echo 'Successful step' bat '''dir exit /B %ERRORLEVEL%''' 
 echo 'Failing step' bat '''find /c "_no.file" "_no.file" exit /B %ERRORLEVEL%''' 
 echo 'Never execute step' bat '''dir" exit /B %ERRORLEVEL%''' }} 
successfully terminates step one and returns from the batch execution, the second step fails the build and the third step never gets executed. 
Can somebody please confirm that this solution works for them too? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [golang-plugin] (JENKINS-27499) Global config page is broken when loaded before the tool installer data has been fetched

[raitis.dembovs...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raitis Dembovskis commented on  JENKINS-27499 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Global config page is broken when loaded before the tool installer data has been fetched  
 
 
 
 
 
 
 
 
 
 
Same with Global Tool Configuration screen in Jenkins 2.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] [core] (JENKINS-33820) Consistent naming of 'Create Item' action

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

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33820 
 
 
 
  Consistent naming of 'Create Item' action  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34489) Pipeline 'bat' does not terminate immediately

[nick.sonnev...@smartward.com.au (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Sonneveld created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34489 
 
 
 
  Pipeline 'bat' does not terminate immediately  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Attachments:
 

 jenkins-capture-error-error.log, jenkins-capture-error-failed-to-terminate-at-all.log, jenkins-capture-error-succes.log, jenkins-capture-error.groovy 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Apr/28 7:49 AM 
 
 
 

Environment:
 

 Jenkins 2.0, Windows 2012 R2 
 
 
 

Labels:
 

 workflow pipeline 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Nick Sonneveld 
 
 
 
 
 
 
 
 
 
 
When a pipeline job is terminated while executing a batch script, it will sometimes continue running the batch file after terminating the batch file's child process. This means you cannot reliably check if the process was terminated by Jenkins or if 

[JIRA] [workflow-plugin] (JENKINS-34376) Cannot easily/safely catch exceptions without disrupting job abortion

[nick.sonnev...@smartward.com.au (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Sonneveld updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34376 
 
 
 
  Cannot easily/safely catch exceptions without disrupting job abortion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Sonneveld 
 
 
 

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] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException

[luis.custo...@gmail.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Luis Custodio commented on  JENKINS-27547 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException  
 
 
 
 
 
 
 
 
 
 
Hi Mark Fink, please check just after the plugin info table: "This plugin is up for adoption. No active maintainer - Looking for new maintainer" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [jira-plugin] (JENKINS-34457) Jira REST SocketTimeoutException

[radek.anton...@quiddia.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Radek Antoniuk commented on  JENKINS-34457 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jira REST SocketTimeoutException  
 
 
 
 
 
 
 
 
 
 
So this might be JENKINS-25829...  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [performance-plugin] (JENKINS-27547) Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException

[m...@mark-fink.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Fink commented on  JENKINS-27547 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Performance Trend Per Test Case For Jmeter Give Error javax.servlet.ServletException  
 
 
 
 
 
 
 
 
 
 
Luis Custodio I do not comprehend your last comment. The ticket is assigned to Manuel Carrasco (Manuel Carrasco), who according to the plugin page is the active maintainer. I believe he currently has 60+ open tickets so I think there is something wrong with how tickets are assigned. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [performance-plugin] (JENKINS-27671) java.lang.Error: Unresolved compilation problem: Messages cannot be resolved

[m...@mark-fink.de (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Fink commented on  JENKINS-27671 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved  
 
 
 
 
 
 
 
 
 
 
I can confirm the exact same issue with Jenkins ver. 1.656. This is already an old issue so any plans if / when this will be 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.