[JIRA] (JENKINS-15950) Problem committing to a repository
Yury Pukhalsky created JENKINS-15950 Problem committing to a repository Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 28/Nov/12 8:01 AM Description: I suffer from a problem when the configuration changes cannot be committed. I encounter it only when renaming jobs. In that case i need to manually remove the files on the server to enable SCM sync again. The part of a log file: Nov 28, 2012 11:55:32 AM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue SEVERE: Error while processing commit queue : Error while checking in file to scm repository Nov 28, 2012 11:55:32 AM hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles FINER: THROW hudson.plugins.scm_sync_configuration.exceptions.LoggableException: Error while checking in file to scm repository at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.processCommitsQueue(ScmSyncConfigurationBusiness.java:212) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.access$000(ScmSyncConfigurationBusiness.java:28) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:142) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:140) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Nov 28, 2012 11:55:32 AM hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles SEVERE: checkinFiles Problem during SCM commit : svn: E175002: Commit failed (details follow): svn: E175002: DELETE /svn/repo/!svn/wrk/57800346-3b01-0010-817c-3597605f57e4/ADMIN/jenkins/jobs/test_svwi failed Nov 28, 2012 11:55:32 AM hudson.plugins.scm_sync_configuration.SCMManipulator FINE: Checking in SCM files ... Nov 28, 2012 11:55:32 AM hudson.plugins.scm_sync_configuration.SCMManipulator FINE: Deleting SCM hierarchy /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs/test_svwi from SCM ... Nov 28, 2012 11:55:32 AM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness FINEST: Processing commit : Commit hudson.plugins.scm_sync_configuration.model.Commit@cd25328 : Author : Elizaveta Sheina Comment : Job GroupA_SVWI_make_dist hierarchy renamed from jobs/test_svwi to jobs/GroupA_SVWI_make_dist by sheina Changeset : A jobs/GroupA_SVWI_make_dist/ A config.xml D jobs/test_svwi/ Project: Jenkins Priority: Blocker Reporter: Yury Pukhalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14797) SVN_URL and SVN_REVISION environment variables are missing
Oresztesz Margaritisz commented on JENKINS-14797 SVN_URL and SVN_REVISION environment variables are missing It works with Subversion plug-in version 1.43. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor updated JENKINS-15128 Renaming job doesnt work with Git Change By: Frédéric Camblor (28/Nov/12 8:17 AM) Description: Thisisdueto[SCM-694|http://jira.codehaus.org/browse/SCM-694]whichhasbeenfixed.Oncereleased,weshouldalignonv1.9tofixcurrentissue Notethatbothsvnandgitrenameshavebeendeactivatedin0.0.6.1becauseofthisissue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15950) Problem committing to a repository
Frédéric Camblor closed JENKINS-15950 as Fixed Problem committing to a repository Duplicate of JENKINS-15128. Closing current issue, please, watch comment the latter one. Thanks Change By: Frédéric Camblor (28/Nov/12 8:19 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor updated JENKINS-15128 Renaming job doesnt work with Git Change By: Frédéric Camblor (28/Nov/12 8:20 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9166) SCM Sync saves previous version, not the most recent change
Frédéric Camblor commented on JENKINS-9166 SCM Sync saves previous version, not the most recent change No feedback on this issue ? Nobody tried the v0.0.6.1 ? If nothing lives here for 2 weeks, I'll close the issue, considering it fixed in 0.0.6.1. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10967) Commit message doesn't appear whereas file is commited
Frédéric Camblor commented on JENKINS-10967 Commit message doesnt appear whereas file is commited No feedback on this issue ? Nobody tried the v0.0.6.1 ? If nothing lives here for 2 weeks, I'll close the issue, considering it fixed in 0.0.6.1. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13233) Regex plus character becomes space in search and no results shown
Frédéric Camblor updated JENKINS-13233 Regex plus character becomes space in search and no results shown Change By: Frédéric Camblor (28/Nov/12 8:32 AM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13232) Exception when using Global Build Search
Frédéric Camblor closed JENKINS-13232 as Duplicate Exception when using Global Build Search Duplicate of JENKINS-13233 Change By: Frédéric Camblor (28/Nov/12 8:33 AM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14567) Add a test button to SCM Sync Configuration
Frédéric Camblor updated JENKINS-14567 Add a test button to SCM Sync Configuration Change By: Frédéric Camblor (28/Nov/12 8:35 AM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Yury Pukhalsky commented on JENKINS-15128 Renaming job doesnt work with Git I don't understand. The MSCM1.8.1 is out there for almost one month, but the restriction isn't yet lifted. Or we wait for 1.9 (i don't know what ”align” means in that case)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Yury Pukhalsky edited a comment on JENKINS-15128 Renaming job doesnt work with Git I don't understand. The MSCM1.8.1 is out there for almost one month, but the restriction isn't yet lifted. Or we wait for 1.9 (i don't know what “align” means in that case)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git If you're not happy about how fast things are done, don't hesitate to contribute... plugin is opensource. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor edited a comment on JENKINS-15128 Renaming job doesnt work with Git If you're not happy about how fast things are done, don't hesitate to contribute... plugin is opensource. Maven scm api is a dependency of scm-sync-config plugin. The latest thing to do since 1.8.1 is released, is to align scm-sync-plugin on this version, test if no regression is implied, and release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Yury Pukhalsky commented on JENKINS-15128 Renaming job doesnt work with Git No, no problem at all with how fast the things are done! At least you do it. Other problems i've reported are being ignored altogether But well, «À cheval donné on ne regarde pas la denture» = I just need to evaluate the time until it's fixed. For example, if it takes one year, i will revert back to our self-written system to store SCM config in SVN. If it takes one month, i'll tell people to stop renaming for a while. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Yury Pukhalsky edited a comment on JENKINS-15128 Renaming job doesnt work with Git No, no problem at all with how fast the things are done! At least you do it. Other problems i've reported are being ignored altogether But well, «À cheval donné on ne regarde pas la denture» = I just need to evaluate the time until it's fixed. For example, if it takes one year, i will revert back to our self-written system to store Jenkins config in SVN. If it takes one month, i'll tell people to stop renaming for a while. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11830) Uploading FPR to 360 Server with HTTPS fails
samngms updated JENKINS-11830 Uploading FPR to 360 Server with HTTPS fails Change By: samngms (28/Nov/12 10:23 AM) Summary: Erroruploading Uploading FPRto Fortify 360 ServerwithHTTPSfails This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Paul Jackson commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit If it helps to track this down, I have just started seeing this behavior on our Jenkins. When we only had one job triggered by a gerrit trigger then everything was ok. As soon as I added another job with a gerrit trigger, jobs starting executing twice. We are using Jenkins 1.491, Gerrit trigger 2.5.3, and gerrit 2.2.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15951) unable to use clearcase view which is already present. instead it is deleting that view.
Divakar Kanagaraj created JENKINS-15951 unable to use clearcase view which is already present. instead it is deleting that view. Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: clearcase, plugin Created: 28/Nov/12 10:57 AM Description: Hi Folks, unable to use the clearcase view which is already present. clearcase view: dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win location of view: \\NT64OSBLD2\vwstore_d\dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win i installed "https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin" version 1.3.11 and configured with below values. View tag: dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win but it has removed this view instead of using this. below are the information from logfile. dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win $ cleartool lsview -cview -s INFO computeChangeLogBeforeCheckout = false INFO computeChangeLogAfterCheckout = true winnt_vc100_psepro_c++ $ cleartool lsview dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win \\NT64OSBLD2\vwstore_d\dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win Removing view tag because it exists, but the view path doesn't. winnt_vc100_psepro_c++ $ cleartool rmview -force -tag dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win cleartool: Error: Unable to remove "\\NT64OSBLD2\vwstore_d\dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win": Operation not permitted. cleartool: Error: Unable to remove view "\\NT64OSBLD2\vwstore_d\dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win". FATAL: UCM ClearCase failed. exit code=1 winnt_vc100_psepro_c++ $ cleartool rmtag -view dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win winnt_vc100_psepro_c++ $ cleartool mkview -snapshot -stream ostore_7.4_int@\vobs_ostore_pvob -tag dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win -vws \\vm-ntdivakar1.bedford.progress.com\views\dynamic\dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win.vws dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win cleartool: Error: Attempt to get location information on "\\vm-ntdivakar1.bedford.progress.com\views\dynamic\dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win.vws" failed: No such file or directory. FATAL: UCM ClearCase failed. exit code=1 java.io.IOException: cleartool did not return the expected exit code. Command line="mkview -snapshot -stream ostore_7.4_int@\vobs_ostore_pvob -tag dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win -vws \\vm-ntdivakar1.bedford.progress.com\views\dynamic\dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win.vws dkanagar_ostore_7.4_psecpp.vc10.nt64.sym.win", actual exit code=1 i think if we change the environment variable "CLEARCASE_VIEWPATH" (The absolute path to the ClearCase view is available as an environment variable named CLEARCASE_VIEWPATH.), it will resolve. but there is no information to tell how to change this variable. my requirement is to use the clearcase view which is already present. let me know if you need any other information. Thank you in advance. Best Regards, Divakar Project: Jenkins Labels: plugin clearcase Priority: Blocker Reporter: Divakar Kanagaraj This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15952) Checkstyle project wont transfer all files from slave to master
Julia S.Simon created JENKINS-15952 Checkstyle project wont transfer all files from slave to master Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-core, checkstyle Created: 28/Nov/12 11:09 AM Description: I have Checkstlye static analysis plugin installed for a build of a large php codebase. It executes at the end of the build CHECKSTYLE Collecting checkstyle analysis files... CHECKSTYLE Finding all files that match the pattern source/CodeError.xml CHECKSTYLE Parsing 1 files in /var/hudson/workspace/check-static-analisys-geoffrey CHECKSTYLE Successfully parsed file /var/hudson/workspace/check-static-analisys-geoffrey/source/CodeError.xml of module with 4152 warnings. But then not all files are correctly transfered to the master, resulting in blank pages when you want to their content. In an example build, in the master folder I get 1378 files with 0 size and only 50 with actual content. Project: Jenkins Priority: Minor Reporter: Julia S.Simon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Sergey D commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 We are getting the same issue periodically on Win2008R2 64bit, jdk1.7.0_06, Jenkins 1.478. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15952) Checkstyle project wont transfer all files from slave to master
Ulli Hafner commented on JENKINS-15952 Checkstyle project wont transfer all files from slave to master Are there exceptions in the log? How is your slave connected to the master? What OS is running on your master and slave? Which Jenkins and plug-in versions are you using? Are the not transferred files random? I.e., does the next build transfer another set of files? Or the same? Is there a specific pattern in the not transferred files? Are these files checked out in your workspace folder? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13521) Missing option E-mail notification (Post-build Actions)
Ben Golding commented on JENKINS-13521 Missing option E-mail notification (Post-build Actions) Fixed for me in 0.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15575) No Post-Build Actions Are Ever Run
Ben Golding commented on JENKINS-15575 No Post-Build Actions Are Ever Run Fixed for me in 0.6 (actually JENKINS-13521 is fixed, I didn't configure any other post build action besides email) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? This issue was happening on 100% of builds for me. Since updating 0.5 to 0.6 yesterday, the exception is gone. I guess more time is needed in case this is an intermittent issue as some users are reporting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Ben Golding commented on JENKINS-15519 BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException (copy of my comment from JENKINS-13915) This issue was happening on 100% of builds for me. Since updating 0.5 to 0.6 yesterday, the exception is gone. I guess more time is needed in case this is an intermittent issue as some users are reporting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13519) Unhelpful message when job name is wrong
Ben Golding commented on JENKINS-13519 Unhelpful message when job name is wrong This is fixed in 0.6 or earlier: ERROR: Failed to run DSL Script com.cloudbees.plugins.flow.JobNotFoundException: Item some_nonexistent_job_namenot found (or isn't a job). at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13522) Missing option Restrict where this project can be run / always run on master
Ben Golding commented on JENKINS-13522 Missing option Restrict where this project can be run / always run on master Option "Restrict where this project can be run" is available in 0.6 (actually was added in some earlier version, I think). I validated this seems to work as expected using 'master' and 'some_linux_slave_hostname' and 'some_windows_slave_hostname' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12695) Upload fails when using Fortify 3.30
samngms commented on JENKINS-12695 Upload fails when using Fortify 3.30 For Fortify 3.x, we only look for 3 files fortify-common-3.x.jar wsclient-3.x.jar wsobjects-3.x.jar I have double checked, SCA 3.30 has those files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15799) loosing matrix sub builds
Thomas Reinicke updated JENKINS-15799 loosing matrix sub builds Change By: Thomas Reinicke (28/Nov/12 1:51 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14955) Wrong links created on summary on a multijob execution
Björn Pedersen commented on JENKINS-14955 Wrong links created on summary on a multijob execution I can confirm this behaviour: it only occurs if jenkins is started with --prefix=something. The links in the console output are correct. (same as https://issues.jenkins-ci.org/browse/JENKINS-14952) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15656) Java Web Start Slave Agent Terminating Connection on Mountain Lion
Michael Sica commented on JENKINS-15656 Java Web Start Slave Agent Terminating Connection on Mountain Lion I discovered my problem was the same as Fredrik's. My remote FS root was incorrect. The error messaging around this misconfiguration could be better. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15656) Java Web Start Slave Agent Terminating Connection on Mountain Lion
Michael Sica resolved JENKINS-15656 as Not A Defect Java Web Start Slave Agent Terminating Connection on Mountain Lion Change By: Michael Sica (28/Nov/12 2:56 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git I won't have time to work on scm-sync-config 'til mid-december. But after, this issue (and more generally, every critical/blocking issues) is in my short list This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15953) Build-Flow: Broken job links on console output page of a flow
Thomas Ernst created JENKINS-15953 Build-Flow: Broken job links on console output page of a flow Issue Type: Bug Assignee: Nicolas De Loof Attachments: build-flow-broken-links.png Components: build-flow Created: 28/Nov/12 3:16 PM Description: Hi guys, i've got a flow that triggers a couple of jobs. The problem is that the generated job links shown on the console output page of the flow are broken. The pattern of those links is always 127.0.0.1:8080/job/XXX and since this jenkins instance is running on a remote host, those wont work. I'm running jenkins ver. 1.492 behind an apache server with mod_proxy. Thanks for your help. Best regards Thomas Ernst Project: Jenkins Priority: Major Reporter: Thomas Ernst This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15954) [RTC Plugin] NullPointerException
bokc created JENKINS-15954 [RTC Plugin] NullPointerException Issue Type: Bug Affects Versions: current Assignee: Deluan Quintão Components: rtc Created: 28/Nov/12 3:17 PM Description: $ scm accept -u -P -d D:\Jenkins\jobs\RTC-Artemis-Main-HSQL\workspace -s "Main Artemis Dev" --flow-components -o -v -c 8244 8246 Espace de travail inchangé. FATAL: null java.lang.NullPointerException at com.deluan.jenkins.plugins.rtc.changelog.JazzChangeSet.copyItemsFrom(JazzChangeSet.java:150) at com.deluan.jenkins.plugins.rtc.JazzClient.accept(JazzClient.java:112) at com.deluan.jenkins.plugins.rtc.JazzSCM.checkout(JazzSCM.java:104) at hudson.model.AbstractProject.checkout(AbstractProject.java:1324) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1518) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: RTC V4.0.0.1 Project: Jenkins Labels: plugin scm rtc Priority: Blocker Reporter: bokc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15955) Tree query support with config.xml
Danny Staple created JENKINS-15955 Tree query support with config.xml Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 28/Nov/12 3:31 PM Description: Could an enhancement be made so that tree query can be made into the config.xml data - for example if wanting to query the scm branchspec on a selection of jobs. Project: Jenkins Priority: Minor Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15956) Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded
Liya Katz created JENKINS-15956 Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded Issue Type: Bug Assignee: Roni Licht Components: jenkins-multijob-plugin Created: 28/Nov/12 3:39 PM Environment: MultiJob version 1.7 Project: Jenkins Priority: Critical Reporter: Liya Katz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15584) [xunit] processing CppUnit-1.12.1 failed
Adoudev commented on JENKINS-15584 [xunit] processing CppUnit-1.12.1 failed Hi, Problem solved : the job uses "Set environment variables" to set PATH, and in this PATH, java 1.5.0 is specified, so it overloads java 1.6 specified on the slave... Thanks for your help, it was indeed a java version 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
[JIRA] (JENKINS-14916) Stackoverflow in annonymous mode
Karl-Heinz Marbaise commented on JENKINS-14916 Stackoverflow in annonymous mode Tested with current version 1.492 ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14916) Stackoverflow in annonymous mode
Karl-Heinz Marbaise updated JENKINS-14916 Stackoverflow in annonymous mode Change By: Karl-Heinz Marbaise (28/Nov/12 3:58 PM) Component/s: favorite 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
[JIRA] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Jesse Glick commented on JENKINS-13995 Would like the ability to disable hover-over context menus. The main problem I see with the right mouse button is discoverability: so few web apps use it that a user may never think to look for it. Also it would conflict with browser-specific functions available on links, such as opening in a new tab. That could possibly be worked around by placing the original link at the top of the context menu so you can right-click on it again for these functions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Jesse Glick commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 @allinonething: my comment about Java 7 applies to 1.483+. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
Jesse Glick commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 By the way the “remember the cause of the initialization failure…” diagnostic patch is in 1.487, so if a Java 6 user of this build (or newer) can still reproduce, please attach your log file here for analysis. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15957) All build executors permanently Dead!
Bruce Adams commented on JENKINS-15957 All build executors permanently Dead! Of course because I tried to upgrade to 1.492 which also has this problem I now cannot easily downgrade to an earlier version to see if that fixes 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
[JIRA] (JENKINS-15957) All build executors permanently Dead!
Bruce Adams updated JENKINS-15957 All build executors permanently Dead! Attached SystemInfo.html Change By: Bruce Adams (28/Nov/12 4:07 PM) Attachment: systemInfo.html Environment: lsb_release-aLSBVersion: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarchDistributorID: RedHatEnterpriseServerDescription: RedHatEnterpriseLinuxServerrelease5.8(Tikanga)Release: 5.8Codename: Tikangajava-versionjavaversion1.6.0_34Java(TM)SERuntimeEnvironment(build1.6.0_34-b04)JavaHotSpot(TM)64-BitServerVM(build20.9-b04,mixedmode) RHEL5x86_64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15957) All build executors permanently Dead!
Bruce Adams commented on JENKINS-15957 All build executors permanently Dead! lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch Distributor ID: RedHatEnterpriseServer Description: Red Hat Enterprise Linux Server release 5.8 (Tikanga) Release: 5.8 Codename: Tikanga java -version java version "1.6.0_34" Java(TM) SE Runtime Environment (build 1.6.0_34-b04) Java HotSpot(TM) 64-Bit Server VM (build 20.9-b04, mixed mode) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11461) FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
William Lichtenberger commented on JENKINS-11461 FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset This is a pretty old issue, and doesn't look like it's had any activity. I run into this error rather frequently for jobs running on slaves 5 hours. Is there a known work around? We have a work order to investigate fixing it, but that would be foolish if there's already a solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15535) Do not perform Fortify 360 uploading at all if no Project Id specified.
SCM/JIRA link daemon commented on JENKINS-15535 Do not perform Fortify 360 uploading at all if no Project Id specified. Code changed in jenkins User: samngms Path: src/main/java/org/jvnet/hudson/plugins/fortify360/FPRPublisher.java http://jenkins-ci.org/commit/fortify360-plugin/77a17d5331cd48cb3fb0aa5f507a1550906b4083 Log: Bug fix: JENKINS-15535, the plugin now only submit FPR to SSC and run the jobAssignment task if projId is larger than 0 Compare: https://github.com/jenkinsci/fortify360-plugin/compare/9139b9fb4600...77a17d5331cd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14253) Discard Old Builds does not remove builds from Matrix-Axes
Robert OBrien commented on JENKINS-14253 Discard Old Builds does not remove builds from Matrix-Axes We are also experiencing same issue. Have started using matrix builds on a few more projects now and have run out of disk space on jenkins server, which blocks any more builds running. Currently using version 1.486 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15958) hg password not set correctly when contained in the url
Martin Häcker created JENKINS-15958 hg password not set correctly when contained in the url Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gui Created: 28/Nov/12 5:06 PM Description: I've configured my build job to poll from a hg repository and build when it detected changes. This failed because the authorization was not working correctly. To reproduce: Create a new build job Set it to get it's data from a hg repository with a url of the form http://username:password/path/to/repo enable repository polling see that it doesn't work. For us the problem was that although the mercurial url contained username and password, the password did not get retained in the url in the .hg/hgrc config. i.e. it would read cat .hg/hgrc paths default = http://user@host/path/to/hg/ instead of cat .hg/hgrc paths default = http://user:password@host/path/to/hg/ Project: Jenkins Priority: Major Reporter: Martin Häcker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15959) Adding detail to the 'Fixed Warnings' screen
Nilesh Dubey created JENKINS-15959 Adding detail to the Fixed Warnings screen Issue Type: New Feature Affects Versions: current Assignee: Ulli Hafner Components: pmd Created: 28/Nov/12 5:06 PM Description: The plugin shows me number of new and fixed. For the new violations added, the plugin shows me the priority as well. But for the fix ones, it only shows me the filename and violation type that was fixed. Not the violation priority. Is there a way to get the violation priority? Also, the views for 'Added' and 'Fixed' violations is completely different. Can both the views made same? Environment: All Project: Jenkins Labels: plugin Priority: Major Reporter: Nilesh Dubey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15960) Enable Remote access API
Nilesh Dubey created JENKINS-15960 Enable Remote access API Issue Type: New Feature Affects Versions: current Assignee: peterkittreilly Components: violations Created: 28/Nov/12 5:09 PM Description: Can remote access API be enabled in the violations plugin? Project: Jenkins Labels: plugin Priority: Major Reporter: Nilesh Dubey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13287) Error on apply configuration when changing job name
Sam Giles
commented on JENKINS-13287
Error on apply configuration when changing job name
I'm seeing this with 1.466. Steps I used to reproduce:
I have one build named "xyz"
I create a new build called "xyz-temp"
I delete "xyz" using the Jenkins interface
I try to rename "xyz-temp" to "xyz" hit Apply and I get an empty pop up error box, hit "Save" and I get a Failed to Parse Form data error. And the form JSON has an empty key:
JSON={"":"xyz (Trunk Branch)\nbr/.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12372) Git automatic installation
Scott Armit commented on JENKINS-12372 Git automatic installation I don't believe the automatic installation via this Git plugin works. At least not in any way I could figure out. Given an archive of a git installation with standard subdirectories: bin lib lib64 libexec share No matter what combination of options I tried, it could never find the Git binary even though it was properly extracted. Leaving the default values of an automatic installation, uses the "Name" field as the binary. So filling in the path to binary (which by the way is hidden as soon as you select "Install automatically"), just adds subdirs to the extract path. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Petri Sirkkala commented on JENKINS-13995 Would like the ability to disable hover-over context menus. Maybe a dropdown menu could work. Place a small triangle before the link and bind mouseclick listener to it. So then it might be discovered, it would be separate from normal links and would not popup unneccessarily. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15927) pull available information from Ivy files
Matt Benson updated JENKINS-15927 pull available information from Ivy files Change By: Matt Benson (28/Nov/12 5:17 PM) Summary: ivy-report-plugin: pullavailableinformationfromIvyfiles Component/s: ivy-report Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7183) Error finding org.apache.ivy.Ivy from ArtifactoryIvySettingsConfigurator
Matt Benson updated JENKINS-7183 Error finding org.apache.ivy.Ivy from ArtifactoryIvySettingsConfigurator Change By: Matt Benson (28/Nov/12 5:31 PM) Summary: Errorfindingorg.apache. iny ivy .IvyfromArtifactoryIvySettingsConfigurator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15002) Parameterized trigger passes no parameters from Ivy Project
Matt Benson updated JENKINS-15002 Parameterized trigger passes no parameters from Ivy Project Change By: Matt Benson (28/Nov/12 5:31 PM) Summary: ParameterizedtriggerpassesnoparametersfromIvy Prioject 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
[JIRA] (JENKINS-5755) Definition of the revision for the latest strategies
Matt Benson updated JENKINS-5755 Definition of the revision for the latest strategies Change By: Matt Benson (28/Nov/12 5:33 PM) Summary: Defintion Definition oftherevisionforthelatest strategie strategies This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15603) Cannot find changelist number for arbitrary job (api/xml should list it)
SCM/JIRA link daemon commented on JENKINS-15603 Cannot find changelist number for arbitrary job (api/xml should list it) Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceTagAction.java http://jenkins-ci.org/commit/perforce-plugin/a2524426e9055fafdbc12a26ed48233b9ecf3746 Log: JENKINS-15603 attempting to fix non-working export for changenumber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15963) EnvInject properties not consistently used for SCM
Travis Vitek
created JENKINS-15963
EnvInject properties not consistently used for SCM
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Attachments:
config.xml
Components:
envinject
Created:
28/Nov/12 7:23 PM
Description:
Properties set in the job configuration can be used in the SCM configuration, but they do not appear to be applied to the 'Poll SCM' build trigger.
In our environment, we specify the Perforce 'Client View Type' as 'View Map from File', and the file name depends on project parameters. When such a build is triggered manually, the parameters are applied. Here is the the first few lines of output from the 'Console Output' for a manual build.
Started by user Travis Vitek
[EnvInject] - Loading node environment variables.
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keeping Jenkins system variables.
[EnvInject] - Keeping Jenkins build variables.
[EnvInject] - Adding build parameters as variables.
[EnvInject] - Injecting as environment variables the properties content
PROJECT_BRANCH=main
PROJECT_NAME=tools
[EnvInject] - Variables injected successfully.
[EnvInject] - Injecting contributions.
Building remotely on jayhawk in workspace /build/jenkins-slave/workspace/jenkins-test
Deleting project workspace... Read ClientSpec from: //projects/main-tools.clientspec
[jenkins-test] $ "C:\Program Files\Perforce\p4.exe" print -q //projects/main-tools.clientspec
But when the the 'Poll SCM' build trigger is used, the parameters are not applied. Here is the output of the 'Perforce Polling Log'
Started on Nov 28, 2012 11:17:51 AM
Looking for changes...
Using node: jayhawk
Read ClientSpec from: //projects/${PROJECT_BRANCH}-${PROJECT_NAME}.clientspec
[jenkins-slave] $ "C:\Program Files\Perforce\p4.exe" print -q //projects/${PROJECT_BRANCH}-${PROJECT_NAME}.clientspec
Project:
Jenkins
Priority:
Major
Reporter:
Travis Vitek
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson updated JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Change By: Andrew Erickson (28/Nov/12 7:29 PM) Summary: CVSplugin2. 0-2. 7breaksGerritTrigger(v2.5.2and2.6.0)configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15964) All configuration screens are stuck LOADING
kurt stam created JENKINS-15964 All configuration screens are stuck LOADING Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 28/Nov/12 8:16 PM Description: All configuration screen appear with a gray overlay saying "LOADING" after upgrading to the latest version - 1.492-1.1 This blocks me to change any configuration. 15:08:41.570 SyntaxError: syntax error @ /jenkins/static/4db0d85f/scripts/hudson-behavior.js:5 15:08:41.572 ReferenceError: crumb is not defined @ /jenkins/job/Auto%20intk-codev.crm.itsquote/configure:8 15:08:41.583 ReferenceError: createSearchBox is not defined @ /jenkins/job/Auto%20intk-codev.crm.itsquote/configure:8 15:08:41.587 ReferenceError: updateBuildHistory is not defined @ /jenkins/job/Auto%20intk-codev.crm.itsquote/configure:55 15:08:41.789 ReferenceError: isInsideRemovable is not defined @ /jenkins/adjuncts/4db0d85f/lib/form/hetero-list/hetero-list.js:7 15:08:41.795 ReferenceError: iota is not defined @ /jenkins/adjuncts/4db0d85f/lib/form/breadcrumb-config-outline/init.js:6 In the logs I see (similar to https://issues.jenkins-ci.org/browse/JENKINS-15940) Nov 28, 2012 2:43:56 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.tasks.Maven$DescriptorImpl.getHelpFile(Maven.java:399) at hudson.maven.MavenModuleSet$DescriptorImpl.getHelpFile(MavenModuleSet.java:1189) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at
[JIRA] (JENKINS-15965) Currently building links point to wrong downstream projects when concurent builds are active
Devin Linnington created JENKINS-15965 Currently building links point to wrong downstream projects when concurent builds are active Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 28/Nov/12 8:57 PM Description: We have a multijob job that manages a bunch of downstream jobs. All the jobs have concurrency enabled meaning they can have multiple builds going at the same time. When you look at a running multijob build, it will have links at the bottom saying what's running. However it seems if there are multiple builds running in the downstream job, the multijob build actually presents the status and the links to the last build of that downstream job, instead of the build the multijob job actually triggered. The console displays the correct build and status (saying the correct build has finished, etc). Environment: Linux, Jenkins 1.485 Project: Jenkins Labels: multi-job concurrent-build Priority: Minor Reporter: Devin Linnington This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14730) Support File Multi Extended Choice parameters
Devin Linnington commented on JENKINS-14730 Support File Multi Extended Choice parameters It would be good if the multijob plugin simply supported running phases inside of the conditional build-step plugin. https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin That would solve your issue, however if you try to do that now the multijob page looses it's nice layout. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14730) Support File Multi Extended Choice parameters
Devin Linnington updated JENKINS-14730 Support File Multi Extended Choice parameters Change By: Devin Linnington (28/Nov/12 9:00 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15966) Build flow breaks when triggering next job
j serup created JENKINS-15966 Build flow breaks when triggering next job Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 28/Nov/12 9:41 PM Description: I have recently upgraded the build flow plugin from 0.5 to 0.6. I have a build flow with multiple jobs. Now and then the build flow fails with an error (see below) when triggering the next job in the list. If I simple re-run the build flow it normally works again. I have not changed any of the jobs or experienced this before upgrading. I have not found a way to reproduce the error, it seems to happen randomly. ERROR: Failed to run DSL Script java.lang.NullPointerException: Cannot get property 'e' on null object at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:56) at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:156) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:452) at com.cloudbees.plugins.flow.JobInvocation.propertyMissing(JobInvocation.groovy:64) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaClassImpl.invokeMissingProperty(MetaClassImpl.java:752) at groovy.lang.MetaClassImpl$11.getProperty(MetaClassImpl.java:1761) at org.codehaus.groovy.runtime.callsite.GetEffectivePogoPropertySite.getProperty(GetEffectivePogoPropertySite.java:84) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at com.cloudbees.plugins.flow.JobInvocation.run(JobInvocation.groovy:48) at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:72) at sun.reflect.GeneratedMethodAccessor707.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:230) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120) at com.cloudbees.plugins.flow.FlowDelegate.build(FlowDSL.groovy:166) at com.cloudbees.plugins.flow.FlowDelegate$build.callCurrent(Unknown Source) at com.cloudbees.plugins.flow.FlowDelegate.build(FlowDSL.groovy:152) at sun.reflect.GeneratedMethodAccessor704.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:361) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141) at Script1$_run_closure1.doCall(Script1.groovy:1) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when it can't start cmd.exe to run p4.exe
Rob Petti commented on JENKINS-15904 Perforce plugin issues wrong error message when it cant start cmd.exe to run p4.exe Where are you seeing the actual error? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15967) Android Emulator Plugin no longer works with r20.0.0.3.
Jørgen Tjernø created JENKINS-15967 Android Emulator Plugin no longer works with r20.0.0.3. Issue Type: Bug Affects Versions: current Assignee: Jørgen Tjernø Components: android-emulator Created: 28/Nov/12 10:18 PM Description: The following message is being printed, and the build aborts: [android] Required Android tools not found in PATH; cannot continue Project: Jenkins Priority: Critical Reporter: Jørgen Tjernø This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Loren Keagle commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs I can confirm that removing all build history seems to stabilize the system. I noticed that I had an assortment of items in my build history. Some jobs had each build in a directory based on its build number. Some had build directories that were timestamped. Some were timestamped, but also had a symbolic link named after the build number, but pointing to a timestamp directory. I also manually deleted all of the lastBuilt and lastFailed links in the job directories. Nothing has failed since, but it sucks that I have to rebuild every job in order to turn all those little circles from gray to green again. So it seems as though there's some assumptions being made regarding the layout and naming conventions of build output directories. I don't know if it's due to a combination of plugins or the base Jenkins code not cleaning up after itself. I guess it could be related to clocks and DST, but I'm pretty sure my problems started before we jumped forward. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15964) All configuration screens are stuck LOADING
viral shah commented on JENKINS-15964 All configuration screens are stuck LOADING HI I'm facing the same problem. I'm not able to create new job as well. Is there any temporary solution to this ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15940) WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException
viral shah commented on JENKINS-15940 WARNING: Caught exception evaluating: descriptor.getHelpFile(attrs.field). Reason: java.lang.NullPointerException HI I'm facing the same problem. I'm not able to create new job as well. Is there any temporary solution to this ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15967) Android Emulator Plugin no longer works with r20.0.0.3.
Jørgen Tjernø assigned JENKINS-15967 to Christopher Orr Android Emulator Plugin no longer works with r20.0.0.3. Potential pull request to fix this: https://github.com/jenkinsci/android-emulator-plugin/pull/19 Change By: Jørgen Tjernø (29/Nov/12 12:00 AM) Assignee: JørgenTjernø ChristopherOrr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15967) Android Emulator Plugin no longer works with r20.0.0.3.
SCM/JIRA link daemon commented on JENKINS-15967 Android Emulator Plugin no longer works with r20.0.0.3. Code changed in jenkins User: Jørgen P. Tjernø Path: src/main/java/hudson/plugins/android_emulator/sdk/Tool.java src/main/java/hudson/plugins/android_emulator/util/Utils.java http://jenkins-ci.org/commit/android-emulator-plugin/04c6fedb0fa692ef903f21e502e93542019e70a3 Log: Don't look for specific emulator binaries. Only look for the main emulator binary when validating an SDK root - don't look for the emulator64-* binaries (only in r21+) and the -mips and -x86 binaries (only in r12+). This resolves JENKINS-15967. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15967) Android Emulator Plugin no longer works with r20.0.0.3.
Christopher Orr closed JENKINS-15967 as Fixed Android Emulator Plugin no longer works with r20.0.0.3. Version 2.7.1 of the plugin has been released, which includes this fix. Change By: Christopher Orr (29/Nov/12 12:27 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15968) JClouds Instance Creation template selection from list saves incorrectly
Adam Rofer created JENKINS-15968 JClouds Instance Creation template selection from list saves incorrectly Issue Type: Bug Assignee: abayer Components: jclouds Created: 29/Nov/12 1:54 AM Description: Selecting a template from list under JClouds Instance Creation: Template: "abcd-xx-xxx in cloud y-y-yy" -- saves in job's config.xml as manualTemplateNameabcd/manualTemplateName (actual a-z characters above replaced with junk a-z characters to hide identity information) Project: Jenkins Priority: Major Reporter: Adam Rofer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs
Maxfield Stewart created JENKINS-15969 Build Stats Plugin Returns so much data it hangs Issue Type: Bug Assignee: Frédéric Camblor Attachments: screen.png Components: global-build-stats, plugin Created: 29/Nov/12 1:54 AM Description: Using Global-Build-Stats 1.3 and Jenkins 1.470 I've configured about 6 graphs in our Jenkins environment. Now when clicking the global build stats link from the manage jenkins options, I get the attached screenshot. See the chrome network details in the image, what appears to be happening is the request to the following URL: http://jenkins:8080/plugin/global-build-stats/api/json?depth=2 Never stops returning data, it reaches roughly 536kb of JSON streams before the browser just hangs/crashes/gives up. The charts I have plotted are 3 build stats charts for fairly busy Continuous Integration jobs over the past 14 days (daily aggregated stats over 14 days for success/fail etc) And the same time interval for Average Build Time. The individual api's for each chart work fine if I request the specific JSON data for the chart, I get accurate and clear data. Such as: http://jenkins:8080/plugin/global-build-stats/api/json?depth=2buildStatConfigId=qTJa$m7WnHjwPakLc7PLhaer$ze*zypA Due to this issue however, I cannot configure any new charts, or remove charts. So I need two solutions. First, I need to get access to the configuration screen, which means I need a way to delete a chart configuration manually without relying on the configuration screen in Jenkins. Second, I need to know if this limitation is by design, if I've done something wrong, is this a genuine bug, can I fix this? Project: Jenkins Priority: Minor Reporter: Maxfield Stewart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12372) Git automatic installation
Scott Armit commented on JENKINS-12372 Git automatic installation Thanks wernight for the idea. However, I should've pointed out that my particular issues are on Linux, not Windows. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15970) JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action
Adam Rofer created JENKINS-15970 JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action Issue Type: Improvement Assignee: abayer Components: jclouds Created: 29/Nov/12 2:44 AM Description: Some cloud providers have limits on rate of instance creation: e.g. 2/second, 25/minute. If 3 instances are specified in JClouds Instance Creation for a build, then it will fail because it will exceed the provider's limit by trying to request 3 concurrently. Introducing a "delay between requests" (e.g. 1-10 seconds) would resolve this issue at little relative cost to the build time. NOTE: this feature could instead be added for the Cloud Instance Template in the Configure System section of Jenkins which would fix a similar issue: if multiple concurrent builds that are attached to this label are executed at the same time causes this rate to be exceeded (I think) Project: Jenkins Priority: Major Reporter: Adam Rofer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15885) Not able to any configutation changes for existing jobs and new jobs
Andrew Hendley commented on JENKINS-15885 Not able to any configutation changes for existing jobs and new jobs I have experienced this myself with older and latest Jenkins (v 1.487) using Firefox 9 (corporate limitation sorry) and was once able to clear the local machine browser cache, but this no longer seem to work anymore. Even tried disabling some of the add-ons of Firefox or white-listing the URL, but no good. I then tried using Jenkins under IE 8 (again corporate limitation and not ideal) but all is good. Not sure what is happening really, but will continue to investigate (when I can). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15885) Not able to any configutation changes for existing jobs and new jobs
Andrew Hendley edited a comment on JENKINS-15885 Not able to any configutation changes for existing jobs and new jobs I have experienced this myself with older and more recent Jenkins (v 1.487) using Firefox 9 (corporate limitation sorry) and was once able to clear the local machine browser cache, but this no longer seem to work anymore. Even tried disabling some of the add-ons of Firefox or white-listing the URL, but no good. I then tried using Jenkins under IE 8 (again corporate limitation and not ideal) but all is good. Not sure what is happening really, but will continue to investigate (when I can). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when it can't start cmd.exe to run p4.exe
Markus Strand
commented on JENKINS-15904
Perforce plugin issues wrong error message when it cant start cmd.exe to run p4.exe
The error handling completely hides certain types of errors, and just says 'No output for...'
src\main\java\com\tek42\perforce\parse\AbstractPerforceTemplate.java:
throw new PerforceException("No output for: " + debugCmd);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12732) Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs
hiteswar kumar commented on JENKINS-12732 Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs can share update for this issue? i am also facing this isuee- copying .git objects from sub project to main project . jenkins lTS:1.447.2 copy artifect plugin:1.24 at main project configure: trigger builds on other project -sub_project copy artifact from another project project name sub_project, which build-Copy from workspace of latest completed build enable Flatten directories at sub projectsub_project: Build-execute shell repo init and repo sync git repository stacktrack at main project is below for your reference: Build step 'Trigger/call builds on other projects' changed build result to SUCCESS ERROR: Failed to copy artifacts from sub project: ** hudson.util.IOException2: Failed to copy /home/hudsonslave/root/workspace/sub_project/.repo/manifests/.git/objects/pack/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx to /home/hudsonslave/root/workspace/sub_project/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:97) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:248) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:215) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:697) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.io.FileNotFoundException: /home/hudsonslave/root/workspace/EXPERIMENTAL_22709304_trigger_from_SELD_check/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:194) at java.io.FileOutputStream.init(FileOutputStream.java:145) at hudson.FilePath$26.call(FilePath.java:1350) at hudson.FilePath$26.call(FilePath.java:1346) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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 'Copy artifacts from another project' 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
[JIRA] (JENKINS-12732) Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs
hiteswar kumar edited a comment on JENKINS-12732 Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs can share update for this issue? i am also facing this isuee- copying .git objects from sub project to main project . jenkins lTS:1.447.2 copy artifect plugin:1.24 at main project configure: trigger builds on other project -sub_project copy artifact from another project project name sub_project, which build-Copy from workspace of latest completed build enable Flatten directories at sub projectsub_project: Build-execute shell repo init and repo sync git repository stacktrack at main project is below for your reference: Build step 'Trigger/call builds on other projects' changed build result to SUCCESS ERROR: Failed to copy artifacts from sub project: ** hudson.util.IOException2: Failed to copy /home/hudsonslave/root/workspace/sub_project/.repo/manifests/.git/objects/pack/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx to /home/hudsonslave/root/workspace/sub_project/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:97) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:248) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:215) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:697) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.io.FileNotFoundException: /home/hudsonslave/root/workspace/main_project/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:194) at java.io.FileOutputStream.init(FileOutputStream.java:145) at hudson.FilePath$26.call(FilePath.java:1350) at hudson.FilePath$26.call(FilePath.java:1346) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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 'Copy artifacts from another project' 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
[JIRA] (JENKINS-12732) Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs
hiteswar kumar edited a comment on JENKINS-12732 Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs can share update for this issue? i am also facing this isuee- copying .git objects from sub project to main project . jenkins lTS:1.447.2 copy artifect plugin:1.24 at main project configure: trigger builds on other project -sub_project copy artifact from another project project name sub_project, which build-Copy from workspace of latest completed build enable Flatten directories at sub projectsub_project: Build-execute shell repo init and repo sync git repository stacktrack at main project is below for your reference: Build step 'Trigger/call builds on other projects' changed build result to SUCCESS ERROR: Failed to copy artifacts from sub project: ** hudson.util.IOException2: Failed to copy /home/hudsonslave/root/workspace/sub_project/.repo/manifests/.git/objects/pack/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx to /home/hudsonslave/root/workspace/main_project/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:97) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:248) at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:215) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:697) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:467) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Caused by: java.io.FileNotFoundException: /home/hudsonslave/root/workspace/main_project/pack-c5eb0a5b960078895187994136dfb4513c1878c4.idx (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:194) at java.io.FileOutputStream.init(FileOutputStream.java:145) at hudson.FilePath$26.call(FilePath.java:1350) at hudson.FilePath$26.call(FilePath.java:1346) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 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 'Copy artifacts from another project' 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
