[JIRA] [publish-over-ssh-plugin] (JENKINS-35231) Prime size must be multiple of 64 error after upgrading Publish-over-SSH from 1.13 to 1.14

2016-06-05 Thread dalfga...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandre Klein edited a comment on  JENKINS-35231 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prime size must be multiple of 64 error after upgrading Publish-over-SSH from 1.13 to 1.14  
 
 
 
 
 
 
 
 
 
 Not sure if it is related, but which version of Jenkins are you using? What is I had  the  version of Java on Jenkins and on the machine you tried  same problem with 1.14. Downgrading this plugin  to  send files to?  1.13 solved this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [publish-over-ssh-plugin] (JENKINS-35231) Prime size must be multiple of 64 error after upgrading Publish-over-SSH from 1.13 to 1.14

2016-06-05 Thread dalfga...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandre Klein commented on  JENKINS-35231 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Prime size must be multiple of 64 error after upgrading Publish-over-SSH from 1.13 to 1.14  
 
 
 
 
 
 
 
 
 
 
Not sure if it is related, but which version of Jenkins are you using? What is the version of Java on Jenkins and on the machine you tried to send files 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] [git-client-plugin] (JENKINS-30045) Git client plugin does not work with new Git for Windows 2.5.0

2016-06-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-30045 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Git client plugin does not work with new Git for Windows 2.5.0  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/2a2c6d339dcda8556b267f8a3584a5dd762be387 Log: Add mingw64 dir to ssh location guesser - windows git 2.8.0 
Implement ssh executable test in CliGitAPIImplTest, not applicable to JGit. 
May help 

JENKINS-30045
, 

JENKINS-28943
, 

JENKINS-25297
, & 

JENKINS-21806
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25297) ssh executable not found. The git plugin only supports official git client

2016-06-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25297 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ssh executable not found. The git plugin only supports official git client  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/2a2c6d339dcda8556b267f8a3584a5dd762be387 Log: Add mingw64 dir to ssh location guesser - windows git 2.8.0 
Implement ssh executable test in CliGitAPIImplTest, not applicable to JGit. 
May help 

JENKINS-30045
, 

JENKINS-28943
, 

JENKINS-25297
, & 

JENKINS-21806
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-21806) Windows git-client plugin assumes ssh.exe is in same directory as git.exe

2016-06-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-21806 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows git-client plugin assumes ssh.exe is in same directory as git.exe  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/2a2c6d339dcda8556b267f8a3584a5dd762be387 Log: Add mingw64 dir to ssh location guesser - windows git 2.8.0 
Implement ssh executable test in CliGitAPIImplTest, not applicable to JGit. 
May help 

JENKINS-30045
, 

JENKINS-28943
, 

JENKINS-25297
, & 

JENKINS-21806
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28943) Windows git cannot clone ssh repo if Git is referenced from cmd directory and is in a non-default location

2016-06-05 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-28943 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows git cannot clone ssh repo if Git is referenced from cmd directory and is in a non-default location  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java http://jenkins-ci.org/commit/git-client-plugin/2a2c6d339dcda8556b267f8a3584a5dd762be387 Log: Add mingw64 dir to ssh location guesser - windows git 2.8.0 
Implement ssh executable test in CliGitAPIImplTest, not applicable to JGit. 
May help 

JENKINS-30045
, 

JENKINS-28943
, 

JENKINS-25297
, & 

JENKINS-21806
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [blueocean-plugin] (JENKINS-35312) Log line numbers stop rendering at screen height

2016-06-05 Thread mne...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Neale resolved as Postponed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Working on migrating issues over that cover this one. Thanks! 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35312 
 
 
 
  Log line numbers stop rendering at screen height  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Neale 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Postponed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [p4-plugin] (JENKINS-33417) P4 and Sonar plugins generates circular dependency warning

2016-06-05 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fix Released in 2.4.1 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33417 
 
 
 
  P4 and Sonar plugins generates circular dependency warning  
 
 
 
 
 
 
 
 
 

Change By:
 
 Allan BURDAJEWICZ 
 
 
 

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] [teamconcert-git-plugin] (JENKINS-35360) teamconcert-git-plugin don´t work with parameter

2016-06-05 Thread robson.kraikko...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robson Miranda updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35360 
 
 
 
  teamconcert-git-plugin don´t work with parameter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Robson Miranda 
 
 
 
 
 
 
 
 
 
 Hi. I install this plugin and i'm trying use it with parameterized build on Jenkins.So, on a Jenkins job, i create a parameter (string) called WI to receive the user typed value at job start.On work item id field i typed $WI value.But when i save the job, the field value returns to 0 (plugin default value).I think should be possible the user choose the Work Item ID at job start, because otherwise the user should always change the job configuration before run it. There are Is there  a solution for 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] [teamconcert-git-plugin] (JENKINS-35360) teamconcert-git-plugin don´t work with parameter

2016-06-05 Thread robson.kraikko...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robson Miranda created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35360 
 
 
 
  teamconcert-git-plugin don´t work with parameter  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Krishna Kishore 
 
 
 

Attachments:
 

 teamconcert-git.jpg 
 
 
 

Components:
 

 teamconcert-git-plugin 
 
 
 

Created:
 

 2016/Jun/05 7:32 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Robson Miranda 
 
 
 
 
 
 
 
 
 
 
Hi. I install this plugin and i'm trying use it with parameterized build on Jenkins. So, on a Jenkins job, i create a parameter (string) called WI to receive the user typed value at job start. On work item id field i typed $WI value. But when i save the job, the field value returns to 0 (plugin default value). 
I think should be possible the user choose the Work Item ID at job start, because otherwise the user should always change the job configuration before run it. There are a solution for this? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 

[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken

2016-06-05 Thread jakub.czapli...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jakub Czaplicki commented on  JENKINS-34948 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken  
 
 
 
 
 
 
 
 
 
 
Updated the plugin to ver.1.09, rerun my Jenkins jobs a couple of times. All works as expected. The issue indeed has been fixed. 
I've updated https://wiki.jenkins-ci.org/display/JENKINS/Assembla+Auth+Plugin with the ver.no. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.

2016-06-05 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Ignore me. It was a permissions problem caused by restoring a backup of the plugin when it failed. All works just fine. Thanks and sorry  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35242 
 
 
 
  Upgraded to new AWS-SDK plugin, jenkins would not start.  
 
 
 
 
 
 
 
 
 

Change By:
 
 jake bishop 
 
 
 

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] [workflow-plugin] (JENKINS-35359) Limit concurrent builds for 1 MultiBranch project

2016-06-05 Thread philippe.la...@me.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Philippe Labat created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35359 
 
 
 
  Limit concurrent builds for 1 MultiBranch project  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 

Components:
 

 workflow-plugin 
 
 
 

Created:
 

 2016/Jun/05 5:18 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Philippe Labat 
 
 
 
 
 
 
 
 
 
 
I am currently running the latest version of the Pipeline plugin and i have created a multi-branch job. Everything is running fine on my Jenkinsfile but i would like to limit only 1 concurrent build for my entire multi-branch project. I see that you can set the option individually for the sub-sequent (branch) job but i would like to know if there is a way to limit it for the entire folder. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
   

[JIRA] [hp-application-automation-tools-plugin] (JENKINS-30743) How to update the HP LoadRunner Jenkins plugin to see Controller

2016-06-05 Thread ka...@hpe.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yafim Kazak commented on  JENKINS-30743 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: How to update the HP LoadRunner Jenkins plugin to see Controller  
 
 
 
 
 
 
 
 
 
 
Hi, This feature hasn't been added to the plugin control in jenkins. You can change it manually on line PerformanceTestRunner.cs:352 - change the 0 to 1. 
"_engine.ShowMainWindow(1);" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [publish-over-dropbox-plugin] (JENKINS-34937) Cannot create new credentials of type Dropbox

2016-06-05 Thread rcgr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 René de Groot commented on  JENKINS-34937 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cannot create new credentials of type Dropbox  
 
 
 
 
 
 
 
 
 
 
The exception points in the direction of a self-build hpi without updating the Config.java with a personal Dropbox API key or installing an older then 1.0.5 version. See https://github.com/rcgroot/jenkins-publish-over-dropbox-plugin option 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [script-security-plugin] (JENKINS-35358) Notification to admins on new pending script approval

2016-06-05 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35358 
 
 
 
  Notification to admins on new pending script approval  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Andrew Bayer 
 
 
 

Components:
 

 script-security-plugin 
 
 
 

Created:
 

 2016/Jun/05 3:36 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
The only way an admin can now there's a new pending script approval currently is to go to the manage page and see the section for script approval. There should be a configurable option for pushing notifications (email at the least, possibly other forms) upon new pending approval requests. 
Along with that, the message in the console log should be expanded to say that the admins have been notified of the request for approval. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[JIRA] [script-security-plugin] (JENKINS-35357) Script security should save and track rejections

2016-06-05 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35357 
 
 
 
  Script security should save and track rejections  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Andrew Bayer 
 
 
 

Components:
 

 script-security-plugin 
 
 
 

Created:
 

 2016/Jun/05 3:32 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
It would be handy to store a record of rejections by admins, so that we could have the messaging in logs be different for those signatures etc than ones that have not yet been either accepted or rejected. "Unclassified" runtime errors don't make a lot of sense if the admin has already classified it as rejected! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
  

[JIRA] [aws-java-sdk-plugin] (JENKINS-35242) Upgraded to new AWS-SDK plugin, jenkins would not start.

2016-06-05 Thread jake.bis...@netdudes.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 jake bishop reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I tried to update to 1.10.45.2. Jenkins will now start but it seems to crash all the aws plugins and they show as nolonger installed. If i try to install them from the plugin manager it looks like it works and suggest to restart. Then the plgins are not installed again. 
Strangely it says " You have data stored in an older format and/or unreadable data." when i go to manage jenkins. This data looks like: 

 
 

Type 
 

Name 
 

Error
 
 
 

hudson.model.Hudson
 

 
 

CannotResolveClassException: hudson.plugins.ec2.EC2Cloud
 
 
 

com.cloudbees.plugins.credentials.SystemCredentialsProvider
 

 
 

CannotResolveClassException: com.cloudbees.jenkins.plugins.awscredentials.AWSCredentialsImpl
 
 

 
Any ideas? Let me know if i can provide any more info. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35242 
 
 
 
  Upgraded to new AWS-SDK plugin, jenkins would not start.  
 
 
 
 
 
 
 
 
 

Change By:
 
 jake bishop 
 
 
 

Resolution:
 

[JIRA] [docker-plugin] (JENKINS-29497) Multiple Docker Clouds - only 1 container starts up when jobs are queueing

2016-06-05 Thread gentoo.inte...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-29497 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Multiple Docker Clouds - only 1 container starts up when jobs are queueing  
 
 
 
 
 
 
 
 
 
 
Tony Owens i think i fixed this in https://github.com/KostyaSha/yet-another-docker-plugin feel free to try while docker-plugin is not maintained. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35333) New job creation popup

2016-06-05 Thread samat...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Samat Davletshin assigned an issue to Samat Davletshin 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35333 
 
 
 
  New job creation popup  
 
 
 
 
 
 
 
 
 

Change By:
 
 Samat Davletshin 
 
 
 

Assignee:
 
 Samat Davletshin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35356) Support for Stash Backup Client

2016-06-05 Thread pawel.grzegrzo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pawel Grzegrzolka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35356 
 
 
 
  Support for Stash Backup Client  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pawel Grzegrzolka 
 
 
 

Environment:
 
 Jenkins 1.625Git plugin 2.4.0Stash Notifier 1.9.0 REPO plugin 1.10.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] [git-plugin] (JENKINS-35356) Support for Stash Backup Client

2016-06-05 Thread pawel.grzegrzo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pawel Grzegrzolka updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35356 
 
 
 
  Support for Stash Backup Client  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pawel Grzegrzolka 
 
 
 

Component/s:
 
 repo-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [git-plugin] (JENKINS-35356) Support for Stash Backup Client

2016-06-05 Thread pawel.grzegrzo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pawel Grzegrzolka created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35356 
 
 
 
  Support for Stash Backup Client  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Mark Waite 
 
 
 

Components:
 

 git-plugin, stashnotifier-plugin 
 
 
 

Created:
 

 2016/Jun/05 8:30 AM 
 
 
 

Environment:
 

 Jenkins 1.625  Git plugin 2.4.0  Stash Notifier 1.9.0 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Pawel Grzegrzolka 
 
 
 
 
 
 
 
 
 
 
When Stash Backup Client is running Jenkins fails with polling logs. 

 

Stash is currently unavailable:
- The system is unavailable while maintenance is being performed.
- Stash is unavailable while it is being backed up
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Stash is currently unavailable:
- The system is unavailable while maintenance is being performed.
- Stash is unavailable while it is being backed up
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
fatal: cannot obtain manifest ssh://path_to_geritt_manifest
Done. Took 1 min 10 sec
Changes found
 

 
There is the same behavior in Bamboo: