[JIRA] [core] (JENKINS-27939) DefaultJnlpSlaveReceiver should return true when rejecting a takeover.

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-27939 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DefaultJnlpSlaveReceiver should return true when rejecting a takeover.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/slaves/DefaultJnlpSlaveReceiver.java core/src/test/java/jenkins/slaves/DefaultJnlpSlaveReceiverTest.java http://jenkins-ci.org/commit/jenkins/9a3e5518baa044ce2fedf25af73490d58b0d3976 Log: Merge pull request #1649 from deadmoose/follow_the_api_rules 
[FIXED JENKINS-27939] - DefaultJnlpSlaveReceiver should return true when rejecting a takeover. 
Compare: https://github.com/jenkinsci/jenkins/compare/056fe9a30901...9a3e5518baa0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27939) DefaultJnlpSlaveReceiver should return true when rejecting a takeover.

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27939 
 
 
 
  DefaultJnlpSlaveReceiver should return true when rejecting a takeover.  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [core] (JENKINS-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dawidsibin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dawid Sibiński commented on  JENKINS-27310 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 
 
Could you specify in details how you fixed this problem? I have the same issue, getting error: Invalid tool ID 1.0.1 [Gradle] - [ERROR] Can't retrieve the Gradle executable. Build step 'Invoke Gradle script' marked build as failure Archiving artifacts Finished: FAILURE 
and I also do not have a file hudson.plugins.gradle.GradleInstaller.json i JENKINS_HOME/updates ... But how could I get these file and where to get it from ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dawidsibin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dawid Sibiński edited a comment on  JENKINS-27310 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 
 Could you specify in details how you fixed this problem? I have the same issue, getting error:Invalid tool ID 1.0.1[Gradle] - [ERROR] Can't retrieve the Gradle executable.Build step 'Invoke Gradle script' marked build as failureArchiving artifactsFinished: FAILUREand I also do not have a file hudson.plugins.gradle.GradleInstaller.json i JENKINS_HOME/updates ... But how could I get  these  this  file and where to get it from ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dawidsibin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dawid Sibiński reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I'm reopening the issue as I thing the resolution is not properly provided in that ticket's despription.  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27310 
 
 
 
  gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dawid Sibiński 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dawidsibin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dawid Sibiński edited a comment on  JENKINS-27310 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 
 I'm reopening the issue as I thing the resolution is not properly provided in that ticket's despription.    I would only like to add that my envoronment is Ubuntu server. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dan...@beckweb.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-27310 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 
 
If you just installed Gradle Plugin, you need to 'Check Now' in Manage Jenkins » Manage Plugins » Advanced. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-20879 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SSH Credentials (private key with passphrase) do not work  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/0e67e3d4003124d98db540b86f27d0c4d1347493 Log: Merge pull request #168 from thomasgl-orange/JENKINS-20879 
JENKINS-20879 - make sure $SSH_ASKPASS is not ignored on Unix. 
Does not fix the passphrase protected private keys on Windows,  just on Unix machines. 
Compare: https://github.com/jenkinsci/git-client-plugin/compare/2f0cd5d3ce52...0e67e3d40031 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-20879 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SSH Credentials (private key with passphrase) do not work  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Thomas de Grenier de Latour Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/21bc7357e20649bf3c96ed1cd12471ea330abe5d Log: JENKINS-20879 - make sure $SSH_ASKPASS is not ignored 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work

2015-05-16 Thread mark.earl.wa...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-20879 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SSH Credentials (private key with passphrase) do not work  
 
 
 
 
 
 
 
 
 
 
Thanks Thomas de Grenier de Latour for the pull request. It should be included in the next release of the git client plugin (likely either 1.17.2 or 1.18.0). 
Please note that the pull request only helped in my testing on Linux machines, not on Windows. The Windows machines continue to behave incorrectly with command line git when using a passphrase protected private key. Refer to the comments in the pull request for more details on the cases tested and the test results. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28425) UI: Build history overflows

2015-05-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev started work on  JENKINS-28425 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

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-28425) UI: Build history overflows

2015-05-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev assigned an issue to Thomas Suckow 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28425 
 
 
 
  UI: Build history overflows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Assignee:
 
 Thomas Suckow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dawidsibin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dawid Sibiński commented on  JENKINS-27310 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 
 
I did that and then it told me it cannot find android-22 SDK tools. So I updated the Android SDK and now my build's error is: [Android_builds] $ /var/lib/jenkins/tools/hudson.plugins.gradle.GradleInstallation/2.2.1/bin/gradle clean build Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure Archiving artifacts Finished: FAILURE 
and it crashed my server at all. I'm following https://www.digitalocean.com/community/tutorials/how-to-build-android-apps-with-jenkins. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-27939) DefaultJnlpSlaveReceiver should return true when rejecting a takeover.

2015-05-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-27939 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DefaultJnlpSlaveReceiver should return true when rejecting a takeover.  
 
 
 
 
 
 
 
 
 
 
Marked as lts-candidate (not for the incoming LTS) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27939) DefaultJnlpSlaveReceiver should return true when rejecting a takeover.

2015-05-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27939 
 
 
 
  DefaultJnlpSlaveReceiver should return true when rejecting a takeover.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oleg Nenashev 
 
 
 

Labels:
 
 lts-candidate 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28437) /lib/layout/task also initiates GET request when post=true

2015-05-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28437 
 
 
 
  /lib/layout/task also initiates GET request when post=true  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 16/May/15 12:17 PM 
 
 
 

Labels:
 

 layout jelly 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
Simple  but then proceeds to href as normal link do. If the URL accepts GET then request is sent twice (POST then GET). It if does not, after POSTing on background user get 'POST is required' error. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
  

[JIRA] [core] (JENKINS-17290) Category titles in Available Plugins list appear wrong in reverse sort order

2015-05-16 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-17290 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Category titles in Available Plugins list appear wrong in reverse sort order  
 
 
 
 
 
 
 
 
 
 
Resubmitted as https://github.com/jenkinsci/jenkins/pull/1708 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27748) Jenkins loses history (task page and overview)

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-27748 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins loses history (task page and overview)  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/model/RunMap.java http://jenkins-ci.org/commit/jenkins/c1e3a64eea8889b5483343f9bc717bb803fd8357 Log: Merge pull request #1693 from fbelzunc/runmap-retrieve 
JENKINS-27748 Improve exception management in RunMap#retrieve 
Compare: https://github.com/jenkinsci/jenkins/compare/5adf5fa9050c...c1e3a64eea88 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-blocker-plugin] (JENKINS-22059) Use parameters in build-blocker Regulary Expression

2015-05-16 Thread imakow...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ireneusz Makowski commented on  JENKINS-22059 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Use parameters in build-blocker Regulary _expression_  
 
 
 
 
 
 
 
 
 
 
Can you please add this feature? Or support relation in case of blocking example: 
RootFolder -SubFolder1 -JobA -SubFolder2 -JobB 
It will be great if I can specify in JobB: ../SubFolder1/JobA 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25298) Able to rerun jobs from view

2015-05-16 Thread pat...@diabol.se (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25298 
 
 
 
  Able to rerun jobs from view  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-22947) If first job in pipeline is queued, no new pipeline instance is shown in view

2015-05-16 Thread pat...@diabol.se (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22947 
 
 
 
  If first job in pipeline is queued, no new pipeline instance is shown in view  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-27584) NullPointerException in ManualStep.getManualStepLatest

2015-05-16 Thread pat...@diabol.se (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.0 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27584 
 
 
 
  NullPointerException in ManualStep.getManualStepLatest  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-27667) Unable to view more than 10 pipelines

2015-05-16 Thread pat...@diabol.se (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.0 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27667 
 
 
 
  Unable to view more than 10 pipelines  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [delivery-pipeline-plugin] (JENKINS-22921) Build Now menu to trigger the pipeline manually

2015-05-16 Thread pat...@diabol.se (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released in 0.9.0 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-22921 
 
 
 
  Build Now menu to trigger the pipeline manually  
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrik Boström 
 
 
 

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] [core] (JENKINS-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dawidsibin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dawid Sibiński commented on  JENKINS-27310 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 
 
Ok, I reinstalled Android SDK and did like you said and it is fine now . Thank you! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [core] (JENKINS-27310) gradle automatic install Invalid tool ID

2015-05-16 Thread dawidsibin...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dawid Sibiński resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27310 
 
 
 
  gradle automatic install Invalid tool ID  
 
 
 
 
 
 
 
 
 

Change By:
 
 Dawid Sibiński 
 
 
 

Status:
 
 Reopened 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] [delivery-pipeline-plugin] (JENKINS-28347) Doesn't detect promotion "Trigger/call builds on other projects"

2015-05-16 Thread pat...@diabol.se (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrik Boström commented on  JENKINS-28347 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Doesn't detect promotion "Trigger/call builds on other projects"  
 
 
 
 
 
 
 
 
 
 
Create PR with a fix for it. Can you please test it? https://github.com/Diabol/delivery-pipeline-plugin/pull/110 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28438) OS X installation - force use of Java 7 or 8

2015-05-16 Thread pl...@goodeast.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Suh created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28438 
 
 
 
  OS X installation - force use of Java 7 or 8  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 16/May/15 8:37 PM 
 
 
 

Environment:
 

 OS X 10.8, 10.9, 10.10, any recent Jenkins version 
 
 
 

Labels:
 

 mac 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Paul Suh 
 
 
 
 
 
 
 
 
 
 
As per request attached to comment on changes needed to OS X installer.  
When running from the command line (as opposed to instantiating a JVM programmatically), Java 7 or Java 8 on OS X has a dependency on the very old Java 6 installation for OS X, available at http://support.apple.com/kb/DL1572. When the user installs the Java 6 package from Apple, /usr/bin/java points to the Java 6 installation. Oracle Java installs into /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home. To run a Java 8 JVM from the command line, the user needs to give the full path to the "java" executable – /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java. 

[JIRA] [android-emulator-plugin] (JENKINS-28378) Option to start emulators only if there are no devices connected already.

2015-05-16 Thread spinkel...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Søren Ranneries commented on  JENKINS-28378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Option to start emulators only if there are no devices connected already.  
 
 
 
 
 
 
 
 
 
 
Pull request: https://github.com/jenkinsci/android-emulator-plugin/pull/50 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [authorize-project-plugin] (JENKINS-26670) Support WorkflowJob for Authorize Project

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26670 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support WorkflowJob for Authorize Project  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: pom.xml src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty.java src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/AnonymousAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategy.java src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/testutil/AuthorizeProjectJenkinsRule.java http://jenkins-ci.org/commit/authorize-project-plugin/9365f685c1fb5e89594a18fac8de9a92b19a99dc Log: Merge pull request #8 from ikedam/feature/

JENKINS-26670
_SupportWorkflowJob 
[FIXED JENKINS-26670] Support Job including WorkflowJob 
Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/440d75a4ea5e...9365f685c1fb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [authorize-project-plugin] (JENKINS-26670) Support WorkflowJob for Authorize Project

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26670 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support WorkflowJob for Authorize Project  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: pom.xml src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java src/test/java/org/jenkinsci/plugins/authorizeproject/testutil/AuthorizeProjectJenkinsRule.java http://jenkins-ci.org/commit/authorize-project-plugin/135849e85bb050329b079136380c3d1e005b0130 Log: 

JENKINS-26670
 Added a test for WorkflowJob as a test for Job. It's commented out as workflow requires Jenkins 1.580.1. Comment in those codes in pom.xml and ProjectQueueItemAuthenticatorTest to run that test locally. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [authorize-project-plugin] (JENKINS-26670) Support WorkflowJob for Authorize Project

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26670 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support WorkflowJob for Authorize Project  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectProperty.java src/main/java/org/jenkinsci/plugins/authorizeproject/AuthorizeProjectStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticator.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/AnonymousAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/TriggeringUsersAuthorizationStrategy.java src/test/java/org/jenkinsci/plugins/authorizeproject/ProjectQueueItemAuthenticatorTest.java http://jenkins-ci.org/commit/authorize-project-plugin/63c5d2a2ee91cee3ffb587958bcbdeb51fbc7f56 Log: [FIXED JENKINS-26670] Support Job including WorkflowJob 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [authorize-project-plugin] (JENKINS-26670) Support WorkflowJob for Authorize Project

2015-05-16 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26670 
 
 
 
  Support WorkflowJob for Authorize Project  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

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] [jobcopy-builder-plugin] (JENKINS-28439) New operation: disable job

2015-05-16 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28439 
 
 
 
  New operation: disable job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 
 ikedam 
 
 
 

Components:
 

 jobcopy-builder-plugin 
 
 
 

Created:
 

 17/May/15 12:11 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 ikedam 
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/jobcopy-builder-plugin/pull/3 
 
We are using a working job as a template. This way when we create a new project in Jenkins and it will have all updates to that working job. I have added a disable drop down the new jobs will not get started when they are created (i.e. started using svn pull).
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

  

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

2015-05-16 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-28298 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Can bypass the security check of authorize-project with CLI and REST of Jenkins 1.580.1  
 
 
 
 
 
 
 
 
 
 
Throwing RuntimeException or Error don't help. Any exceptions are wrapped with InvocationTargetException by Java reflection and wrapped with XStreamException by xstream. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28440) Allow to reject specific configurations via REST and CLI

2015-05-16 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28440 
 
 
 
  Allow to reject specific configurations via REST and CLI  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 ikedam 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 17/May/15 12:55 AM 
 
 
 

Environment:
 

 Jenkins >= 1.545 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 ikedam 
 
 
 
 
 
 
 
 
 
 
Plugins could reject configurations via REST and CLI in Jenkins < 1.545 by throwing exceptions in readResolve. Authorize Project plugin performs authentications with this behavior. 
Jenkins 1.545 suppresses exceptions in readResolve in 

JENKINS-21024
 (also backported to Jenkins 1.532.3). This results that throwing exceptions in readResolve prevents reading configurations into memories via REST / CLI but cannot prevents saving them to the disk. Authorize-project doesn't perform authentications when Jenkins reads configurations from the disk and allows bypassing authentications. 
Jenkins 1.551 introduced XStream2#addCriticalField in SECURITY-107 (also backported to Jenkins 1.532.2) which triggers critical errors by exceptions in readResolve but only applied to system configurations, not applied project configurations via REST / CLI. (Exceptions are suppressed in CopyOnWriteList) 
  

[JIRA] [core] (JENKINS-28440) Allow to reject specific configurations via REST and CLI

2015-05-16 Thread de...@ikedam.jp (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 ikedam commented on  JENKINS-28440 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow to reject specific configurations via REST and CLI  
 
 
 
 
 
 
 
 
 
 
This might mean Authorize Project plugin should provide another way for authentication. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.