date:20130430















































Ulli Hafner
 created  JENKINS-17786


Make all warnings parsers work on slaves















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:00 AM



Description:


The available warnings parsers of the violations plug-in could be also used in the warnings plug-in. However, due to the design of the violations plug-in, these parsers can't be used on a slave. In order to be used in a master slave environment, all those parsers should be converted to native warnings parsers. 




Project:


Jenkins



Priority:


Major



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17787) Replace Codenarc parser with native parser















































Ulli Hafner
 created  JENKINS-17787


Replace Codenarc parser with native parser















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:03 AM



Description:



parsers.add(new ViolationsAdapter(new CodenarcParser(),
Messages._Warnings_Codenarc_ParserName(),
Messages._Warnings_Codenarc_LinkName(),
Messages._Warnings_Codenarc_TrendName()));





Project:


Jenkins



Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17787) Replace Codenarc parser with native parser















































Ulli Hafner
 updated  JENKINS-17787


Replace Codenarc parser with native parser
















Change By:


Ulli Hafner
(30/Apr/13 6:04 AM)




Issue Type:


Bug
Task



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17788) Replace CSSLinit parser with native parser















































Ulli Hafner
 created  JENKINS-17788


Replace CSSLinit parser with native parser















Issue Type:


Task



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:06 AM



Description:



parsers.add(new ViolationsAdapter(new CodenarcParser(),
Messages._Warnings_Codenarc_ParserName(),
Messages._Warnings_Codenarc_LinkName(),
Messages._Warnings_Codenarc_TrendName()));





Project:


Jenkins



Labels:


DEVTOOLS




Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17789) Replace Gendarme parser with native parser















































Ulli Hafner
 created  JENKINS-17789


Replace Gendarme parser with native parser















Issue Type:


Task



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:08 AM



Description:



parsers.add(new ViolationsAdapter(new CssLintParser(),
Messages._Warnings_CssLint_ParserName(),
Messages._Warnings_CssLint_LinkName(),
Messages._Warnings_CssLint_TrendName()));





Project:


Jenkins



Labels:


DEVTOOLS




Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17788) Replace CSSLinit parser with native parser















































Ulli Hafner
 updated  JENKINS-17788


Replace CSSLinit parser with native parser
















Change By:


Ulli Hafner
(30/Apr/13 6:07 AM)




Description:


{code}parsers.add(newViolationsAdapter(new
CodenarcParser
CssLintParser
(),Messages.
_Warnings_Codenarc_ParserName
_Warnings_CssLint_ParserName
(),Messages.
_Warnings_Codenarc_LinkName
_Warnings_CssLint_LinkName
(),Messages.
_Warnings_Codenarc_TrendName
_Warnings_CssLint_TrendName
()));{code}



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17789) Replace Gendarme parser with native parser















































Ulli Hafner
 updated  JENKINS-17789


Replace Gendarme parser with native parser
















Change By:


Ulli Hafner
(30/Apr/13 6:09 AM)




Description:


{code}parsers.add(newViolationsAdapter(new
CssLintParser
GendarmeParser
(),Messages.
_Warnings_CssLint_ParserName
_Warnings_Gendarme_ParserName
(),Messages.
_Warnings_CssLint_LinkName
_Warnings_Gendarme_LinkName
(),Messages.
_Warnings_CssLint_TrendName
_Warnings_Gendarme_TrendName
()));{code}



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17790) Replace JCReport parser with native parser















































Ulli Hafner
 created  JENKINS-17790


Replace JCReport parser with native parser















Issue Type:


Task



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:22 AM



Description:



parsers.add(new ViolationsAdapter(new GendarmeParser(),
Messages._Warnings_Gendarme_ParserName(),
Messages._Warnings_Gendarme_LinkName(),
Messages._Warnings_Gendarme_TrendName()));





Project:


Jenkins



Labels:


DEVTOOLS




Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17790) Replace JCReport parser with native parser















































Ulli Hafner
 updated  JENKINS-17790


Replace JCReport parser with native parser
















Change By:


Ulli Hafner
(30/Apr/13 6:23 AM)




Description:


{code}parsers.add(newViolationsAdapter(new
GendarmeParser
JcReportParser
(),Messages.
_Warnings_Gendarme_ParserName
_Warnings_JCReport_ParserName
(),Messages.
_Warnings_Gendarme_LinkName
_Warnings_JCReport_LinkName
(),Messages.
_Warnings_Gendarme_TrendName
_Warnings_JCReport_TrendName
()));{code}



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17791) Replace Pep8 parser with native parser















































Ulli Hafner
 updated  JENKINS-17791


Replace Pep8 parser with native parser
















Change By:


Ulli Hafner
(30/Apr/13 6:24 AM)




Description:


{code}parsers.add(newViolationsAdapter(new
JcReportParser
Pep8Parser
(),Messages.
_Warnings_JCReport_ParserName
_Warnings_Pep8_ParserName
(),Messages.
_Warnings_JCReport_LinkName
_Warnings_Pep8_LinkName
(),Messages.
_Warnings_JCReport_TrendName
_Warnings_Pep8_TrendName
()));{code}



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17791) Replace Pep8 parser with native parser















































Ulli Hafner
 created  JENKINS-17791


Replace Pep8 parser with native parser















Issue Type:


Task



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:23 AM



Description:



parsers.add(new ViolationsAdapter(new JcReportParser(),
Messages._Warnings_JCReport_ParserName(),
Messages._Warnings_JCReport_LinkName(),
Messages._Warnings_JCReport_TrendName()));





Project:


Jenkins



Labels:


DEVTOOLS




Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17792) Replace PerlCritic parser with native parser















































Ulli Hafner
 updated  JENKINS-17792


Replace PerlCritic parser with native parser
















Change By:


Ulli Hafner
(30/Apr/13 6:25 AM)




Description:


{code}parsers.add(newViolationsAdapter(new
Pep8Parser
PerlCriticParser
(),Messages.
_Warnings_Pep8_ParserName
_Warnings_PerlCritic_ParserName
(),Messages.
_Warnings_Pep8_LinkName
_Warnings_PerlCritic_LinkName
(),Messages.
_Warnings_Pep8_TrendName
_Warnings_PerlCritic_TrendName
()));{code}



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17792) Replace PerlCritic parser with native parser















































Ulli Hafner
 created  JENKINS-17792


Replace PerlCritic parser with native parser















Issue Type:


Task



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:24 AM



Description:



parsers.add(new ViolationsAdapter(new Pep8Parser(),
Messages._Warnings_Pep8_ParserName(),
Messages._Warnings_Pep8_LinkName(),
Messages._Warnings_Pep8_TrendName()));





Project:


Jenkins



Labels:


DEVTOOLS




Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17794) Replace StyleCop parser with native parser

2013-04-30 Thread sylvain.vey...@keyconsulting.fr (JIRA)















































Ulli Hafner
 created  JENKINS-17794


Replace StyleCop parser with native parser















Issue Type:


Task



Assignee:


Ulli Hafner



Components:


warnings



Created:


30/Apr/13 6:26 AM



Description:



parsers.add(new ViolationsAdapter(new PyLintParser(),
Messages._Warnings_PyLint_ParserName(),
Messages._Warnings_PyLint_LinkName(),
Messages._Warnings_PyLint_TrendName()));





Project:


Jenkins



Labels:


DEVTOOLS




Priority:


Minor



Reporter:


Ulli Hafner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-12670) Double Build Polling Issue with Subversion Plugin

2013-04-30 Thread somek...@gmail.com (JIRA)















































Mathieu Jobin
 commented on  JENKINS-12670


Double Build Polling Issue with Subversion Plugin















similar issue with Git pulling. using Jenkins ver. 1.474




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-12670) Double Build Polling Issue with Subversion Plugin

2013-04-30 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-12670


Double Build Polling Issue with Subversion Plugin















Are the clocks of your subversion server and your Jenkins server(s) in sync?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-11564) Line number anchors for jobName/number/consoleFull

2013-04-30 Thread sp...@helten.dk (JIRA)















































David Langeland
 commented on  JENKINS-11564


Line number anchors for jobName/number/consoleFull















That sounds really good - and thanks for replying.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.















































Sylvain Veyrié
 commented on  JENKINS-17058


Publish over SSH plugin XML configuration cannot be read on jenkins start up.















Still KO for us with 1.513 (same Jenkins instance than Maxime Ménard).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testlink] (JENKINS-17795) Wrong values on TestLink result page in jenkins when using platforms

Paul Zimmermann
created JENKINS-17795

Wrong values on TestLink result page in jenkins when using platforms

Issue Type:

Improvement

Affects Versions:

current

Assignee:

Bruno P. Kinoshita

Components:

testlink

Created:

30/Apr/13 8:33 AM

Description:

I just tested the plugin with tap-files that include platform information. The test results (4 Tests, 2 Platforms) are correctly transmitted to testlink. In Jenkins the plugin reports a total amount of 4 tests (8 would be correct). The execution state of all 4 testcases ist "not run" (correct would be 4 passes, 2 failes, 2 not run). Platform information is not shown in the table.

This is not really a malfunction, I just think that the platform feature is not yet implemented in the Jenkins output part of the TestLink Plugin. Because the output is wrong it could be disabled when using platforms - as a quick solution?

Thanks for the plugin - it's great
Paul

Environment:

Testlink 1.9.6, Jenkins TestLink Plugin 3.5

Project:

Jenkins

Priority:

Minor

Reporter:

Paul Zimmermann

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[JIRA] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500

2013-04-30 Thread rzan...@java.net (JIRA)















































rzanner
 updated  JENKINS-17734


Claim Report view reports Error Status: 500
















To me this is a major issue since it' a "Major loss of function." of the Claim plugin when I'm not able to see it's only view!!!





Change By:


rzanner
(30/Apr/13 8:47 AM)




Priority:


Minor
Major



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [claim] (JENKINS-17734) Claim Report view reports Error Status: 500

2013-04-30 Thread rzan...@java.net (JIRA)













































 
rzanner
 edited a comment on  JENKINS-17734


Claim Report view reports Error Status: 500
















To me this is a major issue since it' a "Major loss of function." of the Claim plugin when I'm not able to see it's only view!!!

I was tempted to upgrade it to "BLOCKER" since I cannot use my personal Jenkins start page at all - but since this JIRA instance is related to Jenkins as a whole, I did not want to go that far.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-17796) Maven 2/3 _-Project Job Unable to commit files svn: E155004

2013-04-30 Thread epikur2...@java.net (JIRA)















































epikur2412
 updated  JENKINS-17796


Maven 2/3 _-Project Job Unable to commit files svn: E155004
















Change By:


epikur2412
(30/Apr/13 8:54 AM)




Environment:


JenkinsV.1513/WindowsServer2008
/Subversion1.7.8/Tortoisesvnclient1.7.8/Maven3.x



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [xunit] (JENKINS-17797) x-unit option not to fail if there isn't a test results file

2013-04-30 Thread pedro.r...@mog-solutions.com (JIRA)















































pedro reis
 created  JENKINS-17797


x-unit option not to fail if there isnt a test results file















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Gregory Boissinot



Components:


xunit



Created:


30/Apr/13 9:02 AM



Description:


We are running the Job build in many platforms, and now we have one cross-platform, so now the cppunit will fail for just this case, not generating the test results file.
It would be important to have a checkbox allowing not to fail if there aren't test files for this cross-platform case.




Environment:


any




Fix Versions:


current



Project:


Jenkins



Priority:


Major



Reporter:


pedro reis

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [xunit] (JENKINS-17797) x-unit option not to fail if there isn't a test results file

2013-04-30 Thread pedro.r...@mog-solutions.com (JIRA)















































pedro reis
 updated  JENKINS-17797


x-unit option not to fail if there isnt a test results file
















Change By:


pedro reis
(30/Apr/13 9:02 AM)




Description:


WearerunningtheJobbuildinmanyplatforms,andnowwehaveonecross-platform,sonowthecppunitwillfailforjustthiscase,notgeneratingthetestresultsfile.Itwouldbeimportanttohaveacheckboxallowingnottofailiftherearenttest
result
filesforthiscross-platformcase.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testlink] (JENKINS-17795) Wrong values on TestLink result page in jenkins when using platforms
















































Paul Zimmermann
 closed  JENKINS-17795 as Fixed


Wrong values on TestLink result page in jenkins when using platforms
















Although the result table in testlink doesn't support plattforms I made a mistake - I used absolute pathes in the result seeking strategy - does not work. However plattforms seem to be problematic, but I have to test a bit more...





Change By:


Paul Zimmermann
(30/Apr/13 9:12 AM)




Status:


Open
Closed





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [jenkins-multijob-plugin] (JENKINS-17799) Parallel executed job doesn't stop processing when failed

2013-04-30 Thread save...@yahoo.de (JIRA)

Sascha Vet
created JENKINS-17799

Parallel executed job doesnt stop processing when failed

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

jenkins-multijob-plugin

Created:

30/Apr/13 9:30 AM

Description:

Two sub-jobs S1 and S2 calling the same job A. Internally multijob starts the job A only once (by the way a great behavior, very helpful in my use case). Job A fails and S1 stops with the status FAILED. But in sub-job S2 job A gets the status PENDING and the workflow continues whether job A fails or not.

Workflow sketch:

MainJob

Subjob S1
Step 1
Job A - fails, subjob s2 stops and result is failed
Step 2
Job B - not executed (expected)
Subjob S2
Step 1
Job A - status pending. After failing - execution goes on
Step 2
Job C - executed (BUG!)

Project:

Jenkins

Labels:

plugin
parallel

Priority:

Minor

Reporter:

Sascha Vet

[JIRA] [jenkins-multijob-plugin] (JENKINS-17799) Parallel executed job doesn't stop processing when failed

2013-04-30 Thread save...@yahoo.de (JIRA)















































Sascha Vet
 updated  JENKINS-17799


Parallel executed job doesnt stop processing when failed
















Change By:


Sascha Vet
(30/Apr/13 9:32 AM)




Description:


Twosub-jobsS1andS2callingthesamejobA.InternallymultijobstartsthejobAonlyonce(bythewayagreatbehavior,veryhelpfulinmyusecase).JobAfailsandS1stopswiththestatusFAILED.Butinsub-jobS2jobAgetsthestatusPENDINGandtheworkflowcontinueswhetherjobAfailsornot.Workflowsketch:MainJob-SubjobS1-
-
Step1-
--
JobA-fails,subjobs2stopsandresultisfailed-
-
Step2-
--
JobB-notexecuted(expected)-SubjobS2-
-
Step1-
--
JobA-statuspending.Afterfailing-executiongoeson-
-
Step2-
--
JobC-executed(BUG!)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [copyartifact] (JENKINS-17680) Upgrade to new Copy Artifacts version erases all job names to copy from

2013-04-30 Thread langui...@semipol.de (JIRA)















































Johannes Wienke
 commented on  JENKINS-17680


Upgrade to new Copy Artifacts version erases all job names to copy from















I'd really like to see an automatic migration path for this.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [warnings] (JENKINS-17762) Renaming the Clang parsers silently breaks Jenkins configs

2013-04-30 Thread jenkins.li...@sailmaker.co.uk (JIRA)















































Richard Buckle
 commented on  JENKINS-17762


Renaming the Clang parsers silently breaks Jenkins configs















Hi Ulli, you can find the configs at https://github.com/richardbuckle/AdvancedJenkins in the "jobs" subdirectory. The commit in question is https://github.com/richardbuckle/AdvancedJenkins/commit/67d706fbb15da8fad66b3749a656098195df58ee

If you've any questions do please ask.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testlink] (JENKINS-17795) Wrong values on TestLink result page in jenkins when using platforms

2013-04-30 Thread brunodepau...@yahoo.com.br (JIRA)















































Bruno P. Kinoshita
 commented on  JENKINS-17795


Wrong values on TestLink result page in jenkins when using platforms















Hello Paul! I'll start a new cycle to work on Jenkins and plug-ins in the next days. In the meantime, feel free to add more comments with your findings here, or submit pull requests via GitHub. 

Thank you! 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testlink] (JENKINS-17801) TAP-attachments produce file not found error

Paul Zimmermann
created JENKINS-17801

TAP-attachments produce file not found error

Issue Type:

Bug

Assignee:

Bruno P. Kinoshita

Components:

testlink

Created:

30/Apr/13 11:31 AM

Description:

If test results (tap-files) are not directly stored in the workspace-folder, I get a file not found error when the testlink plugin tries to attach the result files. So no attachment is stored with the test results in testlink.

my tap-files are in a subfolder $workspace/testresults.
the result seeking strategy is testresults/*.tap.
test results are definitly found and correctly transmitted to testlink
the plugin tries to open the tap-file in $workspace/xyz.tap instead of $workspace/testresults/xyz.tap
if I disable the include attachment option there is no error produced
also there is no error when I store the test results in the workspace folder

Thanks.
Paul

Environment:

Testlink Plugin 3.5, Testlink 1.9.6

Project:

Jenkins

Priority:

Major

Reporter:

Paul Zimmermann

[JIRA] [core] (JENKINS-17715) Display Name is not shown















































SCM/JIRA link daemon
 commented on  JENKINS-17715


Display Name is not shown















Code changed in jenkins
User: ssogabe
Path:
 changelog.html
 core/src/main/java/hudson/Functions.java
 core/src/main/java/hudson/model/AbstractItem.java
 core/src/test/java/hudson/FunctionsTest.java
http://jenkins-ci.org/commit/jenkins/55a68acca970dca12dcde6028b56a784d0c7c5fa
Log:
  FIXED JENKINS-17715 Display Name is not shown






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17715) Display Name is not shown
















































SCM/JIRA link daemon
 resolved  JENKINS-17715 as Fixed


Display Name is not shown
















Change By:


SCM/JIRA link daemon
(30/Apr/13 11:50 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [svnmerge] (JENKINS-16723) NPE when performing integration.















































chirag Patel
 started work on  JENKINS-16723


NPE when performing integration.
















Change By:


chirag Patel
(30/Apr/13 11:56 AM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [svnmerge] (JENKINS-16723) NPE when performing integration.
















































chirag Patel
 assigned  JENKINS-16723 to chirag Patel



NPE when performing integration.
















Change By:


chirag Patel
(30/Apr/13 11:56 AM)




Assignee:


KohsukeKawaguchi
chiragPatel



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [svnmerge] (JENKINS-16723) NPE when performing integration.















































chirag Patel
 commented on  JENKINS-16723


NPE when performing integration.















I try to remove merge info manually still it is not working i am getting same error
ERROR: Publisher jenkins.plugins.svnmerge.IntegrationPublisher aborted due to exception
java.lang.NullPointerException
	at org.tmatesoft.svn.core.SVNException.init(SVNException.java:50)
	at org.tmatesoft.svn.core.SVNException.init(SVNException.java:37)
	at jenkins.plugins.svnmerge.FeatureBranchProperty$2.invoke(FeatureBranchProperty.java:273)
	at jenkins.plugins.svnmerge.FeatureBranchProperty$2.invoke(FeatureBranchProperty.java:247)
	at hudson.FilePath.act(FilePath.java:904)
	at hudson.FilePath.act(FilePath.java:877)
	at jenkins.plugins.svnmerge.FeatureBranchProperty.integrate(FeatureBranchProperty.java:247)
	at jenkins.plugins.svnmerge.IntegrateAction.perform(IntegrateAction.java:141)
	at jenkins.plugins.svnmerge.IntegrateAction.perform(IntegrateAction.java:130)
	at jenkins.plugins.svnmerge.IntegrationPublisher.perform(IntegrationPublisher.java:47)
	at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)
	at hudson.model.Run.execute(Run.java:1600)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [svnmerge] (JENKINS-16723) NPE when performing integration.















































chirag Patel
 updated  JENKINS-16723


NPE when performing integration.
















Change By:


chirag Patel
(30/Apr/13 11:58 AM)




Assignee:


chiragPatel
KohsukeKawaguchi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [gui] (JENKINS-3107) Advanced section should be expanded if it is customized















































Jesse Glick
 commented on  JENKINS-3107


Advanced section should be expanded if it is customized















https://github.com/jenkinsci/ant-plugin/pull/5 for example.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testlink] (JENKINS-17802) TAP files with platform information and recursive result seeking strategy

Paul Zimmermann
created JENKINS-17802

TAP files with platform information and recursive result seeking strategy

Issue Type:

Improvement

Assignee:

Bruno P. Kinoshita

Components:

testlink

Created:

30/Apr/13 12:20 PM

Description:

Hi there,
I have some trouble with result seeking strategies, tap files and platforms. In detail:

my tap-files are in subfolders testresults/platform1/tf1.tap and testresults/platform2/tf1.tap
the result seeking strategy "testresults/*/.tap" works almost fine: the test results are correctly transmitted to testlink (platform dependent), but: in TestLink the testcase tree shows only gray (not run) entries. If I click on them they show the correct test result (not passed) for ALL plattforms
if I remove one platform (and the corresponding tap-file) everything works find.
strange: if there are 4 testcases and only 1 has 2 platforms assigned to it ALL testcases are displayed as not run.

Hope that helps in any way.
Thanks!
Paul

Environment:

Testlink 1.9.6, TestLink Plugin 3.5

Project:

Jenkins

Priority:

Major

Reporter:

Paul Zimmermann

[JIRA] [testlink] (JENKINS-17802) TAP files with platform information and recursive result seeking strategy















































Paul Zimmermann
 updated  JENKINS-17802


TAP files with platform information and recursive result seeking strategy
















Change By:


Paul Zimmermann
(30/Apr/13 12:48 PM)




Description:


Hithere,Ihavesometroublewithresultseekingstrategies,tapfilesandplatforms.Indetail:-mytap-filesareinsubfolderstestresults/platform1/tf1.tapandtestresults/platform2/tf1.tap-theresultseekingstrategytestresults/**/*.tap
worksalmostfine:
bringsonly
the
test
platform2
results
arecorrectlytransmitted
totestlink
(platformdependent),but:inTestLinkthetestcasetreeshowsonlygray(notrun)entries.IfIclickonthemtheyshowthecorrecttestresult(notpassed)forALLplattforms
-ifIremoveoneplatform(andthecorrespondingtap-file)everythingworksfind.
-strange:ifthereare4
Theproblemis,thatIhave
testcases
assignedtotwoplatforms
and
only1has
Ihave
2
platforms
tapfileswithseparateresultsforeachplatform.TheTestLinkPluginonlytakesthesecondtapfile(samefilenameasthefirstone)andoverwritesthevaluesofthefirstone.SoinTestLinkthetreeentryisgray(showstheresultoverall
assigned
platforms).SohowcanIcollectseparateresultsfortwoplatforms?Onetap-Filewithtwoplatforminformationdontseem
to
itALLtestcasesaredisplayedasnotrun
work
.
..
Hopethathelpsinanyway.Thanks!Paul



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17715) Display Name is not shown

2013-04-30 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-17715


Display Name is not shown















Integrated in  jenkins_main_trunk #2498
 FIXED JENKINS-17715 Display Name is not shown (Revision 55a68acca970dca12dcde6028b56a784d0c7c5fa)

 Result = SUCCESS
s.sogabe : 55a68acca970dca12dcde6028b56a784d0c7c5fa
Files : 

	core/src/main/java/hudson/model/AbstractItem.java
	changelog.html
	core/src/main/java/hudson/Functions.java
	core/src/test/java/hudson/FunctionsTest.java





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-8423) Slave priority

2013-04-30 Thread alex.ouzou...@me.com (JIRA)















































Alex Ouzounis
 commented on  JENKINS-8423


Slave priority















+1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild

2013-04-30 Thread alex.ouzou...@me.com (JIRA)















































Alex Ouzounis
 commented on  JENKINS-16845


NullPointer in getPreviousBuild















Since 1.511 and clearing/deleting the bad builds problem is officially gone 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [active-directory] (JENKINS-17803) AD plugin 1.3.1 doesn't handle non-ascii names correctly

2013-04-30 Thread jcro...@emss.co.za (JIRA)















































Johan Cronje
 created  JENKINS-17803


AD plugin 1.3.1 doesnt handle non-ascii names correctly















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


active-directory



Created:


30/Apr/13 1:56 PM



Description:


We just upgraded AD plugin to 1.3.1.
Now I am unable to log in, it seems to be due to my surname containing an 'é'.
Verified by downgrading to 1.3.0, then all is well.

Here is the log:

org.acegisecurity.BadCredentialsException: Failed to retrieve user information for jcronje; nested exception is javax.naming.InvalidNameException: CN=Johan Cronj\u00E9,OU=Internal,OU=Users,OU=EMSS,DC=domain,DC=,DC=: [LDAP: error code 34 - 208F: LdapErr: DSID-0C090715, comment: Error processing name, data 0, v1db1]; remaining name 'CN=Johan Cronj\u00E9,OU=Internal,OU=Users,OU=EMSS,DC=,DC=,DC='
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:309)
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:193)
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:137)
	at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
	at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
	at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
	at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
	at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227)
	at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:636)
Caused by: javax.naming.InvalidNameException: CN=Johan

[JIRA] [subversion] (JENKINS-12670) Double Build Polling Issue with Subversion Plugin

2013-04-30 Thread somek...@gmail.com (JIRA)















































Mathieu Jobin
 commented on  JENKINS-12670


Double Build Polling Issue with Subversion Plugin















in our case, we do not have a subversion server. we are using git and our remote is github.com. I am trusting they are synchronized, although I cannot verify.

our jenkins server shows the following.

looks like we may have a little delay. but I'm not an ntp specialist

ntpq peers
 remote   refid  st t when poll reach   delay   offset  jitter
==
+173.44.32.10128.138.140.44   2 u  757 1024  177   27.666  -25.743  21.265
*lswb-man-01.ser 209.51.161.238   2 u  587 1024  3772.216  -36.146  21.229
ntpq

you think this could be the cause? I can try to reduce that offset.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-12670) Double Build Polling Issue with Subversion Plugin

2013-04-30 Thread somek...@gmail.com (JIRA)















































Mathieu Jobin
 commented on  JENKINS-12670


Double Build Polling Issue with Subversion Plugin















oh, its in ms, -36.146ms does not sounds like a bad time difference  

I think we're good.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-8423) Slave priority

2013-04-30 Thread dell.gr...@soundideas.co.uk (JIRA)















































Dell Green
 commented on  JENKINS-8423


Slave priority















thanks for the heads up on the plugin info. if i get some spare time i'll have a look at writing a plugin, havent written one before.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [tap] (JENKINS-17804) tapResults TAP Test Results filtering by test status

2013-04-30 Thread ron...@sitesell.com (JIRA)















































Real ONeil
 created  JENKINS-17804


tapResults TAP Test Results filtering by test status















Issue Type:


Improvement



Assignee:


Bruno P. Kinoshita



Components:


tap



Created:


30/Apr/13 3:11 PM



Description:


Some of our jobs have a very large number of tests.  The capability to hide passed tests from the tapResults page would greatly help in homing in on those tests which fail.




Project:


Jenkins



Labels:


tap
results




Priority:


Minor



Reporter:


Real ONeil

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [tap] (JENKINS-17804) tapResults TAP Test Results filtering by test status

2013-04-30 Thread brunodepau...@yahoo.com.br (JIRA)















































Bruno P. Kinoshita
 commented on  JENKINS-17804


tapResults TAP Test Results filtering by test status















Sounds like a good idea. I believe we can include this feature in the next release. 

Thanks!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [tap] (JENKINS-13451) Enhance tap-plugin UI using TAP Formatter HTML as basis

2013-04-30 Thread ron...@sitesell.com (JIRA)















































Real ONeil
 reopened  JENKINS-13451


Enhance tap-plugin UI using TAP Formatter HTML as basis
















Hi Bruno,

Can we request this be re-opened?  Some of that functionality(especially the ability to see additional unknown lines, the ability to only show failed and the ability to hide the data until clicked on for a cleaner report) would be particularly useful for jobs with a very large number of associated tests such as ours.

It would go a long ways towards making the testResult page far easier to navigate and organize.

Much appreciated,
Real





Change By:


Real ONeil
(30/Apr/13 3:43 PM)




Resolution:


WontFix





Status:


Closed
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [gui] (JENKINS-17805) Naming a Jenkins installation

2013-04-30 Thread edo...@gmail.com (JIRA)















































edo kan
 created  JENKINS-17805


Naming a Jenkins installation















Issue Type:


New Feature



Affects Versions:


current



Assignee:


Unassigned


Components:


gui



Created:


30/Apr/13 3:42 PM



Description:


I've two separate Jenkins installations in my company. I need to understand which instance I'm looking. I've created a description but it is displayed only on dashboard. 

I thought there must be a way to change the browser title until I saw layout.jelly where title tag is set.

Please consider adding a feature to name a Jenkins installation, so instead of seeing "Dashboard Jenkins", I see "ABCD Dashboard Jenkins"





Environment:


windows 2012




Project:


Jenkins



Labels:


jenkins
gui




Priority:


Major



Reporter:


edo kan

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [tap] (JENKINS-13451) Enhance tap-plugin UI using TAP Formatter HTML as basis

2013-04-30 Thread brunodepau...@yahoo.com.br (JIRA)















































Bruno P. Kinoshita
 commented on  JENKINS-13451


Enhance tap-plugin UI using TAP Formatter HTML as basis















Hi Real, 

Feel free to reopen it. We'll discuss it later when I start a new cycle for Jenkins plug-ins 

Hope that helps
/Bruno



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents
















































SCM/JIRA link daemon
 resolved  JENKINS-17775 as Fixed


IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents
















Change By:


SCM/JIRA link daemon
(30/Apr/13 4:09 PM)




Status:


InProgress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents















































SCM/JIRA link daemon
 commented on  JENKINS-17775


IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 maven-plugin/src/main/java/hudson/maven/MavenBuildInformation.java
 maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
 maven-plugin/src/main/java/hudson/maven/reporters/MavenFingerprinter.java
http://jenkins-ci.org/commit/jenkins/0c4fe2ddbac2963c0b633fe27bb1a6016134da50
Log:
  FIXED JENKINS-17775 Find (model) parent POMs properly during fingerprint recording at end of build.


Compare: https://github.com/jenkinsci/jenkins/compare/3f0f25fc6ba9...0c4fe2ddbac2




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-15717) InvalidClassException on SwapSpaceMonitor.MonitorTask















































Jesse Glick
 updated  JENKINS-15717


InvalidClassException on SwapSpaceMonitor.MonitorTask
















Reporters try running with a different slave remote FS root and/or a fresh copy of slave.jar. Looks to me like there is an old cache that has not been cleared. Either that or a buggy version of Java (which?).





Change By:


Jesse Glick
(30/Apr/13 4:27 PM)




Summary:


Failedtomonitorwarning
InvalidClassExceptiononSwapSpaceMonitor.MonitorTask





Labels:


serialization





Component/s:


core





Component/s:


slave-status



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-16560) Failure to rewrite files during rekeying on Windows Server 2003 R2

2013-04-30 Thread david_od...@yahoo.com (JIRA)















































David Odren
 commented on  JENKINS-16560


Failure to rewrite files during rekeying on Windows Server 2003 R2















Thank you shinsato!  I was able to work around the issue by re-keying the the background as well.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [embeddable-build-status] (JENKINS-17798) build badge icon requires authentication















































Jesse Glick
 commented on  JENKINS-17798


build badge icon requires authentication















Is this actually a bug? If the builds are not readable by anonymous, then the badge should not be visible either, because it would expose information about the build that you have asked to hide.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-9142) Add Build Step button broken in job configure page

2013-04-30 Thread matt.kr...@mlb.com (JIRA)















































Matt Krone
 commented on  JENKINS-9142


Add Build Step button broken in job configure page















I was able to resolve this issue by resolving a context path docBase misconfiguration in my tomcat configuration (server.xml).




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents

2013-04-30 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-17775


IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents















Integrated in  jenkins_main_trunk #2500
 FIXED JENKINS-17775 Find (model) parent POMs properly during fingerprint recording at end of build. (Revision 0c4fe2ddbac2963c0b633fe27bb1a6016134da50)

 Result = SUCCESS
Jesse Glick : 0c4fe2ddbac2963c0b633fe27bb1a6016134da50
Files : 

	changelog.html
	maven-plugin/src/main/java/hudson/maven/reporters/MavenFingerprinter.java
	maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
	maven-plugin/src/main/java/hudson/maven/MavenBuildInformation.java





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [copyartifact] (JENKINS-17596) NullPointerException on project rename
















































Jesse Glick
 resolved  JENKINS-17596 as Duplicate


NullPointerException on project rename
















Change By:


Jesse Glick
(30/Apr/13 5:20 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ant] (JENKINS-17705) NullPointerException when rename a job (Status Code: 500)
















































Jesse Glick
 resolved  JENKINS-17705 as Duplicate


NullPointerException when rename a job (Status Code: 500)
















Change By:


Jesse Glick
(30/Apr/13 5:20 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [copyartifact] (JENKINS-17447) NPE when renaming job
















































Jesse Glick
 resolved  JENKINS-17447 as Fixed


NPE when renaming job
















Was fixed in 4203fe7c16fe4bbe4efbc9bae87a329dfc1ec393.





Change By:


Jesse Glick
(30/Apr/13 5:21 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [copyartifact] (JENKINS-17447) NPE when renaming job
















































Jesse Glick
 assigned  JENKINS-17447 to Jesse Glick



NPE when renaming job
















Change By:


Jesse Glick
(30/Apr/13 5:23 PM)




Assignee:


JesseGlick



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [concurrent-build] (JENKINS-15098) svnexternals causing issues with concurrent builds

2013-04-30 Thread ai...@kevlarnetworks.com (JIRA)















































Aidan Lawn
 commented on  JENKINS-15098


svnexternals causing issues with concurrent builds















I see same issue with concurrent jobs.
Jenkins version: Jenkins ver. 1.491
Jenkins Subversion plugin version: 1.45 (was also occurring on 1.43 - I updated to latest but didn't help)

As a workaround I am going to have to make a parent job that does the checkout first, then the concurrent jobs can run. Not ideal and make not be suitable for others situations.

Note: We only see this issue under load, when I guess slower running checkouts makes the chance of collision higher.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [concurrent-build] (JENKINS-15098) svnexternals causing issues with concurrent builds

2013-04-30 Thread ai...@kevlarnetworks.com (JIRA)













































 
Aidan Lawn
 edited a comment on  JENKINS-15098


svnexternals causing issues with concurrent builds
















I see same issue with concurrent jobs.
Jenkins version: Jenkins ver. 1.491
Jenkins Subversion plugin version: 1.45 (was also occurring on 1.43 - I updated to latest but didn't help)

As a workaround I am going to have to make a parent job that does the checkout first, then the concurrent jobs can run. Not ideal and may not be suitable for others situations.

Note: We only see this issue under load, when I guess slower running checkouts makes the chance of collision higher.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-flow] (JENKINS-17806) Retry logic locks in case Jenkins is going to shutdown

2013-04-30 Thread soid....@hotmail.com (JIRA)















































Greg Temchenko
 created  JENKINS-17806


Retry logic locks in case Jenkins is going to shutdown















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


build-flow



Created:


30/Apr/13 6:15 PM



Description:


If Jenkins is going to shutdown and don't start new tasks, and the build flow job restarts a task (using retry() statement) and waits when it's done, then we have Jenkins locked when it can't shutdown and can't trigger new jobs.




Project:


Jenkins



Priority:


Minor



Reporter:


Greg Temchenko

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [hockeyapp] (JENKINS-17807) HockeyAppRecorder.getProjectActions throws NullPointerException

2013-04-30 Thread yildra...@gmail.com (JIRA)















































Guido van Loon
 created  JENKINS-17807


HockeyAppRecorder.getProjectActions throws NullPointerException















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


hockeyapp



Created:


30/Apr/13 6:21 PM



Description:


When getProjectActions is called before current build has a result, it throws a NullPointerException. The following code fails when the current build has no result yet, getResult() return null: 

CollectionAbstractBuild?, ? predicated = CollectionUtils.select(builds, new Predicate() {
public boolean evaluate(Object o) {
return ((AbstractBuild?, ?) o).getResult().isBetterOrEqualTo(
		Result.SUCCESS);
}
});

Steps to reproduce:
1. Configure EnvInject plugin to prepare the environment (use the EnvInjectListener)
2. Add HockeyApp plugin

EnvInject listener will call getProjectActions before the current build has a result.





Project:


Jenkins



Priority:


Major



Reporter:


Guido van Loon

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [hockeyapp] (JENKINS-17807) HockeyAppRecorder.getProjectActions throws NullPointerException

2013-04-30 Thread yildra...@gmail.com (JIRA)















































Guido van Loon
 updated  JENKINS-17807


HockeyAppRecorder.getProjectActions throws NullPointerException
















Change By:


Guido van Loon
(30/Apr/13 6:24 PM)




Description:


WhengetProjectActionsiscalledbeforecurrentbuildhasaresult,itthrowsaNullPointerException.Thefollowingcodefailswhenthecurrentbuildhasnoresultyet,getResult()
return
returns
null:CollectionAbstractBuild?,?predicated=CollectionUtils.select(builds,newPredicate(){publicbooleanevaluate(Objecto){return((AbstractBuild?,?)o).getResult().isBetterOrEqualTo(		Result.SUCCESS);}});Stepstoreproduce:1.ConfigureEnvInjectplugintopreparetheenvironment(usetheEnvInjectListener)2.AddHockeyApppluginEnvInjectlistenerwillcallgetProjectActionsbeforethecurrentbuildhasaresult.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-15717) InvalidClassException on SwapSpaceMonitor.MonitorTask

2013-04-30 Thread asmu...@gmail.com (JIRA)















































Asmund Ostvold
 commented on  JENKINS-15717


InvalidClassException on SwapSpaceMonitor.MonitorTask















I am running on a FC 17 using rpm jenkins-1.513-1.1.noarch and slaves are all local on the computer.  Only 1-2 out of the 18  nodes get this issue.  Jenkins "node" are named ao1, ao2, ao3 ao18 it is mostly ao1 and ao10 that get the issue. Current version on java used is:

 /usr/bin/java -version
java version "1.7.0_19"
OpenJDK Runtime Environment (fedora-2.3.9.1.fc17-x86_64)
OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)


Reproducing steps:
Remote FS root is /tmp/.  I stopped Jenkins made sure there was not slave.jar in /tmp. Started Jenkins and I got the issue. 

For node ao1 I have issues with 2 monitoring values: 

Apr 30, 2013 8:13:58 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run
WARNING: Failed to monitor ao1 for Free Swap Space
java.io.InvalidClassException: hudson.node_monitors.SwapSpaceMonitor$MonitorTask; local class incompatible: stream classdesc serialVersionUID = 1, local class serialVersionUID = 1184166703664094906
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:604)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
at hudson.remoting.UserRequest.perform(UserRequest.java:98)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)

Apr 30, 2013 8:13:58 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run
WARNING: Failed to monitor ao1 for Free Temp Space
hudson.util.IOException2: remote file operation failed: /tmp at hudson.remoting.Channel@35f5a0f0:ao1
at hudson.FilePath.act(FilePath.java:900)
at hudson.FilePath.act(FilePath.java:877)
at hudson.node_monitors.TemporarySpaceMonitor$1.getFreeSpace(TemporarySpaceMonitor.java:73)
at hudson.node_monitors.DiskSpaceMonitorDescriptor.monitor(DiskSpaceMonitorDescriptor.java:169)
at hudson.node_monitors.DiskSpaceMonitorDescriptor.monitor(DiskSpaceMonitorDescriptor.java:49)
at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:246)
Caused by: java.io.IOException: Remote call on ao1 failed
at hudson.remoting.Channel.call(Channel.java:681)
at hudson.FilePath.act(FilePath.java:893)
... 5 more
Caused by: java.lang.Error: Failed to deserialize the Callable object.
at hudson.remoting.UserRequest.perform(UserRequest.java:104)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.reflect.UndeclaredThrowableException
at com.sun.proxy.$Proxy5.fetch2(Unknown Source)
at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:127)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2451)
at

[JIRA] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39

2013-04-30 Thread david.robill...@gmail.com (JIRA)















































David Robillard
 commented on  JENKINS-15587


Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39















Same issue here.

OS : Windows Server 2008 R2 Standard Service Pack 1 with latest patches (as of April 30th, 2013)
JDK : Java version 1.6.0_43
Jenkins : 1.513

Same exact stack trace as the ones in this issue.

Let me know if I can help debug this issue?

Thanks,

David



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-17484) jelly null pointer
















































Jesse Glick
 resolved  JENKINS-17484 as Duplicate


jelly null pointer
















Change By:


Jesse Glick
(30/Apr/13 8:01 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-15309) NPE (isEmpty) from main.groovy
















































SCM/JIRA link daemon
 resolved  JENKINS-15309 as Fixed


NPE (isEmpty) from main.groovy
















Change By:


SCM/JIRA link daemon
(30/Apr/13 8:00 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-15309) NPE (isEmpty) from main.groovy















































SCM/JIRA link daemon
 commented on  JENKINS-15309


NPE (isEmpty) from main.groovy















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/ListView.java
 test/src/test/java/hudson/model/ListViewTest.java
 test/src/test/resources/hudson/model/ListViewTest/nullJobNames/config.xml
http://jenkins-ci.org/commit/jenkins/fd31a5d85c0a1fd4a310ced04bb3b714469b2d43
Log:
  FIXED JENKINS-15309 Be robust against serialized ListView with jobNames==null.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'

Matt Seashore
created JENKINS-17808

notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang

Issue Type:

Bug

Assignee:

Unassigned

Components:

subversion

Created:

30/Apr/13 8:33 PM

Description:

With version 1.44 the notifyCommit wget request returns in well under a second (almost instantly). With Jenkins Subversion plugin 1.45 the notifyCommit wget returns in around 20 seconds (that's the issue).

This slow response time is made worse by having this being called by a post-commit hook in SVN and the prescribed wget call doesn't not provide a 'tries' argument for retries, this causes wget to retry 20 times. The symptom is that I updated Jenkins and SVN commits suddenly take minutes of time (due to the interaction between wget retrying and the notifyCommit call taking 20 seconds).

I suspect this slowness has to do with svn:externals being resolved as that was added in 1.45 (Fixed: support for svn:externals (issue #16217 and issue #13790) and we have a lot of externals. If this is the case I would think that notifyCommit to return before resolving svn:externals.

I posted this question on the Google Group as well: https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/subversion%7Csort:date/jenkinsci-dev/nFGCnv_xyv4/a5IGqI1Hox0J

I can also provide more information if needed, just let me know what I can do or what would be helpful.

Environment:

Verified Bug with Jenkins 1.480.2 on RHEL 4 running under Tomcat 5 (notify commit slow with SVN 1.45, fast with 1.44)

Also verified bug with Jenkins 1.512 on CentOS 5.7 running under Winstone (notify commit slow with SVN 1.45, fast with SVN plugin 1.45)

On each server, we have subversion (1.7) repository with many external links (20) is set up to notify jenkins with the post-commit hook recommended on the Jenkins Subversion Wiki.

Project:

Jenkins

Priority:

Major

Reporter:

Matt Seashore

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'















































Matt Seashore
 updated  JENKINS-17808


notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang
















Change By:


Matt Seashore
(30/Apr/13 8:38 PM)




Description:


Withversion1.44thenotifyCommitwgetrequestreturnsinwellunderasecond(almostinstantly).WithJenkinsSubversionplugin1.45thenotifyCommitwgetreturnsinaround20seconds(thatstheissue).Thisslowresponsetimeismadeworsebyhavingthisbeingcalledbyapost-commithookinSVNandtheprescribedwgetcalldoesntnotprovideatriesargumentforretries,thiscauseswgettoretry20times.ThesymptomisthatIupdatedJenkinsandSVNcommitssuddenlytakeminutesoftime(duetotheinteractionbetweenwgetretryingandthenotifyCommitcalltaking20seconds).Isuspectthisslownesshastodowithsvn:externalsbeingresolvedasthatwasaddedin1.45(Fixed:supportforsvn:externals(issue#16217andissue#13790)andwehavealotofexternals.IfthisisthecaseIwouldthinkthatnotifyCommittoreturnbeforeresolvingsvn:externals.IpostedthisquestionontheGoogleGroupaswell:https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/subversion%7Csort:date/jenkinsci-dev/nFGCnv_xyv4/a5IGqI1Hox0JIcanalsoprovidemoreinformationifneeded,justletmeknowwhatIcandoorwhatwouldbehelpful.
Stepstoreproduce:-HaveanSVNrepositorywithquiteafewsvn:externals(Ihaventcreatedarepositoryfromscratchtotest)-Setupapostcommithookasperhttps://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugintonotifyjenkinsoncommit.-PerformaSVNcommitandnotifyittakesalongtime(2minutes)tocommit.-Checktheaccesslogandyoucanseewgetretryingabout20times.IfyourunwgetmanuallyagainstnotifyCommitanditwilltakeabout20seconds-farlongerthanthe2secondlimit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'















































Matt Seashore
 updated  JENKINS-17808


notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang
















Change By:


Matt Seashore
(30/Apr/13 8:41 PM)




Description:


Withversion1.44thenotifyCommitwgetrequestreturnsinwellunderasecond(almostinstantly).WithJenkinsSubversionplugin1.45thenotifyCommitwgetreturnsinaround20seconds(thatstheissue).Thisslowresponsetimeismadeworsebyhavingthisbeingcalledbyapost-commithookinSVNandtheprescribedwgetcalldoesntnotprovideatriesargumentforretries,thiscauseswgettoretry20times.ThesymptomisthatIupdatedJenkinsandSVNcommitssuddenlytakeminutesoftime(duetotheinteractionbetweenwgetretryingandthenotifyCommitcalltaking20seconds).Isuspectthisslownesshastodowithsvn:externalsbeingresolvedasthatwasaddedin1.45(Fixed:supportforsvn:externals(issue#16217andissue#13790)andwehavealotofexternals.IfthisisthecaseIwouldthinkthatnotifyCommittoreturnbeforeresolvingsvn:externals.IpostedthisquestionontheGoogleGroupaswell:https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/subversion%7Csort:date/jenkinsci-dev/nFGCnv_xyv4/a5IGqI1Hox0JIcanalsoprovidemoreinformationifneeded,justletmeknowwhatIcandoorwhatwouldbehelpful.Stepstoreproduce:-HaveanSVNrepositorywithquiteafewsvn:externals(Ihaventcreatedarepositoryfromscratchtotest
-IjustknowwehavequiteafewexternalsandhaveseeninthelogthembeingresolvedonwhennotifyCommitiscalled
)-Setupapostcommithookasperhttps://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugintonotifyjenkinsoncommit.-PerformaSVNcommitandnotifyittakesalongtime(2minutes)tocommit.-Checktheaccesslogandyoucanseewgetretryingabout20times.IfyourunwgetmanuallyagainstnotifyCommitanditwilltakeabout20seconds-farlongerthanthe2secondlimit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'















































Matt Seashore
 updated  JENKINS-17808


notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang
















Change By:


Matt Seashore
(30/Apr/13 8:41 PM)




Description:


Withversion1.44thenotifyCommitwgetrequestreturnsinwellunderasecond(almostinstantly).WithJenkinsSubversionplugin1.45thenotifyCommitwgetreturnsinaround20seconds(thatstheissue).Thisslowresponsetimeismadeworsebyhavingthisbeingcalledbyapost-commithookinSVNandtheprescribedwgetcalldoesntnotprovideatriesargumentforretries,thiscauseswgettoretry20times.ThesymptomisthatIupdatedJenkinsandSVNcommitssuddenlytakeminutesoftime(duetotheinteractionbetweenwgetretryingandthenotifyCommitcalltaking20seconds).Isuspectthisslownesshastodowithsvn:externalsbeingresolvedasthatwasaddedin1.45(Fixed:supportforsvn:externals(issue#16217andissue#13790)andwehavealotofexternals.IfthisisthecaseIwouldthinkthatnotifyCommittoreturnbeforeresolvingsvn:externals.IpostedthisquestionontheGoogleGroupaswell:https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/subversion%7Csort:date/jenkinsci-dev/nFGCnv_xyv4/a5IGqI1Hox0JIcanalsoprovidemoreinformationifneeded,justletmeknowwhatIcandoorwhatwouldbehelpful.Stepstoreproduce:-HaveanSVNrepositorywithquiteafewsvn:externals(Ihaventcreatedarepositoryfromscratchtotest-IjustknowwehavequiteafewexternalsandhaveseeninthelogthembeingresolvedonwhennotifyCommitiscalled)-Setupapostcommithookasperhttps://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugintonotifyjenkinsoncommit.-PerformaSVNcommitand
notify
notice
ittakesalongtime(2minutes)tocommit.-Checktheaccesslogandyoucanseewgetretryingabout20times.IfyourunwgetmanuallyagainstnotifyCommitanditwilltakeabout20seconds-farlongerthanthe2secondlimit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'















































Matt Seashore
 updated  JENKINS-17808


notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang
















Change By:


Matt Seashore
(30/Apr/13 8:42 PM)




Environment:


VerifiedBugwithJenkins1.480.2onRHEL4runningunderTomcat5(notifycommitslowwithSVN1.45,fastwith1.44)AlsoverifiedbugwithJenkins1.512onCentOS5.7runningunderWinstone(notifycommitslowwithSVN1.45,fastwithSVNplugin1.
45
44
)Oneachserver,wehavesubversion(1.7)repositorywithmanyexternallinks(20)issetuptonotifyjenkinswiththepost-commithookrecommendedontheJenkinsSubversionWiki.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'















































Matt Seashore
 updated  JENKINS-17808


notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang
















Change By:


Matt Seashore
(30/Apr/13 8:44 PM)




Description:


Withversion1.44thenotifyCommitwgetrequestreturnsinwellunderasecond(almostinstantly).WithJenkinsSubversionplugin1.45thenotifyCommitwgetreturnsinaround20seconds(thatstheissue).Thisslowresponsetimeismadeworsebyhavingthisbeingcalledbyapost-commithookinSVNandtheprescribedwgetcalldoesnt
not
provideatriesargument
for
tolimit
retries
,this
.This
causeswgettoretry20times.ThesymptomisthatIupdatedJenkinsandSVNcommitssuddenlytakeminutesoftime(duetotheinteractionbetweenwgetretryingandthenotifyCommitcalltaking20seconds).Isuspectthisslownesshastodowithsvn:externalsbeingresolvedasthatwasaddedin1.45(Fixed:supportforsvn:externals(issue#16217andissue#13790)andwehavealotofexternals.IfthisisthecaseIwouldthinkthatnotifyCommit
to
could
return
aresponse
beforeresolvingsvn:externals.IpostedthisquestionontheGoogleGroupaswell:https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/subversion%7Csort:date/jenkinsci-dev/nFGCnv_xyv4/a5IGqI1Hox0JIcanalsoprovidemoreinformationifneeded,justletmeknowwhatIcandoorwhatwouldbehelpful.Stepstoreproduce:-HaveanSVNrepositorywithquiteafewsvn:externals(Ihaventcreatedarepositoryfromscratchtotest-IjustknowwehavequiteafewexternalsandhaveseeninthelogthembeingresolvedonwhennotifyCommitiscalled)-Setupapostcommithookasperhttps://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugintonotifyjenkinsoncommit.-PerformaSVNcommitandnoticeittakesalongtime(2minutes)tocommit.-Checktheaccesslogandyoucanseewgetretryingabout20times.IfyourunwgetmanuallyagainstnotifyCommitanditwilltakeabout20seconds-farlongerthanthe2secondlimit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-15309) NPE (isEmpty) from main.groovy

2013-04-30 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-15309


NPE (isEmpty) from main.groovy















Integrated in  jenkins_main_trunk #2501
 FIXED JENKINS-15309 Be robust against serialized ListView with jobNames==null. (Revision fd31a5d85c0a1fd4a310ced04bb3b714469b2d43)

 Result = SUCCESS
Jesse Glick : fd31a5d85c0a1fd4a310ced04bb3b714469b2d43
Files : 

	test/src/test/java/hudson/model/ListViewTest.java
	test/src/test/resources/hudson/model/ListViewTest/nullJobNames/config.xml
	changelog.html
	core/src/main/java/hudson/model/ListView.java





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [m2release] (JENKINS-17778) Allow to specify module versions when releasing multi module projects

2013-04-30 Thread tu...@slac.stanford.edu (JIRA)

Massimiliano Turri
commented on JENKINS-17778

Allow to specify module versions when releasing multi module projects

After further investigation it seems that, at the maven execution level, the problem with multi-module projects is due to the provided properties: developmentVersion and releaseVersion. When these properties are provided the versions of the child modules are forced to be identical to the version of the parent project.

The m2release plugin provides the configuration option "Default versioning mode". At the moment it seems that it does not allow users to change it from its default value of "None" which seems to correspond to allowing users to specify one single version for all modules.

One simple solution might be to allow users to choose as default versioning something like "let maven pick" which would correspond to a maven execution command without the properties "developmentVersion" and "releaseVersion".

In this instance the versions should be picked up from the pom files of each of the sub-modules.

Thanks!

[JIRA] [core] (JENKINS-16956) Authentication associated with a build















































Jesse Glick
 commented on  JENKINS-16956


Authentication associated with a build















CommandDuringBuild should also automatically authenticate you based on the running build.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'















































Matt Seashore
 updated  JENKINS-17808


notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang
















Change By:


Matt Seashore
(30/Apr/13 9:46 PM)




Description:


Withversion1.44thenotifyCommitwgetrequestreturnsinwellunderasecond(almostinstantly).WithJenkinsSubversionplugin1.45thenotifyCommitwgetreturnsinaround20seconds
(
.Thisbasicallymeans
that
stheissue
evenifweconfigurewgettohavea30secondtimeout(andnotretry
)
.
allSVNcommitstake30secondsataminimum!
Thisslowresponsetimeismadeworsebyhavingthisbeingcalledbyapost-commithookinSVNandtheprescribedwgetcalldoesntprovideatriesargumenttolimitretries.Thiscauseswgettoretry20times.ThesymptomisthatIupdatedJenkinsandSVNcommitssuddenlytakeminutesoftime(duetotheinteractionbetweenwgetretryingandthenotifyCommitcalltaking20seconds).Isuspectthisslownesshastodowithsvn:externalsbeingresolvedasthatwasaddedin1.45(Fixed:supportforsvn:externals(issue#16217andissue#13790)andwehavealotofexternals.IfthisisthecaseIwouldthinkthatnotifyCommitcouldreturnaresponsebeforeresolvingsvn:externals.IpostedthisquestionontheGoogleGroupaswell:https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/subversion%7Csort:date/jenkinsci-dev/nFGCnv_xyv4/a5IGqI1Hox0JIcanalsoprovidemoreinformationifneeded,justletmeknowwhatIcandoorwhatwouldbehelpful.Stepstoreproduce:-HaveanSVNrepositorywithquiteafewsvn:externals(Ihaventcreatedarepositoryfromscratchtotest-IjustknowwehavequiteafewexternalsandhaveseeninthelogthembeingresolvedonwhennotifyCommitiscalled)-Setupapostcommithookasperhttps://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugintonotifyjenkinsoncommit.-PerformaSVNcommitandnoticeittakesalongtime(2minutes)tocommit.-Checktheaccesslogandyoucanseewgetretryingabout20times.IfyourunwgetmanuallyagainstnotifyCommitanditwilltakeabout20seconds-farlongerthanthe2secondlimit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-17808) notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to 'hang'















































Matt Seashore
 updated  JENKINS-17808


notifyCommit response time far slower in Subversion plugin 1.45 vs 1.44 - causes svn checkouts to hang
















Change By:


Matt Seashore
(30/Apr/13 9:47 PM)




Description:


Withversion1.44thenotifyCommitwgetrequestreturnsinwellunderasecond(almostinstantly).WithJenkinsSubversionplugin1.45thenotifyCommitwgetreturnsinaround20seconds.Thisbasicallymeansthatevenifweconfigurewgettohavea30secondtimeout(andnotretry)allSVNcommitstake
30
~20
secondsataminimum!Thisslowresponsetimeismadeworsebyhavingthisbeingcalledbyapost-commithookinSVNandtheprescribedwgetcalldoesntprovideatriesargumenttolimitretries.Thiscauseswgettoretry20times.ThesymptomisthatIupdatedJenkinsandSVNcommitssuddenlytakeminutesoftime(duetotheinteractionbetweenwgetretryingandthenotifyCommitcalltaking20seconds).Isuspectthisslownesshastodowithsvn:externalsbeingresolvedasthatwasaddedin1.45(Fixed:supportforsvn:externals(issue#16217andissue#13790)andwehavealotofexternals.IfthisisthecaseIwouldthinkthatnotifyCommitcouldreturnaresponsebeforeresolvingsvn:externals.IpostedthisquestionontheGoogleGroupaswell:https://groups.google.com/forum/?fromgroups=#!searchin/jenkinsci-dev/subversion%7Csort:date/jenkinsci-dev/nFGCnv_xyv4/a5IGqI1Hox0JIcanalsoprovidemoreinformationifneeded,justletmeknowwhatIcandoorwhatwouldbehelpful.Stepstoreproduce:-HaveanSVNrepositorywithquiteafewsvn:externals(Ihaventcreatedarepositoryfromscratchtotest-IjustknowwehavequiteafewexternalsandhaveseeninthelogthembeingresolvedonwhennotifyCommitiscalled)-Setupapostcommithookasperhttps://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugintonotifyjenkinsoncommit.-PerformaSVNcommitandnoticeittakesalongtime(2minutes)tocommit.-Checktheaccesslogandyoucanseewgetretryingabout20times.IfyourunwgetmanuallyagainstnotifyCommitanditwilltakeabout20seconds-farlongerthanthe2secondlimit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [publish-over-ssh] (JENKINS-17809) Problem executing commands on Windows over SSH

2013-04-30 Thread e...@wp.pl (JIRA)

Maciej Jaros
created JENKINS-17809

Problem executing commands on Windows over SSH

Issue Type:

Bug

Assignee:

bap

Components:

publish-over-ssh

Created:

30/Apr/13 10:07 PM

Description:

When trying to execute a command over SSH I get:
SSH: EXEC: STDOUT/STDERR from command [.../some.exe
] ...
AllowDesktopAccess failed.
Unable to execute command or shell on remote system: Failed to Execute process.

This seems like a bug because SSH seem to work otherwise:
1. Transferring files with Jenkins over SSH works fine.
2. Executing commands from PuTTy, from my other Windows machine works (it is a bit slow, but works).
3. Executing commands from the computer Jenkins is on (over command line ssh client) also works.

Currently FreeSSHd is running as a service and I've set up logging in with Windows auth, but auth itself seem to be working fine even with Jenkins (test of setup passed, transferring files works fine).

Environment:

Jenkins is on CentOS on Tomcat,

SSH server is on Windows 7 x32 (FreeSSHd as a service).

Project:

Jenkins

Labels:

windows
ssh

Priority:

Major

Reporter:

Maciej Jaros

[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds















































SCM/JIRA link daemon
 commented on  JENKINS-15081


Errors with multiple EC2 Clouds















Code changed in jenkins
User: Francis Upton
Path:
 src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java
 src/main/java/hudson/plugins/ec2/EC2Computer.java
 src/main/java/hudson/plugins/ec2/EC2ComputerLauncher.java
 src/main/java/hudson/plugins/ec2/EC2OndemandSlave.java
 src/main/java/hudson/plugins/ec2/EC2SpotSlave.java
 src/main/java/hudson/plugins/ec2/SlaveTemplate.java
 src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java
http://jenkins-ci.org/commit/ec2-plugin/5da8f6be66e839e33923cbf5e8b62b0f6c4b7bfc
Log:
  Merge pull request #48 from rsennewald/jenkins-15081

Fix to allow multiple EC2Clouds (fix for JENKINS-15081)


Compare: https://github.com/jenkinsci/ec2-plugin/compare/881b2b80e488...5da8f6be66e8




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds

2013-04-30 Thread fran...@oaklandsoftware.com (JIRA)
















































Francis Upton
 resolved  JENKINS-15081 as Fixed


Errors with multiple EC2 Clouds
















Change By:


Francis Upton
(30/Apr/13 11:08 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [jenkins-multijob-plugin] (JENKINS-17810) Multijob hierarchy is not shown when jobs inside of the phases are Monitor an external job

2013-04-30 Thread vorbi...@gmail.com (JIRA)















































Vitaliy Orbidan
 created  JENKINS-17810


Multijob hierarchy is not shown when jobs inside of the phases are Monitor an external job















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


jenkins-multijob-plugin



Created:


30/Apr/13 11:17 PM



Description:


Trying to group some of the "Monitor an external job" type of jobs into a multijob view to display so called steps' status.
Unfortunately the Multijob view does not show




Environment:


Windows




Project:


Jenkins



Priority:


Major



Reporter:


Vitaliy Orbidan

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ec2] (JENKINS-14124) Failed to connect AMI when Jenkins has defined 2 EC2 regions















































Ray Sennewald
 commented on  JENKINS-14124


Failed to connect AMI when Jenkins has defined 2 EC2 regions















This is a duplicate of JENKINS-15081 and has been resolved with this merge: https://github.com/jenkinsci/ec2-plugin/commit/5da8f6be66e839e33923cbf5e8b62b0f6c4b7bfc .



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ec2] (JENKINS-14124) Failed to connect AMI when Jenkins has defined 2 EC2 regions
















































Ray Sennewald
 resolved  JENKINS-14124 as Duplicate


Failed to connect AMI when Jenkins has defined 2 EC2 regions
















Change By:


Ray Sennewald
(30/Apr/13 11:49 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ec2] (JENKINS-12669) ec2 plugin fails to launch slave with The instance ID 'i-xxxx' does not exist when more than 1 region is configured.
















































Ray Sennewald
 resolved  JENKINS-12669 as Duplicate


ec2 plugin fails to launch slave with The instance ID i- does not exist when more than 1 region is configured.
















This is again a duplicate of JENKINS-15081 which is fixed with this merge: https://github.com/jenkinsci/ec2-plugin/commit/5da8f6be66e839e33923cbf5e8b62b0f6c4b7bfc .





Change By:


Ray Sennewald
(30/Apr/13 11:51 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ec2] (JENKINS-12547) ec2-plugin doesn't allow for multiple EC2 clouds to be configured