date:20130709















































kutzi
 updated  JENKINS-17974


SVN plugin always overwrites --depth parameters
















Change By:


kutzi
(09/Jul/13 10:05 AM)




Summary:


SVNplugin
ignores
alwaysoverwrites
--depthparameters



























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-17931) cvs rlog files in /tmp are not deleted

2013-07-09 Thread adrien.cl...@gls-france.com (JIRA)















































Adrien CLERC
 commented on  JENKINS-17931


cvs rlog files in /tmp are not deleted















I've made some tests as you suggested:


	"su - hudson" and try to rm one cvsXXrlog. The operation completed successfully.
	Shutdown jenkins. All files are still here, after the process stop.





























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







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

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)
















Change By:


Vijendra Patil
(09/Jul/13 10:13 AM)




Summary:


Need
Security\
Impersonation
Feature
support
for
executing
JenkinsJobs
asadifferentuser(Securityrelatedfeature)



























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-17974) SVN plugin always overwrites --depth parameters
















































kutzi
 assigned  JENKINS-17974 to kutzi



SVN plugin always overwrites --depth parameters
















Change By:


kutzi
(09/Jul/13 10:13 AM)




Assignee:


jbq
kutzi



























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-17974) SVN plugin always overwrites --depth parameters













































 
kutzi
 edited a comment on  JENKINS-17974


SVN plugin always overwrites --depth parameters
















So, actually it doesn't 'ignore' the depth option, but overwrites it in any case, right?

I'm not terribly in favor of this feature as it basically sounds to me like you are working around the fact that your SVN repository is not organised optimally.
However, since this would - according to the pull request (https://github.com/jenkinsci/subversion-plugin/pull/46) - only require a single new value in an existing drop-down menu, I could live with 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] [subversion] (JENKINS-17974) SVN plugin always overwrites --depth parameters
















































kutzi
 resolved  JENKINS-17974 as Fixed


SVN plugin always overwrites --depth parameters
















Change By:


kutzi
(09/Jul/13 10:14 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] [active-directory] (JENKINS-18453) Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)
















Change By:


Vijendra Patil
(09/Jul/13 10:16 AM)




Component/s:


credentials



























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







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

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)

Vijendra Patil
edited a comment on JENKINS-18453

Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)

Jesse, Thanks for sharing your thoughts on this. Well, we can do this in a much simpler way. This is how we can do this.

A checkbox should be present on the Create Job page of Jenkins saying "Execute\Build as another User" OR "Execute\Build Job using logged on user credential". Then if we create a Job with this checkbox checked, and when we build the Job by clicking on the Build button, it should do either of the two,

1. If we implement "Execute\Build as another User" option, then it should simply prompt for a popup\dialog asking to provide user credential. Then the job should execute all the Build Steps, using the credential passed. (i.e., If I pass my credential vipa...@mycompany.com, password123, then it should use this credential to execute all the MSBuild command that we specified in the Build step of the Jenkin Job.).

2. If we implement "Execute\Build Job using logged on user credential" option, then its little tricky and it should execute the Job (Build Steps commands) using the credential of the logged on user, without asking for any dialog to provide user credential, as it should use logged on user credential.

Option 1 seems very easy and very simple to implement. While option 2 seems little tricky and require integration with Credential Plugin.

I am glad that you liked the idea and thought its useful. If possible then can we get option 1 implemented. In .Net I know how to implement impersonation (http://platinumdogs.me/2008/10/30/net-c-impersonation-with-network-credentials/) but not sure about how can we do this in Java (found this article but not sure https://svn.apache.org/repos/asf/jackrabbit/branches/2.0/jackrabbit-core/src/test/java/org/apache/jackrabbit/api/security/user/ImpersonationTest.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] [dashboard-view] (JENKINS-6289) Sort list of available dashboards alphabetically

2013-07-09 Thread s.sog...@gmail.com (JIRA)
















































sogabe
 assigned  JENKINS-6289 to sogabe



Sort list of available dashboards alphabetically
















Change By:


sogabe
(09/Jul/13 10:42 AM)




Assignee:


PeterHayes
sogabe



























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-6289) Sort list of available dashboards alphabetically

2013-07-09 Thread s.sog...@gmail.com (JIRA)
















































sogabe
 resolved  JENKINS-6289 as Fixed


Sort list of available dashboards alphabetically
















See https://github.com/jenkinsci/dashboard-view-plugin/commit/cbc20ccc00ee160ed9490dcd1bcbe74338033769





Change By:


sogabe
(09/Jul/13 10:50 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-14032) No jobs showing up in view after upgrade to 1.466















































evernat
 commented on  JENKINS-14032


No jobs showing up in view after upgrade to 1.466















@KC
Is this still an 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] [active-directory] (JENKINS-18453) Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)
















Change By:


Vijendra Patil
(09/Jul/13 11:16 AM)




Description:


Hi,IneedtoexecutefewoftheJenkinsjobssuchasReleasetoProductionthroughJenkinsUIusingloggedonuser
orusinganotheruser
credential.Thereasonis,
wehaveoneinstanceofJenkinsCIonwhichalltheJenkinsJobssuchasBuildMyApp,ReleaseMyApToQAetc.areconfigured.BoththeDevelopersaswellasSupportteammembersareadminonthisJenkinsapplicationInstanceaswellasontheJenkinsserver.Rightnow,theseJobsgetsexecutedusingthecredentialofserviceaccountwhichtheTomcatServiceisrunningwith,onwhichJenkinsishosted.Now,theproblemis,wecantusethesameinstancetoreleasedeployableitemstoProductionastheserviceaccountdoesnthavepermissiontoaccessProductionWebSeverstocopycodeonit.Andmoreover,
itstheSupportTeamMemberswhohaveaccesstotheproductionboxes
,so
.So
inordertodeployanycodebasetoproduction,alltheWindowsDeployCommands(ex,create,updatefiles,folderetc.)needstoberunwithspecificusercredentialwhohasaccesstotheProductionBox.ItriedusingparameterizedpluginbutcouldntabletopassthePasswordsuccessfullytothebatchfilewhichcontainsMSDeployinstructions.IcheckedRolebasedsecurityplugin,projectmatrix,activedirectoryetc,butthatdoesnthelpmemuch.IjustneedapluginwhichshouldaskforusertoprovidetheircredentialbeforestartbuildingtheJobandshouldusetheusercredentialtogetthejobexecuted,sothatmyMSDeploycommandwillbeabletodeploythecodeonProductionboxes,whentheSupportteammemberbuildthatJobusingtheircredential.Iwishtherewassupportforimpersonation.RightnowalltheJenkinsJobsaregettingexecutedusingtheserviceaccountwhichtheTomcatserviceisconfiguredtorunwithonwhichJenkinsishosted.BothDevelopersandSupportteammembersareADMINonbothJenkinswebserveraswellasonJenkinswebapplication.Iamlookingforwardtothefollowing.=EachjobcanhaveacheckboxsayExecuteusinganotherusercredential
orExecuteusingloggedonusercredential
.NowwhenwestartthejobbyclickingonBuildbutton,whichishavingExecuteusinganotherusercredentialcheckboxchecked,theapplicationshouldasktoprovidecredentialthatneedstobeusedforBuildingthatJob.Thatjobshouldgetexecutedthenwiththatparticularcredential.SoevenifIcanbeabletorunthejobReleaseToProductionusingmycredentialthenitwillnotsucceedasIdonthaveaccesstoProductionwebserversforcreatingfiles,foldersetc.ButwhenthesamejobgetsexecutedbySupportteam,itshouldsucceedastheyhaveaccesstoProductionserversforcreatingfiles,folders,executinganyMSDeploycommands.==Anyhelpwouldbeappreciated.



























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-15858) Jenkinks UI slow due to constant build record loading

2013-07-09 Thread s.sog...@gmail.com (JIRA)
















































sogabe
 resolved  JENKINS-15858 as Fixed


Jenkinks UI slow due to constant build record loading
















fixed in 2.8





Change By:


sogabe
(09/Jul/13 11:17 AM)




Status:


InProgress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-7678) Frozen build after channel stopped















































evernat
 commented on  JENKINS-7678


Frozen build after channel stopped















@Arnaud
Is this still an issue for you?
Given "agentThreadDump", the slave was recording disk usage. Is it related to your 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] [active-directory] (JENKINS-18453) Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)
















Change By:


Vijendra Patil
(09/Jul/13 11:21 AM)




Description:


Hi,IneedtoexecutefewoftheJenkinsjobssuchasReleasetoProductionthroughJenkinsUIusingloggedonuserorusinganotherusercredential.Thereasonis,wehaveoneinstanceofJenkinsCIonwhichalltheJenkinsJobssuchasBuildMyApp,ReleaseMyApToQAetc.areconfigured.BoththeDevelopersaswellasSupportteammembersareadminonthisJenkinsapplicationInstanceaswellasontheJenkinsserver.Rightnow,theseJobsgetsexecutedusingthecredentialofserviceaccountwhichtheTomcatServiceisrunningwith,onwhichJenkinsishosted.Now,theproblemis,wecantusethesameinstancetoreleasedeployableitemstoProductionastheserviceaccountdoesnthavepermissiontoaccessProductionWebSeverstocopycodeonit.Andmoreover,itstheSupportTeamMemberswhohaveaccesstotheproductionboxes.Soinordertodeployanycodebasetoproduction,alltheWindowsDeployCommands(ex,create,updatefiles,folderetc.)needstoberunwithspecificusercredentialwhohasaccesstotheProductionBox.
TheonlyoptionweareleftwithnowistohaveanotherserverwhichtheSupportTeamown,andhavealltheReleaseToProductionJobssetuponthisseparateinstanceofJenkins,whichonlySupportteammemberareADMINonit.
ItriedusingparameterizedpluginbutcouldntabletopassthePasswordsuccessfullytothebatchfilewhichcontainsMSDeployinstructions.IcheckedRolebasedsecurityplugin,projectmatrix,activedirectoryetc,butthatdoesnthelpmemuch.IjustneedapluginwhichshouldaskforusertoprovidetheircredentialbeforestartbuildingtheJobandshouldusetheusercredentialtogetthejobexecuted,sothatmyMSDeploycommandwillbeabletodeploythecodeonProductionboxes,whentheSupportteammemberbuildthatJobusingtheircredential.Iwishtherewassupportforimpersonation.RightnowalltheJenkinsJobsaregettingexecutedusingtheserviceaccountwhichtheTomcatserviceisconfiguredtorunwithonwhichJenkinsishosted.BothDevelopersandSupportteammembersareADMINonbothJenkinswebserveraswellasonJenkinswebapplication.Iamlookingforwardtothefollowing.=EachjobcanhaveacheckboxsayExecuteusinganotherusercredentialorExecuteusingloggedonusercredential.NowwhenwestartthejobbyclickingonBuildbutton,whichishavingExecuteusinganotherusercredentialcheckboxchecked,theapplicationshouldasktoprovidecredentialthatneedstobeusedforBuildingthatJob.Thatjobshouldgetexecutedthenwiththatparticularcredential.SoevenifIcanbeabletorunthejobReleaseToProductionusingmycredentialthenitwillnotsucceedasIdonthaveaccesstoProductionwebserversforcreatingfiles,foldersetc.ButwhenthesamejobgetsexecutedbySupportteam,itshouldsucceedastheyhaveaccesstoProductionserversforcreatingfiles,folders,executinganyMSDeploycommands.==Anyhelpwouldbeappreciated.
Thisisgoingtobeaveryusefulfeaturetoeveryoneindeed.



























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-13707) Job disables itself during execution, when using environment variables in repository url















































evernat
 commented on  JENKINS-13707


Job disables itself during execution, when using environment variables in repository url















Is it reproduced with recent versions of Jenkins and of plugins?



























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







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

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)
















Change By:


Vijendra Patil
(09/Jul/13 11:23 AM)




Description:


Hi,IneedtoexecutefewoftheJenkinsjobssuchasReleasetoProductionthroughJenkinsUIusingloggedonuserorusinganotherusercredential.Thereasonis,wehaveoneinstanceofJenkinsCIonwhichalltheJenkinsJobssuchasBuildMyApp,ReleaseMyApToQAetc.areconfigured.BoththeDevelopersaswellasSupportteammembersareadminonthisJenkinsapplicationInstanceaswellasontheJenkinsserver.Rightnow,theseJobsgetsexecutedusingthecredentialofserviceaccountwhichtheTomcatServiceisrunningwith,onwhichJenkinsishosted.Now,theproblemis,wecantusethesameinstancetoreleasedeployableitemstoProductionastheserviceaccountdoesnthavepermissiontoaccessProductionWebSeverstocopycodeonit.Andmoreover,itstheSupportTeamMemberswhohaveaccesstotheproductionboxes.Soinordertodeployanycodebasetoproduction,alltheWindowsDeployCommands(ex,create,updatefiles,folderetc.)needstoberunwithspecificusercredentialwhohasaccesstotheProductionBox.TheonlyoptionweareleftwithnowistohaveanotherserverwhichtheSupportTeamown,andhavealltheReleaseToProductionJobssetuponthisseparateinstanceofJenkins,whichonlySupportteammemberareADMINonit.ItriedusingparameterizedpluginbutcouldntabletopassthePasswordsuccessfullytothebatchfilewhichcontainsMSDeployinstructions.IcheckedRolebasedsecurityplugin,projectmatrix,activedirectoryetc,butthatdoesnthelpmemuch.IjustneedapluginwhichshouldaskforusertoprovidetheircredentialbeforestartbuildingtheJobandshouldusetheusercredentialtogetthejobexecuted,sothatmyMSDeploycommandwillbeabletodeploythecodeonProductionboxes,whentheSupportteammemberbuildthatJobusingtheircredential.Iwishtherewassupportforimpersonation.RightnowalltheJenkinsJobsaregettingexecutedusingtheserviceaccountwhichtheTomcatserviceisconfiguredtorunwithonwhichJenkinsishosted.BothDevelopersandSupportteammembersareADMINonbothJenkinswebserveraswellasonJenkinswebapplication.Iamlookingforwardtothefollowing.=EachjobcanhaveacheckboxsayExecuteusinganotherusercredentialorExecuteusingloggedonusercredential.NowwhenwestartthejobbyclickingonBuildbutton,whichishavingExecuteusinganotherusercredentialcheckboxchecked,theapplicationshouldasktoprovidecredentialthatneedstobeusedforBuildingthatJob.Thatjobshouldgetexecutedthenwiththatparticularcredential.SoevenifIcanbeabletorunthejobReleaseToProductionusingmycredentialthenitwillnotsucceedasIdonthaveaccesstoProductionwebserversforcreatingfiles,foldersetc.ButwhenthesamejobgetsexecutedbySupportteam,itshouldsucceedastheyhaveaccesstoProductionserversforcreatingfiles,folders,executinganyMSDeploycommands.
TheFlow:AcheckboxshouldbepresentontheCreateJobpageofJenkinssayingExecute\BuildasanotherUserORExecute\BuildJobusingloggedonusercredential.ThenifwecreateaJobwiththischeckboxchecked,andwhenwebuildtheJobbyclickingontheBuildbutton,itshoulddoeitherofthetwo,1.IfweimplementExecute\BuildasanotherUseroption,thenitshouldsimplypromptforapopup\dialogaskingtoprovideusercredential.ThenthejobshouldexecutealltheBuildSteps,usingthecredentialpassed.(i.e.,IfIpassmycredentialvipa...@mycompany.com,password123,thenitshouldusethiscredentialtoexecutealltheMSBuildcommandthatwespecifiedintheBuildstepoftheJenkinJob.).2.IfweimplementExecute\BuildJobusingloggedonusercredentialoption,thenitslittletrickyanditshouldexecutetheJob(BuildStepscommands)usingthecredentialoftheloggedonuser,withoutaskingforanydialogtoprovideusercredential,asitshoulduseloggedonusercredential.Option1seemsveryeasyandverysimpletoimplement.Whileoption2seemslittletrickyandrequireintegrationwithCredentialPlugin.Ifpossiblethencanwegetoption1implemented.In.NetIknowhowtoimplementimpersonation(http://platinumdogs.me/2008/10/30/net-c-impersonation-with-network-credentials/)butnotsureabouthowcanwedothisinJava(foundthisarticlebutnotsurehttps://svn.apache.org/repos/asf/jackrabbit/branches/2.0/jackrabbit-core/src/test/java/org/apache/jackrabbit/api/security/user/ImpersonationTest.java).
==Anyhelpwouldbeappreciated.Thisisgoingtobeaveryusefulfeaturetoeveryoneindeed.

[JIRA] [subversion] (JENKINS-10771) hudson.util.IOException2: remote file operation failed

2013-07-09 Thread mar...@mcbeister.de (JIRA)















































Marcel Beister
 commented on  JENKINS-10771


hudson.util.IOException2: remote file operation failed















+1 ... same issue here:
Jenkins: version 1.522
Host and Slaves: all on latest Java 7 x64 version, all running Windows 7 x64
The problem comes and goes, reconnecting the slave seems to help from time to time. The log usually says something like "java.lang.NoClassDefFoundError" e.g. in the subversion plugin. The slaves.jar file is up-to-date on all slaves.

Is there any way to debug this problem because this is a really annoying 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] [core] (JENKINS-14122) Build Executors on Nodes enter infinite hang

2013-07-09 Thread christian.lippha...@googlemail.com (JIRA)















































evernat
 commented on  JENKINS-14122


Build Executors on Nodes enter infinite hang















Is it reproduced with a recent Jenkins version?



























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] (JENKINS-17769) GitSCM.skipTag is broken in GitPublisher















































Christian Lipphardt
 commented on  JENKINS-17769


GitSCM.skipTag is broken in GitPublisher















I have the same issue:

Reproduce:

Add git repos
Check 'merge before build'
Check 'skip internal tag'
Add 'Git Publisher' as postbuild step
Check 'Push Only If Build Succeeds'
Check 'Merge Results'
Run build

-- Error

ERROR: Failed to push merge to origin repository
 [8mha:WB+LCABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mhudson.plugins.git.GitException: Could not delete tag jenkins-test0-1
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.deleteTag(CliGitAPIImpl.java:901)
	at hudson.plugins.git.GitAPI.deleteTag(GitAPI.java:212)
	at hudson.plugins.git.GitPublisher$2.invoke(GitPublisher.java:237)
	at hudson.plugins.git.GitPublisher$2.invoke(GitPublisher.java:223)
	at hudson.FilePath.act(FilePath.java:839)
	at hudson.FilePath.act(FilePath.java:821)
	at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:223)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710)
	at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685)
	at hudson.model.Build$RunnerImpl.post2(Build.java:162)
	at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632)
	at hudson.model.Run.run(Run.java:1463)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:239)
Caused by: hudson.plugins.git.GitException: Command "git tag -d jenkins-test0-1" returned status code 1:
stdout: 
stderr: error: tag 'jenkins-test0-1' not found.

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:740)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:750)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.deleteTag(CliGitAPIImpl.java:899)
	... 15 more
Pushing HEAD to branch integration at repo origin
Build step 'Git Publisher' changed build result to FAILURE
Build step 'Git Publisher' marked build as failure
Finished: FAILURE




























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-18426) When repository URL contains variable causes checkout from wrong SVN path

2013-07-09 Thread rbier...@home.nl (JIRA)















































Ron Bierman
 commented on  JENKINS-18426


When repository URL contains variable causes checkout from wrong SVN path















I tried to reproduce your issue but I'm not able to. 


	Do you have jenkins slaves running?
	What SVN workspace version are you using?






























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] [envinject] (JENKINS-18665) EnvInject not handling spaces correctly

2013-07-09 Thread andrejohn....@gmail.com (JIRA)















































Andre Mas
 updated  JENKINS-18665


EnvInject not handling spaces correctly
















Change By:


Andre Mas
(09/Jul/13 11:51 AM)




Summary:


EncInject
EnvInject
nothandlingspacescorrectly



























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







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

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)

2013-07-09 Thread hkhandhe...@nvidia.com (JIRA)















































hardik khandhedia
 commented on  JENKINS-18453


Need Impersonation support for executing Jenkins Jobs as a different user (Security related feature)















this is indeed a very useful feature 

it would be a great value addition to 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] [core] (JENKINS-18438) Node monitoring should run in parallel

2013-07-09 Thread f...@cessfil.net (JIRA)















































Philippe Jandot
 reopened  JENKINS-18438


Node monitoring should run in parallel
















This changes breaks node monitoring report.
See previous comments





Change By:


Philippe Jandot
(09/Jul/13 12:02 PM)




Resolution:


Fixed





Status:


Resolved
Reopened





Assignee:


KohsukeKawaguchi



























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







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

[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config

2013-07-09 Thread stefan.luetzkend...@projektron.de (JIRA)















































Stefan Lützkendorf
 commented on  JENKINS-18667


NullPointerException when saving job config















I have a similiar problem.

Saving a Job WITHOUT ANY changes causes NPE in

	at org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger.getLogFile(BuildResultTrigger.java:46)


javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:217)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
	at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
	at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:36)
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:32)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at

[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config

2013-07-09 Thread stefan.luetzkend...@projektron.de (JIRA)















































Stefan Lützkendorf
 updated  JENKINS-18667


NullPointerException when saving job config
















Change By:


Stefan Lützkendorf
(09/Jul/13 12:02 PM)




Affects Version/s:


current





Component/s:


buildresulttrigger



























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







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

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support to Build OR Execute Build Steps of Jenkins Jobs with different user credential















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support to Build OR Execute Build Steps of Jenkins Jobs with different user credential
















Change By:


Vijendra Patil
(09/Jul/13 12:16 PM)




Summary:


NeedImpersonationsupport
forexecuting
toBuildORExecuteBuildStepsof
JenkinsJobs
asa
with
differentuser
(Securityrelatedfeature)
credential





Description:


Hi,IneedtoexecutefewoftheJenkinsjobssuchasReleasetoProductionthroughJenkinsUIusingloggedonuserorusinganotherusercredential.Thereasonis,wehaveoneinstanceofJenkinsCIonwhichalltheJenkinsJobssuchasBuildMyApp,ReleaseMyApToQAetc.areconfigured.BoththeDevelopersaswellasSupportteammembersareadminonthisJenkinsapplicationInstanceaswellasontheJenkinsserver.Rightnow,theseJobsgetsexecutedusingthecredentialofserviceaccountwhichtheTomcatServiceisrunningwith,onwhichJenkinsishosted.Now,theproblemis,wecantusethesameinstancetoreleasedeployableitemstoProductionastheserviceaccountdoesnthavepermissiontoaccessProductionWebSeverstocopycodeonit.Andmoreover,itstheSupportTeamMemberswhohaveaccesstotheproductionboxes.Soinordertodeployanycodebasetoproduction,alltheWindowsDeployCommands(ex,create,updatefiles,folderetc.)needstoberunwithspecificusercredentialwhohasaccesstotheProductionBox.TheonlyoptionweareleftwithnowistohaveanotherserverwhichtheSupportTeamown,andhavealltheReleaseToProductionJobssetuponthisseparateinstanceofJenkins,whichonlySupportteammemberareADMINonit.ItriedusingparameterizedpluginbutcouldntabletopassthePasswordsuccessfullytothebatchfilewhichcontainsMSDeployinstructions.IcheckedRolebasedsecurityplugin,projectmatrix,activedirectoryetc,butthatdoesnthelpmemuch.IjustneedapluginwhichshouldaskforusertoprovidetheircredentialbeforestartbuildingtheJobandshouldusetheusercredentialtogetthejobexecuted,sothatmyMSDeploycommandwillbeabletodeploythecodeonProductionboxes,whentheSupportteammemberbuildthatJobusingtheircredential.Iwishtherewassupportforimpersonation.
RightnowalltheJenkinsJobsaregettingexecutedusingtheserviceaccountwhichtheTomcatserviceisconfiguredtorunwithonwhichJenkinsishosted.BothDevelopersandSupportteammembersareADMINonbothJenkinswebserveraswellasonJenkinswebapplication.
Iamlookingforwardtothefollowing.=
EachjobcanhaveacheckboxsayExecuteusinganotherusercredentialorExecuteusingloggedonusercredential.NowwhenwestartthejobbyclickingonBuildbutton,whichishavingExecuteusinganotherusercredentialcheckboxchecked,theapplicationshouldasktoprovidecredentialthatneedstobeusedforBuildingthatJob.Thatjobshouldgetexecutedthenwiththatparticularcredential.SoevenifIcanbeabletorunthejobReleaseToProductionusingmycredentialthenitwillnotsucceedasIdonthaveaccesstoProductionwebserversforcreatingfiles,foldersetc.ButwhenthesamejobgetsexecutedbySupportteam,itshouldsucceedastheyhaveaccesstoProductionserversforcreatingfiles,folders,executinganyMSDeploycommands.

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support to Build\Execute Jenkins Jobs(all build steps commands basically) with different user credential















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support to Build\Execute Jenkins Jobs(all build steps commands basically) with different user credential
















Change By:


Vijendra Patil
(09/Jul/13 12:21 PM)




Summary:


NeedImpersonationsupporttoBuild
OR
\
Execute
BuildStepsof
JenkinsJobs
(allbuildstepscommandsbasically)
withdifferentusercredential



























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







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

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support to Build\Execute Jenkins Jobs(all Build Steps commands basically) with different user credential















































Vijendra Patil
 updated  JENKINS-18453


Need Impersonation support to Build\Execute Jenkins Jobs(all Build Steps commands basically) with different user credential
















Change By:


Vijendra Patil
(09/Jul/13 12:22 PM)




Summary:


NeedImpersonationsupporttoBuild\ExecuteJenkinsJobs(all
buildsteps
BuildSteps
commandsbasically)withdifferentusercredential



























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] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config

2013-07-09 Thread theta...@java.net (JIRA)















































thetaphi
 commented on  JENKINS-18667


NullPointerException when saving job config















I can confirm, in ScriptTrigger it is the same: Save without any changes causes NPE.



























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-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive















































Jesse Glick
 updated  JENKINS-18660


10,000+ jobs tied to a label make Node index page unusably unresponsive
















Change By:


Jesse Glick
(09/Jul/13 12:34 PM)




Labels:


performance



























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-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive















































Jesse Glick
 commented on  JENKINS-18660


10,000+ jobs tied to a label make Node index page unusably unresponsive















Is this really “minor” given that the original report claimed 60sec load time per page as a result of this? And should it be lts-candidate?



























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] [walldisplay] (JENKINS-18670) Disabled jobs remain on wall display

2013-07-09 Thread k...@birkelund.me (JIRA)















































Kim Birkelund
 created  JENKINS-18670


Disabled jobs remain on wall display















Issue Type:


Bug



Assignee:


Christian Pelster



Components:


walldisplay



Created:


09/Jul/13 12:41 PM



Description:


1. Create a wall display that omits disabled builds.
2. Create a job on that wall.
3. Disable job.

The job remains on the wall until page is updated (i.e. F5, not the internal wall update).




Project:


Jenkins



Priority:


Major



Reporter:


Kim Birkelund

























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-18671) Clock Difference broken on Manage Nodes page

2013-07-09 Thread andreas.b...@ericsson.com (JIRA)















































Andréas Berg
 created  JENKINS-18671


Clock Difference broken on Manage Nodes page















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


jenkins_node_clock_difference.png



Components:


core



Created:


09/Jul/13 12:54 PM



Description:


Since we upgraded from Jenkins 1.520 to 1.522 the Clock Difference is broken on the Manage Nodes page. Master and all slaves are in sync but Jenkins reports something completely different. Master and any slave running on the same server as master is reported correctly.




Environment:


Jenkins 1.522 on Ubuntu 13.04, nodes on solaris sparc, solaris x86 and redhat linux.




Project:


Jenkins



Priority:


Major



Reporter:


Andréas Berg

























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-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive

2013-07-09 Thread stephenconno...@java.net (JIRA)















































stephenconnolly
 commented on  JENKINS-18660


10,000+ jobs tied to a label make Node index page unusably unresponsive















I don't know how many users have 10,000+ jobs, so far as I know Daniel was the first to identify this issue. I have no issue with upgrading to Major. 

I thought a fix had to be in trunk for 2wk+ before considering for LTS. If it can be flagged as such immediately, fine by me (and presume Daniel too)



























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















































Martin dAnjou
 commented on  JENKINS-17265


Builds disappearing from history















Seeing this problem coming back on LTS 1.509.2. I have no idea how to debug...



























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-18213) Copying an existing job to a new one gives an error woth Status Code: 500

2013-07-09 Thread sch_...@web.de (JIRA)















































Uwe Schneider
 commented on  JENKINS-18213


Copying an existing job to a new one gives an error woth Status Code: 500















I can reproduce this problem with jenkins version 1.510.



























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-18672) NPE when reading JUnit reports

2013-07-09 Thread b.vo...@buddyandselly.com (JIRA)















































Bu Vo
 created  JENKINS-18672


NPE when reading JUnit reports















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


junit



Created:


09/Jul/13 1:53 PM



Description:


When reading the generated reports I get the following exception

Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
java.lang.NullPointerException
at hudson.tasks.junit.CaseResult.getPackageName(CaseResult.java:289)
at hudson.tasks.junit.TestResult.tally(TestResult.java:578)
	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:118)
	at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90)
	at hudson.FilePath.act(FilePath.java:905)
	at hudson.FilePath.act(FilePath.java:878)
	at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87)
	at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:121)
	at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:133)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1618)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:247)

example xml result:

?xml version="1.0" encoding="UTF-8"?
testsuite name="User with two api keys" tests="1" time="0.409146879" failures="0" errors="0" skipped="0"
  testcase name="User with two api keys #api_key returns the first api key" time="0.408775226"
  /testcase
  system-out
  /system-out
  system-err
  /system-err
/testsuite




Environment:


ruby 1.9.3-p448

rails 3.2.13

rspec 2.13.1

ci_reporter 1.9.0

jenkins 1.521




Project:


Jenkins



Priority:


Major



Reporter:


Bu Vo

























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-17363) Ludicrously slow load time [with lazyloading]

2013-07-09 Thread r...@cybikbase.com (JIRA)















































Renaud Lepage
 updated  JENKINS-17363


Ludicrously slow load time [with lazyloading]
















Change By:


Renaud Lepage
(09/Jul/13 1:58 PM)




Labels:


ridiculous
slow





Environment:


LatestJenkins,Linux
ecamolx0800.mo.ca.am.ericsson.se
/redactedhostname/
2.6.18-194.el5#1SMPTueMar1621:52:39EDT2010x86_64x86_64x86_64GNU/Linux,SuSemostprobably.



























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-18673) Nested JUnit testsuites are not displayed correctly

2013-07-09 Thread olivier.martin...@gmail.com (JIRA)















































Olivier Martin
 created  JENKINS-18673


Nested JUnit testsuites are not displayed correctly















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


report.xml, Screenshot-1.png, Screenshot-2.png



Components:


junit



Created:


09/Jul/13 2:00 PM



Description:


The nested testsuites do not seem to be displayed correctly by Jenkins.

Here is my JUnit test report:

?xml version="1.0" encoding="utf-8"?
testsuites name="My Testsuites"
testsuite name="TestSuite A"
 testsuite name="Nested TestSuite 1"
  testcase name="TestCase 1" time="0" /
  testcase name="TestCase 2" time="0" /
 /testsuite
 testsuite name="Nested TestSuite 2"
  testcase name="TestCase 3" time="0" /
  testcase name="TestCase 4" time="0" /
 /testsuite
/testsuite
testsuite name="TestSuite B"
 testsuite name="Nested TestSuite 3"
  testcase name="TestCase 5" time="0" /
  testcase name="TestCase 6" time="0" /
 /testsuite
 testsuite name="Nested TestSuite 4"
  testcase name="TestCase 7" time="0" /
  testcase name="TestCase 8" time="0" /
 /testsuite
/testsuite
/testsuites


From the attached screenshot, we can clearly see Jenkins does not support the first level testsuite.

My "TestSuite A" and "TestSuite B" are not displayed. And all my "Nested TestSuite N" are attached to the root testuites.

From this fixed bug: https://issues.jenkins-ci.org/browse/JENKINS-6545, it looks Jenkins is expected to support nested testsuites.




Environment:


Jenkins ver. 1.514




Project:


Jenkins



Priority:


Major



Reporter:


Olivier Martin

























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-14122) Build Executors on Nodes enter infinite hang

2013-07-09 Thread lionh...@onlinehome.de (JIRA)















































Martin Schröder
 commented on  JENKINS-14122


Build Executors on Nodes enter infinite hang















 Is it reproduced with a recent Jenkins version?

We have not yet seen it to recur since switching to the LTS-release 1.509.1 some weeks ago.
Before that, we followed the non-LTS releases relatively closely. The last versions we used before the switch to LTS was 1.497 and 1.501; one of them experienced the problem at least once.


As said in the bug description, it is very rarely-occurring bug. Even before, we sometimes had half a year of stable runtime before it struck and necessitated a reboot. But apart from that, the uptime since the last reboot does not seem to matter. The issue can strike freely even hours after a reboot.


In short: We have not seen it in the LTS-release, but we can't say for certain that the bug is gone.



























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







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

[JIRA] [robot-plugin] (JENKINS-9386) Links to local screenshots in Robot plugin don't work if I view logs from Original report files

2013-07-09 Thread kormb...@gmail.com (JIRA)















































Kevin Ormbrek
 commented on  JENKINS-9386


Links to local screenshots in Robot plugin dont work if I view logs from Original report files















This is resolved in 1.2.1 with the Other files to copy option. For Selenium2Library, value */.png for Other files to copy would archive screenshots in the Robot Framework results and make the log contain proper screenshots.



























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-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration opened

2013-07-09 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 created  JENKINS-18674


TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration opened















Issue Type:


Bug



Assignee:


nidaley



Components:


core, plot



Created:


09/Jul/13 2:12 PM



Description:


When plot plugin publisher (Plot build data) is configured for a job and the configuration is opened again, the loading will never finish.

The _javascript_ error is identified as TypeError: registry is undefined.




Environment:


1.522




Project:


Jenkins



Priority:


Major



Reporter:


Oliver Gondža

























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] [robot-plugin] (JENKINS-18675) Failure in suite teardown does not fail test cases

2013-07-09 Thread kormb...@gmail.com (JIRA)















































Kevin Ormbrek
 created  JENKINS-18675


Failure in suite teardown does not fail test cases















Issue Type:


Bug



Affects Versions:


current



Assignee:


jpiironen



Components:


robot-plugin



Created:


09/Jul/13 2:21 PM



Description:


When generating the report and log files from the output file, Robot Framework marks all tests failed if the suite teardown failed. The Jenkins plugin does not do the same.




Project:


Jenkins



Priority:


Major



Reporter:


Kevin Ormbrek

























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-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration opened

2013-07-09 Thread fabr...@antidot.com (JIRA)















































Fabrice Flore-Thébault
 commented on  JENKINS-18674


TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration opened















i can confirm this issue ; if i remove the hudson.plugins.plot.PlotPublisher plugin="plot@1.5" section in the config.xml of the project and restart jenkins, the config for plots gets lost but the configure tab is working 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] [core] (JENKINS-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened

2013-07-09 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 updated  JENKINS-18674


TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened
















Change By:


Oliver Gondža
(09/Jul/13 2:27 PM)




Summary:


TypeError:registryisundefinedinprototype.js:5621whenplotpluginpublisherconfiguration
opened
reopened





Description:


Whenplotpluginpublisher(Plotbuilddata)isconfiguredforajobandtheconfigurationis
openedagain
reopened
,theloadingwillneverfinish.The_javascript_errorisidentifiedas{{TypeError:registryisundefined}}
at:{{noformat}}varrespondersForEvent=registry
.
get(eventName);{{noformat}}



























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-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened

2013-07-09 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 updated  JENKINS-18674


TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened
















Change By:


Oliver Gondža
(09/Jul/13 2:27 PM)




Description:


Whenplotpluginpublisher(Plotbuilddata)isconfiguredforajobandtheconfigurationisreopened,theloadingwillneverfinish.The_javascript_errorisidentifiedas{{TypeError:registryisundefined}}at:{
{
noformat}
}
varrespondersForEvent=registry.get(eventName);{
{
noformat}
}



























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] [envinject] (JENKINS-14144) Build config history getting spammed

2013-07-09 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 commented on  JENKINS-14144


Build config history getting spammed















Proposal for a partial workaround : https://github.com/jenkinsci/envinject-plugin/pull/17

Seems current design (to add/remove a technical buildwrapper) introduce a possible race condition :
with concurrent builds enabled, build 1 may remove buildWrapper after build 2 added one, but before it actually was used to set build 2 environment. 



























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







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

[JIRA] [active-directory] (JENKINS-18453) Need Impersonation support to Build\Execute Jenkins Jobs(all Build Steps commands basically) with different user credential















































Jesse Glick
 commented on  JENKINS-18453


Need Impersonation support to Build\Execute Jenkins Jobs(all Build Steps commands basically) with different user credential















Option #1 is useless for jobs with automatic triggers.

Please note that the existence of an issue in JIRA, or comments agreeing that the described feature would be useful, do not imply that anyone has any plans to work on such a feature, unless you write it yourself or pay someone to do it for you (such as using the freedomsponsors.org link on this page).



























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-18671) Clock Difference broken on Manage Nodes page

2013-07-09 Thread ptsamou...@gmail.com (JIRA)















































Pete Tsamouris
 commented on  JENKINS-18671


Clock Difference broken on Manage Nodes page















Same here, nodes from 3months ahead to 3 days behind.
Upgraded from 1.519 to 1.522.




























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-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive















































Jesse Glick
 updated  JENKINS-18660


10,000+ jobs tied to a label make Node index page unusably unresponsive
















Change By:


Jesse Glick
(09/Jul/13 2:41 PM)




Labels:


lts-candidate
performance



























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-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive















































Jesse Glick
 commented on  JENKINS-18660


10,000+ jobs tied to a label make Node index page unusably unresponsive















I thought a fix had to be in trunk for 2wk+ before considering for LTS.

It can be flagged at any time; the two-week rule applies to merging 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-18671) Clock Difference broken on Manage Nodes page

2013-07-09 Thread andreas.b...@ericsson.com (JIRA)















































Andréas Berg
 updated  JENKINS-18671


Clock Difference broken on Manage Nodes page
















Change By:


Andréas Berg
(09/Jul/13 3:03 PM)




Description:


SinceweupgradedfromJenkins1.520to1.522theClockDifferenceisbrokenontheManageNodespage.MasterandallslavesareinsyncbutJenkinsreportssomethingcompletelydifferent.Masterandanyslaverunningonthesameserverasmasterisreportedcorrectly.
Wehave3Jenkinsserversdisplayingthesamesymptoms.



























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-18671) Clock Difference broken on Manage Nodes page

2013-07-09 Thread mar...@mcbeister.de (JIRA)















































Marcel Beister
 commented on  JENKINS-18671


Clock Difference broken on Manage Nodes page















Same here: one node is 15 mins ahead, the other one is 4d 16h ahead.
Is it possible that this is related to remote file system problems e.g. described in 10771?



























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-18671) Clock Difference broken on Manage Nodes page

2013-07-09 Thread andreas.b...@ericsson.com (JIRA)















































Andréas Berg
 commented on  JENKINS-18671


Clock Difference broken on Manage Nodes page















This issue appeared for us after upgrading from 1.520 to 1.522. I've never seen this behaviour before so I doubt its realted to #10771 as that issue has existed for almost two years.



























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-18671) Clock Difference broken on Manage Nodes page

2013-07-09 Thread mar...@mcbeister.de (JIRA)















































Marcel Beister
 commented on  JENKINS-18671


Clock Difference broken on Manage Nodes page















A manual refresh is done almost instantly, the time difference remains the same 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] [maven2] (JENKINS-10777) On M2 job, with only one sudmodule built, link to maven site failed with 404 message.

2013-07-09 Thread tho...@tveon.dk (JIRA)















































Thomas Vestergaard Trolle
 commented on  JENKINS-10777


On M2 job, with only one sudmodule built, link to maven site failed with 404 message.















Yes, it is reproducible on version 1.522. I will see, if I can find time to make a demo-project.



























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-18676) Allow CommandInterpreters to set build status based on script result

2013-07-09 Thread ktur...@precisioninfinity.com (JIRA)















































Precision Developer
 created  JENKINS-18676


Allow CommandInterpreters to set build status based on script result















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


09/Jul/13 3:56 PM



Description:


Our company has been using Jenkins for a while now and have been wanting to improve the flexibility of script-based functions to support setting the status of the build to something other than SUCCESS or FAILED. So far, we've worked around the issue using cli commands, but I don't see why this couldn't be an option for plugin developers to setup using an inherited method.




Project:


Jenkins



Labels:


jenkins
plugin
core




Priority:


Major



Reporter:


Precision Developer

























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-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers

2013-07-09 Thread arturo.du...@etask.it (JIRA)















































Arturo Duran
 created  JENKINS-18677


Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers















Issue Type:


Bug



Affects Versions:


current



Assignee:


wolfs



Components:


all-changes



Created:


09/Jul/13 4:00 PM



Description:


After upgrading to version 1.522, some jobs were not correctly loaded once restarting jenkins. The following error is shown for some jobs in the jenkins log while restarting:

Jul 9, 2013 10:15:55 AM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job Base-Checkout.Install
java.lang.NoSuchFieldError: triggers
at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:187)



Not sure which specific configuration inside that jobs cause the problem but once jenkins is started the jobs are not listed nor located by other jobs that depend on them






Due Date:


08/Jul/13 12:00 AM




Environment:


CentOS 6.3

JDK  1.6.0_37-b06






Project:


Jenkins



Priority:


Major



Reporter:


Arturo Duran

























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] [envinject] (JENKINS-14144) Build config history getting spammed















































Jesse Glick
 updated  JENKINS-14144


Build config history getting spammed
















#18 now.





Change By:


Jesse Glick
(09/Jul/13 4:04 PM)




URL:


https://github.com/jenkinsci/envinject-plugin/pull/18



























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-07-09 Thread christian.k.2...@gmail.com (JIRA)















































Christian K.
 commented on  JENKINS-12827


api should return the build number that was queued.















Another idea for a workaround would be to make the build parametrized, e.g. with a parameter "id". On the remote side you could than generate a unique and deterministic build ID that you can later recognize in the builds XML/JSON description.



























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.

Invitation: Urgent Respond. @ Tue Jul 9, 2013 12:30pm - 1:30pm (adamssaa...@gmail.com)

2013-07-09 Thread Adams Saad

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20130709T163000Z
DTEND:20130709T173000Z
DTSTAMP:20130709T163328Z
ORGANIZER;CN=adamssaa...@gmail.com:mailto:adamssaa...@gmail.com
UID:r8f7o7kaes0grif8o9b7h6q...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Jenkins Issues;X-NUM-GUESTS=0:mailto:jenkinsci-issues@googlegroups.
 com
CREATED:20130709T163315Z
DESCRIPTION:Dear Friend\,\n\nGreeting to you\n\nI am (Mr. Adams Saad) and I
  know that this message will come as a surprise to you\, since we don’t kno
 w each other\, but pay attention and understand my reason of contacting you
  through this via email\, for the purpose of introduction\; I have a busine
 ss proposal in the tune of ($10.m)\n\nWe shall share in ratio of 40% for yo
 u and 60% for me. Finally\, should you be interested to operate this projec
 t with me\, reply me urgently and I will give you the full details for us t
 o move forward.\n\nYour earliest response to this letter will be appreciate
 d and also Your Full Name\,Your full residential address\, Your occupation\
 , Your City\, Your Country of origin\, Your Mobile phone\, Your age\, Your 
 marital status And Phone Number is needed for Easy communication. Mobile + 
 226 61055848.\n\nYours faithfully\,\n\nMr. Adams Saad. (adamssaad1@postafio
 k.hu)\nView your event at http://www.google.com/calendar/event?action=VIEW;
 eid=cjhmN283a2FlczBncmlmOG85YjdoNnFoazAgamVua2luc2NpLWlzc3Vlc0Bnb29nbGVncm9
 1cHMuY29ttok=MjEjYWRhbXNzYWFkNTNAZ21haWwuY29tNTk5ZDM3OWYyYTJjZWY5OTQxNjg2M
 mI3YjRmNzA1ZjYyM2RhY2Q2Mgctz=America/New_Yorkhl=en.
LAST-MODIFIED:20130709T163319Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Urgent Respond.
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

[JIRA] [repository] (JENKINS-17756) The jenkins repository is in the jenkins RPM

2013-07-09 Thread florian.k...@dvag.com (JIRA)















































Florian Koch
 commented on  JENKINS-17756


The jenkins repository is in the jenkins RPM















Hi,

i also agree, we have an pulp server for rpm, and all internal servers connect to this server instead of an external url, with this repo file included, yum breaks with error, can not connect, so we always need to ensure that the repo file is removed.

please fix this!

regards _fk



























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] [repository] (JENKINS-17756) The jenkins repository is in the jenkins RPM

2013-07-09 Thread florian.k...@dvag.com (JIRA)













































 
Florian Koch
 edited a comment on  JENKINS-17756


The jenkins repository is in the jenkins RPM
















Hi,

i also agree, we have an pulp server for rpm, and all internal servers connect to this server instead of an external url, with this repo file included, yum breaks with error, can not connect, so we always need to ensure that the repo file is removed.

please fix this!

regards Florian



























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-trigger] (JENKINS-13829) Race condition in Queue.pop()
















































evernat
 resolved  JENKINS-13829 as Fixed


Race condition in Queue.pop()
















As said in the comment of the commit, this issue was fixed by working around and storing the parameters.
So I suppose that this issue can be resolved as fixed.





Change By:


evernat
(09/Jul/13 4:58 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] [gerrit-trigger] (JENKINS-13829) Race condition in Queue.pop()















































evernat
 updated  JENKINS-13829


Race condition in Queue.pop()
















Change By:


evernat
(09/Jul/13 4:59 PM)




Component/s:


gerrit-trigger





Component/s:


core



























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







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

[JIRA] [teamconcert] (JENKINS-18293) Team Concert plugin cannot cope with symbolic links

2013-07-09 Thread heath...@ca.ibm.com (JIRA)
















































Heather Fraser-Dube
 resolved  JENKINS-18293 as Fixed


Team Concert plugin cannot cope with symbolic links
















Updated the help and the main page to indicate the setup for symbolic links





Change By:


Heather Fraser-Dube
(09/Jul/13 5:28 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] [teamconcert] (JENKINS-18284) Team Concert plugin doesn't load components as root folders

2013-07-09 Thread heath...@ca.ibm.com (JIRA)
















































Heather Fraser-Dube
 resolved  JENKINS-18284 as Fixed


Team Concert plugin doesnt load components as root folders
















The help has been updated to indicate for customized load, a build definition should be used. 





Change By:


Heather Fraser-Dube
(09/Jul/13 5:39 PM)




Status:


Open
Resolved





Assignee:


HeatherFraser-Dube





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] [teamconcert] (JENKINS-18419) Snapshot name is missing build number

2013-07-09 Thread sco...@ca.ibm.com (JIRA)
















































Scott Cowan
 resolved  JENKINS-18419 as Fixed


Snapshot name is missing build number
















Change By:


Scott Cowan
(09/Jul/13 5:55 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] [release] (JENKINS-18548) Release build runs different than manual build

2013-07-09 Thread sco...@ca.ibm.com (JIRA)















































Scott Cowan
 updated  JENKINS-18548


Release build runs different than manual build
















Change By:


Scott Cowan
(09/Jul/13 5:59 PM)




Component/s:


release





Component/s:


teamconcert



























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] [tfs] (JENKINS-18587) TFS Plugin - History command causes authenticate exception

2013-07-09 Thread cjasprom...@yahoo.com (JIRA)
















































CJ Aspromgos
 resolved  JENKINS-18587 as Wont Fix


TFS Plugin - History command causes authenticate exception
















The problem was a web proxy was being used to access TFS.  The solution was to unset the HTTP_PROXY env var.





Change By:


CJ Aspromgos
(09/Jul/13 6:06 PM)




Status:


Open
Resolved





Resolution:


WontFix



























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







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

[JIRA] [role-strategy] (JENKINS-18648) [Backward-compatibility] - NPE in case of new role group types (ex, slave roles)

2013-07-09 Thread o.v.nenas...@gmail.com (JIRA)
















































Oleg Nenashev
 resolved  JENKINS-18648 as Fixed


[Backward-compatibility] - NPE in case of new role group types (ex, slave roles)
















https://github.com/jenkinsci/role-strategy-plugin/pull/4

Fix Version: 1.1.3





Change By:


Oleg Nenashev
(09/Jul/13 7:42 PM)




Status:


InProgress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18678) Builds disappear from build history in LTS 1.509.2















































Martin dAnjou
 created  JENKINS-18678


Builds disappear from build history in LTS 1.509.2















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


jenkins-missing-builds.png



Components:


core



Created:


09/Jul/13 8:20 PM



Description:


Builds disappear from build history in Jenkins LTS 1.509.2.

We upgraded from 1.492 on Thursday before a long weekend, so not much happened over the weekend. Four days later, that is today, we lost some builds. We recovered them by reloading from disk this morning. Later in the afternoon of the same day, a project was renamed, and some of its builds went missing.

Here are the builds of the renamed job on disk:

$ ls -l
total 25
lrwxrwxrwx 1 jenkins jenkins  19 Mar  1 13:29 1 - 2013-03-01_13-29-26
lrwxrwxrwx 1 jenkins jenkins  19 Mar  1 13:31 2 - 2013-03-01_13-31-20
drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-01_13-29-26
drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-01_13-31-20
drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-01_13-32-42
drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-28_09-56-31
drwxrwxr-x 3 jenkins jenkins 141 Jul  9 08:24 2013-03-28_10-02-11
lrwxrwxrwx 1 jenkins jenkins  19 Mar  1 13:32 3 - 2013-03-01_13-32-42
lrwxrwxrwx 1 jenkins jenkins  19 Mar 28 09:56 4 - 2013-03-28_09-56-31
lrwxrwxrwx 1 jenkins jenkins  19 Mar 28 10:02 5 - 2013-03-28_10-02-11
lrwxrwxrwx 1 jenkins jenkins   1 Jul  9 14:23 lastFailedBuild - 4
lrwxrwxrwx 1 jenkins jenkins   1 Jul  9 14:23 lastStableBuild - 5
lrwxrwxrwx 1 jenkins jenkins   1 Jul  4 11:18 lastSuccessfulBuild - 5
lrwxrwxrwx 1 jenkins jenkins   2 Jul  9 14:23 lastUnstableBuild - -1
lrwxrwxrwx 1 jenkins jenkins   1 Jul  9 14:23 lastUnsuccessfulBuild - 4



How do I debug this? One thing looks odd: the dates on the symbolic links differ from the dates in the build history, and differ from the directories they actually link.




Environment:


Linux




Project:


Jenkins



Priority:


Critical



Reporter:


Martin dAnjou

























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-18678) Builds disappear from build history in LTS 1.509.2















































Martin dAnjou
 updated  JENKINS-18678


Builds disappear from build history in LTS 1.509.2
















Change By:


Martin dAnjou
(09/Jul/13 8:27 PM)




Description:


BuildsdisappearfrombuildhistoryinJenkinsLTS1.509.2.Weupgradedfrom1.492onThursdaybeforealongweekend,sonotmuchhappenedovertheweekend.Fourdayslater,thatistoday,welostsomebuilds.Werecoveredthembyreloadingfromdiskthismorning.Laterintheafternoonofthesameday,aprojectwasrenamed,andsomeofitsbuildswentmissing.Herearethebuildsoftherenamedjobondisk:{noformat}$ls-ltotal25lrwxrwxrwx1jenkinsjenkins19Mar113:291-2013-03-01_13-29-26lrwxrwxrwx1jenkinsjenkins19Mar113:312-2013-03-01_13-31-20drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-29-26drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-31-20drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-32-42drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-28_09-56-31drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-28_10-02-11lrwxrwxrwx1jenkinsjenkins19Mar113:323-2013-03-01_13-32-42lrwxrwxrwx1jenkinsjenkins19Mar2809:564-2013-03-28_09-56-31lrwxrwxrwx1jenkinsjenkins19Mar2810:025-2013-03-28_10-02-11lrwxrwxrwx1jenkinsjenkins1Jul914:23lastFailedBuild-4lrwxrwxrwx1jenkinsjenkins1Jul914:23lastStableBuild-5lrwxrwxrwx1jenkinsjenkins1Jul411:18lastSuccessfulBuild-5lrwxrwxrwx1jenkinsjenkins2Jul914:23lastUnstableBuild--1lrwxrwxrwx1jenkinsjenkins1Jul914:23lastUnsuccessfulBuild-4{noformat}
Thediskshows5builds,1through5,buttheGUIonlyshows4and5,itismissing1,2,and3.
HowdoIdebugthis?Onethinglooksodd:thedatesonthesymboliclinksdifferfromthedatesinthebuildhistory,anddifferfromthedirectoriestheyactuallylink.



























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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'

2013-07-09 Thread mmaxw...@jackhenry.com (JIRA)















































mark 3000
 commented on  JENKINS-17475


Backup stops when processing some file like latestfailedbuild















Confirmed on Windows machine with Jenkins 1.518 and ThinBackup 1.7.2: 
"builds\lastFailedBuild' exists but is not a directory"



























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-18678) Builds disappear from build history in LTS 1.509.2















































Martin dAnjou
 updated  JENKINS-18678


Builds disappear from build history in LTS 1.509.2
















Change By:


Martin dAnjou
(09/Jul/13 8:36 PM)




Description:


BuildsdisappearfrombuildhistoryinJenkinsLTS1.509.2.Weupgradedfrom1.492on
Thursdaybeforealongweekend,sonotmuchhappenedovertheweekend
July4thandthenrenamedsomebuilds
.Fourdayslater
,thatistoday,
we
lostsome
realizedtherenamed
builds
hadgonemissing
.Werecoveredthembyreloadingfromdiskthismorning.Laterintheafternoon
ofthesameday
,
a
another
projectwasrenamed,andsomeofitsbuildswentmissing
too
.Herearethebuildsoftherenamedjobondisk:{noformat}$ls-ltotal25lrwxrwxrwx1jenkinsjenkins19Mar113:291-2013-03-01_13-29-26lrwxrwxrwx1jenkinsjenkins19Mar113:312-2013-03-01_13-31-20drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-29-26drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-31-20drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-32-42drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-28_09-56-31drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-28_10-02-11lrwxrwxrwx1jenkinsjenkins19Mar113:323-2013-03-01_13-32-42lrwxrwxrwx1jenkinsjenkins19Mar2809:564-2013-03-28_09-56-31lrwxrwxrwx1jenkinsjenkins19Mar2810:025-2013-03-28_10-02-11lrwxrwxrwx1jenkinsjenkins1Jul914:23lastFailedBuild-4lrwxrwxrwx1jenkinsjenkins1Jul914:23lastStableBuild-5lrwxrwxrwx1jenkinsjenkins1Jul411:18lastSuccessfulBuild-5lrwxrwxrwx1jenkinsjenkins2Jul914:23lastUnstableBuild--1lrwxrwxrwx1jenkinsjenkins1Jul914:23lastUnsuccessfulBuild-4{noformat}Thediskshows5builds,1through5,buttheGUIonlyshows4and5,itismissing1,2,and3.HowdoIdebugthis?Onethinglooksodd:thedatesonthesymboliclinksdifferfromthedatesinthebuildhistory,anddifferfromthedirectoriestheyactuallylink.



























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-18679) Back button navigation to a form should be disabled















































Jesse Glick
 created  JENKINS-18679


Back button navigation to a form should be disabled















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


09/Jul/13 8:39 PM



Description:


f:form should disable back button navigation, at least when l:lazy was used on the previous page: as https://github.com/jenkinsci/jenkins/commit/dbdf1d53472289437eced13efb87b76a55029186 mentions, returning to a Jenkins form can cause all sorts of problems.




Project:


Jenkins



Labels:


_javascript_




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] [core] (JENKINS-18678) Builds disappear from build history in LTS 1.509.2















































Martin dAnjou
 updated  JENKINS-18678


Builds disappear from build history in LTS 1.509.2
















Change By:


Martin dAnjou
(09/Jul/13 8:41 PM)




Description:


BuildsdisappearfrombuildhistoryinJenkinsLTS1.509.2.Weupgradedfrom1.492onJuly4thandthenrenamed
somebuilds
onebuild
.Fourdayslaterwerealizedtherenamed
builds
build
had
gonemissing
lostsomeorallofitshistory
.Werecovered
them
thehistory
byreloadingfromdiskthismorning.Laterintheafternoon,anotherprojectwasrenamed,andsomeofits
builds
buildhistory
wentmissingtoo.Herearethebuildsoftherenamedjobondisk:{noformat}$ls-ltotal25lrwxrwxrwx1jenkinsjenkins19Mar113:291-2013-03-01_13-29-26lrwxrwxrwx1jenkinsjenkins19Mar113:312-2013-03-01_13-31-20drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-29-26drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-31-20drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-01_13-32-42drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-28_09-56-31drwxrwxr-x3jenkinsjenkins141Jul908:242013-03-28_10-02-11lrwxrwxrwx1jenkinsjenkins19Mar113:323-2013-03-01_13-32-42lrwxrwxrwx1jenkinsjenkins19Mar2809:564-2013-03-28_09-56-31lrwxrwxrwx1jenkinsjenkins19Mar2810:025-2013-03-28_10-02-11lrwxrwxrwx1jenkinsjenkins1Jul914:23lastFailedBuild-4lrwxrwxrwx1jenkinsjenkins1Jul914:23lastStableBuild-5lrwxrwxrwx1jenkinsjenkins1Jul411:18lastSuccessfulBuild-5lrwxrwxrwx1jenkinsjenkins2Jul914:23lastUnstableBuild--1lrwxrwxrwx1jenkinsjenkins1Jul914:23lastUnsuccessfulBuild-4{noformat}Thediskshows5builds,1through5,buttheGUIonlyshows4and5,itismissing1,2,and3.HowdoIdebugthis?Onethinglooksodd:thedatesonthesymboliclinksdifferfromthedatesinthebuildhistory,anddifferfromthedirectoriestheyactuallylink.



























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-18680) View.onJobRenamed should be deprecated















































Jesse Glick
 created  JENKINS-18680


View.onJobRenamed should be deprecated















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


09/Jul/13 8:45 PM



Description:


View.onJobRenamed does not work well with item groups. Jenkins could instead include a single ItemListener which told views when a job was renamed, relieving the code doing the rename (such as in Jenkins or Folder) from having to call this method. (Same for deletions.) That would also allow views to be notified when a job in a subfolder (which ListView now supports) is renamed, which is currently not possible. Perhaps onJobRenamed should be deprecated, and a new callback introduced which can handle jobs in subfolders and also cross-folder moves.




Project:


Jenkins



Labels:


api
folders




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] [core] (JENKINS-18681) ItemGroupMixIn.redirectAfterCreateItem should be overridable















































Jesse Glick
 created  JENKINS-18681


ItemGroupMixIn.redirectAfterCreateItem should be overridable















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


09/Jul/13 8:47 PM



Description:


Currently ItemGroupMixIn.redirectAfterCreateItem is hardcoded to append configure to the item URL, which is not necessarily appropriate for all items. For example, in general after creating a new folder your next action is not going to be to configure the folder, which is rarely necessary. Rather, there should be some overridable method (e.g. a TopLevelItem extension interface?) permitting specific item types to specify where they wish to redirect to.




Project:


Jenkins



Labels:


api
folders




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] [core] (JENKINS-18682) Strange NoClassDefFoundError on slave with flexible-publish

2013-07-09 Thread magn...@java.net (JIRA)















































magnayn
 created  JENKINS-18682


Strange NoClassDefFoundError on slave with flexible-publish















Issue Type:


Bug



Assignee:


bap



Components:


core, flexible-publish



Created:


09/Jul/13 9:22 PM



Description:


At the end of the job:


Waiting for Jenkins to finish collecting data
channel stopped
Run condition Always enabling perform for step Archive the artifacts
Archiving artifacts
ERROR: Failed to archive artifacts: */.log
hudson.util.IOException2: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.POSIXFactory
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1943)
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:137)
	at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)
	at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)
	at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)
	at org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:88)
	at org.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:96)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:969)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1618)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:242)
Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.POSIXFactory
	at hudson.remoting.Channel$4.adapt(Channel.java:755)
	at hudson.remoting.Channel$4.adapt(Channel.java:750)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1941)
	... 15 more
Caused by: java.lang.NoClassDefFoundError: Could not initialize class jnr.posix.POSIXFactory
	at hudson.os.PosixAPI.jnr(PosixAPI.java:30)
	at hudson.util.IOUtils.mode(IOUtils.java:125)
	at hudson.util.io.TarArchiver.visit(TarArchiver.java:102)
	at hudson.util.DirScanner$Glob.scan(DirScanner.java:133)
	at hudson.FilePath.writeToTar(FilePath.java:1979)
	at hudson.FilePath.access$1000(FilePath.java:169)
	at hudson.FilePath$36.invoke(FilePath.java:1920)
	at hudson.FilePath$36.invoke(FilePath.java:1916)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2388)
	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)
Build step 'Flexible publish' changed build result to FAILURE
Finished: FAILURE




Environment:


Jenkins 






Project:


Jenkins



Priority:


Major



Reporter:


magnayn

[JIRA] [core] (JENKINS-17721) StringIndexOutOfBoundsException in PackageResult.findCorrespondingResult















































Jesse Glick
 updated  JENKINS-17721


StringIndexOutOfBoundsException in PackageResult.findCorrespondingResult
















Change By:


Jesse Glick
(09/Jul/13 9:33 PM)




Labels:


junitlts
1.509.2
-
candidate
fixedjunit



























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-15652) ArrayIndexOutOfBoundsException from AbstractLazyLoadRunMap.search















































Jesse Glick
 updated  JENKINS-15652


ArrayIndexOutOfBoundsException from AbstractLazyLoadRunMap.search
















Change By:


Jesse Glick
(09/Jul/13 9:34 PM)




Labels:


exceptionlts
1.509.2
-
candidate
fixedexception



























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-17728) NPE from MatrixConfiguration.newBuild















































Jesse Glick
 updated  JENKINS-17728


NPE from MatrixConfiguration.newBuild
















Change By:


Jesse Glick
(09/Jul/13 9:33 PM)




Labels:


exceptionlts
1.509.2
-
candidate
fixedexception
matrix



























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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session















































Jesse Glick
 updated  JENKINS-17684


Dashboard web pages dont render correctly in Chrome because of bad cache/session
















Change By:


Jesse Glick
(09/Jul/13 9:34 PM)




Labels:


lts
1.509.2
-
candidate
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-17724) /about no longer shows third-party licenses















































Jesse Glick
 updated  JENKINS-17724


/about no longer shows third-party licenses
















Change By:


Jesse Glick
(09/Jul/13 9:34 PM)




Labels:


lts
1.509.2
-
candidate
fixed
regression



























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-5408) Quoting Issue with JDK Installer with Windows Slave















































Jesse Glick
 updated  JENKINS-5408


Quoting Issue with JDK Installer with Windows Slave
















Change By:


Jesse Glick
(09/Jul/13 9:34 PM)




Labels:


1.509.2-fixed



























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







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

[JIRA] [maven] (JENKINS-17402) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact















































Jesse Glick
 updated  JENKINS-17402


Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact
















Change By:


Jesse Glick
(09/Jul/13 9:34 PM)




Labels:


lts
1.509.2
-
candidate
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-18427) parameter description don't use MarkupFormatter















































Jesse Glick
 updated  JENKINS-18427


parameter description dont use MarkupFormatter
















Change By:


Jesse Glick
(09/Jul/13 9:40 PM)




Labels:


lts-candidate
security



























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] [jobconfighistory] (JENKINS-16793) badges which appear in the build history, needs to be optional

2013-07-09 Thread iamhell...@gmail.com (JIRA)
















































George Kinlay
 closed  JENKINS-16793 as Fixed


badges which appear in the build history, needs to be optional
















Thanks 





Change By:


George Kinlay
(09/Jul/13 10:10 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-18678) Builds disappear from build history in LTS 1.509.2













































 
Martin dAnjou
 edited a comment on  JENKINS-18678


Builds disappear from build history in LTS 1.509.2
















I am observing that the Jenkins GUI only shows the 2 most recent builds in the build history. I am up to build 16, and Jenkins only shows builds 15 and 16 in the build history.



























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-18678) Builds disappear from build history in LTS 1.509.2