date:20130403















































Roni Licht
 commented on  JENKINS-17291


No separate view for multijob builds.















Hi Jan,
Can you please describe or even send a screenshot for your request?
What would you like to see for each multijob 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] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'

2013-04-03 Thread cata...@adobe.com (JIRA)















































david catalan
 commented on  JENKINS-7695


archiving throws hudson.util.IOException2: java.io.IOException: request to write 3977 bytes exceeds size in header of 41955006















I confirm the issue still occurs on 1.508:

hudson.util.IOException2: java.io.IOException: request to write '8192' bytes exceeds size in header of '27566743' bytes for entry 'logs/error.log'
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1903)
	at com.michelin.cio.hudson.plugins.copytoslave.CopyToMasterNotifier.perform(CopyToMasterNotifier.java:93)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1620)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '8192' bytes exceeds size in header of '27566743' bytes for entry 'logs/error.log'
	at hudson.remoting.Channel$4.adapt(Channel.java:705)
	at hudson.remoting.Channel$4.adapt(Channel.java:700)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1901)
	... 9 more
Caused by: java.io.IOException: request to write '8192' bytes exceeds size in header of '27566743' bytes for entry 'logs/error.log'
	at hudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)
	at hudson.util.io.TarArchiver.visit(TarArchiver.java:115)
	at hudson.util.DirScanner$Glob.scan(DirScanner.java:133)
	at hudson.FilePath.writeToTar(FilePath.java:1939)
	at hudson.FilePath.access$1000(FilePath.java:168)
	at hudson.FilePath$36.invoke(FilePath.java:1880)
	at hudson.FilePath$36.invoke(FilePath.java:1876)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	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:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

Can someone please have a look at this issue and give us some advice?

Is there any way to help debugging it?

Ie. could a possible reason be that the file is being read/write (by another process) during the archive process?



























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-17291) No separate view for multijob builds.

2013-04-03 Thread java.arti...@javacraft.org (JIRA)















































Jan Goyvaerts
 commented on  JENKINS-17291


No separate view for multijob builds.















Currently, when creating a multijob view, there is no possibility to tell what job(s) you want in the view. The view shows an aggregation of all known multijobs jobs.

This request is really about having the possibility for choosing one or more jobs - for example:

1) Click on the + tab.
2) Select multijob view type.
3) Click "OK".
4) Customize the view.
5) Select which multi-job job(s) you want to see in the view.
6) Click "Apply".

The view would show the typical multi-job staged view of the job(s) selected in (5). Currently however there is no (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/groups/opt_out.

[JIRA] [subversion] (JENKINS-17369) SVNKit 1.6.7 has authentication bugs















































Pim Do
 commented on  JENKINS-17369


SVNKit 1.6.7 has authentication bugs















Ok, I have found out now that the problems I'm having are not directly related with SVNKit (yet).
Apparently the subversion plugin is trying to communicate too our subversion using the proxy.
This means it is neglecting the proxy exclusions set at http://jenkins-host/jenkins/pluginManager/advanced.
Why is this made so hard to use?



























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-17284) Jenkins cant display multijob view graphically if a job in phase not exists
















































Roni Licht
 resolved  JENKINS-17284 as Fixed


Jenkins cant display multijob view graphically if a job in phase not exists
















If a job in phase does not exist it will not be displayed.





Change By:


Roni Licht
(03/Apr/13 8:46 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] [jenkins-multijob-plugin] (JENKINS-17284) Jenkins cant display multijob view graphically if a job in phase not exists
















































Roni Licht
 assigned  JENKINS-17284 to Roni Licht



Jenkins cant display multijob view graphically if a job in phase not exists
















Change By:


Roni Licht
(03/Apr/13 8:45 AM)




Assignee:


RoniLicht



























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-17153) Dependency on parameterized-trigger should not be optional?
















































Roni Licht
 assigned  JENKINS-17153 to Roni Licht



Dependency on parameterized-trigger should not be optional?
















Change By:


Roni Licht
(03/Apr/13 8:53 AM)




Assignee:


RoniLicht



























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-17153) Dependency on parameterized-trigger should not be optional?

2013-04-03 Thread alain.valle...@non.schneider-electric.com (JIRA)
















































Roni Licht
 resolved  JENKINS-17153 as Fixed


Dependency on parameterized-trigger should not be optional?
















The parameterized-triggered plugin has became mandatory and not optional.





Change By:


Roni Licht
(03/Apr/13 8:54 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] [klocwork] (JENKINS-16026) Success build record lose after restart of Jenkins service















































Alain VALLETON
 commented on  JENKINS-16026


Success build record lose after restart of Jenkins service















Same effect here with Jenkins 1.480.3, Klocwork plugin 1.14.1 on Windows XP 32bit SP3.

When we restart the Jenkins server, the successful Klocwork builds disappear.



























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] [clearcase-ucm] (JENKINS-17445) If Jenkins job fails cancel deliver Jenkins can never get out of this situation, case 8671















































Christian Wolfgang
 updated  JENKINS-17445


If Jenkins job fails cancel deliver Jenkins can never get out of this situation, case 8671
















Change By:


Christian Wolfgang
(03/Apr/13 9:15 AM)




Summary:


IfJenkinsjobfailscanceldeliverJenkinscannevergetoutofthissituation
,case8671



























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] [clearcase-ucm] (JENKINS-17445) If Jenkins job fails cancel deliver Jenkins can never get out of this situation















































Christian Wolfgang
 created  JENKINS-17445


If Jenkins job fails cancel deliver Jenkins can never get out of this situation















Issue Type:


Bug



Assignee:


Praqma Support



Components:


clearcase-ucm



Created:


03/Apr/13 9:14 AM



Project:


Jenkins



Priority:


Critical



Reporter:


Christian Wolfgang

























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] [clearcase-ucm] (JENKINS-17445) If Jenkins job fails cancel deliver Jenkins can never get out of this situation, case 8671
















































Christian Wolfgang
 resolved  JENKINS-17445 as Fixed


If Jenkins job fails cancel deliver Jenkins can never get out of this situation, case 8671
















Change By:


Christian Wolfgang
(03/Apr/13 9:15 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] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775

2013-04-03 Thread tech.supratim.sama...@gmail.com (JIRA)
















































Christian Wolfgang
 resolved  JENKINS-17067 as Fixed


Finding the correct delivering Stream to cancel, case 8775
















Change By:


Christian Wolfgang
(03/Apr/13 9:20 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] [mail] (JENKINS-17446) Failed SCM authentification results in ABORTED state without notification

2013-04-03 Thread robert.lie...@cam-systems.de (JIRA)

Robert Lieske
created JENKINS-17446

Failed SCM authentification results in ABORTED state without notification

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Attachments:

jenkins_emailnotification.PNG

Components:

mail, notification, subversion

Created:

03/Apr/13 9:35 AM

Description:

After SCM authentification data turned invalid, further builds were marked as ABORTED in the Build History. There was no mail sent notifying of the problem!
Projects Mail configuration is shown in the attachment.

The following is shown on the console:
-
Gestartet durch Benutzer anonymous
Building in workspace #
Reverting #. to depth infinity with ignoreExternals: false
Updating https://svn.# at revision '#'
ERROR: Subversion update has been canceled
Build wurde abgebrochen
Notifying upstream projects of job completion
Finished: ABORTED
-

Suggested action: mark failed SCM checkout as FAILED, which would probably trigger the notification mail.
Alternative suggested action: add option to receive notification Mail with failed SCM checkout.

Environment:

Jenkins: 1.480.3

Subversion Plugin: 1.45

Project:

Jenkins

Priority:

Major

Reporter:

Robert Lieske

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-17442) When connecting to TestLink, finding error ClassCastException















































Supratim Samanta
 updated  JENKINS-17442


When connecting to TestLink, finding error ClassCastException
















Change By:


Supratim Samanta
(03/Apr/13 9:48 AM)




Priority:


Major
Critical



























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-16476) Add Last Completed Build to permalink list

2013-04-03 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 commented on  JENKINS-16476


Add Last Completed Build to permalink list















lastSuccessfulBuild only counts stable builds, not unstable



























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-17254) Multijob view last succes / last failure columns shows status instead of #of days/hours since
















































Roni Licht
 resolved  JENKINS-17254 as Fixed


Multijob view last succes / last failure columns shows status instead of  #of days/hours since
















Change By:


Roni Licht
(03/Apr/13 9:51 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] [jenkins-multijob-plugin] (JENKINS-17254) Multijob view last succes / last failure columns shows status instead of #of days/hours since
















































Roni Licht
 assigned  JENKINS-17254 to Roni Licht



Multijob view last succes / last failure columns shows status instead of  #of days/hours since
















Change By:


Roni Licht
(03/Apr/13 9:51 AM)




Assignee:


RoniLicht



























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

2013-04-03 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 created  JENKINS-17447


NPE when renaming job















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


stacktrace.txt



Components:


copyartifact



Created:


03/Apr/13 9:57 AM



Description:


Renaming a job caused the attached stacktrace.




Environment:


1.26 on Jenkins 1.509




Project:


Jenkins



Priority:


Critical



Reporter:


James Howe

























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-17070) Missing times with multiconfiguration projects
















































Roni Licht
 assigned  JENKINS-17070 to Roni Licht



Missing times with multiconfiguration projects
















Change By:


Roni Licht
(03/Apr/13 10:19 AM)




Assignee:


RoniLicht



























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-17070) Missing times with multiconfiguration projects
















































Roni Licht
 resolved  JENKINS-17070 as Duplicate


Missing times with multiconfiguration projects
















JENKINS-17254





Change By:


Roni Licht
(03/Apr/13 10:19 AM)




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] [cvs] (JENKINS-17383) CVS plugin detect changes in 'rlog' but not in 'update'

2013-04-03 Thread icruz...@gmail.com (JIRA)















































Isaac Cruz
 commented on  JENKINS-17383


CVS plugin detect changes in rlog but not in update















Update2: I have been testing the java CVS client, and discovered this issue is caused by the "-C" option.

If I execute this:
$ java org.netbeans.lib.cvsclient.commandLine.CVSCommand update -C -d -P
cvs update: Updating .
cvs update: warning: testfile was lost
U testfile

The testfile is NOT updated (in spite of the output).

If I execute this:
$ java org.netbeans.lib.cvsclient.commandLine.CVSCommand update -d -P
cvs update: Updating .
U testfile

The testfile is updated correctly



























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-13275) Jenkins stops handling HTTP/AJP requests after some time















































Marc Günther
 commented on  JENKINS-13275


Jenkins stops handling HTTP/AJP requests after some time















Actually I don't know, back then we switched from using ajp to http, which fixed the problems for us. We never tried ajp again.



























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] [config-rotator] (JENKINS-17229) Config Rotator does not trig on new baseline (our case 8789)
















































Christian Wolfgang
 resolved  JENKINS-17229 as Fixed


Config Rotator does not trig on new baseline (our case 8789)
















Change By:


Christian Wolfgang
(03/Apr/13 11:07 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] [config-rotator] (JENKINS-14746) Use nothing to build (grey builds) if there is no new baselines, our case 6843
















































Christian Wolfgang
 resolved  JENKINS-14746 as Fixed


Use nothing to build (grey builds) if there is no new baselines, our case  6843
















Change By:


Christian Wolfgang
(03/Apr/13 11:07 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] [grinder] (JENKINS-13326) Grinder plugin: Mean Response Length in graph is incorrect

2013-04-03 Thread ever...@free.fr (JIRA)















































evernat
 updated  JENKINS-13326


Grinder plugin: Mean Response Length in graph is incorrect 
















changing component





Change By:


evernat
(03/Apr/13 11:10 AM)




Labels:


plugin





Assignee:


asgeirn





Component/s:


grinder





Component/s:


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/groups/opt_out.

[JIRA] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23

2013-04-03 Thread yves.schum...@ti8m.ch (JIRA)















































Yves Schumann
 commented on  JENKINS-17366


ssh slave login via keyfile not working in 0.23















Same here. Interaction with credential plugin seems to be wrong/broken. Rollback to 0.22 solved the problem.



























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-17448) System setting http.nonProxyHosts not handled properly















































Pim Do
 created  JENKINS-17448


System setting http.nonProxyHosts not handled properly















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


subversion



Created:


03/Apr/13 11:45 AM



Description:


The system parameter http.nonProxyHosts managed by uberSVN is not resolved correctly by the Jenkins subversion plugin.

For instance the setting: .intranet|localhost|127.0.0.1 only works for localhost and 127.0.0.1, no proxy bypass is done for servers in the intranet belonging to the domain .intranet.




Environment:


subversion plugin 1.39, 1.45

jenkins 1.508

uberSVN WANdisco 2013 - #13.2-3153 SVN - 1.7 

openSuSe




Project:


Jenkins



Labels:


proxy
Jenkins
subversion
ubersvn




Priority:


Major



Reporter:


Pim Do

























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] [rebuild] (JENKINS-15882) rebuild plugin should not store non-stored password parameter

2013-04-03 Thread kacynski.w...@aoins.com (JIRA)















































Walter Kacynski
 commented on  JENKINS-15882


rebuild plugin should not store non-stored password parameter















I pulled down version 1.19 of the Rebuilder plugin but I don't see an option to configure this behavior.  What am I missing?



























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-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject















































Pim Do
 commented on  JENKINS-17264


m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject















I encounter it in 1.508 and 1.509 as well
What is the issue 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/groups/opt_out.

[JIRA] [m2release] (JENKINS-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject

2013-04-03 Thread jenkins-ci....@michael-prokop.at (JIRA)















































Pim Do
 updated  JENKINS-17264


m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
















Change By:


Pim Do
(03/Apr/13 12:34 PM)




Affects Version/s:


current



























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-17449) Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful

Michael Prokop
created JENKINS-17449

Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

core

Created:

03/Apr/13 1:00 PM

Description:

I upgraded a system to Jenkins v1.509 and noticed a custom script breaks now which used to work fine. The reason seems to be a change which seems to have been introduced somewhere around v1.509 if I'm not mistaken.

Old behaviour:

ls -la /var/lib/jenkins/jobs/foo/lastSuccessful
lrwxrwxrwx 1 jenkins nogroup 26 Feb 1 22:00 /var/lib/jenkins/jobs/foo/lastSuccessful - builds/2013-02-01_22-00-34/

New behaviour:

ls -la /var/lib/jenkins/jobs/foo/lastSuccessful
lrwxrwxrwx 1 jenkins nogroup 26 Apr 3 07:02 /var/lib/jenkins/jobs/foo/lastSuccessful - builds/lastSuccessfulBuild/

People using the target's name of the symlink (like "2013-02-01_22-00-34" in my example) inside scripts for further processing might have broken scripts due to that change.

Could someone please confirm this change and the reason for that change?

Project:

Jenkins

Priority:

Major

Reporter:

Michael Prokop

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

2013-04-03 Thread francois.dum...@vehco.com (JIRA)















































François Dumont
 commented on  JENKINS-17058


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















I'm wondering how this issue is not In Progress. Kinda disturbing regression, guys!



























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-17449) Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful















































kutzi
 commented on  JENKINS-17449


Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful















Probably related to JENKINS-16089 resp. https://github.com/jenkinsci/jenkins/commit/88feabb4296d6483bdb5c85fed489e5014161ca5



























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] [cppcheck] (JENKINS-17450) warning and performance not counted

2013-04-03 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 created  JENKINS-17450


warning and performance not counted















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


cppcheck



Created:


03/Apr/13 2:09 PM



Description:


There are entries in the report table with severity of "warning" and "performance", but they are not included in the totals or the graph.




Project:


Jenkins



Priority:


Major



Reporter:


James Howe

























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] [all-changes] (JENKINS-17336) in the jenkins 1.506 version My Views doesn't work

2013-04-03 Thread peek824545...@gmail.com (JIRA)















































Yuu Yamashita
 commented on  JENKINS-17336


in the jenkins 1.506 version My Views doesnt work















This is reproducing on our installation of Jenkins 1.506.

I ran tests and found that the problem has been introduced from SHA:c8fafe1c8acdd7e5016a8f12f666907eae7d3174, but I have not be able to fix it 



























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-17449) Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful













































 
kutzi
 edited a comment on  JENKINS-17449


Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful
















AFAIK the format of these links has been defined nowhere, so I guess it's very hard to argue that this change is a bug.
If your external script is depending on some detail on how the links were generated and is failing now because of how they are generated now than that's IMHO just a problem of your script - because it's seemingly not following the symlink to the end.



























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-17449) Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful















































kutzi
 commented on  JENKINS-17449


Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful















AFAIK the format of these links has been defined nowhere, so I guess it's very hard to argue that this change is a bug.
If your external script is depending on some detail on how the links were generated and is failing now because of how they are generated now than that's IMHO just a problem of your script - because it's seemingly not following the symlink to the end.



























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-17449) Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful















































kutzi
 updated  JENKINS-17449


Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful
















Change By:


kutzi
(03/Apr/13 2:18 PM)




Priority:


Major
Minor



























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-17451) projects tied to slave shows unrelated maven module jobs

2013-04-03 Thread jenkins-ci....@michael-prokop.at (JIRA)















































Marc Günther
 created  JENKINS-17451


projects tied to slave shows unrelated maven module jobs















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


03/Apr/13 2:26 PM



Description:


In the slave status page, there is a list of jobs called "Projects tied to slave name". That list should only show jobs that are explicitely tied to this slave.

For me it als shows lots of modules of maven style jobs that have nothing to do with that particular slave whatsoever. Only the module part of the job is shown here, not the top level maven job it belongs to.

So far I have found no pattern which jobs are shown where. I suspected it to be the last used slave, but it is not.




Project:


Jenkins



Priority:


Major



Reporter:


Marc Günther

























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-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject

2013-04-03 Thread oldel...@java.net (JIRA)
















































Richard Mortimer
 resolved  JENKINS-17264 as Duplicate


m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
















Duplicate of JENKINS-13465. Fix for that has just been integrated (not released yet though).






Change By:


Richard Mortimer
(03/Apr/13 2:30 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] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes

2013-04-03 Thread david.pars...@gmail.com (JIRA)
















































David Pärsson
 closed  JENKINS-13140 as Not A Defect


Disconnected slaves come back online within a few minutes
















Change By:


David Pärsson
(03/Apr/13 2:31 PM)




Status:


Resolved
Closed



























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-16974) Build Now link on MultiJob page doesn't work

2013-04-03 Thread phi...@googlemail.com (JIRA)















































Philipp Mohrenweiser
 commented on  JENKINS-16974


Build Now link on MultiJob page doesnt work















some more details:
the post request generated is build somehow wrong:
i get this js exception:

POST http://myjenkins/job/my-job/undefined 404 (Not Found) prototype.js:1585
Ajax.Request.Class.create.request prototype.js:1585
Ajax.Request.Class.create.initialize prototype.js:1550
(anonymous function) prototype.js:452
klass prototype.js:101
build myjenkins:167
onclick myjenkins:51


so i assume the uri building is either done wrong by the plugin, or the markup might be wrong, so jenkins's build builder is assuming a wrong element



























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] [update-center] (JENKINS-17029) update-center.json seems to be broken

2013-04-03 Thread jel...@web.de (JIRA)















































Ali Jelveh
 updated  JENKINS-17029


update-center.json seems to be broken
















Just did a fresh installation on a ubuntu 12.04 machine:

$ wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
$ sudo vi /etc/apt/sources.list.d/jenkins.list
Add "deb http://pkg.jenkins-ci.org/debian binary/"
$ sudo apt-get update
$ sudo apt-get install jenkins

and I'm getting an 

SEVERE: ERROR: Digest mismatch: computed=Z2TCx+SJViE/ramc6FtkJFZ3rR0= vs expected=YDF3DewMNvr8sz4yn1vv16a996U= in update site default





Change By:


Ali Jelveh
(03/Apr/13 2:50 PM)




Environment:


1.503,1.504,1.505
,1.509



























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] [update-center] (JENKINS-17029) update-center.json seems to be broken

2013-04-03 Thread jel...@web.de (JIRA)













































 
Ali Jelveh
 edited a comment on  JENKINS-17029


update-center.json seems to be broken
















Just did a fresh installation on a ubuntu 12.04 machine:

$ wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
$ sudo vi /etc/apt/sources.list.d/jenkins.list
Add "deb http://pkg.jenkins-ci.org/debian binary/"
$ sudo apt-get update
$ sudo apt-get install jenkins

and I'm getting an 

SEVERE: ERROR: Digest mismatch: computed=Z2TCx+SJViE/ramc6FtkJFZ3rR0= vs expected=YDF3DewMNvr8sz4yn1vv16a996U= in update site default


on Jenkins 1.509



























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] [testflight] (JENKINS-17313) TestFlight Plugin - NullPointerException on new build with Perforce SCM

2013-04-03 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 commented on  JENKINS-17313


TestFlight Plugin - NullPointerException on new build with Perforce SCM















You can also hit this issue by saving the project while a build of it is currently running. It basically comes down to AbstractBuild.getResult() returning null when the build is in the early stages of running, but the testflight plugin doesn't check for that case. I've made a quick fix and submitted a pull request: https://github.com/jenkinsci/testflight-plugin/pull/22



























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-17449) Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful















































Michael Prokop
 commented on  JENKINS-17449


Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful















ACK, the fix was easy for me. I just wanted to report this issue since other people might stumble upon it as well. So if developers decide that this is not an issue feel free to close it, I just wanted to report it since this change broke a real-life setup.



























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-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available

2013-04-03 Thread adham_has...@phoenix.com (JIRA)















































Adham Hassan
 commented on  JENKINS-17343


Jenkins is no more WinXP compliant :  CreateSymbolicLinkW is not available















Confirmed that replacing the JENKINS_HOME\jre folder with what jre7 folder I have in installed in C:\Program Files\Java\jre7, fixes this issue for my Windows Server 2003 SP2 Jenkins installation.



























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] [gerrit] (JENKINS-17452) a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger

2013-04-03 Thread gargiulo.gia...@gmail.com (JIRA)















































Giovanni Gargiulo
 created  JENKINS-17452


a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger















Issue Type:


Bug



Affects Versions:


current



Assignee:


jyrkiput



Components:


gerrit, gerrit-trigger



Created:


03/Apr/13 3:08 PM



Description:


Using
Jenkins 1.509
Jenkins GIT client plugin 1.0.5
Jenkins GIT plugin 1.3.0
Gerrit Trigger 2.9.0

The following error is thrown:
Retriggered by user anonymous for Gerrit: http://172.18.48.95/1
Building in workspace /home/ggargiulo/.jenkins/workspace/destination-management-gerrit
Checkout:destination-management-gerrit / /home/ggargiulo/.jenkins/workspace/destination-management-gerrit - hudson.remoting.LocalChannel@2a081f8f
Using strategy: Gerrit-Plugin
Fetching changes from 1 remote Git repository
Fetching upstream changes from origin
FATAL: org/spearce/jgit/lib/ObjectId
java.lang.NoClassDefFoundError: org/spearce/jgit/lib/ObjectId
	at hudson.plugins.gerrit.buildchoosers.GerritBuildChooser.parseCommit(GerritBuildChooser.java:111)
	at hudson.plugins.gerrit.buildchoosers.GerritBuildChooser.sortRevList(GerritBuildChooser.java:90)
	at hudson.plugins.gerrit.buildchoosers.GerritBuildChooser.getCandidateRevisions(GerritBuildChooser.java:46)
	at hudson.plugins.git.util.BuildChooser.getCandidateRevisions(BuildChooser.java:81)
	at hudson.plugins.git.util.BuildChooser.getCandidateRevisions(BuildChooser.java:71)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1044)
	at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942)
	at hudson.FilePath.act(FilePath.java:865)
	at hudson.FilePath.act(FilePath.java:838)
	at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1364)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:670)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:575)
	at hudson.model.Run.execute(Run.java:1575)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
Caused by: java.lang.ClassNotFoundException: org.spearce.jgit.lib.ObjectId
	at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
	... 19 more




Project:


Jenkins



Priority:


Major



Reporter:


Giovanni Gargiulo

























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] [slave-setup] (JENKINS-17453) Slave Path to java executable not working properly

2013-04-03 Thread jmcca...@pervasive.com (JIRA)

Jim McCaskey
created JENKINS-17453

Slave Path to java executable not working properly

Issue Type:

Bug

Affects Versions:

current

Assignee:

Kohsuke Kawaguchi

Components:

slave-setup

Created:

03/Apr/13 3:48 PM

Description:

I was trying to use "Let Jenkins control this Windows slave as a Windows service" and specifying "Path to java executable" in the configuration dialog.

This drove me crazy for good long while. In that "Path to java executable" box, I had put this in:

C:\Program Files\Java\jre7\bin\java.exe

Well, the service would not start. I looked on the slave and noticed this in jenkins-slave.xml.

executableC:\Program Files\Java\jre7\bin\java.exew.exe/executable

Notice the extra =w.exe= on there.

I changed "Path to java executable" box, to this:

C:\Program Files\Java\jre7\bin\java

And it worked fine. One of two things should happen:

If the path to java is specified, use that with out adding anything to it.
Modify the help for that field to document the above scenario

Environment:

Centos 6.4 Server Running Jenkins 1.508

Windows Server 2012 Standard

Project:

Jenkins

Priority:

Minor

Reporter:

Jim McCaskey

[JIRA] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade

2013-04-03 Thread william.so...@drillinginfo.com (JIRA)















































will soula
 commented on  JENKINS-17386


Gradle.properties ignored after 1.22 upgrade















The above commit is certainly the one that broke this and here is the pull request:
https://github.com/jenkinsci/gradle-plugin/pull/12

It appears that the gradle plugin has changed the way gradle works and 
has taken a default that is different than gradle's default.  I would 
not expect the plugin to have different defaults than the actual tool, 
it leads to confusion when things don't work like is documented online.

I know I can override the GRADLE_USER_HOME variable with the -g switch 
and a few other methods, which is what the author of the pull request 
should have done, -g $WORKSPACE.

Its like the git plugin suddenly changed and now if you leave branches blank 
it only checks master instead of all branches.

Another workaround would be putting -g /home/build user/.gradle in the switches.



























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-03 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-9142


Add Build Step button broken in job configure page















Similar problem here: choosing items from "Add axis" in a matrix job didn't work; the JS console showed a 404 for all three available axis types.

Running in an incognito browser window, it worked fine (we don't use any authentication in Jenkins at the moment).

As with Christer Moren above, I had maybe 90 JSESSIONID cookies in my regular browser window for the Jenkins domain.  Restarting the browser didn't fix things, but clearing all cookies for the domain did...



























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-03 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-9142


Add Build Step button broken in job configure page















For what it's worth, I did enable bound object logging, but no output was ever shown.

Only when I opened the incognito browser window, where the problem didn't exist, did I start to see bound object logs appearing.  The logs themselves in this case were unremarkable.



























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-17454) Difficult to determine parameters of queue items















































Jesse Glick
 created  JENKINS-17454


Difficult to determine parameters of queue items















Issue Type:


Improvement



Assignee:


Jesse Glick



Components:


core



Created:


03/Apr/13 4:18 PM



Description:


The parameters of queued builds are only visible in the tooltips of entries from the build queue on the Jenkins index page, not in the build history widget of the individual jobs. This makes it difficult to tell what parameterized builds are going to be run.

Also the existing tooltips show internal class names suitable for a debugger, rather than a proper human-friendly display.




Project:


Jenkins



Labels:


ui
queue
parameter




Priority:


Minor



Reporter:


Jesse Glick

























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] [CocoaPods] (JENKINS-17455) need documentation about using this with the Xcode plugin, to build an ipa file

2013-04-03 Thread dmor...@excelliscorp.com (JIRA)















































Dan Morrow
 created  JENKINS-17455


need documentation about using this with the Xcode plugin, to build an ipa file















Issue Type:


Task



Assignee:


Leif Janzik



Components:


CocoaPods



Created:


03/Apr/13 4:25 PM



Description:


I'm using cocoapods to bring dependencies into my project. I'm also using the Xcode plugin, to build my app. The problem that I'm having is tying all of these things together, so that I can generate an "ipa" file. 

I would really like to see a guide about how to change my project's build settings, so that these things can all work together. Right now, I haven't cracked it. But surely it's possible.




Project:


Jenkins



Priority:


Major



Reporter:


Dan Morrow

























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-17449) Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful
















































kutzi
 resolved  JENKINS-17449 as Not A Defect


Jenkins 1.509 has different behaviour with symlink handling of e.g. lastSuccessful
















Change By:


kutzi
(03/Apr/13 4:24 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/groups/opt_out.

[JIRA] [CocoaPods] (JENKINS-17455) need documentation about using this with the Xcode plugin, to build an ipa file

2013-04-03 Thread dmor...@excelliscorp.com (JIRA)















































Dan Morrow
 updated  JENKINS-17455


need documentation about using this with the Xcode plugin, to build an ipa file
















Change By:


Dan Morrow
(03/Apr/13 4:25 PM)




Component/s:


xcode



























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] [android-emulator] (JENKINS-17456) Documentation missing for Create Android build files build step

2013-04-03 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 created  JENKINS-17456


Documentation missing for Create Android build files build step















Issue Type:


Bug



Assignee:


Christopher Orr



Components:


android-emulator



Created:


03/Apr/13 4:56 PM



Description:


In UpdateProjectBuilder, the help file links to that of the InstallPrerequisitesBuilder.




Project:


Jenkins



Priority:


Minor



Reporter:


Christopher Orr

























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-17402) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact















































Jesse Glick
 updated  JENKINS-17402


Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact
















Probably related to fix of JENKINS-13222, but the bug is in the Maven plugin: MavenModuleSet.getItem(String) may return null if there is no such child but it may not throw some unchecked exception.





Change By:


Jesse Glick
(03/Apr/13 5:01 PM)




Component/s:


maven





Component/s:


copyartifact



























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-17365) copyartifact 1.26 does not expand label expressions in parameter field, copies all of them

2013-04-03 Thread stanislav.bashkirt...@gmail.com (JIRA)

Jesse Glick
resolved JENKINS-17365 as Wont Fix

copyartifact 1.26 does not expand label expressions in parameter field, copies all of them

The previous storage format was ambiguous about what was a parameter filter and what was part of the job path for e.g. matrix jobs. As of 1.26 an unambiguous format is used.

There is a one-time migration which attempts to guess what you meant in the old case: if there is a / in the name, and there is a = in the name, and no job with the specified full name exists, then the name is split on the last /, with the first part being the project name and the second part being the parameter filter. Otherwise the name is assumed to be a matrix project name and the parameters field is left empty.

I am not surprised that this heuristic is not correct in every case but I am not sure if it can be improved. If you think it can, please file a pull request against this plugin with a test demonstrating the more precise migration using @LocalData.

Change By:

Jesse Glick
(03/Apr/13 5:10 PM)

Status:

Open
Resolved

Resolution:

WontFix

[JIRA] [copyartifact] (JENKINS-17365) copyartifact 1.26 does not expand label expressions in parameter field, copies all of them

2013-04-03 Thread jtaylor.deb...@googlemail.com (JIRA)















































Julian Taylor
 commented on  JENKINS-17365


copyartifact 1.26 does not expand label expressions in parameter field, copies all of them















for the record I avoided the autorewrite by changing projectName to project in all job xml 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/groups/opt_out.

[JIRA] [xcode] (JENKINS-17457) get a non-existing directory problem when making an IPA after building a workspace.

2013-04-03 Thread dmor...@excelliscorp.com (JIRA)

Dan Morrow
created JENKINS-17457

get a non-existing directory problem when making an IPA after building a workspace.

Issue Type:

Bug

Assignee:

Unassigned

Components:

xcode

Created:

03/Apr/13 5:45 PM

Description:

I'm using cocoapods for dependency management. It requires that apps get build using a workspace file, instead of a regular project file. And it adds a "Pods" project into that workspace, which is used by my app.

So, in my xcode settings in the Jenkins job, the only things I set are the "schema" and "workspace" settings. It builds the app just fine, but the "Build IPA" step fails.

The message that I get is:
Cannot remove .ipa files from a non-existing directory: /Users/jenkins/.jenkins/jobs/myapp/workspace/build/-iphoneos

So, it appears that it expects my app to exist in a directory named "build", relative to my project. And since I'm not specifying configuration, there's no "Release" in front of the "-iphoneos" part of the path.

So, is there anything I can do to fix this?

Environment:

Xcode 4.6.1

Project:

Jenkins

Priority:

Major

Reporter:

Dan Morrow

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

2013-04-03 Thread westhus...@gmail.com (JIRA)















































Adam Westhusing
 commented on  JENKINS-15587


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















I didn't have these exceptions occurring in my Jenkins instance until I upgraded from 1.506 to 1.509.  Now these occur all the time, specifically with some of the projects I've created since upgrading.



























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] [infrastructure] (JENKINS-17458) Wiki macro not using POM SCM element

2013-04-03 Thread m2spr...@springdot.org (JIRA)















































Max Spring
 created  JENKINS-17458


Wiki macro not using POM SCM element















Issue Type:


Bug



Assignee:


Unassigned


Components:


infrastructure



Created:


03/Apr/13 5:51 PM



Description:


Regarding the jenkins-plugin-info Wiki macro: It appears that the "Source Code" field is generated by simply appending the plugin name to "https://github.com/jenkinsci/" instead of leveraging the plugin's SCM pom element.
This fails where there are several plugins in one Git repository.
E.g. on https://wiki.jenkins-ci.org/display/JENKINS/Jenkow+Activiti+Explorer the GitHub link is wrong.
See the plugin's POM: https://github.com/jenkinsci/jenkow-plugin/blob/master/jenkow-activiti-explorer/plugin/pom.xml#L50




Project:


Jenkins



Priority:


Minor



Reporter:


Max Spring

























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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39

2013-04-03 Thread jos...@java.net (JIRA)















































Jose Sa
 commented on  JENKINS-15587


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















Check the scripts I've added in JENKINS-17265 which may help you detect and cleanup those kind of situations.



























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-17454) Difficult to determine parameters of queue items

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















































dogfood
 commented on  JENKINS-17454


Difficult to determine parameters of queue items















Integrated in  jenkins_main_trunk #2431
 FIXED JENKINS-17454 Display parameters of queue items in build history widget. (Revision 750da1a7c0700655129d594d56bfc41214891e50)

 Result = SUCCESS
Jesse Glick : 750da1a7c0700655129d594d56bfc41214891e50
Files : 

	core/src/main/java/hudson/model/FileParameterValue.java
	core/src/main/resources/lib/hudson/queue.jelly
	core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
	changelog.html
	core/src/main/java/hudson/model/PasswordParameterValue.java
	core/src/main/java/hudson/model/StringParameterValue.java
	core/src/main/java/hudson/model/BooleanParameterValue.java
	core/src/main/java/hudson/model/JobParameterValue.java
	core/src/main/java/hudson/model/RunParameterValue.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] [email-ext] (JENKINS-16990) unable to resolve class hudson.maven.reporters.SurefireAggregatedReport in groovy template

2013-04-03 Thread slide.o....@gmail.com (JIRA)
















































Alex Earl
 resolved  JENKINS-16990 as Fixed


unable to resolve class hudson.maven.reporters.SurefireAggregatedReport in groovy template
















Set the class loader for the SimpleTemplateEngine.





Change By:


Alex Earl
(03/Apr/13 6: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] [nested-view] (JENKINS-17352) Manage columns
















































stanislav bashkirtsev
 assigned  JENKINS-17352 to stanislav bashkirtsev



Manage columns
















Change By:


stanislav bashkirtsev
(03/Apr/13 6:18 PM)




Assignee:


stanislavbashkirtsev



























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] [nested-view] (JENKINS-17352) Manage columns

2013-04-03 Thread stanislav.bashkirt...@gmail.com (JIRA)















































stanislav bashkirtsev
 started work on  JENKINS-17352


Manage columns
















Change By:


stanislav bashkirtsev
(03/Apr/13 6:18 PM)




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] [core] (JENKINS-17459) Little red/yellow/green icons should get you to Console everywhere















































Marc Günther
 created  JENKINS-17459


Little red/yellow/green icons should get you to Console everywhere















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


03/Apr/13 6:59 PM



Description:


For example in the "Build Time Trend" list of a project, one cannot click into the little red/yellow/blue icons to get to the Console, like you can in the Build History on the left.




Project:


Jenkins



Priority:


Trivial



Reporter:


Marc Günther

























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-17039) sort order of plugin list is not working by default















































Marc Günther
 commented on  JENKINS-17039


sort order of plugin list is not working by default















I don't know, this somehow feels wrong. Why would the getter know anything about the sort order of the presentation? Why should it sort by name and in what direction?

This should be handled by the same class that does the sorting in all other cases. It is already displaying that little arrow to indicate that the list is sorted, it is also that class' responsibility to actually sort the list.



























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-17125) FingerprintAction Serializiation Bug
















































Jesse Glick
 resolved  JENKINS-17125 as Duplicate


FingerprintAction Serializiation Bug
















JENKINS-16845 filed first so tracking there, though this issue has a far better explanation.





Change By:


Jesse Glick
(03/Apr/13 7:12 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-17265) Builds disappearing from history
















































Jesse Glick
 resolved  JENKINS-17265 as Duplicate


Builds disappearing from history
















Seems to be the same as JENKINS-16845.





Change By:


Jesse Glick
(03/Apr/13 7:13 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-16845) NullPointer in getPreviousBuild















































Jesse Glick
 started work on  JENKINS-16845


NullPointer in getPreviousBuild
















Change By:


Jesse Glick
(03/Apr/13 7:13 PM)




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] [core] (JENKINS-16845) NullPointer in getPreviousBuild
















































Jesse Glick
 assigned  JENKINS-16845 to Jesse Glick



NullPointer in getPreviousBuild
















Change By:


Jesse Glick
(03/Apr/13 7:13 PM)




Assignee:


KohsukeKawaguchi
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] [core] (JENKINS-17039) sort order of plugin list is not working by default















































Jesse Glick
 commented on  JENKINS-17039


sort order of plugin list is not working by default















Probably an issue in _javascript_ then; check sortable.js.



























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] [junit] (JENKINS-5698) Show test-result directly from reportng/testng generated html

2013-04-03 Thread bashakhal...@gmail.com (JIRA)















































Khalith Basha
 commented on  JENKINS-5698


Show test-result directly from reportng/testng generated html















Its done. We have to use HTML report plugin in jenkins 



























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] [junit] (JENKINS-5698) Show test-result directly from reportng/testng generated html

2013-04-03 Thread bashakhal...@gmail.com (JIRA)
















































Khalith Basha
 closed  JENKINS-5698 as Wont Fix


Show test-result directly from reportng/testng generated html
















Its done. We have to use HTML report plugin in jenkins 





Change By:


Khalith Basha
(03/Apr/13 7:29 PM)




Status:


Resolved
Closed



























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-17265) Builds disappearing from history

2013-04-03 Thread westhus...@gmail.com (JIRA)













































 
Adam Westhusing
 edited a comment on  JENKINS-17265


Builds disappearing from history
















The shell scripts don't work when the jobs have spaces in the names.  What modifications need to be made to the scripts to adapt it to be able to work when there are spaces in the job names?

Additionally, running this script in Cygwin on Windows is generating output that indicates EVERY build has a missing build link.



























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-17125) FingerprintAction Serializiation Bug















































Jesse Glick
 commented on  JENKINS-17125


FingerprintAction Serializiation Bug















The patch seems wrong. onLoad, not onAttached, should be called when loading existing builds. Unfortunately onLoad does not pass the Run as a parameter; it is documented that the Run may be kept in a field.

What I am wondering is how you got a build.xml like this to begin with. I do not get this format when I create a new job with fingerprints. I get


hudson.tasks.Fingerprinter_-FingerprintAction
  build class="build" reference="../../.."/
  record
entry
  stringx.txt/string
  stringc614bcfdc7abb8eae48c5c820cd1f274/string
/entry
  /record
/hudson.tasks.Fingerprinter_-FingerprintAction


as I would expect.



























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-17125) FingerprintAction deserialization leads to NPE















































Jesse Glick
 updated  JENKINS-17125


FingerprintAction deserialization leads to NPE
















Change By:


Jesse Glick
(03/Apr/13 7:42 PM)




Summary:


FingerprintAction
SerializiationBug
deserializationleadstoNPE



























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-17125) FingerprintAction deserialization leads to NPE















































Jesse Glick
 commented on  JENKINS-17125


FingerprintAction deserialization leads to NPE















…and this is true even when I run on 1.494 as you seem to have done.



























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] [email-ext] (JENKINS-17344) Config pages broken by No such property: compressBuildLog

2013-04-03 Thread slide.o....@gmail.com (JIRA)
















































Alex Earl
 closed  JENKINS-17344 as Cannot Reproduce


Config pages broken by No such property: compressBuildLog
















The property definitely exists in the class. Can't reproduce this even when trying to upgrade from 2.25 to 2.27.1





Change By:


Alex Earl
(03/Apr/13 7:51 PM)




Status:


Open
Closed





Resolution:


CannotReproduce



























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-17125) FingerprintAction deserialization leads to NPE















































Jesse Glick
 updated  JENKINS-17125


FingerprintAction deserialization leads to NPE
















Change By:


Jesse Glick
(03/Apr/13 7:55 PM)




Description:


FingerprintActionhasthefollowingfield:{code}privatefinalAbstractBuildbuild;{code}ThisfieldlinkstoanAbstractBuild,whichinturnhasthefollowingfield:{code}protectedtransientfinalJobTproject;{code}OnceJenkinpersistsaruntoafile,thebuildfromtheFingerprintActionwillbesaved,buttheprojectitselfwillnotgetsaved.Anexamplefragmentfromoneofthebuildfileslookslikethis:{code
:xml
}hudson.tasks.Fingerprinter_-FingerprintActionbuildclass=buildactionshudson.model.ParametersActionreference=../../../../hudson.model.ParametersAction/hudson.model.CauseActionreference=../../../../hudson.model.CauseAction/hudson.plugins.copyartifact.CopyArtifact_-EnvActionreference=../../../../hudson.plugins.copyartifact.CopyArtifact_-EnvAction/hudson.tasks.Fingerprinter_-FingerprintActionreference=../../..//actionsnumber17/numberstartTime1358250655935/startTimeresultSUCCESS/resultduration4488/durationcharsetUTF-8/charsetkeepLogfalse/keepLogbuiltOn/builtOnworkspace/opt/hudson/files/jobs/Deploy/workspace/workspacehudsonVersion1.494/hudsonVersionscmclass=hudson.scm.NullChangeLogParser/culpritsclass=com.google.common.collect.EmptyImmutableSortedSet//build...{code}Whenthefilesarereadandtheobjectsarecreated,theprojectfieldremainsempty.Duringintialization,theonLoad()methodiscalled:{code}@OverrideprotectedRretrieve(Filed)throwsIOException{if(newFile(d,build.xml).exists()){//ifthebuildresultfileisntinthedirectory,ignoreit.try{Rb=cons.create(d);b.onLoad();if(LOGGER.isLoggable(FINE))LOGGER.log(FINE,Loaded+b.getFullDisplayName(),newThisIsHowItsLoaded());returnb;}catch(IOExceptione){LOGGER.log(Level.WARNING,couldnotload+d,e);}catch(InstantiationErrore){LOGGER.log(Level.WARNING,couldnotload+d,e);}}returnnull;}{code}ThismethodinvokesonLoad()onallactionsthatimplementRunAction:{code}for(Actiona:getActions())if(ainstanceofRunAction)((RunAction)a).onLoad();{code}TheFingerprintActiondoesimplementtheRunActioninterface,andthemethodisimplementedasfollows:{code}publicvoidonLoad(){//sharedatastructurewithnearbybuilds,buttokeeplazyloadingefficient,//dontgobackthehistoryforever.if(rand.nextInt(2)!=0){Runpb=build.getPreviousBuild();if(pb!=null){FingerprintActiona=pb.getAction(FingerprintAction.class);if(a!=null)compact(a);}}}{code}Buildisset,sogetPreviousBuild()canbecalled,thiswillhoweverfailbecausetheprojectisnull(duetothetransientfield)andwillthrowaNullPointerException.Thiscausesverystrangebehaviorassometimespagesareworking,sometimestheyarenot.Therearealotofstacktracesaroundthatactuallylooklikeasiftheywerecausedbythesameproblem,forexample:https://issues.jenkins-ci.org/browse/JENKINS-16845StackTracelookslikethis:{code}Causedby:java.lang.NullPointerException	athudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207)	athudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349)	athudson.model.Run.onLoad(Run.java:315)	athudson.model.RunMap.retrieve(RunMap.java:221)	athudson.model.RunMap.retrieve(RunMap.java:59)	atjenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638)	atjenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:601)	atjenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:344)	athudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:207)	athudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:100)	athudson.model.RunMap$1.next(RunMap.java:107)	athudson.model.RunMap$1.next(RunMap.java:96)	athudson.widgets.HistoryWidget.getRenderList(HistoryWidget.java:133)	...122more{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

[JIRA] [core] (JENKINS-17125) FingerprintAction deserialization leads to NPE

2013-04-03 Thread bieringer.domi...@gmx.at (JIRA)

Dominik Bieringer
commented on JENKINS-17125

FingerprintAction deserialization leads to NPE

We got or have XML files (build.xml) like the one you showed very often, however, there is a small number of build.xml files that looks like the one that I described. Isn't that related to how the whole memory object tree get's serialized to the file and also depends on whether the same objects are used or not to represent the builds?

However, after we fixed the code the way I described, we never faced the issue again and Jenkins is working like charm now. We had the following issues before:

The build list on the left side when you go to a project was not showing correctly (sometimes it was empty, othertimes it was full, but when clicking "more builds", it got empty and did not load correctly)
The mails (success mails, failure mails, etc... for builds) were not sent correctly. We got the mentioned exception during the build.
The build pipeline plugin was not showing correctly and we saw the same exception in the log files.

[JIRA] [junit] (JENKINS-14089) JUnit report - Quarantine intermittent tests

2013-04-03 Thread samuel.n...@taitradio.com (JIRA)















































samuel nobs
 commented on  JENKINS-14089


JUnit report - Quarantine intermittent tests















fork on github: https://github.com/samsta/claim-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/groups/opt_out.

[JIRA] [core] (JENKINS-17125) FingerprintAction deserialization leads to NPE

Jesse Glick
commented on JENKINS-17125

FingerprintAction deserialization leads to NPE

Right, I think the busted serialization format is probably the result of a BuildReference being cleared and a different AbstractBuild being created than the FingerprintAction was originally produced with. So there are two problems:

Making sure that does not happen.
Recovering gracefully from the broken format.

For the second part, your proposed patch is unacceptable (I think) because it breaks the general RunAction contract. I am working on a different patch that acknowledges that the FingerprintAction is incomplete and just limits the damage (no exceptions printed, most things with the fingerprints work).

Not sure what to do about the first part. Seems like a fundamental flaw. (Though I am unable to reproduce it even by making AbstractLazyLoadRunMap.unwrap usually return null.) The best I can think of is to cache all the RunAction instances in a build using strong references so it is guaranteed they will not be collected.

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















































Jesse Glick
 stopped work on  JENKINS-16845


NullPointer in getPreviousBuild
















Change By:


Jesse Glick
(03/Apr/13 8:32 PM)




Status:


InProgress
Open



























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