date:20130626













































 
Jeroen Mostert
 edited a comment on  JENKINS-18312


changelog browsing uses the wrong path to Redmine
















I'm running Redmine 2.3.1 ( and latest redmine 0.13 plugin in Jenkins)

For revision view the format in Redmine 2.3.1 is:
  http://redmineHost/redmine/projects/projectName/repository/revisions/revision



























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] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime















































Yuu Yamashita
 commented on  JENKINS-18311


Jenkins 1.518 fails to load plugin ruby-runtime















This problem with Jenkins 1.518 has been fixed in ruby-runtime 0.11. See also https://github.com/jenkinsci/jenkins.rb/issues/82.

// But I found another problem of ruby-runtime 0.11 on Jenkins 1.519
// I'll report it later.



























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] [ruby-runtime] (JENKINS-18311) Jenkins 1.518 fails to load plugin ruby-runtime
















































Yuu Yamashita
 resolved  JENKINS-18311 as Fixed


Jenkins 1.518 fails to load plugin ruby-runtime
















This problem has been fixed in ruby-runtime 0.11.





Change By:


Yuu Yamashita
(26/Jun/13 1:19 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18310) ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
















































Yuu Yamashita
 closed  JENKINS-18310 as Duplicate


ruby-runtime throws java.lang.IncompatibleClassChangeError on start up
















Change By:


Yuu Yamashita
(26/Jun/13 1:20 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-14090) SCMCheckoutStrategy extension is not functional for Matrix projects

2013-06-26 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-14090


SCMCheckoutStrategy extension is not functional for Matrix projects















Is it still an issue in recent Jenkins versions?



























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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine















































Jeroen Mostert
 stopped work on  JENKINS-18312


changelog browsing uses the wrong path to Redmine
















Change By:


Jeroen Mostert
(26/Jun/13 1:29 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine















































Jeroen Mostert
 started work on  JENKINS-18312


changelog browsing uses the wrong path to Redmine
















Change By:


Jeroen Mostert
(26/Jun/13 1:29 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] [all-changes] (JENKINS-18513) Slowness in Jenkins

2013-06-26 Thread aswini.rajaseka...@gmail.com (JIRA)















































Aswini Rajasekaran
 created  JENKINS-18513


Slowness in Jenkins















Issue Type:


Bug



Assignee:


wolfs



Attachments:


jenkins heapdump.txt



Components:


all-changes



Created:


26/Jun/13 1:28 PM



Description:


Hi, I am running standalone instance of Jenkins version 1.514 in Linux. When many selenium tests are run, jenkins becomes very slow and even loading the browser takes a very long time. It has been like this for a long time. I got a heap dump at that time when jenkins was too slow. Can anyone findout what the issue is and let me know if I upgrade to 1.519 this issue will get resolved?
Also, please let me know if you need any more details.
Thanks, Aswini




Project:


Jenkins



Priority:


Major



Reporter:


Aswini Rajasekaran

























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-18513) Slowness in Jenkins

2013-06-26 Thread aswini.rajaseka...@gmail.com (JIRA)















































Aswini Rajasekaran
 updated  JENKINS-18513


Slowness in Jenkins
















Change By:


Aswini Rajasekaran
(26/Jun/13 1:31 PM)




Description:


Hi,IamrunningstandaloneinstanceofJenkinsversion1.514inLinux.Whenmanyseleniumtestsarerun,jenkinsbecomesveryslowandevenloadingthebrowsertakesaverylongtime.Ithasbeenlikethisforalongtime.Igotaheapdumpatthattimewhenjenkinswastooslow.CananyonefindoutwhattheissueisandletmeknowifIupgradeto1.519thisissuewillgetresolved?Also,pleaseletmeknowifyouneedanymoredetails.
Jenkinsrunson4coreprocessorwith8GBRAMand32bitOS.
Thanks,Aswini



























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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine















































Jeroen Mostert
 updated  JENKINS-18312


changelog browsing uses the wrong path to Redmine
















Change By:


Jeroen Mostert
(26/Jun/13 1:32 PM)




Labels:


changelog
pluginredminesubversion





Component/s:


repository



























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] [ui-changes] (JENKINS-18514) Who is in the queue?

2013-06-26 Thread shannonck...@gmail.com (JIRA)

Shannon Kerr
created JENKINS-18514

Who is in the queue?

Issue Type:

Improvement

Affects Versions:

current

Assignee:

Unassigned

Components:

ui-changes

Created:

26/Jun/13 1:32 PM

Description:

I'm using Jenkins 1.519. I have setup a generic job that developers can do a "one off" build as needed. The job is parameterized and requests the user select the branch they want to build for from a list of available branches.

My issue is, when a build gets into the queue, I can't tell who put job there/initiated it. I could add a parameter to the build that requests the user's name/ID, but it seems like there should be some way for me to know who owns a job in the queue.

There may be a case where I need to cancel a build for a lower priority activity and it would be good at least to notify the person(s). Also, if I know who is in the queue, they may actually need to be in the queue ahead of me, so I shouldn't cancel their job.

Environment:

Ubuntu 12.04 Server, VMWare Fusion

Fix Versions:

current

Project:

Jenkins

Labels:

jenkins
queue

Priority:

Major

Reporter:

Shannon Kerr

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] [maven2] (JENKINS-14222) Building Maven jobs on slave fails when settings.xml is not in the default location.

2013-06-26 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-14222


Building Maven jobs on slave fails when settings.xml is not in the default location.















In Jenkins 1.519, I see a "Settings file" field, in the advanced build section below the "Goals and options" field of the configuration page of a Maven project.
This settings file for the project can be a path on the filesystem, either relative to the workspace or absolute on the filesystem.

So it seems to me that you can define the settings file to use for your job and that this issue is already 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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
















































Jeroen Mostert
 assigned  JENKINS-18312 to Łukasz Jąder



changelog browsing uses the wrong path to Redmine
















Change By:


Jeroen Mostert
(26/Jun/13 1:37 PM)




Assignee:


gaooh
ŁukaszJąder



























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-18513) Slowness in Jenkins

2013-06-26 Thread aswini.rajaseka...@gmail.com (JIRA)















































Aswini Rajasekaran
 updated  JENKINS-18513


Slowness in Jenkins
















Change By:


Aswini Rajasekaran
(26/Jun/13 1:42 PM)




Description:


Hi,IamrunningstandaloneinstanceofJenkinsversion1.514inLinux.Whenmanyseleniumtestsarerun,jenkinsbecomesveryslowandevenloadingthebrowsertakesaverylongtime.Ithasbeenlikethisforalongtime.Igotaheapdumpatthattimewhenjenkinswastooslow.CananyonefindoutwhattheissueisandletmeknowifIupgradeto1.519thisissuewillgetresolved?Also,pleaseletmeknowifyouneedanymoredetails.Jenkinsrunson4coreprocessorwith8GBRAMand32bitOS.
AlsoCPUusagegoesto400%whenmultipleseleniumtestsarerunandJenkinsisveryslow.
Thanks,Aswini



























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-18513) Slowness in Jenkins

2013-06-26 Thread aswini.rajaseka...@gmail.com (JIRA)















































Aswini Rajasekaran
 updated  JENKINS-18513


Slowness in Jenkins
















Change By:


Aswini Rajasekaran
(26/Jun/13 2:04 PM)




Attachment:


hs_err_pid21945.log





Description:


Hi,IamrunningstandaloneinstanceofJenkinsversion1.514inLinux.Whenmanyseleniumtestsarerun,jenkinsbecomesveryslowandevenloadingthebrowsertakesaverylongtime.Ithasbeenlikethisforalongtime.Igotaheapdumpatthattimewhenjenkinswastooslow.CananyonefindoutwhattheissueisandletmeknowifIupgradeto1.519thisissuewillgetresolved?Also,pleaseletmeknowifyouneedanymoredetails.Jenkinsrunson4coreprocessorwith8GBRAMand32bitOS.AlsoCPUusagegoesto400%whenmultipleseleniumtestsarerunandJenkinsisveryslow.
Aftersometime,JenkinsJVMcrasheditselfgeneratingalogfile.Ihaveattachedthegeneratedlogfilealso.
Thanks,Aswini



























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] [dashboard-view] (JENKINS-18515) Improve folder support

2013-06-26 Thread te...@java.net (JIRA)















































teilo
 updated  JENKINS-18515


Improve folder support
















Change By:


teilo
(26/Jun/13 2:07 PM)




Description:


Whilstthedashboardviewnowworkswithfoldersisitonlyabletocreateaviewinafolderandusejobsimmediatelywithinthatfolder.Itiscommononlargeinstancestohavemanylevelsoffolders,tothelevelthatasingleSCMprojectmaybeinitsownfoldercontainingmultiplejobtypes(e.g.code_review,commit,reporting,acceptance_tests).Itisdesiredtobeabletocreateadashboardviewofsomeofthejobsinsubfolders(orinanyotherfolderinthehierarchy).e.g.givethefollowinghierarchy
{noformat}
/+-project|+-main_branch||+-code_review||+-commit||\-reporting|||+-foobar_branch|+-code_review|+-commit|\-reporting|+-shared_lib
|
+-main_branch|
|
+-code_review|
|
+-commit|
|
\-reporting|
|

|
+-foobar_branch
|
+-code_review
|
+-commit
|
\-reporting
{noformat}


Itwouldbedesirabletocreateadashboardin\project\thatlooksatthe\shared_lib\main_branch\commitand\project\main_branch\commit



























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] [scm-sync-configuration] (JENKINS-18516) Bad urls while restoring configuration

2013-06-26 Thread da...@walend.net (JIRA)

David Walend
created JENKINS-18516

Bad urls while restoring configuration

Issue Type:

Bug

Assignee:

Frédéric Camblor

Components:

scm-sync-configuration

Created:

26/Jun/13 2:10 PM

Description:

scm-sync-configuration had two bad urls. I was able to figure out one of them, but not the other.

On https://10.0.0.61:8443/jenkins/configure, the link "Reload" pointed to https://10.0.0.61:8443/plugin/scm-sync-configuration/reloadAllFilesFromScm . It was missing the jenkins layer. https://10.0.0.61:8443/jenkins/plugin/scm-sync-configuration/reloadAllFilesFromScm worked.

On https://10.0.0.61:8443/jenkins/plugin/scm-sync-configuration/reloadAllFilesFromScm , the link "here" pointed to https://10.0.0.61:8443/reload . I wasn't able to figure that one out. I wound up restoring the job by hand.

Environment:

Jenkins running on tomcat7 in EC2.

Project:

Jenkins

Priority:

Major

Reporter:

David Walend

[JIRA] [dashboard-view] (JENKINS-18515) Improve folder support

2013-06-26 Thread te...@java.net (JIRA)

teilo
created JENKINS-18515

Improve folder support

Issue Type:

Improvement

Assignee:

Peter Hayes

Components:

dashboard-view

Created:

26/Jun/13 2:05 PM

Description:

Whilst the dashboard view now "works" with folders is it only able to create a view in a folder and use jobs immediately within that folder.

It is common on large instances to have many levels of folders, to the level that a single SCM project may be in its own folder containing multiple job types (e.g. code_review, commit, reporting, acceptance_tests).

It is desired to be able to create a dashboard view of some of the jobs in subfolders (or in any other folder in the hierarchy).

e.g. give the following hierarchy

/
+-project

+-main_branch

+-code_review

+-commit

reporting

+-foobar_branch

+-code_review

+-commit

reporting

+-shared_lib

+-main_branch

+-code_review

+-commit

reporting

+-foobar_branch

+-code_review

+-commit

reporting

It would be desirable to create a dashboard in \project\ that looks at the \shared_lib\main_branch\commit and \project\main_branch\commit

Project:

Jenkins

Priority:

Major

Reporter:

teilo

[JIRA] [core] (JENKINS-17265) Builds disappearing from history

2013-06-26 Thread reece.g.johns...@boeing.com (JIRA)















































Reece Johnston
 commented on  JENKINS-17265


Builds disappearing from history















I just saw the same issue on version 1.511. It occurred after renaming a job and running that job with a scheduled build. Oddly, it did not occur with the first few manual builds.



























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







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

[JIRA] [build-failure-analyzer] (JENKINS-18518) Red highlights not showing when clicking on indications

2013-06-26 Thread micmar...@gmail.com (JIRA)















































Michael Marcil
 created  JENKINS-18518


Red highlights not showing when clicking on indications















Issue Type:


Bug



Affects Versions:


current



Assignee:


Tomas Westling



Components:


build-failure-analyzer



Created:


26/Jun/13 4:07 PM



Description:


Red highlights are not showing in log when clicking on indications.





Environment:


Windows




Project:


Jenkins



Priority:


Major



Reporter:


Michael Marcil

























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-18330) Support :ext: using external shell like Netbeans instead of only internal SSH

2013-06-26 Thread srte...@gmail.com (JIRA)















































Scott Telle
 commented on  JENKINS-18330


Support :ext: using external shell like Netbeans instead of only internal SSH















I have had the same issue that I started looking into this week. I saw that version 1.6 of the cvs plugin allows you to specify the cvs executable. The following release (2.0) is where they added the netbeans java.

With version 1.6 I'm getting somewhere - at least I'm able to try to checkout with the cvsnt binaries... 



























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-18330) Support :ext: using external shell like Netbeans instead of only internal SSH

2013-06-26 Thread j...@assen.demon.co.uk (JIRA)















































John McCabe
 commented on  JENKINS-18330


Support :ext: using external shell like Netbeans instead of only internal SSH















That's interesting. I'm currently using 2.9. It seems a bit mad to have to go back to something as far back as 1.6 for this to be possible.



























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-18330) Support :ext: using external shell like Netbeans instead of only internal SSH

2013-06-26 Thread srte...@gmail.com (JIRA)















































Scott Telle
 commented on  JENKINS-18330


Support :ext: using external shell like Netbeans instead of only internal SSH















I agree - it's not really a downgrade, since it looks like the plugin was completely rewritten in 2.0. I almost wish they had separated these into 2 separate plugins. There seems to be little support for cvs sspi protocols.



























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] [git-client] (JENKINS-18519) Add submodule reference support

2013-06-26 Thread p...@nkey.com.br (JIRA)















































Paul Eipper
 created  JENKINS-18519


Add submodule reference support















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-client



Created:


26/Jun/13 6:41 PM



Description:


Method `submoduleUpdate` should accept `reference` the same way as `clone` does.


git submodule update --init --recursive --reference $reference





Project:


Jenkins



Labels:


git
plugin




Priority:


Major



Reporter:


Paul Eipper

























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] [shiningpanda] (JENKINS-18415) Can't run shining panda jobs in 1.519

2013-06-26 Thread t...@mindsnacks.com (JIRA)















































Ted Aronson
 commented on  JENKINS-18415


Cant run shining panda jobs in 1.519















I also have the same issue.  Here's the console log:


hostname $ /usr/bin/python2.7 /mnt/jenkins/shiningpanda/jobs/50768566/virtualenv.py --distribute /mnt/jenkins/shiningpanda/jobs/50768566/virtualenvs/d41d8cd9
New python executable in /mnt/jenkins/shiningpanda/jobs/50768566/virtualenvs/d41d8cd9/bin/python2.7
Also creating executable in /mnt/jenkins/shiningpanda/jobs/50768566/virtualenvs/d41d8cd9/bin/python
Installing distribute...done.
Installing pipdone.
FATAL: file:/var/lib/jenkins/plugins/shiningpanda/WEB-INF/lib/classes.jar!/jenkins/plugins/shiningpanda/workspace/virtualenv.py (No such file or directory)
java.io.FileNotFoundException: file:/var/lib/jenkins/plugins/shiningpanda/WEB-INF/lib/classes.jar!/jenkins/plugins/shiningpanda/workspace/virtualenv.py (No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.init(FileInputStream.java:137)
	at hudson.FilePath$30.invoke(FilePath.java:1667)
	at hudson.FilePath$30.invoke(FilePath.java:1664)
	at hudson.FilePath.act(FilePath.java:905)
	at hudson.FilePath.act(FilePath.java:878)
	at hudson.FilePath.digest(FilePath.java:1664)
	at jenkins.plugins.shiningpanda.interpreters.Virtualenv.getSignature(Virtualenv.java:458)
	at jenkins.plugins.shiningpanda.interpreters.Virtualenv.create(Virtualenv.java:300)
	at jenkins.plugins.shiningpanda.builders.VirtualenvBuilder.perform(VirtualenvBuilder.java:190)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.Build$BuildExecution.build(Build.java:199)
	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
	at hudson.model.Run.execute(Run.java:1593)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:242)



























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] [php] (JENKINS-18520) API Documentation Link Broken

2013-06-26 Thread martin.buchm...@gmail.com (JIRA)















































Martin Buchmayr
 created  JENKINS-18520


API Documentation Link Broken















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


apidoc.PNG



Components:


php



Created:


26/Jun/13 6:56 PM



Description:


I have problems with Jenkins PHP project status view. I tried Docblox and phpDocumentor. The link to the documentation is broken (error 404). The documentation has been created. Have a look on the screenshot.

This is my build.xml (for a zf1 project)

?xml version="1.0" encoding="UTF-8"?
!-- Generated by PHP Project Wizard (PPW) 1.0.4 on Mon Jun 17 12:16:48 CEST 2013 --

project name="surveytool" default="build" basedir="."
property name="source" value="application"/

target name="clean" description="Clean up and create artifact directories"
delete dir="${basedir}/build/api"/
delete dir="${basedir}/build/code-browser"/
delete dir="${basedir}/build/coverage"/
delete dir="${basedir}/build/logs"/
delete dir="${basedir}/build/pdepend"/

mkdir dir="${basedir}/build/api"/
mkdir dir="${basedir}/build/code-browser"/
mkdir dir="${basedir}/build/coverage"/
mkdir dir="${basedir}/build/logs"/
mkdir dir="${basedir}/build/pdepend"/
/target

target name="phpunit" description="Run unit tests using PHPUnit and generates junit.xml and clover.xml"
exec executable="phpunit" failonerror="true"/
/target

target name="parallelTasks" description="Run the pdepend, phpmd, phpcpd, phpcs, phpdoc and phploc tasks in parallel using a maximum of 2 threads."
parallel threadCount="2"
sequential
antcall target="pdepend"/
antcall target="phpmd"/
/sequential
antcall target="phpcpd"/
antcall target="phpcs"/
!-antcall target="phpdoc"/-
antcall target="docblox"/
antcall target="phploc"/
/parallel
/target

target name="pdepend" description="Generate jdepend.xml and software metrics charts using PHP_Depend"
exec executable="pdepend"
arg line="--jdepend-xml=${basedir}/build/logs/jdepend.xml
  --jdepend-chart=${basedir}/build/pdepend/dependencies.svg
  --overview-pyramid=${basedir}/build/pdepend/overview-pyramid.svg
  ${source}" /
/exec
/target

target name="phpmd" description="Generate pmd.xml using PHPMD"
exec executable="phpmd"
arg line="${source}
  xml
  codesize,design,naming,unusedcode
  --reportfile ${basedir}/build/logs/pmd.xml" /
/exec
/target

target name="phpcpd" description="Generate pmd-cpd.xml using PHPCPD"
exec executable="phpcpd"
arg line="--log-pmd ${basedir}/build/logs/pmd-cpd.xml ${source}" /
/exec
/target

target name="phploc" description="Generate phploc.csv"
exec executable="phploc"
arg line="--log-csv ${basedir}/build/logs/phploc.csv ${source}" /
/exec
/target

target name="phpcs" description="Generate checkstyle.xml using PHP_CodeSniffer"
exec executable="phpcs" output="/dev/null"
arg line="--report=checkstyle
  --report-file=${basedir}/build/logs/checkstyle.xml
  --standard=PEAR
  ${source}" /
/exec
/target
!--
target name="phpdoc" description="Generate API documentation using PHPDocumentor"
 exec executable="phpdoc"
  arg line="-d ${source} -t ${basedir}/build/api" /
 /exec
/target--
 
target name="docblox" description="Generate API documentation using DocBlox"
exec executable="docblox"
arg line="project:run -d ${source} -t ${basedir}/build/api" / 
/exec
/target

target name="phpcb" description="Aggregate tool output with PHP_CodeBrowser"
exec executable="phpcb"
arg line="--log${basedir}/build/logs
  --source

[JIRA] [clearcase-ucm] (JENKINS-16487) Promotion Level being set to INITIAL - our case 8471

Lars Kruse
resolved JENKINS-16487 as Not A Defect

Promotion Level being set to INITIAL - our case 8471

This case does represent an issue; the only the default promotion levels are supported. But since Ronan who opened this case, clearly states that this is apparently not Ronan's concern but rather that the plugin is trying to change the promotion level ...al all

This is by design: We're looking for a baseline with a certain promotion level, and when we're done with it, we'll flip the promotion level - either to the next - or to rejected - dependent on the outcome of the build step.

If we didn't flip the promotion level , the build would simple build the same baseline over and over again.

There is a workaround for this based on setting the promotion level to the option "ANY" in this mode the plugin will build the lates baseline - no matter what promotion level it has.

I'm closing this "Not a defect" and opening a new "Only default Promotion levels are supported" instead.

Change By:

Lars Kruse
(26/Jun/13 7:09 PM)

Status:

Reopened
Resolved

Resolution:

NotADefect

[JIRA] [clearcase-ucm] (JENKINS-18521) Only default Promotion levels are supported















































Lars Kruse
 created  JENKINS-18521


Only default Promotion levels are supported















Issue Type:


Improvement



Assignee:


Praqma Support



Components:


clearcase-ucm



Created:


26/Jun/13 7:06 PM



Description:


The plugin is supporting the default promotion levels:

INITIAL
BUILT
TESTED
RELEASED
REJECTED

If a project is using a custom defined list of promotion levels they are not supported.

We need a sponsor for this feature - contact us at supp...@praqma.com if you want a quote on this feature.




Project:


Jenkins



Labels:


clearcase-ucm
clearcase
promotion




Priority:


Minor



Reporter:


Lars Kruse

























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] [php] (JENKINS-18520) API Documentation Link Broken

2013-06-26 Thread martin.buchm...@gmail.com (JIRA)
















































Martin Buchmayr
 resolved  JENKINS-18520 as Fixed


API Documentation Link Broken
















Sorry I just wrote index.html instead of index.html for my documentation output link... my bad...





Change By:


Martin Buchmayr
(26/Jun/13 7:19 PM)




Status:


Open
Resolved





Fix Version/s:


current





Resolution:


Fixed



























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







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

[JIRA] [component] (JENKINS-18507) some command can't exit in the execute windows batch command (praqma case 9630)















































Lars Kruse
 updated  JENKINS-18507


some command cant exit in the execute windows batch command (praqma case 9630)
















Change By:


Lars Kruse
(26/Jun/13 7:27 PM)




Component/s:


windows-exe-runner



























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] [batch-task] (JENKINS-18507) some command can't exit in the execute windows batch command (praqma case 9630)















































Lars Kruse
 updated  JENKINS-18507


some command cant exit in the execute windows batch command (praqma case 9630)
















Moving this case the batch-task component.





Change By:


Lars Kruse
(26/Jun/13 7:30 PM)




Assignee:


PraqmaSupport





Component/s:


batch-task





Component/s:


component





Component/s:


windows-exe-runner



























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-18522) Cannot check out CVS module using legacy mode

2013-06-26 Thread srte...@gmail.com (JIRA)















































Scott Telle
 created  JENKINS-18522


Cannot check out CVS module using legacy mode















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


cvs



Created:


26/Jun/13 8:33 PM



Description:


We have a lot of legacy projects that are stored in CVS. We use Windows in house and SSPI to authenticate. I am almost able to get a working setup with Jenkins but I have one missing piece - checking out from cvs. 


Conceptually our setup:
CVS Module structure:
/ThirdParty/...
/Applications/...
/Libraries/lib1/
/Libraries/lib2/

I cannot use the current CVS plugin because it doesn't support SSPI, so I downgraded to version 1.6. With this version I use the legacy mode to checkout, because I need the directory structure to stay intact. This works and everything checks out, but then it appears to error looking for the changes. There is no CVS folder created at the root of the project structure and that's where it executes the command, so it dies not finding any changes.

Console log:

Building in workspace D:\bin\Jenkins\web.subject
[web.subject] $ cvs -Q -z3 -d :sspi:vsbuild:/sw_development co -P -D "Wednesday, June 26, 2013 8:01:43 PM UTC" Web.SubjectAssessmentForm
$ computing changelog
cvs log: in directory .:
cvs [log aborted]: there is no version here; do 'cvs checkout' first
ERROR: cvs exited with error code 1
Command line was [Executing 'cvs' with arguments:
'-d:sspi:vsbuild:/sw_development'
'log'
'-S'
'-d'
'=2013-06-25'
'Web.SubjectAssessmentForm'

The ' characters around the executable and arguments are
not part of the command.
] in D:\bin\Jenkins\web.subject
Input text:
START==null==END
Working directory is D:\bin\Jenkins\web.subject
cvs exited with error code 1
Command line was [Executing 'cvs' with arguments:
'-d:sspi:vsbuild:/sw_development'
'log'
'-S'
'-d'
'=2013-06-25'
'Web.SubjectAssessmentForm'

The ' characters around the executable and arguments are
not part of the command.
] in D:\bin\Jenkins\web.subject
Input text:
START==null==END
	at hudson.org.apache.tools.ant.taskdefs.AbstractCvsTask.runCommand(AbstractCvsTask.java:387)
	at hudson.org.apache.tools.ant.taskdefs.AbstractCvsTask.execute(AbstractCvsTask.java:457)
	at hudson.org.apache.tools.ant.taskdefs.cvslib.ChangeLogTask.execute(ChangeLogTask.java:293)
	at hudson.scm.CVSSCM$4.invoke(CVSSCM.java:967)
	at hudson.scm.CVSSCM$4.invoke(CVSSCM.java:887)
	at hudson.FilePath.act(FilePath.java:905)
	at hudson.FilePath.act(FilePath.java:878)
	at hudson.scm.CVSSCM.calcChangeLog(CVSSCM.java:887)
	at hudson.scm.CVSSCM.checkout(CVSSCM.java:429)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1369)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
	at hudson.model.Run.execute(Run.java:1593)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:242)
Finished: FAILURE






Due Date:


05/Jul/13 12:00 AM




Environment:


Windows Server 2008 R2 Standard

CVS plugin version 1.6

Tortoise CVS 




Project:


Jenkins



Priority:


Blocker



Reporter:


Scott Telle

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA,

[JIRA] [build-keeper-plugin] (JENKINS-18523) job keeper not working

2013-06-26 Thread walter.marvin....@nsn.com (JIRA)















































walter marvin
 created  JENKINS-18523


job keeper not working















Issue Type:


Bug



Assignee:


bap



Components:


build-keeper-plugin



Created:


26/Jun/13 9:46 PM



Description:


Fedora Linux 13

Works on some builds but not for others. Some builds are eaten as fast as jobs run




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


walter marvin

























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] [plugin] (JENKINS-18412) Unable to execute SOASTA CloudTest compositions in CentOS

2013-06-26 Thread luiscardozofore...@hotmail.com (JIRA)















































Luis Cardozo
 commented on  JENKINS-18412


Unable to execute SOASTA CloudTest compositions in CentOS















Any comment about this issue?



























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







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

[JIRA] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter

2013-06-26 Thread jacob.robertson.w...@gmail.com (JIRA)















































Jacob Robertson
 commented on  JENKINS-18386


more flexible job filter by parameter















This would be easy to implement, but I don't know of any parameters that use "toString".  If you just mean your own company's custom parameters, then it can still be implemented, it just won't really be easy to test before releasing.  It would be more helpful if you could give an example parameter plugin that I could install and test against.  I tried a couple, but they don't use "toString", so it didn't work.



























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-18438) Node monitoring should run in parallel
















































SCM/JIRA link daemon
 resolved  JENKINS-18438 as Fixed


Node monitoring should run in parallel
















Change By:


SCM/JIRA link daemon
(26/Jun/13 11:30 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18438) Node monitoring should run in parallel















































SCM/JIRA link daemon
 commented on  JENKINS-18438


Node monitoring should run in parallel















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 changelog.html
 core/src/main/java/hudson/FilePath.java
 core/src/main/java/hudson/model/Node.java
 core/src/main/java/hudson/model/Slave.java
 core/src/main/java/hudson/node_monitors/AbstractAsyncNodeMonitorDescriptor.java
 core/src/main/java/hudson/node_monitors/AbstractNodeMonitorDescriptor.java
 core/src/main/java/hudson/node_monitors/ArchitectureMonitor.java
 core/src/main/java/hudson/node_monitors/ClockMonitor.java
 core/src/main/java/hudson/node_monitors/DiskSpaceMonitor.java
 core/src/main/java/hudson/node_monitors/DiskSpaceMonitorDescriptor.java
 core/src/main/java/hudson/node_monitors/ResponseTimeMonitor.java
 core/src/main/java/hudson/node_monitors/SwapSpaceMonitor.java
 core/src/main/java/hudson/node_monitors/TemporarySpaceMonitor.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/test/java/hudson/slaves/NodeListTest.java
http://jenkins-ci.org/commit/jenkins/735713801b130fe247cf17bbca7b4561e41b1d13
Log:
  FIXED JENKINS-18438

Node monitoring should run in parallel to reduce the total round-trip
time in large instances.






























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] [master-slave] (JENKINS-18152) Thread interruption in remoting proxy results in UndeclaredThrowableException
















































SCM/JIRA link daemon
 resolved  JENKINS-18152 as Fixed


Thread interruption in remoting proxy results in UndeclaredThrowableException
















Change By:


SCM/JIRA link daemon
(26/Jun/13 11:49 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] [master-slave] (JENKINS-18152) Thread interruption in remoting proxy results in UndeclaredThrowableException















































SCM/JIRA link daemon
 commented on  JENKINS-18152


Thread interruption in remoting proxy results in UndeclaredThrowableException















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/hudson/remoting/RemoteInvocationHandler.java
http://jenkins-ci.org/commit/remoting/c8c0e818b7ee9d7351ec0424027010c94efbd8ef
Log:
  FIXED JENKINS-18152

Avoid UndeclaredThrowableException by being smart about what exception to propagate and what to wrap.






























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







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

[JIRA] [ec2] (JENKINS-16280) EC2 Plugin will not build Java projects.

2013-06-26 Thread mhader...@sonomatech.com (JIRA)















































Michael Haderman
 commented on  JENKINS-16280


EC2 Plugin will not build Java projects.















We were encountering this error as well.  It seems it was because we were using "~/jenkins" instead of "/home/ubuntu/jenkins" for Remote FS root.



























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-18438) Node monitoring should run in parallel

2013-06-26 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-18438


Node monitoring should run in parallel















Integrated in  jenkins_main_trunk #2671
 FIXED JENKINS-18438 (Revision 735713801b130fe247cf17bbca7b4561e41b1d13)

 Result = SUCCESS
kohsuke : 735713801b130fe247cf17bbca7b4561e41b1d13
Files : 

	core/src/test/java/hudson/slaves/NodeListTest.java
	core/src/main/java/hudson/node_monitors/AbstractNodeMonitorDescriptor.java
	core/src/main/java/hudson/FilePath.java
	core/src/main/java/hudson/node_monitors/TemporarySpaceMonitor.java
	core/src/main/java/jenkins/model/Jenkins.java
	core/src/main/java/hudson/model/Node.java
	core/src/main/java/hudson/node_monitors/ClockMonitor.java
	core/src/main/java/hudson/node_monitors/DiskSpaceMonitorDescriptor.java
	core/src/main/java/hudson/node_monitors/DiskSpaceMonitor.java
	core/src/main/java/hudson/node_monitors/ArchitectureMonitor.java
	core/src/main/java/hudson/node_monitors/SwapSpaceMonitor.java
	core/src/main/java/hudson/model/Slave.java
	core/src/main/java/hudson/node_monitors/AbstractAsyncNodeMonitorDescriptor.java
	changelog.html
	core/src/main/java/hudson/node_monitors/ResponseTimeMonitor.java





























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







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

[JIRA] [core] (JENKINS-12827) api should return the build number that was queued.

2013-06-26 Thread mlh...@umich.edu (JIRA)















































Michael Hess
 commented on  JENKINS-12827


api should return the build number that was queued.















+1,

We really need this as well.  If someone could contact me we would be happy to sponsor it but can't use paypal. 



























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] [other] (JENKINS-18524) Too many open files caused Jenkins crashed

2013-06-26 Thread hanny...@outlook.com (JIRA)















































Youcai HAN
 created  JENKINS-18524


Too many open files caused Jenkins crashed















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


jstack.log, lsof.log, tomcat.log, ulimit.log



Components:


other



Created:


27/Jun/13 12:58 AM



Description:


After Jenkins running for a long time, it suddenly stuck. We checked the log and found too many socket was opened and the number of opened files comes 65535. So it failed to accept new request. Could you please help to check why Jenkins opened so many socket and can't close it?
We have tried to use gc to collect garbage memory, but it can't close these socket. So this should be a bug of Jenkins.
Jun 13, 2013 10:21:12 AM hudson.model.Executor run
SEVERE: Executor threw an exception
hudson.util.IOException2: Failed to create a temporary file in /proj/RBS_IoV/.hudson/jobs/KillZombieProcess
	at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:67)
	at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:54)
	at hudson.util.TextFile.write(TextFile.java:78)
	at hudson.model.Job.saveNextBuildNumber(Job.java:234)
	at hudson.model.Job.assignBuildNumber(Job.java:291)
	at hudson.model.Run.init(Run.java:256)
	at hudson.model.AbstractBuild.init(AbstractBuild.java:158)
	at hudson.model.Build.init(Build.java:92)
	at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:37)
	at sun.reflect.GeneratedConstructorAccessor100.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at hudson.model.AbstractProject.newBuild(AbstractProject.java:982)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1197)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:136)
	at hudson.model.Executor.run(Executor.java:211)
Caused by: java.io.IOException: Too many open files
	at java.io.UnixFileSystem.createFileExclusively(Native Method)
	at java.io.File.checkAndCreate(File.java:1704)
	at java.io.File.createTempFile(File.java:1792)
	at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:65)
	... 15 more
Jun 13, 2013 10:21:12 AM hudson.model.Executor run
SEVERE: Executor threw an exception
hudson.util.IOException2: Failed to create a temporary file in /proj/RBS_IoV/.hudson/jobs/W12A_CLA_R6_CI_testExec_Trigger_Job
	at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:67)
	at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:54)
	at hudson.util.TextFile.write(TextFile.java:78)
	at hudson.model.Job.saveNextBuildNumber(Job.java:234)
	at hudson.model.Job.assignBuildNumber(Job.java:291)
	at hudson.model.Run.init(Run.java:256)
	at hudson.model.AbstractBuild.init(AbstractBuild.java:158)
	at hudson.model.Build.init(Build.java:92)
	at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:37)
	at sun.reflect.GeneratedConstructorAccessor100.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at hudson.model.AbstractProject.newBuild(AbstractProject.java:982)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1197)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:136)
	at hudson.model.Executor.run(Executor.java:211)
Caused by: java.io.IOException: Too many open files
	at java.io.UnixFileSystem.createFileExclusively(Native Method)
	at java.io.File.checkAndCreate(File.java:1704)
	at java.io.File.createTempFile(File.java:1792)
	at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:65)
	... 15 more
Jun 13, 2013 10:21:13 AM org.apache.tomcat.util.net.JIoEndpoint$Acceptor run
SEVERE: Socket accept failed
java.net.SocketException: Too many open files




Environment:


We met this issue on both Solaris

[JIRA] [batch-task] (JENKINS-18507) some command can't exit in the execute windows batch command (praqma case 9630)

2013-06-26 Thread dzyjl2...@yahoo.com.cn (JIRA)















































dzy dzy
 commented on  JENKINS-18507


some command cant exit in the execute windows batch command (praqma case 9630)















When will it come to pass ?



























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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification

2013-06-26 Thread gpjerrymalo...@gmail.com (JIRA)

Jerry Maloney
commented on JENKINS-16332

Leading and trailing underscores are added to commiters email address, unable to send build notification

I believe there may be an issue in MercurialChangeLogParser method MercurialChangeSetList parse(AbstractBuild build, File changelogFile). If I pass in a changelog that looks like the following:
changelog.xml
?xml version='1.0' encoding='UTF-8'?
changesets
changeset author='joe.schmo lt;joe.sc...@example.comgt;'/ !-- note that those escape characters are on purpose and not some relic of posting in Jira --
/changesets

I get a changeset author with the ID and fullname "joe.schmo joe.sc...@example.com", which is the error reported in this ticket. I believe the Digester class from Apache Commons is taking the escaped XML characters in the changesets/changeset/@author attribute and rendering them as underscores.

I pushed a unit test showing this to my fork of mercurial-plugin, but not requesting a pull because I don't have a fix yet.

[JIRA] [ruby-plugin-runtime] (JENKINS-18314) Possible incompatibility between jffi-1.2.7 and jruby 1.6.5 as shipped with ruby-runtime plugin