[JIRA] [gitlab-plugin] (JENKINS-34700) parameters are not "overwritten"

2016-05-09 Thread nico.bol...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nico Bollen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34700 
 
 
 
  parameters are not "overwritten"  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Robin Müller 
 
 
 

Components:
 

 gitlab-plugin 
 
 
 

Created:
 

 2016/May/10 5:46 AM 
 
 
 

Labels:
 

 plugin 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Nico Bollen 
 
 
 
 
 
 
 
 
 
 
We have a number of jobs triggered by gitlab and thus we use the gitlabSourceBranch and gitlabTargetBranch variable to get the correct branch from gitlab. To allow manual triggers we enable the "this job is parameterized" option and set 2 string parameters to some default value and with the same names gitlabSourceBranch and gitlabTargetBranch. Till before about 1 week the job parameters default values where overwritten by the gitlab hook values, but after some updates it's the other way around, so the gitlab hook values are overwritten by the jobs default values... 
 
 
 
 
 
 
 
 
 
 
 
 

 

[JIRA] [scm-sync-configuration-plugin] (JENKINS-30306) SCM plugin stops working after adding a slave

2016-05-09 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allan BURDAJEWICZ commented on  JENKINS-30306 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SCM plugin stops working after adding a slave  
 
 
 
 
 
 
 
 
 
 
How can we be sure this issue is fixed? Could you point us to a snippet in the code that address that 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] [ec2-plugin] (JENKINS-34667) Provision attempt is made when possible slaves count is 0.

2016-05-09 Thread franc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton commented on  JENKINS-34667 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provision attempt is made when possible slaves count is 0.  
 
 
 
 
 
 
 
 
 
 
Version 1.33 released with this fix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-34667) Provision attempt is made when possible slaves count is 0.

2016-05-09 Thread franc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Upton commented on  JENKINS-34667 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provision attempt is made when possible slaves count is 0.  
 
 
 
 
 
 
 
 
 
 
OK, done on master. I will release a new version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-34667) Provision attempt is made when possible slaves count is 0.

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

 
 
 
 
 
 
 
  Re: Provision attempt is made when possible slaves count is 0.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Francis Upton IV Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/f45093e4567290112ca4302e03acacacb50bbc5d Log: 

JENKINS-34667
 Provision attempt is made when possible slaves count is 0. (back out change) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-34699) Not able to clone BitBucket Repo

2016-05-09 Thread lajayku...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ajay Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34699 
 
 
 
  Not able to clone BitBucket Repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ajay Kumar 
 
 
 

Attachment:
 
 screenshot-2.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [bitbucket-plugin] (JENKINS-34699) Not able to clone BitBucket Repo

2016-05-09 Thread lajayku...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ajay Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34699 
 
 
 
  Not able to clone BitBucket Repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ajay Kumar 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [bitbucket-plugin] (JENKINS-34699) Not able to clone BitBucket Repo

2016-05-09 Thread lajayku...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ajay Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34699 
 
 
 
  Not able to clone BitBucket Repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ajay Kumar 
 
 
 
 
 
 
 
 
 
 HI,I am new to Jenkins and trying to setup in my laptop. I have installed it successfully. however I am not able to connect the Jenkins to BitBucket.It says failed to connect as you can see it in the screenshot.!screenshot-2.png! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [bitbucket-plugin] (JENKINS-34699) Not able to clone BitBucket Repo

2016-05-09 Thread lajayku...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ajay Kumar updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34699 
 
 
 
  Not able to clone BitBucket Repo  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ajay Kumar 
 
 
 

Attachment:
 
 screenshot-1.png 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [bitbucket-plugin] (JENKINS-34699) Not able to clone BitBucket Repo

2016-05-09 Thread lajayku...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ajay Kumar created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34699 
 
 
 
  Not able to clone BitBucket Repo  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 bitbucket-plugin 
 
 
 

Created:
 

 2016/May/10 2:09 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ajay Kumar 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are 

[JIRA] [ec2-plugin] (JENKINS-34667) Provision attempt is made when possible slaves count is 0.

2016-05-09 Thread rpilachow...@quickbase.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Pilachowski commented on  JENKINS-34667 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provision attempt is made when possible slaves count is 0.  
 
 
 
 
 
 
 
 
 
 
In case I wasn't clear, I suggest removing this change. I ran both test scenarios using the 

JENKINS-34667
 branch, but the code change removed and both scenarios worked correctly.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-application-automation-tools-plugin] (JENKINS-33410) Honor Reporter.Filter setting in QC

2016-05-09 Thread xu-liang.ku...@hpe.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kuang commented on  JENKINS-33410 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Honor Reporter.Filter setting in QC  
 
 
 
 
 
 
 
 
 
 
 an UFT issue, already send it to UFT team. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-application-automation-tools-plugin] (JENKINS-33410) Honor Reporter.Filter setting in QC

2016-05-09 Thread xu-liang.ku...@hpe.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jason Kuang updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33410 
 
 
 
  Honor Reporter.Filter setting in QC  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jason Kuang 
 
 
 
 
 
 
 
 
 
 When UFT runs a test and returns a value for Err.Number that is non-zero, a setting of "Reporter.Filter=rfDisableAll" can be set within ALM to not log this error. However, the non-zero value still causes a failure to be logged in Jenkins. It would be useful to have HPToolsRunner honor this same setting, and only report a failure to Jenkins when this property isn't set.    Reporter.Filter=rfDisableAll   is current UFT/QTP functionality to disable logging of failures to QC at runtime.  It is used to bypass expected errors that UFT interprets as failures. The issue is that when we have logging off, it does NOT log a failure to QC, which is what we expect.  The bug is that a failure is still logged to Jenkins when logging is disabled.  Jenkins logging should report EXACTLY what QC sees for results, so we end up with a Pass in QC and a Fail in Jenkins.   So we need this flag to be interpreted by Jenkins executions properly too.  This is a UFT issue, not a QC 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] [ec2-plugin] (JENKINS-34667) Provision attempt is made when possible slaves count is 0.

2016-05-09 Thread rpilachow...@quickbase.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Robert Pilachowski commented on  JENKINS-34667 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Provision attempt is made when possible slaves count is 0.  
 
 
 
 
 
 
 
 
 
 
This code change did not solve the problem.  
I tested a slight different scenario than above where both AMIs had provisioned slaves to the cap amount, but all were in the stopped state, i.e. no more slaves could be provisioned. When I started several builds spread across both AMIs, none of the slaves restarted. I suspect this happened because provisionSlaveIfPossible ended without trying to start any stopped slaves. When the old version of the check, (possibleSlavesCount < 0), was done, it would still try to start a stopped slave. 
I believe there is an issue in the logic where provisioning new slaves and starting stopped slaves is treated the same. Instead they should be treated differently and whenever there is a stopped slaves and excess work exists. Or, another option is to have countCurrentEC2Slaves not count stopped slaves. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [analysis-core-plugin] (JENKINS-22295) Trend graph is not immediately updated after configuration change

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

 
 
 
 
 
 
 
  Re: Trend graph is not immediately updated after configuration change  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/AbstractProjectAction.java src/main/java/hudson/plugins/analysis/graph/TrendDetails.java src/main/resources/hudson/plugins/analysis/graph/TrendDetails/index.jelly http://jenkins-ci.org/commit/analysis-core-plugin/ea79d2b6d28c9bf36ed58864d55d8922ce1bd5fc Log: 

JENKINS-22295
 Added fake URL so that graph detail view uses selected graph 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-14720) Warning should display if "fast remote polling" setting cannot be used

2016-05-09 Thread o...@nerdnetworks.org (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Owen Mehegan closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
No longer a bug in current Jenkins and Git plugin. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-14720 
 
 
 
  Warning should display if "fast remote polling" setting cannot be used  
 
 
 
 
 
 
 
 
 

Change By:
 
 Owen Mehegan 
 
 
 

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] [analysis-core-plugin] (JENKINS-22295) Trend graph is not immediately updated after configuration change

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22295 
 
 
 
  Trend graph is not immediately updated after configuration change  
 
 
 
 
 
 
 
 
 

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] [analysis-core-plugin] (JENKINS-22295) Trend graph is not immediately updated after configuration change

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

 
 
 
 
 
 
 
  Re: Trend graph is not immediately updated after configuration change  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/AbstractProjectAction.java src/main/resources/hudson/plugins/analysis/Messages_de.properties src/main/resources/hudson/plugins/analysis/core/AbstractProjectAction/floatingBox.jelly http://jenkins-ci.org/commit/analysis-core-plugin/ed66289f11c453af8e89e50a19c9dde95528b8c4 Log: [FIXED JENKINS-22295] Added fake URL so that graph is updated immediatly after configuration change. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [multi-branch-project-plugin] (JENKINS-34698) Allow picking a Browser for Git

2016-05-09 Thread nolang...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Norbert Lange created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34698 
 
 
 
  Allow picking a Browser for Git  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Matthew DeTullio 
 
 
 

Components:
 

 multi-branch-project-plugin 
 
 
 

Created:
 

 2016/May/09 10:14 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Norbert Lange 
 
 
 
 
 
 
 
 
 
 
Hello, 
Currently there is no way to specify a Browser for linking to the commit/files/diffs for changes. Either there should be a way to specify the Browser in the Piepeline configuration, or there should be a way to - for example - add the browser to the scm variable. 
A third option would be to allow configuring a global mapping between the "host:port" of a connection to a browser. I coded such a scheme and it works for normal Pipelines, but it doesnt for Multibranch Pipeline. With this one could set a mapping from the clone-urls to the projects web-url and additional stuff like browser information 

 

@NonCPS
def call(name) {
def servermap = [
'localhost:10022': [browser: [$class: 'GogsGit', repoUrl: 'http://localhost:10080'],
credentialsId: 'aad288c5-ea8e-4484-8e2d-9dc7abab7910', ],
]
def repomap = [
'tools': [git: 'ssh://git@localhost:10022/mn/tools.git', ],
'firmware': [git: 'ssh://git@localhost:10022/mn/firmware.git', ],
'jenkins-jobscripts': [git: 'ssh://git@localhost:10022/mn/jenkinspipeline.git', ],
]

def repo = repomap[name]

if (repo != null) {
repo = repo.clone()
def url = ""
if (url != null) {
 

[JIRA] [warnings-plugin] (JENKINS-34635) Configuration of trend graph does use wrong URL

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

 
 
 
 
 
 
 
  Re: Configuration of trend graph does use wrong URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/test/java/plugins/AbstractAnalysisTest.java http://jenkins-ci.org/commit/acceptance-test-harness/84f668d75c9e471a4a0c23563964d5b3b6337f39 Log: 

JENKINS-34635
 Added FIXME in test 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] [warnings-plugin] (JENKINS-34635) Configuration of trend graph does use wrong URL

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34635 
 
 
 
  Configuration of trend graph does use wrong 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] [warnings-plugin] (JENKINS-34635) Configuration of trend graph does use wrong URL

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

 
 
 
 
 
 
 
  Re: Configuration of trend graph does use wrong URL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/graph/UserGraphConfigurationView.java http://jenkins-ci.org/commit/analysis-core-plugin/1ce9dcdf150405ab02d5d8a1740a691832bb0441 Log: [FIXED JENKINS-34635] Use project URL when reading trend graph cookie. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-build-step-plugin] (JENKINS-34697) docker-build-step not working with question mark in password

2016-05-09 Thread sebastian.hut...@siroop.ch (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sebastian Hutter created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34697 
 
 
 
  docker-build-step not working with question mark in password  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 vjuranek 
 
 
 

Components:
 

 docker-build-step-plugin 
 
 
 

Created:
 

 2016/May/09 9:00 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.658  Docker Commons Plugin 1.3.1  Credentials Plugin 1.27  docker-build-step 1.34  (for reference: CloudBees Docker Build and Publish plugin 1.2.1) 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Sebastian Hutter 
 
 
 
 
 
 
 
 
 
 
Using a credential with a question mark  in the password is causing the docker-build-step plugin to fail when accessing a private repository in the docker hub. 
In the docker log I can see the following message when trying to run a docker-build-step command (output from a docker pull step): level=error msg="Attempting next endpoint for pull after error: unauthorized: authentication required" 
As soon as I remove the question mark (and replace it by any other character including #) the docker pull is working as expected. 
The credentials themselves are properly setup - I am able to execute the build and publish step from the CloudBees plugin - with or without the question mark in the password. 
 
 
   

[JIRA] [pipeline-stage-view-plugin] (JENKINS-34696) Fix the representation of Parallel Stage in pipeline build (as it is delivery pipeline view)

2016-05-09 Thread alexandre.j.nava...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandre Navarro created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34696 
 
 
 
  Fix the representation of Parallel Stage in pipeline build (as it is delivery pipeline view)  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Sam Van Oort 
 
 
 

Attachments:
 

 delivery-pipeline-view-screenshot.png, pipeline-screenshot.png 
 
 
 

Components:
 

 pipeline-stage-view-plugin 
 
 
 

Created:
 

 2016/May/09 8:54 PM 
 
 
 

Environment:
 

 jenkins 1.651 LTS 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alexandre Navarro 
 
 
 
 
 
 
 
 
 
 
Fix the representation of Parallel Stage in pipeline build (as it is delivery pipeline view) 
1) With a Pipeline build This is my pipeline script 
node { stage 'compile' git 'https://github.com/hermod/hermod-java-ser-impl.git' 
 def mvnHome = tool 'maven-3.3.9' sh "$ {mvnHome} 
/bin/mvn -DskipTests clean install" 
 def deployments = [:] deployments["dev"] =  { stage 'deployOnDev' echo 'deployOnDev' } 
  

[JIRA] [core] (JENKINS-25204) Unhandled UsernameNotFoundException may appear in BasicAuthenticationFilter::doFilter()

2016-05-09 Thread db...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-25204 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unhandled UsernameNotFoundException may appear in BasicAuthenticationFilter::doFilter()  
 
 
 
 
 
 
 
 
 
 
Is this really a use case we want to support? With the tokens no longer being admin-visible, I think we decided this is not valid. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34695) Fixup old data version string 1.651.3

2016-05-09 Thread ogon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34695 
 
 
 
  Fixup old data version string 1.651.3  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/May/09 8:36 PM 
 
 
 

Labels:
 

 lts-candidate 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Oliver Gondža 
 
 
 
 
 
 
 
 
 
 
Backported in .2 with version string referring to mainline: https://github.com/jenkinsci/jenkins/commit/916e759f576fd9aec7eb563f71f6541ceb37f641#commitcomment-17397355. To be adjusted in .3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

[JIRA] [core] (JENKINS-34695) Fixup old data version string 1.651.3

2016-05-09 Thread ogon...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oliver Gondža resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34695 
 
 
 
  Fixup old data version string 1.651.3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Oliver Gondža 
 
 
 

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] [jclouds-plugin] (JENKINS-34684) Jcloud - Unable to create build nodes in Openstack cloud

2016-05-09 Thread davegood...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dave goodine commented on  JENKINS-34684 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jcloud - Unable to create build nodes in Openstack cloud  
 
 
 
 
 
 
 
 
 
 
Fritz Elfert - here is the json: 

 

{"access": {"token": {"issued_at": "2016-05-09T20:31:38.918294", "expires": "2016-05-10T20:31:38Z", "id": "96471d3bdaf245de950a5e8c98dd96cf", "tenant": {"description": "", "enabled": true, "id": "be351b66fff74a25a1e060f101a1889a", "name": "cibuild"}}, "serviceCatalog": [{"endpoints": [{"adminURL": "http://localhost:", "region": "regionOne", "internalURL": "http://localhost:888", "id": "7dbfb467567b400d81a3eeb018e0a41a", "publicURL": "http://localhost:"}], "endpoints_links": [], "type": "rating", "name": "CloudKitty"}, {"endpoints": [{"adminURL": "http://controller-n02.openstack.drillinginfo.com:8774/v2/be351b66fff74a25a1e060f101a1889a", "region": "regionOne", "internalURL": "http://controller-n02.openstack.drillinginfo.com:8774/v2/be351b66fff74a25a1e060f101a1889a", "id": "33dc4970833847db8280ace6fa7dff32", "publicURL": "http://controller-n02.openstack.drillinginfo.com:8774/v2/be351b66fff74a25a1e060f101a1889a"}], "endpoints_links": [], "type": "compute", "name": "nova"}, {"endpoints": [{"adminURL": "http://controller-n02.openstack.drillinginfo.com:9696", "region": "regionOne", "internalURL": "http://controller-n02.openstack.drillinginfo.com:9696", "id": "5e68688c7d1247d39fa0b5535f323840", "publicURL": "http://controller-n02.openstack.drillinginfo.com:9696"}], "endpoints_links": [], "type": "network", "name": "neutron"}, {"endpoints": [{"adminURL": "http://cinder.openstack.drillinginfo.com:8776/v2/be351b66fff74a25a1e060f101a1889a", "region": "regionOne", "internalURL": "http://cinder.openstack.drillinginfo.com:8776/v2/be351b66fff74a25a1e060f101a1889a", "id": "866d4b882b044387955d1809fc3248df", "publicURL": "http://cinder.openstack.drillinginfo.com:8776/v2/be351b66fff74a25a1e060f101a1889a"}], "endpoints_links": [], "type": "volumev2", "name": "cinderv2"}, {"endpoints": [{"adminURL": "http://controller-n01.openstack.drillinginfo.com:9292", "region": "regionOne", "internalURL": "http://controller-n01.openstack.drillinginfo.com:9292", "id": "4b7000e012a94082bfcc3e1745dbe21e", "publicURL": "http://controller-n01.openstack.drillinginfo.com:9292"}], "endpoints_links": [], "type": "image", "name": "glance"}, {"endpoints": [{"adminURL": "http://controller-n01.openstack.drillinginfo.com:8777", "region": "regionOne", "internalURL": "http://controller-n01.openstack.drillinginfo.com:8777", "id": "3f5714f2514247be8947285c7b951dbb", "publicURL": "http://controller-n01.openstack.drillinginfo.com:8777"}], "endpoints_links": [], "type": "metering", "name": "ceilometer"}, {"endpoints": [{"adminURL": "http://controller-n01.openstack.drillinginfo.com:8000/v1", "region": "regionOne", "internalURL": "http://controller-n01.openstack.drillinginfo.com:8000/v1", "id": "55e2b168ac454e369f4207b5a757c4be", "publicURL": "http://controller-n01.openstack.drillinginfo.com:8000/v1"}], "endpoints_links": [], "type": "cloudformation", "name": "heat-cfn"}, {"endpoints": [{"adminURL": "http://cinder.openstack.drillinginfo.com:8776/v1/be351b66fff74a25a1e060f101a1889a", "region": "regionOne", "internalURL": "http://cinder.openstack.drillinginfo.com:8776/v1/be351b66fff74a25a1e060f101a1889a", "id": "cfa7beecf0064c9181bd4d27aebf31e8", "publicURL": "http://cinder.openstack.drillinginfo.com:8776/v1/be351b66fff74a25a1e060f101a1889a"}], "endpoints_links": [], "type": "volume", "name": "cinder"}, {"endpoints": [{"adminURL": "http://controller-n01.openstack.drillinginfo.com:8004/v1/be351b66fff74a25a1e060f101a1889a", "region": "regionOne", "internalURL": "http://controller-n01.openstack.drillinginfo.com:8004/v1/be351b66fff74a25a1e060f101a1889a", "id": 

[JIRA] [delivery-pipeline-plugin] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin

2016-05-09 Thread alexandre.j.nava...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alexandre Navarro commented on  JENKINS-34040 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for Pipeline plugin in the Delivery Pipeline plugin  
 
 
 
 
 
 
 
 
 
 
I have the same issue, important to fix. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [windows-slaves-plugin] (JENKINS-25785) Windows slaves controlled as Windows Service do not use credentials manager

2016-05-09 Thread diogo...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Diogo Guerra commented on  JENKINS-25785 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Windows slaves controlled as Windows Service do not use credentials manager  
 
 
 
 
 
 
 
 
 
 
Vincent Latombe I'm having some problems on using the credentials plugin with jgit and windows slave. It seems that the credentials are never used (not a problem of changes and restarts). I don't know in depth the source but is your patch integrating the credentials plugin with the windows slaves plugin? 
I'm using Jenkins 2.2, git plugin 2.4.4, windows slaves 1.1. It works well with linux slaves but windows ones it doesn'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] [workflow-plugin] (JENKINS-34032) Pipeline plugin workflow step allocates workspace in jenkins root

2016-05-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34032 
 
 
 
  Pipeline plugin workflow step allocates workspace in jenkins root  
 
 
 
 
 
 
 
 
 

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] [cli] (JENKINS-34328) Extract disconnect-node CLI from Core

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

 
 
 
 
 
 
 
  Re: Extract disconnect-node CLI from Core  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Ing. Pavel Janousek Path: core/src/main/java/hudson/cli/DisconnectNodeCommand.java core/src/main/java/hudson/model/Computer.java core/src/main/resources/hudson/cli/Messages.properties core/src/main/resources/hudson/cli/Messages_bg.properties core/src/main/resources/hudson/cli/Messages_da.properties core/src/main/resources/hudson/cli/Messages_de.properties core/src/main/resources/hudson/cli/Messages_es.properties core/src/main/resources/hudson/cli/Messages_ja.properties core/src/main/resources/hudson/cli/Messages_pt_BR.properties core/src/main/resources/hudson/cli/Messages_zh_CN.properties core/src/main/resources/hudson/cli/Messages_zh_TW.properties core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/model/Messages_bg.properties core/src/main/resources/hudson/model/Messages_da.properties core/src/main/resources/hudson/model/Messages_de.properties core/src/main/resources/hudson/model/Messages_es.properties core/src/main/resources/hudson/model/Messages_it.properties core/src/main/resources/hudson/model/Messages_ja.properties core/src/main/resources/hudson/model/Messages_pt_BR.properties core/src/main/resources/hudson/model/Messages_zh_CN.properties core/src/main/resources/hudson/model/Messages_zh_TW.properties test/src/test/java/hudson/cli/DisconnectNodeCommandTest.java http://jenkins-ci.org/commit/jenkins/6feaea8647fe328eb47ea764764897cdb212f3fb Log: JENKINS-34328 CLI command disconnect-node extracted from core to CLI 
disconnect-node extended to accept multiple node names disconnect-node covered by test-cases 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [cli] (JENKINS-34328) Extract disconnect-node CLI from Core

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

 
 
 
 
 
 
 
  Re: Extract disconnect-node CLI from Core  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/cli/DisconnectNodeCommand.java core/src/main/java/hudson/model/Computer.java core/src/main/resources/hudson/cli/Messages.properties core/src/main/resources/hudson/cli/Messages_bg.properties core/src/main/resources/hudson/cli/Messages_da.properties core/src/main/resources/hudson/cli/Messages_de.properties core/src/main/resources/hudson/cli/Messages_es.properties core/src/main/resources/hudson/cli/Messages_ja.properties core/src/main/resources/hudson/cli/Messages_pt_BR.properties core/src/main/resources/hudson/cli/Messages_zh_CN.properties core/src/main/resources/hudson/cli/Messages_zh_TW.properties core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/model/Messages_bg.properties core/src/main/resources/hudson/model/Messages_da.properties core/src/main/resources/hudson/model/Messages_de.properties core/src/main/resources/hudson/model/Messages_es.properties core/src/main/resources/hudson/model/Messages_it.properties core/src/main/resources/hudson/model/Messages_ja.properties core/src/main/resources/hudson/model/Messages_pt_BR.properties core/src/main/resources/hudson/model/Messages_zh_CN.properties core/src/main/resources/hudson/model/Messages_zh_TW.properties test/src/test/java/hudson/cli/DisconnectNodeCommandTest.java http://jenkins-ci.org/commit/jenkins/8f43679945a0c9488f870a5bb9cbc34e461d5723 Log: Merge pull request #2295 from pjanouse/JENKINS-34328 
JENKINS-34328 CLI command disconnect-node extracted from core to CLI 
Compare: https://github.com/jenkinsci/jenkins/compare/3e1bc969f4ec...8f43679945a0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [git-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves

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

 
 
 
 
 
 
 
  Re: git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Boguslaw Klimas Path: src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/FilePathWrapper.java src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java src/main/resources/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition/index.jelly src/test/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinitionTest.java http://jenkins-ci.org/commit/git-parameter-plugin/a9b4abd7790a992478ba623648dc54144347e136 Log: Merge pull request #24 from jenkinsci/feature/JENKINS-16290 
Feature/jenkins 16290 
Compare: https://github.com/jenkinsci/git-parameter-plugin/compare/67da107e69cf...a9b4abd7790a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-34694) BitBucket plugin requires Git polling enabled

2016-05-09 Thread thefriendlyco...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Phillips commented on  JENKINS-34694 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BitBucket plugin requires Git polling enabled  
 
 
 
 
 
 
 
 
 
 
I came across this seemingly related defect in the issue tracker, however the reporter appears to be reporting the opposite behavior from what I'm seeing here. Not sure how that is possible. 
That issue is reportedly caused by SHA1 hashes being excluded in certain situations. It does appear that the Bitbucket server edition does support disabling SHA1 hashes in their web hooks, however I have confirmed that our server has them enabled so I'm not convinced this is causing our problems. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-34694) BitBucket plugin requires Git polling enabled

2016-05-09 Thread thefriendlyco...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Phillips created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34694 
 
 
 
  BitBucket plugin requires Git polling enabled  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 bitbucket-plugin 
 
 
 

Created:
 

 2016/May/09 7:35 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Kevin Phillips 
 
 
 
 
 
 
 
 
 
 
While testing the bitbucket Jenkins plugin with a locally hosted instance of BitBucket (aka: Stash) I discovered that web hooks from BitBucket server to Jenkins only work when the Jenkins jobs have polling enabled for the Git repository. Having only the BitBucket web hook trigger enabled does not appear to be sufficient. 
As a temporary hack I've simply enabled SCM polling triggers in my test jobs and intentionally left the polling interval empty, which essentially disables the SCM polling mechanism. Not only is this annoying, but it is very non-intuitive because it isn't obvious based on the logs and error messages that this is the root cause of the web hook triggering problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
  

[JIRA] [workflow-plugin] (JENKINS-34638) org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random

2016-05-09 Thread budhi...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ashudeep Budhiraja updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34638 
 
 
 
  org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use new java.util.Random  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ashudeep Budhiraja 
 
 
 

Priority:
 
 Major Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json

2016-05-09 Thread kevin.phill...@caris.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Phillips commented on  JENKINS-28877 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket Plugin unable to parse Bitbucket webhook response json  
 
 
 
 
 
 
 
 
 
 
I finally got some time to build the plugin from source using your proposed changes and it appears to work for us. If we could get those changes integrated into an official release of the plugin sooner rather than later that would be awesome. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

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

 
 
 
 
 
 
 
  Re: Option to disable script security approval  
 
 
 
 
 
 
 
 
 
 
Jesse Glick Aren't scripts configured by people with Overall/RunScripts automatically approved? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications

2016-05-09 Thread amu...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz commented on  JENKINS-33507 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications  
 
 
 
 
 
 
 
 
 
 
Yes, you are right. Changes need to be made where you pointed and here. 
And yes, the help tip could be updated. Feel free to send a PR for that if you want. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [branch-api-plugin] (JENKINS-34693) PR jobs links are broken inside Pull Request view

2016-05-09 Thread esc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Emilio Escobar  created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34693 
 
 
 
  PR jobs links are broken inside Pull Request view  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 

Components:
 

 branch-api-plugin 
 
 
 

Created:
 

 2016/May/09 6:02 PM 
 
 
 

Environment:
 

 The environment is a fresh Jenkins 1.642.4. and GitHub Organization Folder Plugin 1.3   When you install GitHub Organization Folder Plugin 1.3 those plugins are also upgraded:   Folders Plugin  GitHub API Plugin  SCM API Plugin  GitHub Branch Source Plugin   _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin  Structs Plugin  Pipeline: Step API  Pipeline: SCM Step  Pipeline: API  Pipeline: Supporting APIs  Pipeline: Groovy  Pipeline: Job  Pipeline: Multibranch  GitHub Organization Folder Plugin   You have to install Branch API Plugin 1.6 because 1.7 doesn't have the Branches / Pull Request views 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Emilio Escobar  
 
 
 
 
 
 
 
 
 
 
Create a new Github Organization Folder job, let it discover organizations, repositories and branches / pull requests. 
When the branches and PRs are built, go to PR view and all the links to PR jobs are broken: 
http://127.0.0.1:8080/job/org-folder/job/private-repo/view/Pull%20Requests/branch/PR-11/ 
But the job should be visited by: 
  

[JIRA] [github-organization-folder-plugin] (JENKINS-34692) Github link points to branch/PR-11 instead of pull/11

2016-05-09 Thread esc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Emilio Escobar  created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34692 
 
 
 
  Github link points to branch/PR-11 instead of pull/11  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 

Attachments:
 

 BrokenGitHubLink.png 
 
 
 

Components:
 

 github-organization-folder-plugin 
 
 
 

Created:
 

 2016/May/09 5:40 PM 
 
 
 

Environment:
 

 The environment is a fresh Jenkins 1.642.4. and GitHub Organization Folder Plugin 1.3   When you install GitHub Organization Folder Plugin 1.3 those plugins are also upgraded:   Folders Plugin  GitHub API Plugin  SCM API Plugin  GitHub Branch Source Plugin  Branch API Plugin  _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin  Structs Plugin  Pipeline: Step API  Pipeline: SCM Step  Pipeline: API  Pipeline: Supporting APIs  Pipeline: Groovy  Pipeline: Job  Pipeline: Multibranch  GitHub Organization Folder Plugin 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Emilio Escobar  
 
 
 
 
 
 
 
 
 
 
Create a new Github Organization Folder job, let it discover organizations, repositories and branches / pull requests. 
Go to a PR build, and click 

[JIRA] [github-organization-folder-plugin] (JENKINS-34691) Create New item copied from github org branch job should not be allowed

2016-05-09 Thread r.m.gra...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Graham created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34691 
 
 
 
  Create New item copied from github org branch job should not be allowed  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kohsuke Kawaguchi 
 
 
 

Components:
 

 github-organization-folder-plugin 
 
 
 

Created:
 

 2016/May/09 5:39 PM 
 
 
 

Environment:
 

 Jenkins v2.0  GitHub Organization Folder Plugin v1.3  GitHub Branch Source Plugin v1.6  Pipeline: Multibranch v2.3  Pipeline: Job v2.1 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Ryan Graham 
 
 
 
 
 
 
 
 
 
 
Actions taken: When creating a new item, if one creates that job as a copy of an existing branch, the resulting job is not editable or deletable. There is no way that I can see to edit or delete the newly created job. 
Use Case: The reason one might want to do this is to turn a given branch build into a recurring task. What I thought was the obvious solution was to create a new item coped from the existing one, with the intention of adding in a schedule trigger. 
Expectation: Ideally, this would just work, but as a stop-gap it should probably have been prevented from happening in the first place by filtering out such immutable/generated jobs as copy-from candidates. 
 
 
 
 
 
 

[JIRA] [maven-plugin] (JENKINS-2687) case sensitive environment variable PATH

2016-05-09 Thread guillaume.missonn...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Guillaume Missonnier edited a comment on  JENKINS-2687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: case sensitive environment variable PATH  
 
 
 
 
 
 
 
 
 
 Got the case sensitive environment variable problem too.For instance, if I set these two variable in my slave agent environment :{code:none}#!/bin/bashexport TEST=TESTexport test=testexec java -jar  /homes2/bxi/bin/ slave.jar{code}My builds got the following in their environment :test=TEST 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-2687) case sensitive environment variable PATH

2016-05-09 Thread guillaume.missonn...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Guillaume Missonnier edited a comment on  JENKINS-2687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: case sensitive environment variable PATH  
 
 
 
 
 
 
 
 
 
 Got the case sensitive environment variable problem too.For instance, if I set these two variable in my slave agent environment :{code:none}#!/bin/bashexport TEST=TESTexport test=testexec java -jar /homes2/bxi/bin/slave.jar{code}My builds got the following in their environment : TEST= test =TEST  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-2687) case sensitive environment variable PATH

2016-05-09 Thread guillaume.missonn...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Guillaume Missonnier edited a comment on  JENKINS-2687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: case sensitive environment variable PATH  
 
 
 
 
 
 
 
 
 
 Got the case sensitive environment variable problem too.For instance, if I set these two variable in my slave agent environment :{code: bash none }#!/bin/bashexport TEST=TESTexport test=testexec java -jar /homes2/bxi/bin/slave.jar{code}My builds got the following in their environment :TEST=test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-2687) case sensitive environment variable PATH

2016-05-09 Thread guillaume.missonn...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Guillaume Missonnier commented on  JENKINS-2687 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: case sensitive environment variable PATH  
 
 
 
 
 
 
 
 
 
 
Got the case sensitive environment variable problem too. 
For instance, if I set these two variable in my slave agent environment : 

 

Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


#!/bin/bash
export TEST=TEST
export test=test

exec java -jar /homes2/bxi/bin/slave.jar
 

 
My builds got the following in their environment : 
TEST=test 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications

2016-05-09 Thread nickbr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Brown commented on  JENKINS-33507 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Bitbucket Server webhooks and Bitbucket Cloud build status notifications  
 
 
 
 
 
 
 
 
 
 
I'm guessing that Bitbucket server auto-register webhook support is not yet implemented, despite the option being presented in the Branch source configuration? 
https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/f50ce24f4afc75e6dae00c44ea20b8fa137bd72d/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/hooks/WebhookAutoRegisterListener.java#L187 
If I enable this option when configuring Jenkins with my Bitbucket Server details and visit http:// [JENKINS_ROOT_URL]/bitbucket-scmsource-hook/notify I get the below error in my browser. 
Until this implemented, could the help-autoRegisterHooks.jelly perhaps be updated to point out BitBucket Server is not supported. I think this means that automatic branch re-indexing of branches will also not happen as this based off SCM change notification, and thus, 'Periodically if not otherwise run' Build Trigger will need to configured so that this happens. 

 

java.lang.Exception: X-Event-Key HTTP header not found
	at org.kohsuke.stapler.HttpResponses.error(HttpResponses.java:83)
	at com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver.doNotify(BitbucketSCMSourcePushHookReceiver.java:68)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-34646) High CPU Usage navigating the UI

2016-05-09 Thread luigi.tagliamont...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Luigi Tagliamonte commented on  JENKINS-34646 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: High CPU Usage navigating the UI  
 
 
 
 
 
 
 
 
 
 
I was not experiencing this behaviour with 1.X release. following the list of the installed plugins: 

 

MapDB API Plugin (mapdb-api): 1.0.6.0
GitHub Branch Source Plugin (github-branch-source): 1.6
Javadoc Plugin (javadoc): 1.3
Pipeline: REST API Plugin (pipeline-rest-api): 1.3
Gradle plugin (gradle): 1.24
SSH Agent Plugin (ssh-agent): 1.10
CVS Plug-in (cvs): 2.12
Pipeline: Basic Steps (workflow-basic-steps): 2.0
_javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1
JUnit Plugin (junit): 1.13
Amazon Web Services SDK (aws-java-sdk): 1.10.45
SSH Slaves plugin (ssh-slaves): 1.11
Token Macro Plugin (token-macro): 1.12.1
_javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1
Git plugin (git): 2.4.4
_javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1
LDAP Plugin (ldap): 1.12
Git server plugin (git-server): 1.6
Mailer Plugin (mailer): 1.17
Job DSL (job-dsl): 1.44
Pipeline: Stage Step (pipeline-stage-step): 2.1
Script Security Plugin (script-security): 1.19
Git client plugin (git-client): 1.19.6
Parameterized Trigger plugin (parameterized-trigger): 2.30
Naginator (naginator): 1.17
SSH Credentials Plugin (ssh-credentials): 1.11
Pipeline: Build Step (pipeline-build-step): 2.0
Multiple SCMs plugin (multiple-scms): 0.6
Run Condition Plugin (run-condition): 1.0
Pipeline: Multibranch (workflow-multibranch): 2.3
Amazon EC2 plugin (ec2): 1.31
PAM Authentication plugin (pam-auth): 1.2
Branch API Plugin (branch-api): 1.7
Pipeline (workflow-aggregator): 2.1
Node Iterator API Plugin (node-iterator-api): 1.5
Pipeline: Stage View Plugin (pipeline-stage-view): 1.3
Flexible Publish Plugin (flexible-publish): 0.15.2
Translation Assistance plugin (translation): 1.14
SCM API Plugin (scm-api): 1.2
Matrix Reloaded Plugin (matrix-reloaded): 1.1.3
Windows Slaves Plugin (windows-slaves): 1.1
Role-based Authorization Strategy (role-strategy): 2.2.0
Matrix Authorization Strategy Plugin (matrix-auth): 1.3.2
conditional-buildstep (conditional-buildstep): 1.3.3
Pipeline: Supporting APIs (workflow-support): 2.0
Plain Credentials Plugin (plain-credentials): 1.1
Maven Integration plugin (maven-plugin): 2.12.1
Ant Plugin (ant): 1.2
External Monitor Job Type Plugin (external-monitor-job): 1.4
Amazon SNS Build Notifier (snsnotify): 1.13
GitHub plugin (github): 1.19.0
Post-Build Script Plug-in (postbuildscript): 0.17
Subversion Plug-in (subversion): 2.5.7
Pipeline: Step API (workflow-step-api): 2.0
Pipeline: Groovy (workflow-cps): 2.2
Any Build Step Plugin (any-buildstep): 0.1
Structs Plugin (structs): 1.1
Matrix Project Plugin (matrix-project): 1.6
Pipeline: SCM Step (workflow-scm-step): 2.0
Pipeline: API (workflow-api): 2.0
Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.0
Folders Plugin (cloudbees-folder): 5.9
Credentials Plugin (credentials): 1.28
jQuery plugin (jquery): 1.11.2-0
Google Login Plugin (google-login): 1.2.1
GitHub Organization Folder Plugin (github-organization-folder): 1.3
GitHub API Plugin (github-api): 1.75
Icon Shim Plugin (icon-shim): 2.0.3
build timeout plugin (build-timeout): 1.16
OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.3
Pipeline: Input Step (pipeline-input-step): 2.0
Pipeline: Nodes and Processes (workflow-durable-task-step): 2.0
Pipeline: Job (workflow-job): 2.1
Durable Task Plugin (durable-task): 1.9
Jackson 2 API Plugin (jackson2-api): 2.7.3
_javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1
Slack Notification Plugin (slack): 1.8
Result: [Plugin:mapdb-api, Plugin:github-branch-source, Plugin:javadoc, Plugin:pipeline-rest-api, Plugin:gradle, Plugin:ssh-agent, Plugin:cvs, 

[JIRA] [build-failure-analyzer-plugin] (JENKINS-27123) Workflow support for Build Failure Analyzer

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

 
 
 
 
 
 
 
  Re: Workflow support for Build Failure Analyzer  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/893e3484a25289c59567c6724f7ce19e3d23c6ee Log: Merge pull request #383 from HRMPW/patch-1 


JENKINS-27123
 Update COMPATIBILITY.md 
Compare: https://github.com/jenkinsci/pipeline-plugin/compare/281eef2ca525...893e3484a252 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-34623) Improve test coverage for basic use cases

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

 
 
 
 
 
 
 
  Re: Improve test coverage for basic use cases  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Armando Fernandez Path: pom.xml src/main/java/hudson/tasks/Ant.java src/main/java/hudson/tasks/_ant/AntConsoleAnnotator.java src/main/java/hudson/tasks/_ant/AntTargetNote.java src/main/resources/hudson/tasks/_ant/Messages.properties src/main/resources/hudson/tasks/_ant/Messages_da.properties src/main/resources/hudson/tasks/_ant/Messages_de.properties src/main/resources/hudson/tasks/_ant/Messages_es.properties src/main/resources/hudson/tasks/_ant/Messages_ja.properties src/main/resources/hudson/tasks/_ant/Messages_pt_BR.properties src/main/resources/hudson/tasks/_ant/Messages_zh_TW.properties src/test/java/hudson/tasks/AntTest.java src/test/java/hudson/tasks/_ant/AntTargetAnnotationTest.java src/test/resources/hudson/tasks/sample-helloworld-ant.zip http://jenkins-ci.org/commit/ant-plugin/9f6c00a7c07dd51878c78a7f7b9d7d0b846f8a52 Log: JENKINS-34565JENKINS-34623 Upgrade to 2.x parent pom. Increase test coverage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-34565) Upgrade Ant plugin to new parent pom

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

 
 
 
 
 
 
 
  Re: Upgrade Ant plugin to new parent pom  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Armando Fernandez Path: pom.xml src/main/java/hudson/tasks/Ant.java src/main/java/hudson/tasks/_ant/AntConsoleAnnotator.java src/main/java/hudson/tasks/_ant/AntTargetNote.java src/main/resources/hudson/tasks/_ant/Messages.properties src/main/resources/hudson/tasks/_ant/Messages_da.properties src/main/resources/hudson/tasks/_ant/Messages_de.properties src/main/resources/hudson/tasks/_ant/Messages_es.properties src/main/resources/hudson/tasks/_ant/Messages_ja.properties src/main/resources/hudson/tasks/_ant/Messages_pt_BR.properties src/main/resources/hudson/tasks/_ant/Messages_zh_TW.properties src/test/java/hudson/tasks/AntTest.java src/test/java/hudson/tasks/_ant/AntTargetAnnotationTest.java src/test/resources/hudson/tasks/sample-helloworld-ant.zip http://jenkins-ci.org/commit/ant-plugin/9f6c00a7c07dd51878c78a7f7b9d7d0b846f8a52 Log: JENKINS-34565JENKINS-34623 Upgrade to 2.x parent pom. Increase test coverage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ant-plugin] (JENKINS-34623) Improve test coverage for basic use cases

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

 
 
 
 
 
 
 
  Re: Improve test coverage for basic use cases  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Armando Fernández Path: pom.xml src/main/java/hudson/tasks/Ant.java src/main/java/hudson/tasks/_ant/AntConsoleAnnotator.java src/main/java/hudson/tasks/_ant/AntTargetNote.java src/main/resources/hudson/tasks/_ant/Messages.properties src/main/resources/hudson/tasks/_ant/Messages_da.properties src/main/resources/hudson/tasks/_ant/Messages_de.properties src/main/resources/hudson/tasks/_ant/Messages_es.properties src/main/resources/hudson/tasks/_ant/Messages_ja.properties src/main/resources/hudson/tasks/_ant/Messages_pt_BR.properties src/main/resources/hudson/tasks/_ant/Messages_zh_TW.properties src/test/java/hudson/tasks/AntTest.java src/test/java/hudson/tasks/_ant/AntTargetAnnotationTest.java src/test/resources/hudson/tasks/sample-helloworld-ant.zip http://jenkins-ci.org/commit/ant-plugin/7dd836b0163020e5e70a69e40d2dee45be846ca0 Log: Merge pull request #16 from armfergom/JENKINS-34623 
Compare: https://github.com/jenkinsci/ant-plugin/compare/982e9cfc4e01...7dd836b01630 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-24003) Unable to wipe out workspace

2016-05-09 Thread dant...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dan tran commented on  JENKINS-24003 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to wipe out workspace  
 
 
 
 
 
 
 
 
 
 
For my case, it has no checkout and unshelved files, will test 1.3.9-SNAPSHOT.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34121) IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3

2016-05-09 Thread stephenconno...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stephenconnolly commented on  JENKINS-34121 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3  
 
 
 
 
 
 
 
 
 
 
So the JNLP4 protocol is implemented already. I am just awaiting approval to release the code. As it uses TLS rather than a home grown cipher system this should not be an issue for JNLP4. (The other change with JNLP4 is that it uses NIO whereas JNLP3 dropped the NIO support) 
If you remove JNLP3 from the list of supported protocols then it should fall back to JNLP2 if I recall the code correctly 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33993) perforce job assumed for every changelist when specifying label

2016-05-09 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Resolved - slated for next release. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33993 
 
 
 
  perforce job assumed for every changelist when specifying label  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Paul Allen 
 
 
 

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] [p4-plugin] (JENKINS-33993) perforce job assumed for every changelist when specifying label

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

 
 
 
 
 
 
 
  Re: perforce job assumed for every changelist when specifying label  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/changes/P4ChangeSet.java http://jenkins-ci.org/commit/p4-plugin/bab531a8f1f2d7409861a6c7ddffc7808e47a559 Log: Protect against null when no jobs are in a changelist. 
JENKINS-33993 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-24003) Unable to wipe out workspace

2016-05-09 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen commented on  JENKINS-24003 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to wipe out workspace  
 
 
 
 
 
 
 
 
 
 
Hi Dan, The latest fix reverts files that might have been open (unshelve files, user edits, etc...). If a file was open then it would block the cleanup of the client. There are a few other situations that may break it, like file permission and Client ownership permissions, but I can't work around that. 
I have started using Jenkins JIRA Agile board: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=141 
So 'Resolve' for me is a submitted fix (available as a snapshot) and 'Closed' when it is released. I'll move this job back to 'Resolved' unless there is a bug? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-34614) ATH ftpd container doesn't seem to be opening port 21 (or running?)

2016-05-09 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer commented on  JENKINS-34614 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ATH ftpd container doesn't seem to be opening port 21 (or running?)  
 
 
 
 
 
 
 
 
 
 
So this is actually a gigantic pain to debug when you're on a Mac, 'cos the setup requires a local Docker process rather than one on a VM. If anyone running Linux would like to debug this sucker, I'd be very appreciative! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-34411) Horizontal scrolling & overflow issues

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

 
 
 
 
 
 
 
  Re: Horizontal scrolling & overflow issues  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Andrew Bayer Path: src/main/java/org/jenkinsci/test/acceptance/selenium/Scroller.java src/main/resources/org/jenkinsci/test/acceptance/selenium/overflow.js src/main/resources/org/jenkinsci/test/acceptance/selenium/scroller.js src/test/java/plugins/MatrixAuthPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/45d11e57750d9ed71b52aadab16c41f73ad4eaba Log: Merge pull request #97 from andresrc/JENKINS-34411 
JENKINS-34411 Horizontal scrolling and scrolling overflows 
Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/066f75f7a7ea...45d11e57750d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-34411) Horizontal scrolling & overflow issues

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

 
 
 
 
 
 
 
  Re: Horizontal scrolling & overflow issues  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Andres Rodriguez Path: src/main/java/org/jenkinsci/test/acceptance/selenium/Scroller.java src/main/resources/org/jenkinsci/test/acceptance/selenium/scroller.js src/test/java/plugins/MatrixAuthPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/254d0151d26d3bf5e71e891650c2303b49b91d49 Log: JENKINS-34411 Account also for horizontal scrolling 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-34411) Horizontal scrolling & overflow issues

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

 
 
 
 
 
 
 
  Re: Horizontal scrolling & overflow issues  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Andres Rodriguez Path: src/main/resources/org/jenkinsci/test/acceptance/selenium/overflow.js http://jenkins-ci.org/commit/acceptance-test-harness/ddc1dac7ff3e036f6d0363e7e698f076b9fd7d5d Log: JENKINS-34411 Better CSS element selection. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-34411) Horizontal scrolling & overflow issues

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

 
 
 
 
 
 
 
  Re: Horizontal scrolling & overflow issues  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Andres Rodriguez Path: src/main/java/org/jenkinsci/test/acceptance/selenium/Scroller.java src/main/resources/org/jenkinsci/test/acceptance/selenium/overflow.js http://jenkins-ci.org/commit/acceptance-test-harness/bf4ecc5ae18566b85853a663bc13733007911fb5 Log: JENKINS-34411 Add overflow override. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


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

2016-05-09 Thread bkris...@ra.rockwell.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brian Krische commented on  JENKINS-32681 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Option to disable script security approval  
 
 
 
 
 
 
 
 
 
 
Why was this closed? This seems like a legitimate request. The use case would be: 
 

A Jenkins administrator and/or a group of trusted users are the only ones able to create jobs.
 

Regular users are only able run jobs.
 
 
If the job creators need functionality outside of the whitelisted/sandbox methods; then they have to approve those scripts. If you have a lot of jobs or your job configurations come from automated methods (version control, provisioning software like puppet or chef); it's not exactly easy or efficient to have another step to approve the scripts. 
In the scenario I describe (trusted job creators and script writers but "untrusted" job runners), script security isn't needed. In that scenario, administrators should be able to disable script security for Groovy Postbuild so that it works like it did prior to the 2.0 release. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [p4-plugin] (JENKINS-24003) Unable to wipe out workspace

2016-05-09 Thread dant...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dan tran commented on  JENKINS-24003 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to wipe out workspace  
 
 
 
 
 
 
 
 
 
 
the fix is in 1.3.9? Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34573) Running out of Heap Memory (2048m)

2016-05-09 Thread raymond.acc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raymond Accary commented on  JENKINS-34573 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Running out of Heap Memory (2048m)  
 
 
 
 
 
 
 
 
 
 
Daniel Beck, here's the generated heap-dump : https://www.dropbox.com/s/5zly2hmbi8dvjop/heapdump.hprof?dl=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] [multiple-scms-plugin] (JENKINS-27674) Build change history is no longer displayed

2016-05-09 Thread dant...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dan tran commented on  JENKINS-27674 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build change history is no longer displayed  
 
 
 
 
 
 
 
 
 
 
version 0.6 wiht STS latest 1.65x does not show detail changes log. only see 'unknown' 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-34687) Analysis plugins should_return_results_via_remote_api failing

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34687 
 
 
 
  Analysis plugins should_return_results_via_remote_api failing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

Summary:
 
 CheckStylePluginTest. Analysis plugins should_return_results_via_remote_api failing 
 
 
 

Component/s:
 
 analysis-core-plugin 
 
 
 
 
 
 
 
 
 
 See https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/CheckStylePluginTest/should_return_results_via_remote_api/ , https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/PmdPluginTest/should_return_results_via_remote_api/, and https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/TaskScannerPluginTest/should_return_results_via_remote_api/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 

[JIRA] [acceptance-test-harness] (JENKINS-34689) PmdPluginTest.should_return_results_via_remote_api failing

2016-05-09 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Bayer resolved as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34689 
 
 
 
  PmdPluginTest.should_return_results_via_remote_api failing  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andrew Bayer 
 
 
 

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] [acceptance-test-harness] (JENKINS-34689) PmdPluginTest.should_return_results_via_remote_api failing

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34689 
 
 
 
  PmdPluginTest.should_return_results_via_remote_api failing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/May/09 3:30 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
See https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/PmdPluginTest/should_return_results_via_remote_api/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This 

[JIRA] [mercurial-plugin] (JENKINS-30189) Add option to ignore certain commits, e.g. by user

2016-05-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-30189 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add option to ignore certain commits, e.g. by user  
 
 
 
 
 
 
 
 
 
 
JENKINS-7239 seems more useful. Most likely you do not so much care about which user made the change, as the fact that the change only touched a particular file (version.properties or the like) which you do not consider interesting enough to warrant a new build. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [acceptance-test-harness] (JENKINS-34690) Analysis collector ATH tests failing

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34690 
 
 
 
  Analysis collector ATH tests failing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness, analysis-collector-plugin 
 
 
 

Created:
 

 2016/May/09 3:34 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
See https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/AnalysisCollectorPluginTest/should_store_trend_selection_in_cookie/, https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/AnalysisCollectorPluginTest/should_have_trend_graph_with_relative_links/ and https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/AnalysisCollectorPluginTest/should_have_clickable_trend_details/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 

[JIRA] [acceptance-test-harness] (JENKINS-34688) AntPluginTest.locallyInstalledAnt failing

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34688 
 
 
 
  AntPluginTest.locallyInstalledAnt failing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/May/09 3:29 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
See https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/AntPluginTest/locallyInstalledAnt/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA 

[JIRA] [acceptance-test-harness] (JENKINS-34687) CheckStylePluginTest.should_return_results_via_remote_api failing

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34687 
 
 
 
  CheckStylePluginTest.should_return_results_via_remote_api failing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/May/09 3:28 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
See https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/CheckStylePluginTest/should_return_results_via_remote_api/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 


[JIRA] [acceptance-test-harness] (JENKINS-34686) NodeLabelParameterPluginTest.run_on_online_slave_and_master_with_node_restriction failing

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34686 
 
 
 
  NodeLabelParameterPluginTest.run_on_online_slave_and_master_with_node_restriction failing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/May/09 3:27 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
See https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/NodeLabelParameterPluginTest/run_on_online_slave_and_master_with_node_restriction/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 

[JIRA] [acceptance-test-harness] (JENKINS-34685) NodeLabelParameterPluginTest.run_on_several_slaves failing

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34685 
 
 
 
  NodeLabelParameterPluginTest.run_on_several_slaves failing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oliver Gondža 
 
 
 

Components:
 

 acceptance-test-harness 
 
 
 

Created:
 

 2016/May/09 3:26 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andrew Bayer 
 
 
 
 
 
 
 
 
 
 
See https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/1876/testReport/plugins/NodeLabelParameterPluginTest/run_on_several_slaves/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This 

[JIRA] [jclouds-plugin] (JENKINS-34684) Jcloud - Unable to create build nodes in Openstack cloud

2016-05-09 Thread fr...@fritz-elfert.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Fritz Elfert commented on  JENKINS-34684 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jcloud - Unable to create build nodes in Openstack cloud  
 
 
 
 
 
 
 
 
 
 
Obviously, something in the openstack response has changed (some single value was expected, but an array value was returned). Similar exceptions have been noticed before, when some openstack components had been updated. To find out the exact reason, please upload the json response again, but NOT beautified but as a single line. Otherwise it is impossible to determine what element started at column 930 originally. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34628) Jenkins core contains dependencies with external static resources

2016-05-09 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-34628 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins core contains dependencies with external static resources  
 
 
 
 
 
 
 
 
 
 
I agree with the change. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34629) Address some NPM warnings

2016-05-09 Thread rec...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34629 
 
 
 
  Address some NPM warnings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [port-allocator-plugin] (JENKINS-31449) Port Allocator Pipeline support

2016-05-09 Thread andre...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Rodriguez stopped work on  JENKINS-31449 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Andres Rodriguez 
 
 
 

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] [port-allocator-plugin] (JENKINS-31449) Port Allocator Pipeline support

2016-05-09 Thread andre...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Rodriguez assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31449 
 
 
 
  Port Allocator Pipeline support  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andres Rodriguez 
 
 
 

Assignee:
 
 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 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] [docker-workflow-plugin] (JENKINS-34654) support copy file from image

2016-05-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34654 
 
 
 
  support copy file from image  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Jesse Glick Nicolas De Loof 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-workflow-plugin] (JENKINS-34654) support copy file from image

2016-05-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick started work on  JENKINS-34654 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

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] [powershell-plugin] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin

2016-05-09 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-34581 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Please add support for Pipelines to the Powershell plugin  
 
 
 
 
 
 
 
 
 
 
For now you should use the bat step with powershell.exe. Making Powershell be a SimpleBuildStep is a bad idea. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-24591) Unable to run perforce commands within build steps

2016-05-09 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Released 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-24591 
 
 
 
  Unable to run perforce commands within build steps  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

Status:
 
 Reopened 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] [jclouds-plugin] (JENKINS-34684) Jcloud - Unable to create build nodes in Openstack cloud

2016-05-09 Thread davegood...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dave goodine created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34684 
 
 
 
  Jcloud - Unable to create build nodes in Openstack cloud  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Fritz Elfert 
 
 
 

Attachments:
 

 jenkins.log.20160509, openstack-response.json 
 
 
 

Components:
 

 jclouds-plugin 
 
 
 

Created:
 

 2016/May/09 2:42 PM 
 
 
 

Environment:
 

 Jenkins Version: 1.580.1  jclouds plugin: 2.8.1-1  Openstack Versions: Icehouse - nova, keystone, neutron; Kilo - glance, cinder  
 
 
 

Labels:
 

 slave jclouds 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 dave goodine 
 
 
 
 
 
 
 
 
 
 
In the last few days, our Jenkins master has lost the ability to communicate with our Openstack installation. When jenkins tries to create a slave, or reconnect to existing slaves after a Jenkins restart, there is an error

[JIRA] [github-branch-source-plugin] (JENKINS-33161) Allow merge commits to be built from origin PRs

2016-05-09 Thread pw...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Wolf commented on  JENKINS-33161 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow merge commits to be built from origin PRs  
 
 
 
 
 
 
 
 
 
 
Yes, Nicholas Brown. We will make sure to include this in BB as well. Our goal is to have as much parity between GH and BB as possible. My first comment was to that effect. Antonio Muñiz 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-25145) Version Jenkins Configuration In Perforce

2016-05-09 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Change 17263 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-25145 
 
 
 
  Version Jenkins Configuration In Perforce   
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

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] [core] (JENKINS-34683) Do not print stack trace if plugin is missing dependencies

2016-05-09 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carlos Sanchez closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34683 
 
 
 
  Do not print stack trace if plugin is missing dependencies  
 
 
 
 
 
 
 
 
 

Change By:
 
 Carlos Sanchez 
 
 
 

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] [core] (JENKINS-34683) Do not print stack trace if plugin is missing dependencies

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

 
 
 
 
 
 
 
  Re: Do not print stack trace if plugin is missing dependencies  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Carlos Sanchez Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/PluginWrapper.java core/src/main/java/hudson/model/UpdateCenter.java core/src/main/java/jenkins/MissingDependencyException.java http://jenkins-ci.org/commit/jenkins/3e1bc969f4eca2ae243f35e72a0a577a40cf2a0c Log: JENKINS-34683 Do not print stack trace if plugin is missing dependencies (#2048) 
JENKINS-34683 - Do not print stack trace if plugin is missing dependencies 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34629) Address some NPM warnings

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

 
 
 
 
 
 
 
  Re: Address some NPM warnings  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: war/package.json http://jenkins-ci.org/commit/jenkins/d7852479fc60afb8d3018cc5596977987812ac6a Log: JENKINS-34629 jenkins-ui (NPM module) is private, used only internally (#2316) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34647) Migrate to 2.x parent pom

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

 
 
 
 
 
 
 
  Re: Migrate to 2.x parent pom  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: .gitignore pom.xml http://jenkins-ci.org/commit/durable-task-plugin/0f09bb54a1b739d944425f16a7c8b736730ecf24 Log: Merge pull request #22 from armfergom/

JENKINS-34647
 


JENKINS-34647
 Migrate to 2.x parent pom. 
Compare: https://github.com/jenkinsci/durable-task-plugin/compare/54e3d3159862...0f09bb54a1b7 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34647) Migrate to 2.x parent pom

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

 
 
 
 
 
 
 
  Re: Migrate to 2.x parent pom  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Armando Fernandez Path: .gitignore pom.xml http://jenkins-ci.org/commit/durable-task-plugin/37e3d6a9967b21fee4a9ff102fb1ea788b387d2a Log: 

JENKINS-34647
 Migrate to 2.x parent pom. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [durable-task-plugin] (JENKINS-34647) Migrate to 2.x parent pom

2016-05-09 Thread afernan...@cloudbees.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Armando Fernandez resolved as Done 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34647 
 
 
 
  Migrate to 2.x parent pom  
 
 
 
 
 
 
 
 
 

Change By:
 
 Armando Fernandez 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Done 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33841) Support for pipeline builds

2016-05-09 Thread nickbr...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Brown commented on  JENKINS-33841 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Support for pipeline builds  
 
 
 
 
 
 
 
 
 
 
Perhaps some overlaps with this? https://github.com/jenkinsci/stashnotifier-plugin/issues/92 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-24003) Unable to wipe out workspace

2016-05-09 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Change 19090 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-24003 
 
 
 
  Unable to wipe out workspace  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

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] [p4-plugin] (JENKINS-34541) correct typo: Trust missmatch! Server fingerprint:

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

 
 
 
 
 
 
 
  Re: correct typo: Trust missmatch! Server fingerprint:  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/client/ConnectionFactory.java http://jenkins-ci.org/commit/p4-plugin/6cfa721efc8607b9812364b7e002a3a27562e431 Log: Typo missmatch. 


JENKINS-34541
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-34541) correct typo: Trust missmatch! Server fingerprint:

2016-05-09 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34541 
 
 
 
  correct typo: Trust missmatch! Server fingerprint:  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

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] [android-emulator-plugin] (JENKINS-33156) Make android-emulator plugin Pipeline-friendly

2016-05-09 Thread ahorn...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andy Horner commented on  JENKINS-33156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Make android-emulator plugin Pipeline-friendly  
 
 
 
 
 
 
 
 
 
 
I think a step like this would work quite well 

 

Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml


step([
$class: 'AndroidEmulator',
osVersion: 'android-23',
screenResolution: '1080x1920',
screenDensity: 'xxhdpi',
deviceLocale: 'en_US',
targetAbi: 'x86',
sdCardSize: '200M',
showWindow: true,
commandLineOptions: '-noaudio -gpu mesa -qemu -m 1024 -enable-kvm'
])
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-33858) Improvement of the P4 Trigger functionality

2016-05-09 Thread pal...@perforce.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-33858 
 
 
 
  Improvement of the P4 Trigger functionality  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Allen 
 
 
 

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.


  1   2   3   >