date:20140408















































Stefano Padovan
 created  JENKINS-22530


ArrayIndexOutOfBoundsException when parsing properties















Issue Type:


Bug



Assignee:


Stefano Padovan



Components:


android-emulator



Created:


08/Apr/14 9:24 AM



Description:


a java property value can be wrapped in more than one line:


name = value\
split\
in\
more\
lines\



The code in hudson.plugins.android_emulator.util.Utils.parseConfigFile does not take this into account and tries to split every non-empty line at the = char. This causes an ArrayIndexOutOfBoundsException in the above situation.

proposed fix:

public static MapString,String parseConfigFile(File configFile) throws IOException {
	FileReader fileReader = new FileReader(configFile);
	BufferedReader reader = new BufferedReader(fileReader);
	Properties properties = new Properties();
	properties.load(reader);
	reader.close();
	
	final MapString,String values = new HashMapString,String();
	for (final EntryObject, Object entry : properties.entrySet()) {
		values.put((String) entry.getKey(), (String) entry.getValue());
	}

	return values;
}






Project:


Jenkins



Priority:


Major



Reporter:


Stefano Padovan

























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/d/optout.

[JIRA] [jobgenerator] (JENKINS-22439) Conditional build steps are no longer resolved when generating jobs after core upgrade to 1.556

2014-04-08 Thread ra...@java.net (JIRA)















































Krzysztof Malinowski
 commented on  JENKINS-22439


Conditional build steps are no longer resolved when generating jobs after core upgrade to 1.556















I use Strings match, Regular _expression_ match and File exists conditions. It used to work OK, resolving strings and regex matches on generation level and keeping File exists condition in the generated job, which was exactly what I wanted. The log was like this:

Before
...
16:30:21 [EnvInject] - Variables injected successfully.
16:30:21 [EnvInject] - Injecting contributions.
16:30:21 Building on master in workspace /jenkins/jenkins_home/jobs/generator-klocwork/workspace@6
16:30:21 
16:30:21 Deleting project workspace... Strings match run condition: string 1=[https://server:8072], string 2=[]
16:30:21 Strings match run condition: string 1=[9.6.2], string 2=[]
16:30:21 Regular _expression_ run condition: _expression_=[^3[24]$], Label=[34]
16:30:21 Regular _expression_ run condition: _expression_=[^27|33$], Label=[34]
16:30:21 Regular _expression_ run condition: _expression_=[^14$], Label=[34]
16:30:22 Finished: SUCCESS



Now, all condition steps are copied into generated job, none is evaluated on the generation level:

After
...
10:40:46 [EnvInject] - Variables injected successfully.
10:40:46 [EnvInject] - Injecting contributions.
10:40:46 Building on master in workspace /jenkins/jenkins_home/jobs/generator-klocwork/workspace
10:40:46 
10:40:47 Deleting project workspace... Finished: SUCCESS



I am not entirely convinced it happened because of core upgrade as they were also some more plugins upgraded at the same time, but it's the only change that comes to my mind which may have affected behavior. Am I missing something here?

BTW. Comparing now those two outputs I noticed two things:
1. The working version used workspace with @6 which I think is used only for concurrent runs of the same job. This has changed.
2. The build was always done on master. I don't know if it's important, but our master is configured to have 0 executors, so that all builds are always run on slaves. This may or may not have impact on this issue, but I thought it's good to mention it for reference.



























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/d/optout.

[JIRA] [parameterized-remote-trigger] (JENKINS-22427) Parameterized Remote Trigger Plugin fails when remote job waits for available executor

2014-04-08 Thread vanpoppel.ke...@gmail.com (JIRA)















































Kevin Van Poppel
 commented on  JENKINS-22427


Parameterized Remote Trigger Plugin fails when remote job waits for available executor















Changing the poll interval didn't change anything here. 
The job already failed before polling the first time, because you get the 404 error.

Do any of you guys know a way to check if the triggerd build is in the remote server's queue?



























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/d/optout.

[JIRA] [android-emulator] (JENKINS-22530) ArrayIndexOutOfBoundsException when parsing properties

2014-04-08 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-22530


ArrayIndexOutOfBoundsException when parsing properties















Do you have an example of an Android emulator config file that shows this problem?
How was it created?



























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/d/optout.

[JIRA] [update-center] (JENKINS-19771) Fresh LTS installation uses non-LTS update site

2014-04-08 Thread langui...@semipol.de (JIRA)















































Johannes Wienke
 commented on  JENKINS-19771


Fresh LTS installation uses non-LTS update site















This is still a major issue for us as we are automating the installation of jenkins and changing the URL with a script is a major pain.



























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/d/optout.

[JIRA] [rabbitmq-consumer] (JENKINS-19296) Impossible to disable TLD checking for RabbitMQ Consumer Plugin

2014-04-08 Thread rin...@java.net (JIRA)
















































rin_ne
 closed  JENKINS-19296 as Wont Fix


Impossible to disable TLD checking for RabbitMQ Consumer Plugin
















No answer by the end of the last month. So closed.





Change By:


rin_ne
(08/Apr/14 10:01 AM)




Status:


Open
Closed





Resolution:


WontFix



























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/d/optout.

[JIRA] [android-emulator] (JENKINS-22530) ArrayIndexOutOfBoundsException when parsing properties















































Stefano Padovan
 commented on  JENKINS-22530


ArrayIndexOutOfBoundsException when parsing properties















see https://github.com/jenkinsci/android-emulator-plugin/pull/35



























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/d/optout.

[JIRA] [android-emulator] (JENKINS-22530) ArrayIndexOutOfBoundsException when parsing properties















































Stefano Padovan
 commented on  JENKINS-22530


ArrayIndexOutOfBoundsException when parsing properties















i created like that 

I have many proguard config files to inclue, so instead of having all of them in one big line i have something like:

proguard.config=\
./proguard.cfg:\
../library1/proguard.cfg:\
../library2/proguard.cfg:\
../library3/proguard.cfg





























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/d/optout.

[JIRA] [android-emulator] (JENKINS-22530) ArrayIndexOutOfBoundsException when parsing properties













































 
Stefano Padovan
 edited a comment on  JENKINS-22530


ArrayIndexOutOfBoundsException when parsing properties
















i created it like that 

I have many proguard config files to inclue, so instead of having all of them in one big line i have something like:

proguard.config=\
./proguard.cfg:\
../library1/proguard.cfg:\
../library2/proguard.cfg:\
../library3/proguard.cfg





























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/d/optout.

[JIRA] [android-emulator] (JENKINS-22530) ArrayIndexOutOfBoundsException when parsing properties

2014-04-08 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-22530


ArrayIndexOutOfBoundsException when parsing properties















Ah right, I was forgetting that this code is also used to parse `project.properties` files.



























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/d/optout.

[JIRA] [email-ext] (JENKINS-22531) Date in changeset is in wrong format















































Nir Reuveny
 created  JENKINS-22531


Date in changeset is in wrong format















Issue Type:


Bug



Assignee:


Alex Earl



Components:


email-ext



Created:


08/Apr/14 11:16 AM



Description:


We use custom jelly email template, and it used to work fine. but at some point (maybe jenkins version upgrade or plugin upgrade), the date is showing as below in the email (seems like wrong unix time conversion)

CHANGES
by XXX1970-01-17T04:01:10+ +0300)

this is an example of an old email we have from the time it worked well:

by XXX2014-03-24 16:54:00 +0200)

this is the section in the jelly template we use:

j:forEach var="cs" items="${changeSet}" varStatus="loop"
  j:set var="hadChanges" value="true" /
  j:set var="aUser" value="${cs.hudsonUser}"/
  TR
TD colspan="2" class="bg2"${spc}by
  B${aUser!=null?aUser.displayName:cs.author.displayName}: /B
  B(${cs.date})/B
  B${cs.msgAnnotated}/B
 /TD

How can we fix this?...
Please help 




Project:


Jenkins



Priority:


Major



Reporter:


Nir Reuveny

























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/d/optout.

[JIRA] [email-ext] (JENKINS-22531) Date in changeset is in wrong format















































Alex Earl
 commented on  JENKINS-22531


Date in changeset is in wrong format















The date comes directly from the changeset object for the SCM you are using, it has nothing to do with email-ext itself. What SCM are you using and did you upgrade that plugin recently?



























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/d/optout.

[JIRA] [email-ext] (JENKINS-22531) Date in changeset is in wrong format















































Nir Reuveny
 commented on  JENKINS-22531


Date in changeset is in wrong format















We use bitbucket. but if I view the git log, it shows the correct timestamp.
we upgraded jenkins and the plugins and moved to bitbucket around the same time, so I'm not sure which one is the cause...
how can we fix 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/d/optout.

[JIRA] [email-ext] (JENKINS-22531) Date in changeset is in wrong format















































Alex Earl
 commented on  JENKINS-22531


Date in changeset is in wrong format















Looks like the git plugin changed the date format they used. https://github.com/jenkinsci/git-plugin/commit/430bdc9b6ed121d653ef2633d2109b259aa8687b 



























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/d/optout.

[JIRA] [metadata-plugin] (JENKINS-22532) 404 Error returned by MetadataChecks on configure pages when jenkins not at server root

2014-04-08 Thread timl...@gmail.com (JIRA)















































Tim Lewy
 created  JENKINS-22532


404 Error returned by MetadataChecks on configure pages when jenkins not at server root















Issue Type:


Bug



Affects Versions:


current



Assignee:


rsandell



Components:


metadata-plugin



Created:


08/Apr/14 11:40 AM



Description:


version metadata-plugin 1.1.0b
jenkins core v1.556
apache tomcat 7.0.52
jenkins acccessible at http://IP:8080/jenkins/

Steps to reproduce:

	Install clean jenkins
	Add metadata plugin
	Login
	Click Manage Jenkins
	Click Manage Nodes
	Click on "master"
	Click "Configure"
	Enable metadata
	Add string metadata item
	Enter any string in name field
	Click in value field



Observed behaviour:

	Apache 404 error displayed under metadata item



Expected Result:

	No errors displayed






Project:


Jenkins



Priority:


Major



Reporter:


Tim Lewy

























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/d/optout.

[JIRA] [email-ext] (JENKINS-22531) Date in changeset is in wrong format















































Nir Reuveny
 commented on  JENKINS-22531


Date in changeset is in wrong format















So what can we do to get the correct format using the email-ext plugin?...



























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/d/optout.

[JIRA] [email-ext] (JENKINS-22531) Date in changeset is in wrong format















































Alex Earl
 commented on  JENKINS-22531


Date in changeset is in wrong format















Since the getDate() method returns a string, you'd have to parse the string back into a date object and then format the date how you want. If you need additional help, please use the mailing list as this is not a 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/d/optout.

[JIRA] [metadata-plugin] (JENKINS-22532) 404 Error returned by MetadataChecks on configure pages when jenkins not at server root

2014-04-08 Thread timl...@gmail.com (JIRA)















































Tim Lewy
 updated  JENKINS-22532


404 Error returned by MetadataChecks on configure pages when jenkins not at server root
















Change By:


Tim Lewy
(08/Apr/14 11:47 AM)




Description:


versionmetadata-plugin1.1.0bjenkinscorev1.556apachetomcat7.0.52jenkinsacccessibleathttp://IP:8080/jenkins/Stepstoreproduce:-Installcleanjenkins-Addmetadataplugin-Login-ClickManageJenkins-ClickManageNodes-Clickonmaster-ClickConfigure-Enablemetadata-Addstringmetadataitem-Enteranystringinnamefield-ClickinvaluefieldObservedbehaviour:-Apache404errordisplayedundermetadataitemExpectedResult:-Noerrorsdisplayed
Issue/SuggestedFix:-Urlsinthejellyfilesareusingpathsrelativefromserverroot,e.g./MetadataChecks/checkName.TheyshouldbeusingoneoftheJenkins/HudsonURLvariablessuchas${rootURL}toobtainthecorrectaddress.



























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/d/optout.

[JIRA] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.

2014-04-08 Thread tomasz.nowodzin...@gmail.com (JIRA)















































Tomasz Nowodziński
 commented on  JENKINS-22011


Performance plugin report not failing build based on relative thresholds.  















Is there any estimated time to fix this issue?



























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/d/optout.

[JIRA] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command

2014-04-08 Thread satyaas...@gmail.com (JIRA)
















































Satya Asati
 assigned  JENKINS-22383 to Satya Asati



Failure found during the build process of RTRT using windows batch command
















Change By:


Satya Asati
(08/Apr/14 12:08 PM)




Assignee:


SatyaAsati



























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/d/optout.

[JIRA] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command

2014-04-08 Thread satyaas...@gmail.com (JIRA)
















































Satya Asati
 assigned  JENKINS-22383 to jenkins jenkins



Failure found during the build process of RTRT using windows batch command
















Change By:


Satya Asati
(08/Apr/14 12:10 PM)




Assignee:


jenkinsjenkins



























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/d/optout.

[JIRA] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command

2014-04-08 Thread satyaas...@gmail.com (JIRA)
















































Satya Asati
 assigned  JENKINS-22383 to Unassigned



Failure found during the build process of RTRT using windows batch command
















Change By:


Satya Asati
(08/Apr/14 12:09 PM)




Assignee:


SatyaAsati



























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/d/optout.

[JIRA] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command

2014-04-08 Thread j.dun...@wintoncapital.com (JIRA)
















































jenkins jenkins
 assigned  JENKINS-22383 to Unassigned



Failure found during the build process of RTRT using windows batch command
















Please do not assign tasks to "Jenkins Jenkins".





Change By:


jenkins jenkins
(08/Apr/14 12:13 PM)




Assignee:


jenkinsjenkins



























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/d/optout.

[JIRA] [config-rotator] (JENKINS-22533) Infinite loop for invalid configuration, our case 10257

2014-04-08 Thread m...@praqma.net (JIRA)















































Mads Nielsen
 created  JENKINS-22533


Infinite loop for invalid configuration, our case 10257















Issue Type:


Bug



Affects Versions:


current



Assignee:


Praqma Support



Components:


config-rotator



Created:


08/Apr/14 12:31 PM



Project:


Jenkins



Priority:


Major



Reporter:


Mads Nielsen

























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/d/optout.

[JIRA] [config-rotator] (JENKINS-22533) Infinite loop for invalid configuration, our case 10257

2014-04-08 Thread m...@praqma.net (JIRA)
















































Mads Nielsen
 resolved  JENKINS-22533 as Fixed


Infinite loop for invalid configuration, our case 10257
















Change By:


Mads Nielsen
(08/Apr/14 12:31 PM)




Status:


Open
Resolved





Fix Version/s:


current





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/d/optout.

[JIRA] [email-ext] (JENKINS-22531) Date in changeset is in wrong format
















































Alex Earl
 resolved  JENKINS-22531 as Not A Defect


Date in changeset is in wrong format
















This is not a bug, it looks like the Git plugin changed the format for the date returned from the change set.





Change By:


Alex Earl
(08/Apr/14 12:28 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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/d/optout.

[JIRA] [clone-workspace] (JENKINS-7260) Clone workspace doesn't copy empty directories when cloning entire workspace

2014-04-08 Thread jfig...@java.net (JIRA)















































jfigler
 commented on  JENKINS-7260


Clone workspace doesnt copy empty directories when cloning entire workspace















Hi  I'm curious if anyone knows of a workaround for this issue?



























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/d/optout.

[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7

2014-04-08 Thread gregpeter...@gmail.com (JIRA)















































Greg Peters
 commented on  JENKINS-22393


Problem deploying EAR to WAS 7















What type of WebSphere are you using? ND? Standard?



























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/d/optout.

[JIRA] [maven] (JENKINS-22534) maven ignore test failures when pom declares buildExtension

2014-04-08 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-22534


maven ignore test failures when pom declares buildExtension















Issue Type:


Bug



Assignee:


Unassigned


Components:


maven



Created:


08/Apr/14 1:35 PM



Description:


to reproduce :


	create a maven project using default archetype.
	setup maven to build it
	change test to fail : `assertTrue(false)`
	jenkins detects test failure




	add build extension co.leantechniques:maven-buildtime-extension:1.0 to pom.xml
	confirm on command line maven still detect test failures :

---
 T E S T S
---
Running foo.AppTest
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec  FAILURE!
testApp(foo.AppTest)  Time elapsed: 0.008 sec   FAILURE!
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at foo.AppTest.testApp(AppTest.java:36)






	run same project on jenkins :

---
 T E S T S
---
Running foo.AppTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec

Results :

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0








Project:


Jenkins



Priority:


Minor



Reporter:


Nicolas De Loof

























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/d/optout.

[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException

2014-04-08 Thread sampo.niska...@iki.fi (JIRA)















































Sampo Niskanen
 commented on  JENKINS-18687


Intermittent failure whilst recording test results caused by java.util.MissingResourceException















I have the same issue (after adding a new slave), but it doesn't seem intermittent.  I've received it twice in a row.

The console output just indicates a failure, though the XML file does not contain any errors:

Recording test results
Build step 'Publish JUnit test result report' changed build result to UNSTABLE
Finished: UNSTABLE

When I go check the test results, I find the following stack trace:

Failed to read test report file /home/weller/jenkins/workspace/TEST_VISUAL/output/junit/TEST-features-visuals-visuals.xml
org.dom4j.DocumentException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages Nested exception: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages
	at org.dom4j.io.SAXReader.read(SAXReader.java:484)
	at org.dom4j.io.SAXReader.read(SAXReader.java:264)
	at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:130)
	at hudson.tasks.junit.TestResult.parse(TestResult.java:274)
	at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:230)
	at hudson.tasks.junit.TestResult.parse(TestResult.java:165)
	at hudson.tasks.junit.TestResult.parse(TestResult.java:148)
	at hudson.tasks.junit.TestResult.init(TestResult.java:124)
	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117)
	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2439)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	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:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)
Caused by: java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages
	at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174)
	at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166)
	at com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:57)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.getProperty(AbstractSAXParser.java:2060)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty(SAXParserImpl.java:490)
	at org.dom4j.io.SAXHelper.setParserProperty(SAXHelper.java:34)
	at org.dom4j.io.SAXReader.configureReader(SAXReader.java:911)
	at org.dom4j.io.SAXReader.read(SAXReader.java:463)
	... 19 more
Nested exception: 
java.util.MissingResourceException: Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.SAXMessages
	at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:174)
	at com.sun.org.apache.xerces.internal.utils.SecuritySupport$7.run(SecuritySupport.java:166)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.org.apache.xerces.internal.utils.SecuritySupport.getResourceBundle(SecuritySupport.java:166)
	at com.sun.org.apache.xerces.internal.util.SAXMessageFormatter.formatMessage(SAXMessageFormatter.java:57)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.getProperty(AbstractSAXParser.java:2060)
	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.setProperty(SAXParserImpl.java:490)
	at org.dom4j.io.SAXHelper.setParserProperty(SAXHelper.java:34)
	at org.dom4j.io.SAXReader.configureReader(SAXReader.java:911)
	at org.dom4j.io.SAXReader.read(SAXReader.java:463)
	at org.dom4j.io.SAXReader.read(SAXReader.java:264)
	at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:130)
	at hudson.tasks.junit.TestResult.parse(TestResult.java:274)
	at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:230)
	at

[JIRA] [matrix-reloaded] (JENKINS-22535) Matrix Reloaded plugin overwrites existing builds

2014-04-08 Thread mirocu...@gmail.com (JIRA)

Miroslav Cupak
created JENKINS-22535

Matrix Reloaded plugin overwrites existing builds

Issue Type:

Bug

Affects Versions:

current

Assignee:

Praqma Support

Components:

matrix-reloaded

Created:

08/Apr/14 2:08 PM

Description:

Occasionally, Matrix Reloaded plugin executes "reloaded" builds with the same build number as the original builds, thus overwriting the original ones and losing the information. In this case, the plugin does not create a build for the matrix parent, it only executes the selected "subbuilds" in the place of the original builds.

This is very tricky to reproduce and although I encountered this many times, I'm not entirely sure if I found a way to reproduce this reliably. The following steps worked most of the time:

1, Execute a matrix build with all the configurations the usual way (without Matrix Reloaded plugin).
2, Use the Matrix Reloaded plugin to execute a single configuration one more time (i.e. we want to have a build not executing all the configurations).
3, Wait for the build to finish, then go to the page of the configuration you built in step 2, i.e. http://server:port/jenkins/job/my_job/my_configuration/my_build_number/. It is important to go to this page rather than the similar page of the parent itself.
4, Click the Matrix Reloaded link, select one of the configurations other than the current one and confirm the dialog. You should now be able to see the configuration executing even though no parent build was spawn.

Project:

Jenkins

Priority:

Major

Reporter:

Miroslav Cupak

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/d/optout.

[JIRA] [matrix-reloaded] (JENKINS-22535) Matrix Reloaded plugin overwrites existing builds

2014-04-08 Thread mirocu...@gmail.com (JIRA)















































Miroslav Cupak
 commented on  JENKINS-22535


Matrix Reloaded plugin overwrites existing builds















PR sent, hopefully this fixes the problem: https://github.com/jenkinsci/Matrix-Reloaded-Plugin/pull/5



























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/d/optout.

[JIRA] [matrix-reloaded] (JENKINS-22535) Matrix Reloaded plugin overwrites existing builds (our case 11118 )

2014-04-08 Thread jbrej...@praqma.net (JIRA)















































Jens  Brejner
 updated  JENKINS-22535


Matrix Reloaded plugin overwrites existing builds (our case 8 )
















Change By:


Jens  Brejner
(08/Apr/14 2:57 PM)




Summary:


MatrixReloadedpluginoverwritesexistingbuilds
(ourcase8)



























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/d/optout.

[JIRA] [core] (JENKINS-22117) ArrayOutofBoundsException when creating a job















































K P
 updated  JENKINS-22117


ArrayOutofBoundsException when creating a job
















Change By:


K P
(08/Apr/14 3:04 PM)




Component/s:


core



























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/d/optout.

[JIRA] [core] (JENKINS-19031) com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1















































K P
 commented on  JENKINS-19031


com.thoughtworks.xstream.converters.ConversionException: Array index out of range: -1 : Array index out of range: -1















I assume this is now resolved by JENKINS-18537 ?



























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/d/optout.

[JIRA] [core] (JENKINS-20858) Images missing from Jenkins UI

2014-04-08 Thread yves.schum...@ti8m.ch (JIRA)















































Yves Schumann
 commented on  JENKINS-20858


Images missing from Jenkins UI















We're facing the same problem with 1.557. Any news here?



























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/d/optout.

[JIRA] [core] (JENKINS-22081) XStream deserialization errors at service startup















































K P
 commented on  JENKINS-22081


XStream deserialization errors at service startup















I suppose this is now resolved by JENKINS-18537 ?



























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/d/optout.

[JIRA] [git] (JENKINS-22536) Date in changeset is in wrong format

Nir Reuveny
created JENKINS-22536

Date in changeset is in wrong format

Issue Type:

Bug

Assignee:

Nicolas De Loof

Components:

git

Created:

08/Apr/14 3:11 PM

Description:

Please see below full problem 'thread'

Actually, if the date is being returned from the Git plugin as 1970-01-17T04:01:10+ +0300), parsing and reformatting won't work. I think you need to open a bug against the Git plugin.

slide

On Tue, Apr 8, 2014 at 5:37 AM, Nir Reuveny wrote:
Hi,

I hope someone can help with this…

We use custom jelly email template, and it used to work fine. (it works if I roll back the git-plugin to 2.0.1), the date is showing as below in the email (seems like wrong unix time conversion)
CHANGES
by XXX:1970-01-17T04:01:10+ +0300)
this is an example of an email when we roll back to git-plugin 2.0.1:
by XXX:2014-03-24 16:54:00 +0200)
this is the section in the jelly template we use:
j:forEach var="cs" items="${changeSet}" varStatus="loop"
j:set var="hadChanges" value="true" /
j:set var="aUser" value="${cs.hudsonUser}"/
TR
TD colspan="2" class="bg2"${spc}by
B${aUser!=null?aUser.displayName:cs.author.displayName}: /B
B(${cs.date})/B
B${cs.msgAnnotated}/B
/TD
I opened a bug and got the below reply… can anyone help here? I’m really unsure exactly what to do… I’m not a developer…
Thanks!
——
Looks like the git plugin changed the date format they used. https://github.com/jenkinsci/git-plugin/commit/430bdc9b6ed121d653ef2633d2109b259aa8687b
added a comment - 08/Apr/14 11:40 AM
So what can we do to get the correct format using the email-ext plugin?...
added a comment - 08/Apr/14 11:42 AM
Since the getDate() method returns a string, you'd have to parse the string back into a date object and then format the date how you want. If you need additional help, please use the mailing list as this is not a bug.

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

Website: http://earl-of-code.com

Project:

Jenkins

Priority:

Major

Reporter:

Nir Reuveny

[JIRA] [core] (JENKINS-22117) ArrayOutofBoundsException when creating a job