date:20151210

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to stephenconnolly 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I had success in the past by providing a unique description. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31991 
 
 
 
  In the Parameter page of a build, credentials values are shown by name, which is not unique  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Component/s:
 
 credentials-plugin 
 
 
 

Component/s:
 
 core 
 
 
 

Assignee:
 
 stephenconnolly 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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://grou

[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-31982) Jenkins UI hangs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck assigned an issue to Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thread Dump basics (and I really hope I'm right with a comment like this ): 
 

Look for "BLOCKED" threads
 

Lock for what object they're blocked on (in this case 4eafeafb)
 

Look for the one thread that owns it (in this case Executor #1 for AMT2-slave)
 

Look at what it does (in this case hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canTake)
 
 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31982 
 
 
 
  Jenkins UI hangs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Component/s:
 
 throttle-concurrent-builds-plugin 
 
 
 

Component/s:
 
 core 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [maven-plugin] (JENKINS-20594) Expose parsed maven project version

2015-12-10 Thread as_kuml...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ali Sadik Kumlali commented on  JENKINS-20594 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Expose parsed maven project version  
 
 
 
 
 
 
 
 
 
 
+1 
POM_VERSION_MAJOR and POM_VERSION_MINOR variables would be quite useful for pipeline version. (e.g. ${POM_VERSION_MAJOR}.${POM_VERSION_MINOR}.${SVN_REVISION}.${BUILD_NUMBER} ) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [sectioned-view-plugin] (JENKINS-24804) javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 227340>200000

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-24804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 227340>20  
 
 
 
 
 
 
 
 
 
 
Alin Stelian The fix Jesse referenced, 

JENKINS-20327
, went into 1.639. So when you're saying it's still in Jenkins today you seem to still be living in October  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-31982) Jenkins UI hangs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-31982 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins UI hangs  
 
 
 
 
 
 
 
 
 
 
1.609.x release should have been solved the problem with UI hanging. That release introduced the asynchronous queue. In addition, UI has caching of queue items. So I would not expect TCB plugin to cause hanging in 1.532. 
BTW it needs an investigation 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [sectioned-view-plugin] (JENKINS-24804) javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 227340>200000

2015-12-10 Thread alinn...@waterford.org (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alin Stelian commented on  JENKINS-24804 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 227340>20  
 
 
 
 
 
 
 
 
 
 
Daniel Beck but you can see the time when I've added the comment  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [other] (JENKINS-31442) Jenkins Wrong Build History (Dec 31, 1969)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Won't Fix 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The Checkmarx plugin/CxSuite plugin is not distributed via the Jenkins community update site, so this is not the right place to report a bug about it. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31442 
 
 
 
  Jenkins Wrong Build History (Dec 31, 1969)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Won't 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] [workflow-plugin] (JENKINS-31154) 2.0: provide better workflow visualization out of the box

2015-12-10 Thread jgpa...@btinternet.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jon Payne commented on  JENKINS-31154 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: 2.0: provide better workflow visualization out of the box  
 
 
 
 
 
 
 
 
 
 
+1 Exactly the same situation here, workflow/pipelines would be very beneficial, both simplifying and enhancing some pipelines that we currently hack together using other plugins, but without visualization we cannot use it. Role on Jan 2016  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [email-ext-plugin] (JENKINS-32003) Job Config.xml is broken if using HTML tags in email template

2015-12-10 Thread adm...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Yu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32003 
 
 
 
  Job Config.xml is broken if using HTML tags in email template  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Alex Earl 
 
 
 

Components:
 

 email-ext-plugin 
 
 
 

Created:
 

 10/Dec/15 9:57 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.638 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Alex Yu 
 
 
 
 
 
 
 
 
 
 
1. Create free style job 2. Add new template and put html tags to email template field 3. Open job config http: //  {jenkins} 
 / job /  {job_name} 
 /config.xml 4. Xml structure is broken, all html tags from template should be escaped For example:

[JIRA] [maven-plugin] (JENKINS-31524) SurefireArchiver ignores updated results when multiple testing plug-ins use the same reports directory

2015-12-10 Thread apr...@tibco.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31524 
 
 
 
  SurefireArchiver ignores updated results when multiple testing plug-ins use the same reports directory  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrian Price 
 
 
 

Summary:
 
 SurefireArchiver ignores updated results when multiple testing plug-ins  configured  use the same reports directory 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-23271) Intermittent Invalid Object ID in remoting module

2015-12-10 Thread patrickdeping...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas De Schampheleire commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
Oleg Nenashev: thanks for the feedback. With this reproduction scenario, given that you are the assignee, does this mean you are currently looking at this? Have you been able to zoom in on the problem? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-23271) Intermittent Invalid Object ID in remoting module

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
Thomas De Schampheleire Yes I'm looking at the issue, but currently there is no ETA. We firstly want to get a scenario with a high reproduction rate. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-23271) Intermittent Invalid Object ID in remoting module

2015-12-10 Thread patrickdeping...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas De Schampheleire commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
Oleg Nenashev Understood, thanks. I'm looking forward to more details when you have them. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32004) Unable to Export Job Results with HP ALM QC Plugin

2015-12-10 Thread sergio_costa...@hotmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sergio costa created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32004 
 
 
 
  Unable to Export Job Results with HP ALM QC Plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ofir Shaked 
 
 
 

Components:
 

 hp-application-automation-tools-plugin 
 
 
 

Created:
 

 10/Dec/15 10:04 AM 
 
 
 

Environment:
 

 Jenkins ver. 1.606  ALM plugin ver. 4.0  ALM QC ver. 11.52 
 
 
 

Labels:
 

 plugin jenkins alm 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 sergio costa 
 
 
 
 
 
 
 
 
 
 
Apparently the plugin works fine and it creates the folder in QC, where its specified with Test Folder and Test set Folder fields. 
The problem is that it is not creating testset and always give me the same error: 
INFO: 'Upload test result to ALM' Post Build Step is being invoked. INFO: 1 test result file found. INFO: Start to upload /jenkinsm/data/jobs/JenkinsTest/builds/22/htmlreports/HTML_Report/TEST-features-JenkinsTest.xml INFO: Start to parse file: /jenkinsm/data/jobs/EthaJenkinsTest/builds/22/htmlreports/HTML_Report/TEST-features-JenkinsTest.xml INFO: parse resut file succeed. INFO: Start t

[JIRA] [hp-application-automation-tools-plugin] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC

2015-12-10 Thread sergio_costa...@hotmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sergio costa updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32004 
 
 
 
  HP Automation Tools Unable to Export Job Results to QC  
 
 
 
 
 
 
 
 
 

Change By:
 
 sergio costa 
 
 
 

Summary:
 
 HP Automation Tools Unable to Export Job Results  with HP ALM  to  QC  Plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [email-ext-plugin] (JENKINS-32003) Job Config.xml is broken if using HTML tags in email template

2015-12-10 Thread adm...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Yu resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32003 
 
 
 
  Job Config.xml is broken if using HTML tags in email template  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Yu 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Assignee:
 
 Alex  Earl  Yu 
 
 
 

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] [email-ext-plugin] (JENKINS-32003) Job Config.xml is broken if using HTML tags in email template

2015-12-10 Thread adm...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Yu closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32003 
 
 
 
  Job Config.xml is broken if using HTML tags in email template  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex Yu 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-31982) Jenkins UI hangs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-31982 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins UI hangs  
 
 
 
 
 
 
 
 
 
 
Wait, what? 

Jenkins 1.532
 
Is this a typo, or is the instance 100+ versions behind? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-31982) Jenkins UI hangs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-31982 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins UI hangs  
 
 
 
 
 
 
 
 
 
 
Not a typo, runs Java 6. 
Oleg Nenashev Do you still care about that version for the plugin? From a core POV I don't, too old. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-31982) Jenkins UI hangs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-31982 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins UI hangs  
 
 
 
 
 
 
 
 
 
 
I suspect it was my mistake. I've thought that the bug is for 1.632... For 1.532 the situation is pretty obvious - such delays happen. The best recommendation would be update the core. We made several attempts to solve the performance issue as a part of JENKINS-27650, but we didn't manage to improve it enough. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-31982) Jenkins UI hangs

2015-12-10 Thread silvi...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Silviu Marchis commented on  JENKINS-31982 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins UI hangs  
 
 
 
 
 
 
 
 
 
 
1.532.2 more specifically. Yes the system is fairly behind, mostly because it was critical that the system was stable, so no one tinkered with it. But now there is this problem and we are strongly considering upgrading to a newer LTS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [testng-plugin] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests

2015-12-10 Thread rks.bc...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 rakesh singh commented on  JENKINS-20985 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: TestNG plugin should has a possibility to use thresholds for failed tests  
 
 
 
 
 
 
 
 
 
 
Is there any update is available to mark build as Stable if some configuration test cases failed ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-28492 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection.  
 
 
 
 
 
 
 
 
 
 
I think the "IP address" here may be the slave name? If so, there may also be two machines claiming to be the same slave. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-30092) node that is marked tempoarily offline is lost across restart

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30092 
 
 
 
  node that is marked tempoarily offline is lost across restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31258) Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins

2015-12-10 Thread apr...@tibco.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31258 
 
 
 
  Jenkins Maven plug-in ignores JUnit-format test results from unknown Maven plug-ins  
 
 
 
 
 
 
 
 
 
 
Fixed in Pull Request #56. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrian Price 
 
 
 
 
 
 
 
 
 
 The Jenkins Maven plug-in ignores JUnit format files in the test results directory ($\{project.build.directory\}/surefire-reports by default). Debugging revealed the cause to be that maven-plugin knows about certain\* test-capable MOJOs and attempts to support unknown MOJOs by making  the following unjustifiable  assumptions  which may or may not be justified, depending on the MOJO in question :# that the MOJO will target the 'test' goal or similar# that the MOJO configuration will have a 'reportsDirectory' property\* maven testing plug-ins known to the Jenkins Maven plug-in / project type as of 2014-12-04 13:40:29:* org.apache.maven.plugins:maven-surefire-plugin* net.kennychua:phantomjs-qunit-runner* org.apache.maven.plugins:maven-failsafe-plugin* com.sun.maven:maven-junit-plugin* org.sonatype.flexmojos:flexmojos-maven-plugin* org.sonatype.tycho:maven-osgi-test-plugin* org.eclipse.tycho:tycho-surefire-plugin* com.jayway.maven.plugins.android.generation2:maven-android-plugin* com.jayway.maven.plugins.android.generation2:android-maven-plugin* org.codehaus.mojo:gwt-maven-plugin* com.smartbear.soapui:soapui-maven-plugin* com.smartbear.soapui:soapui-pro-maven-plugin* com.github.redfish4ktc.soapui:maven-soapui-extension-plugin* com.github.searls:jasmine-maven-plugin* org.terracotta.maven.plugins:toolkit-resolver-plugin* org.scalatest:scalatest-maven-plugin* org.nanoko.playframework:play2-maven-pluginExamples of unknown/unsupported Maven test-capable plug-ins:* com.github.eirslett:frontend-maven-plugin:karma* com.kelveden:maven-karma-plugin:start* com.github.greengerong:maven-ng-protractor:run* org.codehaus.mojo:exec-maven-plugin:exec (can launch any arbitrary testing process)* others, doubtless...In the general 'unknown Maven plug-in' case neither of these assumptions are likely to be valid e.g., com.github.eirslett:frontend-maven-plugin running Karma tests, the goal is 'karma' (phase = 'test' or 'integration-test', typically) and the test output directory is configured in a separate karma.conf.js file.Overall, this means there is no general solution for reporting standard JUnit-format results that have been placed in the Maven-standard location for such results, other than to use only plug-ins that the Jenkins Maven plugin actually knows about! This is inflexible and an unreasonable limitation for a general-purpose CI tool and a highly extensible build tool. I see three possible solutions:# The Jenkins Job configuration for Maven projects provides some declarative means to identify additional test reports.-- PROs:--- straightforward to configure--- no Jenkins-specific POM changes required--- only one set of changes required-- CONs:--- requires explicit configuration in e

[JIRA] [hp-application-automation-tools-plugin] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC

2015-12-10 Thread sergio_costa...@hotmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sergio costa updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32004 
 
 
 
  HP Automation Tools Unable to Export Job Results to QC  
 
 
 
 
 
 
 
 
 

Change By:
 
 sergio costa 
 
 
 
 
 
 
 
 
 
 Apparently the plugin works fine and it creates the folder in QC, where its specified with Test Folder and Test set Folder fields.The problem is that it is not creating testset and always give me the same error:INFO: 'Upload test result to ALM' Post Build Step is being invoked.INFO: 1 test result file found.INFO: Start to upload /jenkinsm/data/jobs/JenkinsTest/builds/22/htmlreports/HTML_Report/TEST-features-JenkinsTest.xmlINFO: Start to parse file: /jenkinsm/data/jobs/ EthaJenkinsTest JenkinsTest /builds/22/htmlreports/HTML_Report/TEST-features-JenkinsTest.xmlINFO: parse resut file succeed.INFO: Start to login to ALM Server.Logged in successfully to ALM Server http://X/qcbin/ using INFO: Checking test folder...INFO: Checking testset folder...INFO: Uploading ALM Entities...*Failed to create Entity:test-sets:parent-id=105name=JenkinsTest Testsubtype-id=hp.qc.test-set.external*INFO: Uploaded /jenkinsm/data/jobs/ EthaJenkinsTest JenkinsTest /builds/22/htmlreports/HTML_Report/TEST-features-JenkinsTest.xml.INFO: 'Upload test result to ALM' Completed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31524) SurefireArchiver ignores updated results when multiple testing plug-ins use the same reports directory

2015-12-10 Thread apr...@tibco.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Price commented on  JENKINS-31524 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SurefireArchiver ignores updated results when multiple testing plug-ins use the same reports directory  
 
 
 
 
 
 
 
 
 
 
Fixed in Pull Request #56. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31718) JNLP slaves can fail to correctly negotiate a transport

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31718 
 
 
 
  JNLP slaves can fail to correctly negotiate a transport  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Labels:
 
 lts 1.625.3 - candidate fixed  regression 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-23271) Intermittent Invalid Object ID in remoting module

2015-12-10 Thread zilvinas.sal...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Z. S. commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
So we've been plagued by this issue a long time. And have some good tips how to reproduce it .. Get a matrix job with 10+ jobs .. and make each one copy an artifact like a big jar (hundreds of megs) from another job in jenkins. The issue seems to happen when all the matrix jobs at the same time pull the artifact. We reduce the problem by putting some sleeps in the matrix jobs to make sure it doesnt run at the same time. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-23271) Intermittent Invalid Object ID in remoting module

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-23271 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Intermittent Invalid Object ID in remoting module  
 
 
 
 
 
 
 
 
 
 
Yep, looks to be similar to what we've seen with R Tyler 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jes Struck edited a comment on  JENKINS-26726 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)  
 
 
 
 
 
 
 
 
 
 Hi, I'm having a similar issue, but both of my pipelines/build chains, are including the one Projects that has Subprojects, and my problem comes when both of the shown the first of these subprojects.Setup:Jenkins:   1.609.3Delivery Pipeline view: 0.9.7my current workaround is to only let one of the pipelines to be shown fully, and the other pipeline is only showing the job's from first job, toward the job the has subprojects but not showing the subsubprojects in this pipeline, which is fare from ideal. [^attachment-name.zip]!attachment-name.jpg|thumbnail! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jes Struck reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Hi, I'm having a similar issue, but both of my pipelines/build chains, are including the one Projects that has Subprojects, and my problem comes when both of the shown the first of these subprojects. 
Setup: Jenkins: 1.609.3 Delivery Pipeline view: 0.9.7 
my current workaround is to only let one of the pipelines to be shown fully, and the other pipeline is only showing the job's from first job, toward the job the has subprojects but not showing the subsubprojects in this pipeline, which is fare from ideal.[^attachment-name.zip]Unable to render embedded object: File (attachment-name.jpg) not found. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26726 
 
 
 
  java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jes Struck 
 
 
 

Resolution:
 
 Cannot Reproduce 
 
 
 

Status:
 
 Closed Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [git-plugin] (JENKINS-31998) Help for feature: Repository URL Failed to connect to repository : Remote host closed connection during handshake

2015-12-10 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The Jenkins project doesn't use bug reports to request technical support help from other users. Bug reports are read by far fewer people than the mailing list, so there is much less chance of help from a bug report than from a message to the jenkins-users mailing list. Please continue to use the mailing list (and google search and other resources) to answer technical support questions. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31998 
 
 
 
   Help for feature: Repository URL Failed to connect to repository : Remote host closed connection during handshake  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

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 option

[JIRA] [git-plugin] (JENKINS-31998) Help for feature: Repository URL Failed to connect to repository : Remote host closed connection during handshake

2015-12-10 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31998 
 
 
 
   Help for feature: Repository URL Failed to connect to repository : Remote host closed connection during handshake  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jes Struck updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-26726 
 
 
 
  java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jes Struck 
 
 
 

Attachment:
 
 jenkins_Delivery_pipeline_exception.log 
 
 
 

Attachment:
 
 Job_setup.jpg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jes Struck edited a comment on  JENKINS-26726 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)  
 
 
 
 
 
 
 
 
 
 Hi, I'm having a similar issue, but both of my pipelines/build chains, are including the one Projects that has Subprojects, and my problem comes when both of the shown the first of these subprojects.Setup:Jenkins:   1.609.3Delivery Pipeline view: 0.9.7my current workaround is to only let one of the pipelines to be shown fully, and the other pipeline is only showing the job's from first job, toward the job the has subprojects but not showing the subsubprojects in this pipeline, which is fare from ideal. I have tried to explain my job setup in this image !Job_setup.jpg|thumbnail!and attached a stacktrace from the log 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31954) StackOverflow in hudson.model.Descriptor$NewInstanceBindInterceptor.onConvert

2015-12-10 Thread nico.bol...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nico Bollen commented on  JENKINS-31954 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: StackOverflow in hudson.model.Descriptor$NewInstanceBindInterceptor.onConvert  
 
 
 
 
 
 
 
 
 
 
Issue still available in Jenkins 1.641 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-32005) Xfvb plugin doesn't remember displayname set via the configuration page

2015-12-10 Thread a3aan.wi...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adriaan Wisse created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32005 
 
 
 
  Xfvb plugin doesn't remember displayname set via the configuration page  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 zregvart 
 
 
 

Components:
 

 xvfb-plugin 
 
 
 

Created:
 

 10/Dec/15 1:36 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Adriaan Wisse 
 
 
 
 
 
 
 
 
 
 
When setting the displayname in the xvfb plugin for a specific job using the advanced settings it will not be stored/remembered after saving. 
I'm using version 1.1.1. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [job-dsl-plugin] (JENKINS-31790) Add support for Ansible Plugin

2015-12-10 Thread lan...@yandex.ru (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev commented on  JENKINS-31790 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add support for Ansible Plugin  
 
 
 
 
 
 
 
 
 
 
Think it can be done as extension point in plugin itself. I'll try to do so on weekend 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy

2015-12-10 Thread eva...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evan Wee commented on  JENKINS-28289 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy  
 
 
 
 
 
 
 
 
 
 
Hi, please ignore #62 as #55 has been redone and merged. 
Would appreciate if jenkinsci/remoting could 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] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy

2015-12-10 Thread eva...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Evan Wee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28289 
 
 
 
  JNLP slave should exclude non proxy hosts when connecting via HTTP proxy  
 
 
 
 
 
 
 
 
 

Change By:
 
 Evan Wee 
 
 
 
 
 
 
 
 
 
 https://issues.jenkins-ci.org/browse/JENKINS-6167The fix submitted for this issue does not take into account the excluded proxy hosts unlike the hudson.remoting.Util.openURLConnection method which implicitly excludes hosts.A fix using the same method as sun.net.www.protocol.http.HttpURLConnection is available here : https://github.com/hypnoce/remoting/commit/67dbd966e628c42a0aa4d3cd91a56a00b7f95030Thanks EDIT:An updated fix that resolves conflicts is here:https://github.com/jenkinsci/remoting/pull/62https://github.com/evanx9/remoting/commit/cb2ded8e8ba6a67dd5996a7ca90a2f4f133ec8eb 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [promoted-builds-plugin] (JENKINS-32006) Promoted Builds Plugin tries to fetch changes from Git

2015-12-10 Thread ole.su...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ole Kristian Sunde created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32006 
 
 
 
  Promoted Builds Plugin tries to fetch changes from Git  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 promoted-builds-plugin 
 
 
 

Created:
 

 10/Dec/15 2:05 PM 
 
 
 

Environment:
 

 Jenkins 1.625.2 on RHEL7 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Ole Kristian Sunde 
 
 
 
 
 
 
 
 
 
 
The promoted builds plugin will try to fetch changes from Git even though the promotion is being executed on a node without the original workspace. 
This happens after upgrading the promoted builds plugin from 2.23.1 to 2.24. 
After downgrading the plugin to 2.23.1 everything works fine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32001) Failure cause column not shown

2015-12-10 Thread tomas.westl...@sonymobile.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Westling commented on  JENKINS-32001 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failure cause column not shown  
 
 
 
 
 
 
 
 
 
 
I tried this out. If there are no failing builds with failure causes, nothing is shown.  This is fine imo, I don't see a reason to write "no failure causes" when nothing is found. 
The problem is that not even the column header is shown, which is due to the code for columnHeader.jelly just containing a nbsp and no text. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32001) Failure cause column not shown

2015-12-10 Thread tomas.westl...@sonymobile.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tomas Westling edited a comment on  JENKINS-32001 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failure cause column not shown  
 
 
 
 
 
 
 
 
 
 I tried this out. If there are no failing builds with failure causes, nothing is shown. This is fine imo, I don't see a reason to write "no failure causes" when nothing is found.The problem is that  not even  the column header is  never  shown,  even when failure causes exist,  which is due to the code for  columnHeader.jelly just containing a nbsp and no text. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32001) Failure cause column not shown

2015-12-10 Thread martin.sto...@iav.de (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Stolle commented on  JENKINS-32001 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failure cause column not shown  
 
 
 
 
 
 
 
 
 
 
Thanks for the reply. I guess the reason my column is not shown is that the downstream builds have the identified failures. The status page of the build correctly identifies the subproject and the failure cause, but this is not working in the view. 
But you are right, you can see the column failure cause if you look at the table with the downstream builds. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [credentials-plugin] (JENKINS-22078) SVN fails revision check for external subprojects

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 john little commented on  JENKINS-22078 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN fails revision check for external subprojects  
 
 
 
 
 
 
 
 
 
 
I have the same issue, it is not solved for us. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [build-failure-analyzer-plugin] (JENKINS-32001) Failure cause column not shown

2015-12-10 Thread martin.sto...@iav.de (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Stolle updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32001 
 
 
 
  Failure cause column not shown  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Stolle 
 
 
 
 
 
 
 
 
 
 Adding the column _ failure cause_ to a view has no effects  if the _failure cause_ is part of a downstream build . Not even the column header is shown. The HTML code shows that an extra column is created but completely without content. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [credentials-plugin] (JENKINS-22078) SVN fails revision check for external subprojects

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 john little edited a comment on  JENKINS-22078 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN fails revision check for external subprojects  
 
 
 
 
 
 
 
 
 
 I have the same issue, it is not solved for us  (brand new installation, settup credentials as directed) .  The issue only happens if some files were updated. It updates everything correctly, then fails with this error. Then I run the build again, and it works. So we have a flip flop between build which works, the one which doesnt, then one which does etc.  We need some way to always run the build twice! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [credentials-plugin] (JENKINS-22078) SVN fails revision check for external subprojects

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 john little edited a comment on  JENKINS-22078 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: SVN fails revision check for external subprojects  
 
 
 
 
 
 
 
 
 
 I have the same issue, it is not solved for us (brand new installation, settup credentials as directed). The issue only happens if some files were updated. It updates everything correctly, then fails with this error. Then I run the build again, and it works. So we have a flip flop between build which works,  the  then  one which doesnt, then one which does etc.  We need some way to always run the build twice! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ansible-plugin] (JENKINS-31790) Add support for Ansible Plugin

2015-12-10 Thread lan...@yandex.ru (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31790 
 
 
 
  Add support for Ansible Plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kirill Merkushev 
 
 
 

Labels:
 
 ansible-plugin job-dsl 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ansible-plugin] (JENKINS-31790) Add support for Ansible Plugin

2015-12-10 Thread lan...@yandex.ru (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kirill Merkushev updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31790 
 
 
 
  Add support for Ansible Plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kirill Merkushev 
 
 
 

Component/s:
 
 ansible-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 john little commented on  JENKINS-21785 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Check for changes in folders linked via svn:externals fails due to missing credentials  
 
 
 
 
 
 
 
 
 
 
in 15 years of using SVN, I have never had to use the realm, nor even known it existed. We have not found a way to get this yet. We are using assembla.com, and have raised a ticket with them to ask them to check their svnserve.conf files, as obviously we dont have access to this. It would a lot of someone could include some real exmaples of what these realms can be, and the entire string which must be pasted into the "Realm" box of the "additional credentials". 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31897) Default parameter value is not used

2015-12-10 Thread amu...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Antonio Muñiz started work on  JENKINS-31897 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Antonio Muñiz 
 
 
 

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] [hp-application-automation-tools-plugin] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC

2015-12-10 Thread sergio_costa...@hotmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sergio costa commented on  JENKINS-32004 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: HP Automation Tools Unable to Export Job Results to QC  
 
 
 
 
 
 
 
 
 
 
Apparently, the problem is that QC don't have hp.qc.test-set.external installed and don't recognize it. It would be nice if was possible to specify this configuration in plugin to use supported subtypes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-29141) trottle-concurrent-build-plugin allowes concureent jobs under circumstances

2015-12-10 Thread c.l...@clerenz.de (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Clemens Loos commented on  JENKINS-29141 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trottle-concurrent-build-plugin allowes concureent jobs under circumstances  
 
 
 
 
 
 
 
 
 
 
Is there any news on this issue? Since updating to jenkins 1.638 (was some 1.5XX before) I face the same issue. When two jobs are triggered nearly at the same time they start running in parallel. When I trigger them manually they will wait for each other. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-29141) trottle-concurrent-build-plugin allowes concureent jobs under circumstances

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-29141 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trottle-concurrent-build-plugin allowes concureent jobs under circumstances  
 
 
 
 
 
 
 
 
 
 
Clemens Loos there was no response from the submitter, so there was no way to proceed. 
For 1.638 it sounds interesting, because it should perform queue snap-shoting correctly. Could you please provide info about job types and other plugins you use? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [github-branch-source-plugin] (JENKINS-32007) There is no messages saying that the repositories listing is being built when it takes long time

2015-12-10 Thread adrien.lecharpent...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Lecharpentier created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32007 
 
 
 
  There is no messages saying that the repositories listing is being built when it takes long time  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 

Components:
 

 github-branch-source-plugin 
 
 
 

Created:
 

 10/Dec/15 3:31 PM 
 
 
 

Environment:
 

 github-branch-source-plugin:1.0 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Adrien Lecharpentier 
 
 
 
 
 
 
 
 
 
 
When we have a lot of repository to list (multiple organizations, etc.) building the list of repositories can take a long time. But there is no message on the UI to say that the list is building, so it looks like there is none. 
A message or a loading animation would be great for the UX. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-21785 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Check for changes in folders linked via svn:externals fails due to missing credentials  
 
 
 
 
 
 
 
 
 
 

We have not found a way to get this yet.
 
john little What about the dozens and dozens of comments on this issue explaining exactly this? Or the actual issue description that contains one possible way to determine the realm name directly below the giant red 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] [github-branch-source-plugin] (JENKINS-31552) GitHub Multibranch Workflow: anonymous checkout credentials should be renamed

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31552 
 
 
 
  GitHub Multibranch Workflow: anonymous checkout credentials should be renamed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Labels:
 
 ux UX 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [github-branch-source-plugin] (JENKINS-32007) There is no messages saying that the repositories listing is being built when it takes long time

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32007 
 
 
 
  There is no messages saying that the repositories listing is being built when it takes long time  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Labels:
 
 UX 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-21785 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Check for changes in folders linked via svn:externals fails due to missing credentials  
 
 
 
 
 
 
 
 
 
 
Daniel Beck, I've decided don't add more comment here. There is enough information about this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 john little commented on  JENKINS-21785 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Check for changes in folders linked via svn:externals fails due to missing credentials  
 
 
 
 
 
 
 
 
 
 
For us, svn --no-auth-cache --config-dir invalid info proto://host:port/path/to/repo does not return any realm info. It returns: 
Path: ourproject URL: https://subversion.assembla.com/svn/ourrepo Relative URL: ^/ Repository Root: https://subversion.assembla.com/svn/ourrepo Repository UUID: 26850efa-2baa-4381-9140-fb0x Revision: 1755 Node Kind: directory Last Changed Author: me Last Changed Rev: 1755 Last Changed Date: 2015-12-10 15:23:10 +0100 (Thu, 10 Dec 2015) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [throttle-concurrent-builds-plugin] (JENKINS-29141) trottle-concurrent-build-plugin allowes concureent jobs under circumstances

2015-12-10 Thread c.l...@clerenz.de (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Clemens Loos commented on  JENKINS-29141 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: trottle-concurrent-build-plugin allowes concureent jobs under circumstances  
 
 
 
 
 
 
 
 
 
 
Hi Oleg Nenashev, these are my Plug-Ins: 
 

analysis-core: 1.74
 

ant: 1.2
 

antisamy-markup-formatter: 1.3
 

autojobs-plugin: 1.0
 

build-pipeline-plugin: 1.4.9
 

categorized-view: 1.8
 

checkstyle: 3.43
 

conditional-buildstep: 1.3.3
 

credentials: 1.24
 

cvs: 2.12
 

dashboard-view: 2.9.6
 

email-ext: 2.40.5
 

emma: 1.29
 

emmacoveragecolumn: 0.0.4
 

external-monitor-job: 1.4
 

fail-the-build-plugin: 1.0
 

findbugs: 4.62
 

flexible-publish: 0.14.1
 

git-client: 1.19.0
 

git: 2.4.0
 

greenballs: 1.15

[JIRA] [xvfb-plugin] (JENKINS-32005) Xfvb plugin doesn't remember displayname set via the configuration page

2015-12-10 Thread scm_issue_l...@java.net (JIRA)

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

 
 
 
 
 
 
 
  Re: Xfvb plugin doesn't remember displayname set via the configuration page  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/Xvfb.java http://jenkins-ci.org/commit/xvfb-plugin/471a35ef803387ce171a6936756293955c466a9a Log: JENKINS-32005 Xfvb plugin doesn't remember displayname set via the  
...configuration page. 
Compare: https://github.com/jenkinsci/xvfb-plugin/compare/2cdc2ceb9f53...471a35ef8033 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 john little commented on  JENKINS-21785 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Check for changes in folders linked via svn:externals fails due to missing credentials  
 
 
 
 
 
 
 
 
 
 
I just realized that jira "hid" 155 comments. I just read them all. we were seeing the following: 
 Assembla Restricted 
Several times, but assumed that the realm could not possible be " Assembla Restricted" as it has spaces in it. We have tried the following under realms: 
" Assembla Restricted" 
"" 
"Assembla Restricted" 
and "https://subversion.assembla.com:443" 
Not knowing which of these is the right way to go. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-10417) Error running builds with configuration matrix and TFS plugin

2015-12-10 Thread r...@mymilligan.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Milligan commented on  JENKINS-10417 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error running builds with configuration matrix and TFS plugin  
 
 
 
 
 
 
 
 
 
 
Any word on a fix for this issue? The Matrix project would solve many of my maintenance problems right now, but the TFS plugin isn't playing nice with it. Could it be configured to not create a workspace for the root build and only for the child builds when in a matrix project? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [xvfb-plugin] (JENKINS-32005) Xfvb plugin doesn't remember displayname set via the configuration page

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in version 1.1.2. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-32005 
 
 
 
  Xfvb plugin doesn't remember displayname set via the configuration page  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

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] [xvfb-plugin] (JENKINS-26555) Workflow plugin support

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closing old issues 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26555 
 
 
 
  Workflow plugin support  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [xvfb-plugin] (JENKINS-28147) Xvfb not terminated when a Maven module rebuild fails inside a plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closing old issues 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28147 
 
 
 
  Xvfb not terminated when a Maven module rebuild fails inside a plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [clang-scanbuild-plugin] (JENKINS-32008) Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration

2015-12-10 Thread francis.lab...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Labrie created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32008 
 
 
 
  Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Josh Kennedy 
 
 
 

Components:
 

 clang-scanbuild-plugin 
 
 
 

Created:
 

 10/Dec/15 4:27 PM 
 
 
 

Environment:
 

 OS X El Capitan 10.11.2  Xcode 7.2  iOS SDK 9.2 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Francis Labrie 
 
 
 
 
 
 
 
 
 
 
Since Xcode 7.2 upgrade including iOS SDK 9.2, Clang Scan-Build plugin can't perform task using the following parameters: 
 

Target SDK: iphonesimulator
 

Build Configuration: Debug
 
 
The iphonesimulator target SDK causes import errors like these: 

 

While building module 'UIKit' imported from /Users/jenkins/Home/jobs/eVA Mobile iOS Application/workspace/iOS-Application/Submodules/eVA Core iOS Library/Submodules/CGI Extensions iOS Library/Frameworks/CGIExte

[JIRA] [xvfb-plugin] (JENKINS-26504) Cannot run low numbered builds with xvfb in jenkins 1.597

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closing old issues 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26504 
 
 
 
  Cannot run low numbered builds with xvfb in jenkins 1.597  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [xvfb-plugin] (JENKINS-26505) java.lang.IllegalArgumentException: Prefix string too short org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.launchXvfb(XvfbBuildWrapper.java:484)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Duplicate 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closing old issues. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-26505 
 
 
 
  java.lang.IllegalArgumentException: Prefix string too short org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.launchXvfb(XvfbBuildWrapper.java:484)  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [xvfb-plugin] (JENKINS-28928) Make XvfbBuildWrapper extend SimpleBuildWrapper

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zregvart closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Closing old issues 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28928 
 
 
 
  Make XvfbBuildWrapper extend SimpleBuildWrapper  
 
 
 
 
 
 
 
 
 

Change By:
 
 zregvart 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [clang-scanbuild-plugin] (JENKINS-32008) Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration

2015-12-10 Thread francis.lab...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Francis Labrie updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32008 
 
 
 
  Failure with Xcode 7.2 with iphonesimulator Target SDK and Debug Build Configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Francis Labrie 
 
 
 

Environment:
 
 OS X El Capitan 10.11.2Xcode 7.2iOS SDK 9.2 checker 277 (October 28, 2015) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31986) OS-related problems with Maven parameters (from job or from build step)

2015-12-10 Thread n...@bardelot.fr (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noël Bardelot commented on  JENKINS-31986 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: OS-related problems with Maven parameters (from job or from build step)  
 
 
 
 
 
 
 
 
 
 
This bug seems to have been introduced with: 

 

commit 58a41bcb182290de681da01ba277b5e0d6211707
Author: Oliver Gondža 
Date:   Sun Feb 8 12:48:12 2015 +0100

[FIXED JENKINS-26684] Escape special chars in maven build step arguments
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-26684) Maven build step fail to launch mvn process when special chars are present in build variables

2015-12-10 Thread n...@bardelot.fr (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Noël Bardelot commented on  JENKINS-26684 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Maven build step fail to launch mvn process when special chars are present in build variables  
 
 
 
 
 
 
 
 
 
 
The regression mentionned by Tobias Oberlies seems to be broader than just the Gerrit Trigger plugin. Please see JENKINS-31986. 
As per Tobias' logs and mine, you can see the CMD execution runs with the command being both single-quoted and double-quoted: 

 

cmd.exe /C '"some command"'
 

 
The double-quotes are clearly the issue here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-32004) HP Automation Tools Unable to Export Job Results to QC

2015-12-10 Thread sergio_costa...@hotmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 sergio costa edited a comment on  JENKINS-32004 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: HP Automation Tools Unable to Export Job Results to QC  
 
 
 
 
 
 
 
 
 
 Apparently, the problem is that QC don't have hp.qc.test-set.external installed and don't recognize it. It would be nice if was possible to specify this configuration in plugin to use supported subtypes  or a way to replace the external for hp . qc.test-set.default. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [gradle-jpi-plugin] (JENKINS-31882) Description not set on plugin

2015-12-10 Thread m...@daniel-spilker.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Spilker resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
The Update Center reads the excerpt from the plugin's wiki page, see Plugin.java#L276. So you need to create a wiki page for your plugin. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31882 
 
 
 
  Description not set on plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Spilker 
 
 
 

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] [robot-plugin] (JENKINS-32009) Strings like a path to some file (/path/to_my_file), is been interpreted as the full address for the link of the results of the test

2015-12-10 Thread dnl31...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 dnl dnl created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32009 
 
 
 
  Strings like a path to some file (/path/to_my_file), is been interpreted as the full address for the link of the results of the test  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 jpiironen 
 
 
 

Components:
 

 robot-plugin 
 
 
 

Created:
 

 10/Dec/15 4:45 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.635 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 dnl dnl 
 
 
 
 
 
 
 
 
 
 
Hil all.. 
I'm using robotframework with jenkins.. 
In my test case, i need to put in the title of the test the path of the file that i need to checkout, exemple: 
Check file /var/myfile (Title of my test case exemple) . 
But on jenkins, its getting 404 when i'm trying to browse the results on fail test, because jenkins is interpreting the "/var/myfile" as part of the link of the result of the test.. 
I try to scape the '/' char with "/var/myfile", '''/var/myfile''' , %2fvar%2fmyfile, //var//myfile , \/var\/myfile  
but still interpreting the "/var/myfile" as part of the link of the result...

[JIRA] [core] (JENKINS-31870) Unable to use LDAP user credentials in build configuration

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

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31870 
 
 
 
  Unable to use LDAP user credentials in build configuration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Component/s:
 
 subversion-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [core] (JENKINS-31536) Jobs hanging in Build Executor even if it is finished

2015-12-10 Thread al.sheph...@intergraph.com (JIRA)

Title: Message Title

Al Shepherd commented on JENKINS-31536

Re: Jobs hanging in Build Executor even if it is finished

I don't know if this helps any, but we have experienced this issue when running scheduled master jobs.
Details: we have a master job that is scheduled to run at 1am every day. This master job invokes other jobs via Conditional step (single) entries in the Build section. When a conditional step triggers a job that has the Warning plug-in configured for it (let's call it job 2), the triggered job (job 2)completes successfully but then control is never returned to the calling (master) job. When the plug-in configuration is removed from job 2 everything runs as it should. If we replace the Warnings plug-in job 2 then trigger a build of this job manually (not via the master job), the plug-in works as advertised (beautifully done by the way). Also, if we set up job 2 as a scheduled job and let it fire off via this trigger the Warnings plug-in behaves as it should.

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-custom-build-environment-plugin] (JENKINS-32010) Container start command argument parsing

2015-12-10 Thread jenj...@zubu.re (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zuBu zubu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32010 
 
 
 
  Container start command argument parsing  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Nicolas De Loof 
 
 
 

Components:
 

 docker-custom-build-environment-plugin 
 
 
 

Created:
 

 10/Dec/15 4:56 PM 
 
 
 

Labels:
 

 plugin 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 zuBu zubu 
 
 
 
 
 
 
 
 
 
 
This bug concerns container start commands with one or more command line options. 
If a container is run from command line like : 
{{docker run -it  "tail -n 20 /etc/passwd" }} the "tail -n 20 /etc/passwd" command is interpreted as: 
{{ "Path": "/bin/sh", "Args": [ "-c", "tail -n 20 /etc/passwd" ],}} 
However if I add the same command without quotes in "Container start command" option it is interpreted as : 
{{ "Path": "/bin/sh", "Args": [ "-c", "tail", "-n", "20", "/etc/passwd" ],}} 
If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) : 
{{ "Path": "/bin/sh", "Args": [ "-c", "'tail", "-n", "20", "/etc/passwd'" ], }} 
Both cases result in errors and the container does not s

[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32010) Container start command argument parsing

2015-12-10 Thread jenj...@zubu.re (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zuBu zubu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32010 
 
 
 
  Container start command argument parsing  
 
 
 
 
 
 
 
 
 

Change By:
 
 zuBu zubu 
 
 
 
 
 
 
 
 
 
 This bug concerns container start commands with one or more command line options.If a container is run from command line like : {{ docker run -it  "tail -n 20 /etc/passwd" }} the "tail -n 20 /etc/passwd" command is interpreted as: {{ "Path": "/bin/sh","Args": ["-c","tail -n 20 /etc/passwd"], }} However if I add the same command without quotes in "Container start command" option it is interpreted as : {{ "Path": "/bin/sh","Args": ["-c","tail","-n","20","/etc/passwd"], }} If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) : {{ "Path": "/bin/sh","Args": ["-c","'tail","-n","20","/etc/passwd'"], }}   Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31850) Tool installer metadata signatuire validation failure on Java 1.8 build 65+

2015-12-10 Thread andres.smer...@centricdigital.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
KK resolved the reopened 

JENKINS-31089
. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-31850 
 
 
 
  Tool installer metadata signatuire validation failure on Java 1.8 build 65+  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

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] [docker-custom-build-environment-plugin] (JENKINS-32010) Container start command argument parsing

2015-12-10 Thread jenj...@zubu.re (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 zuBu zubu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32010 
 
 
 
  Container start command argument parsing  
 
 
 
 
 
 
 
 
 

Change By:
 
 zuBu zubu 
 
 
 
 
 
 
 
 
 
 This bug concerns container start commands with one or more command line options.If a container is run from command line like : {code:java} docker run -it  "tail -n 20 /etc/passwd" {code} the "tail -n 20 /etc/passwd" command is interpreted as: {code:java} "Path": "/bin/sh","Args": ["-c","tail -n 20 /etc/passwd"], {code}   However if I add the same command without quotes in "Container start command" option it is interpreted as : {code:java} "Path": "/bin/sh","Args": ["-c","tail","-n","20","/etc/passwd"], {code}   If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) : {code:java} "Path": "/bin/sh","Args": ["-c","'tail","-n","20","/etc/passwd'"], {code}   Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Smerkin commented on  JENKINS-27457 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)  
 
 
 
 
 
 
 
 
 
 
I still having this issue on version 1.3.4. I generate my EAR package before deploying it, so that part of the process is not involved.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)

2015-12-10 Thread andres.smer...@centricdigital.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Smerkin reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
I still have this issue on ver 1.3.4. I generate the EAR package before deploying it on WAS.  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-27457 
 
 
 
  deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andres Smerkin 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

[JIRA] [websphere-deployer-plugin] (JENKINS-27457) deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)

2015-12-10 Thread andres.smer...@centricdigital.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andres Smerkin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27457 
 
 
 
  deploy is completed however deployed ear(war) doesn't start with a error (SRVE0303E)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Andres Smerkin 
 
 
 

Comment:
 
 I still having this issue on version 1.3.4. I generate my EAR package before deploying it, so that part of the process is not involved.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31536) Jobs hanging in Build Executor even if it is finished

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-31536 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jobs hanging in Build Executor even if it is finished  
 
 
 
 
 
 
 
 
 
 
I find the Node Stalker Plugin in the stack trace of the thread everyone else is waiting for very suspicious. What happens when you disable the plugin, or disable its features (if it offers such options)? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-31536) Jobs hanging in Build Executor even if it is finished