[JIRA] (JENKINS-16199) Jenkins crushes java
Roman Sergeev created JENKINS-16199 Jenkins crushes java Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Java.log, OpenJDKLog Components: core Created: 26/Dec/12 8:46 AM Description: With some period of time Jenkins start crushes Java machine. It's happens 2-10 minutes after start. I've tried: 1. Run Jenkins from Tomcat 5 2. Like a sudo daemon 3. Like a simple java app 4. version 1.492, 1.494 5. No any additional plugins I've tried use 1. Sun Java Linux safephone_development3 2.6.18-308.11.1.el5 #1 SMP Tue Jul 10 08:48:43 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux 2. Open JDK java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.10) (rhel-1.28.1.10.10.el5_8-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) I attached some logs that I've could get. About configure Jenkins: I have master on CentOS, and two slaves on Win and Mac. And i have 12 configured projects. But only 1 executor on each node. No any entries in /var/log/messages, dmesg. It's just crushes java and it all. I saw a few topics with the same problems but no one says what it is and how fix it. Please help me. Environment: uname -a Linux xx 2.6.18-308.11.1.el5 #1 SMP Tue Jul 10 08:48:43 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux CentOS 5.8, 2 CPU, 2 GB, swap 1 GB. Project: Jenkins Priority: Critical Reporter: Roman Sergeev This message is automatically generated by JIRA. 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-16042) NullPointer when collecting successful results
Alexandre MAIS commented on JENKINS-16042 NullPointer when collecting successful results I have the same issue with 1.7 version of Jenkins Multijob plugin and Jenkins ver. 1.494. FATAL: null java.lang.NullPointerException at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.evaluateResult(MultiJobBuild.java:69) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.isFailure(MultiJobBuild.java:59) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:51) at hudson.model.Run.execute(Run.java:1543) at hudson.model.Run.run(Run.java:1489) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) We have a lot of jobs running in production and we receive an email each time something goes wrong. But with this problem, we receive email every time and I fear we miss a real problem. So a fix will be very much appreciated ! This message is automatically generated by JIRA. 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-16016) Global passwords are visible for matrix configuration builds
SCM/JIRA link daemon commented on JENKINS-16016 Global passwords are visible for matrix configuration builds Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java src/test/java/org/jenkinsci/plugins/envinject/EnvInjectPasswordMatrixProjectTest.java http://jenkins-ci.org/commit/envinject-plugin/00a86cfc413b4f9b3b26eb8d2bade66d8d3d3941 Log: Fix JENKINS-16016 Compare: https://github.com/jenkinsci/envinject-plugin/compare/40f6f9cd1782...00a86cfc413b This message is automatically generated by JIRA. 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-16016) Global passwords are visible for matrix configuration builds
Gregory Boissinot resolved JENKINS-16016 as Fixed Global passwords are visible for matrix configuration builds Change By: Gregory Boissinot (26/Dec/12 9:31 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
[JIRA] (JENKINS-16100) Use of variable names with . fail to resolve.
Gregory Boissinot resolved JENKINS-16100 as Wont Fix Use of variable names with . fail to resolve. As in shell scripts, environment variables with dot are not accepted Change By: Gregory Boissinot (26/Dec/12 11:22 AM) 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
[JIRA] (JENKINS-15507) Environment variables are not injected in parent matrix job
Gregory Boissinot resolved JENKINS-15507 as Fixed Environment variables are not injected in parent matrix job Available from EnvInject 1.73 Change By: Gregory Boissinot (26/Dec/12 11:36 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
[JIRA] (JENKINS-16200) Duration parameter doesn't work
Alex Vesely created JENKINS-16200 Duration parameter doesnt work Issue Type: Bug Assignee: Unassigned Components: distfork Created: 26/Dec/12 1:56 PM Description: Using Jenkins 1.495. The -d N option of dist-fork does not actually set anything. No matter what I set it to, the job reports Estimated time: N/A and shows the 'striped' progress bar. Project: Jenkins Priority: Minor Reporter: Alex Vesely This message is automatically generated by JIRA. 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-15559) Build on every online node hangs up after all jobs are complete
Alex Vesely commented on JENKINS-15559 Build on every online node hangs up after all jobs are complete Seems fine on Jenkins-1.495 that I am using now. So the bug can probably be closed, thank you. This message is automatically generated by JIRA. 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-16145) add confirmation page to reload from disk management link
Alex Vesely commented on JENKINS-16145 add confirmation page to reload from disk management link Just thought of the same thing recently. Every action that is not undo-able should have a confirmation screen. This message is automatically generated by JIRA. 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-16201) Join plugin - join job is not run
Alex Vesely created JENKINS-16201 Join plugin - join job is not run Issue Type: Bug Assignee: mdonohue Components: join Created: 26/Dec/12 2:22 PM Description: Using Jenkins 1.495. I have a standard diamond-shaped job configuration. A starts B and C in parallel, and if they both succeed, runs D (using the join plugin). At seemingly random times, D is not being run, even though B and C are both successful. When I look at the console output of B, I see: Notifying upstream build A #80 of job completion Project A still waiting for C builds to complete The console output of C is the same, vice versa: Notifying upstream build A #80 of job completion Project A still waiting for B builds to complete ... so, no sign of D running. Most of the time, however, the jobs work fine. Some additional info that may or may not be helpful: A, B and C are matrix jobs. D is not. D is run from A as a parameterized job (parameters are explicitly set). I actually have a lot of different A, B and C jobs, but only one D job, which is being called with different parameters. The D job has 'concurrent builds' enabled. This shouldn't be a race condition, as the B job takes about 30 minutes and the C job about an hour. ( I have some slave nodes connected, so the jobs are being run on different nodes. However, all matrix jobs (A, B and C) have their parent job 'tied' to the Master. Can you tell me what other information I can provide, or what experiments I can carry out to isolate the problem? Project: Jenkins Priority: Critical Reporter: Alex Vesely This message is automatically generated by JIRA. 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-16201) Join plugin - join job does not run
Alex Vesely updated JENKINS-16201 Join plugin - join job does not run Change By: Alex Vesely (26/Dec/12 2:25 PM) Summary: Joinplugin-joinjob is does notrun Description: UsingJenkins1.495.Ihaveastandarddiamond-shapedjobconfiguration.AstartsBandCinparallel,andiftheybothsucceed, runs starts D(usingthejoinplugin).Atseeminglyrandomtimes,Disnotbeingrun,eventhoughBandCarebothsuccessful.WhenIlookattheconsoleoutputofB,Isee: . NotifyingupstreambuildA#80ofjobcompletion . ProjectAstillwaitingfor[C]buildstocompleteTheconsoleoutputofCisthesame,viceversa: . NotifyingupstreambuildA#80ofjobcompletion . ProjectAstillwaitingfor[B]buildstocomplete...so,nosignofDrunning.Mostofthetime,however,thejobsworkfine.Someadditionalinfothatmayormaynotbehelpful:*A,BandCarematrixjobs.Disnot.*DisrunfromAasaparameterizedjob(parametersareexplicitlyset).*IactuallyhavealotofdifferentA,BandCjobs,butonlyoneDjob,whichisbeingcalledwithdifferentparameters.TheDjobhasconcurrentbuildsenabled. ThetimeswhenIobservetheproblemseemstomatchthetimeofmultipleconcurrentbuilds. *Thisshouldntbearacecondition,astheBjobtakesabout30minutesandtheCjobaboutanhour.(Ihavesomeslavenodesconnected,sothejobsarebeingrunondifferentnodes.However,allmatrixjobs(A,BandC)havetheirparentjobtiedtotheMaster.CanyoutellmewhatotherinformationIcanprovide,orwhatexperimentsIcancarryouttoisolatetheproblem? This message is automatically generated by JIRA. 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-16201) Join plugin - join job does not run
Alex Vesely updated JENKINS-16201 Join plugin - join job does not run Change By: Alex Vesely (26/Dec/12 2:26 PM) Description: UsingJenkins1.495.Ihaveastandarddiamond-shapedjobconfiguration.AstartsBandCinparallel,andiftheybothsucceed,startsD(usingthejoinplugin).Atseeminglyrandomtimes,Disnotbeingrun,eventhoughBandCarebothsuccessful.WhenIlookattheconsoleoutputofB,Isee:.NotifyingupstreambuildA#80ofjobcompletion.ProjectAstillwaitingfor[C]buildstocompleteTheconsoleoutputofCisthesame,viceversa:.NotifyingupstreambuildA#80ofjobcompletion.ProjectAstillwaitingfor[B]buildstocomplete...so,nosignofDrunning.Mostofthetime,however,thejobsworkfine.Someadditionalinfothatmayormaynotbehelpful:*A,BandCarematrixjobs.Disnot.*DisrunfromAasaparameterizedjob(parametersareexplicitlyset).*IactuallyhavealotofdifferentA,BandCjobs,butonlyoneDjob,whichisbeingcalledwithdifferentparameters.TheDjobhasconcurrentbuildsenabled.ThetimewhenIobservetheproblemseemstomatchthetimeofmultipleconcurrentbuilds.*Thisshouldntbearacecondition,astheBjobtakesabout30minutesandtheCjobaboutanhour. ( * Ihavesomeslavenodesconnected,sothejobsarebeingrunondifferentnodes.However,allmatrixjobs(A,BandC)havetheirparentjobtiedtotheMaster.CanyoutellmewhatotherinformationIcanprovide,orwhatexperimentsIcancarryouttoisolatetheproblem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
How to configure Jenkins to run the junit test cases.
Hi I am using ant. So could you please some one tell me how can I configure jenkins to run the junit test cases on peoridic time. Please reply to this asap. Thanks Vikas Patil -- View this message in context: http://jenkins.361315.n4.nabble.com/How-to-configure-Jenkins-to-run-the-junit-test-cases-tp4649779.html Sent from the Jenkins issues mailing list archive at Nabble.com.
[JIRA] (JENKINS-15840) Use variables in URLs
Gregory Boissinot resolved JENKINS-15840 as Wont Fix Use variables in URLs Change By: Gregory Boissinot (26/Dec/12 6:08 PM) Status: InProgress 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
[JIRA] (JENKINS-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Gregory Boissinot updated JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 Regarding the below comments, it is not an EnvInject issue. Assign to core Change By: Gregory Boissinot (26/Dec/12 6:09 PM) Assignee: GregoryBoissinot This message is automatically generated by JIRA. 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-15475) CreateProcess error=87, The parameter is incorrect
Gregory Boissinot resolved JENKINS-15475 as Cannot Reproduce CreateProcess error=87, The parameter is incorrect I'm afraid I'm closing the issue because I can't reproduce it. Please try to isolate the problem from the other plugins and raise a new issue. Change By: Gregory Boissinot (26/Dec/12 6:10 PM) Status: InProgress Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15963) EnvInject properties not consistently used for SCM
Gregory Boissinot resolved JENKINS-15963 as Wont Fix EnvInject properties not consistently used for SCM Change By: Gregory Boissinot (26/Dec/12 6:12 PM) Status: InProgress 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
[JIRA] (JENKINS-13566) EnvInject is messing around with my TEMP variable when username contains a dollar sign
Gregory Boissinot commented on JENKINS-13566 EnvInject is messing around with my TEMP variable when username contains a dollar sign @Vincent Please could you give a comment to the issue JENKINS-15761? What are your opinion? Are your ready to double your slash (back from previous state), any strong impact for you? This message is automatically generated by JIRA. 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-13566) EnvInject is messing around with my TEMP variable when username contains a dollar sign
Gregory Boissinot edited a comment on JENKINS-13566 EnvInject is messing around with my TEMP variable when username contains a dollar sign @Vincent Please could you give a comment to the issue JENKINS-15751? What are your opinion? Are your ready to double your slash (back from previous state), any strong impact for you? This message is automatically generated by JIRA. 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-15751) Cannot escape dollar sign in Windows environment
Gregory Boissinot started work on JENKINS-15751 Cannot escape dollar sign in Windows environment Change By: Gregory Boissinot (26/Dec/12 6:15 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Gregory Boissinot commented on JENKINS-14193 EnvInject doesnt pass variables defined in prebuild step if maven project is used The issue is still in progress. Not yet have been time to do the pull request to Jenkins 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-14739) EnvInject params are overwritten by default string params
Gregory Boissinot resolved JENKINS-14739 as Incomplete EnvInject params are overwritten by default string params Change By: Gregory Boissinot (26/Dec/12 6:33 PM) Status: InProgress Resolved Resolution: Incomplete This message is automatically generated by JIRA. 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-14623) EnvInject ignores changes in system configuration
Gregory Boissinot updated JENKINS-14623 EnvInject ignores changes in system configuration Change By: Gregory Boissinot (26/Dec/12 6:37 PM) Assignee: GregoryBoissinot Component/s: core Component/s: envinject This message is automatically generated by JIRA. 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-14623) EnvInject ignores changes in system configuration
Gregory Boissinot commented on JENKINS-14623 EnvInject ignores changes in system configuration Re-target to core to find if there is 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-14437) envinject fails to really set/override build parameters
Gregory Boissinot commented on JENKINS-14437 envinject fails to really set/override build parameters I'm sorry for my late reply. I reproduce the problem. I'm investigating on 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-15112) Injected Jenkins build env variables not resolved/forwarded
Gregory Boissinot commented on JENKINS-15112 Injected Jenkins build env variables not resolved/forwarded I'm sorry for my late reply. Firstly, EnvInject plugin and Artifactory plugin are independent. The main goal of EnvInject plugin is to provide the ability to inject environment variables before a SCM checkout, after a SCM checkout, at a build step and at a post build step. For each build, all injected environment variables can be retrieved through the dashboard, through a file (multiple format are available, default is txt) in the build directory in the JENKINS_HOME, by REST API (refer to the wiki plugin page). For your use cas, you are able to load your data.properties from the EnvInject plugin and keys will be exported as environment variable names. After I don't know how to integrate it with the Artifactory plugin EnvInject is for now an important plugin in the Jenkins ecosystem and it is the only way to manage properly your job environment variables. If Artifactory plugin gather environment variables before the end of the EnvInject plugin, the conclusion is: Artifactory plugin doesn't gather the right environment variables. Therefore, there are two solutions: 1) Artifactory evolves 2) Switch your job to a more suited 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-15112) Injected Jenkins build env variables not resolved/forwarded
Gregory Boissinot started work on JENKINS-15112 Injected Jenkins build env variables not resolved/forwarded Change By: Gregory Boissinot (26/Dec/12 8:28 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16202) Can't pass $BUILD_NUMBER to downstream build pipeline jobs.
Bruce Edge created JENKINS-16202 Cant pass $BUILD_NUMBER to downstream build pipeline jobs. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 27/Dec/12 12:49 AM Description: There's no mechanism to access the build number from a build done at an earlier state in the pipeline. The use case is that job 1 builds the code, job 2 in the pipeline promotes it to a repository accessible by the test targets. This job 2 needs to know the build number of the build in job 1 in order to use the copy artifacts plugin to, well, copy the artifacts. How can one chain build jobs together with no mechanism to pass parameters from one job to the next? I would think that you would want to be able to define parameters in the first job and have them be available to all downstream jobs. Environment: Linux 64 bit Ubuntu 12.04 Project: Jenkins Priority: Major Reporter: Bruce Edge This message is automatically generated by JIRA. 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-15156) Builds Disappear from Build History after Completion
Yong Guo commented on JENKINS-15156 Builds Disappear from Build History after Completion (updated) I just upgrade to 1.495, then the history goes back! This message is automatically generated by JIRA. 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-12666) Subversion fails first revision check
Sunny Leung
commented on JENKINS-12666
Subversion fails first revision check
I'm also running across this problem.
Using Jenkins to deploy a specific build by adding a repo@${revision} parameter to the SVN URL, using HEAD is fine, but using any specific revision only works when there is anon read access to the repo, which is not desirable for a private repo.
This message is automatically generated by JIRA.
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-12666) Subversion fails first revision check
sunnyl
edited a comment on JENKINS-12666
Subversion fails first revision check
I'm also running across this problem. v 1.495 WAR file.
Using Jenkins to deploy a specific build by adding a repo@${revision} parameter to the SVN URL, using HEAD is fine, but using any specific revision only works when there is anon read access to the repo, which is not desirable for a private repo.
This message is automatically generated by JIRA.
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-12666) Subversion fails first revision check
sunnyl
edited a comment on JENKINS-12666
Subversion fails first revision check
I'm also running across this problem. v 1.495 WAR file, Subversion 1.44
Using Jenkins to deploy a specific build by adding a repo@${revision} parameter to the SVN URL, using HEAD is fine, but using any specific revision only works when there is anon read access to the repo, which is not desirable for a private repo.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
