[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Greg BOUGEARD commented on JENKINS-26582 ISE from RunMap.put after reloading config Yep, we're using a freestyle project with a matrix 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26582) ISE from RunMap.put after reloading config
Greg BOUGEARD commented on JENKINS-26582 ISE from RunMap.put after reloading config Hi, we have the following stacktrace after updating a 1.596 version to 1.605 (and 1.606) : Mar 25, 2015 12:57:18 PM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: /var/lib/jenkins/jobs/service-mysql-migrations_master/configurations/axis-BASE_TAG/prod/builds/218 already existed; will not overwite with service-mysql-migrations_master/BASE_TAG=prod #218 at hudson.model.RunMap.put(RunMap.java:187) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Greg BOUGEARD edited a comment on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Do you think it's a different issue? Mar 25, 2015 12:57:18 PM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: /var/lib/jenkins/jobs/service-mysql-migrations_master/configurations/axis-BASE_TAG/prod/builds/218 already existed; will not overwite with service-mysql-migrations_master/BASE_TAG=prod #218 at hudson.model.RunMap.put(RunMap.java:187) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Greg BOUGEARD edited a comment on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Do you think it's a different issue? Mar 25, 2015 12:57:18 PM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: /var/lib/jenkins/jobs/service-mysql-migrations_master/configurations/axis-BASE_TAG/prod/builds/218 already existed; will not overwite with service-mysql-migrations_master/BASE_TAG=prod #218 at hudson.model.RunMap.put(RunMap.java:187) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Greg BOUGEARD edited a comment on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Do you think it's a different issue? ``` Mar 25, 2015 12:57:18 PM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: /var/lib/jenkins/jobs/service-mysql-migrations_master/configurations/axis-BASE_TAG/prod/builds/218 already existed; will not overwite with service-mysql-migrations_master/BASE_TAG=prod #218 at hudson.model.RunMap.put(RunMap.java:187) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor.run(Executor.java:213) ``` This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Greg BOUGEARD commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Do you think it's a different issue? Mar 25, 2015 12:57:18 PM SEVERE hudson.model.Executor run Unexpected executor death java.lang.IllegalStateException: /var/lib/jenkins/jobs/service-mysql-migrations_master/configurations/axis-BASE_TAG/prod/builds/218 already existed; will not overwite with service-mysql-migrations_master/BASE_TAG=prod #218 at hudson.model.RunMap.put(RunMap.java:187) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor.run(Executor.java:213) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-26739) ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds
Greg BOUGEARD commented on JENKINS-26739 ISE from AbstractLazyLoadRunMap.proposeNewNumber for concurrent matrix builds Hi, we currently have this issue with 1.605 and 1.606 version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22346) jenkins cli command with key fails with - java.io.EOFException
Greg BOUGEARD commented on JENKINS-22346 jenkins cli command with key fails with - java.io.EOFException I have the same issue and there is the log I found (it used to work in 1.542 and does not anymore after updated to 1.556) : Mar 28, 2014 10:53:43 AM WARNING org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator authenticate CLI authentication failure java.io.EOFException at java.io.DataInputStream.readUnsignedShort(DataInputStream.java:340) at java.io.DataInputStream.readUTF(DataInputStream.java:589) at java.io.DataInputStream.readUTF(DataInputStream.java:564) at hudson.cli.Connection.readUTF(Connection.java:86) at hudson.cli.Connection.verifyIdentity(Connection.java:245) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:39) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null
Greg BOUGEARD
commented on JENKINS-16737
java.lang.RuntimeException: No author in changeset null
I'm using a gitjs shell script like this :
#!/bin/sh
TAG_START=$1
TAG_END=$2
function escape_chars {
sed -r -e 's/(["\\])/\\\1/g' -e 's/\t/ /g'
}
function format {
sha=$(git log -n1 --pretty=format:%h $1 | escape_chars)
message=$(git log -n1 --pretty=format:%s $1 | escape_chars)
author=$(git log -n1 --pretty=format:'%aN' $1 | escape_chars)
commit=$(git log -n1 --pretty=format:%H $1 | escape_chars)
date=$(git log -n1 --pretty=format:%ai $1 | escape_chars)
echo "{\"sha\":\"$sha\",\"message\":\"$message\",\"author\":\"$author\",\"commit\":\"$commit\",\"date\":\"$date\"},"
}
#echo "git log ${TAG_START}..${TAG_END}"
for hash in $(git rev-list ${TAG_START}..${TAG_END})
do
format $hash
done
maybe it can inspire 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
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16737) java.lang.RuntimeException: No author in changeset null
Greg BOUGEARD commented on JENKINS-16737 java.lang.RuntimeException: No author in changeset null Hi, I'm getting a quite similar error : 08/01/2014 10:00:27 Archiving artifacts 08/01/2014 10:00:27 FATAL: No author in changeset 506fc54deb5c89c43450dc60a05415198b0atree 08/01/2014 10:00:27 java.lang.RuntimeException: No author in changeset 506fc54deb5c89c43450dc60a05415198b0atree 08/01/2014 10:00:27 at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:336) 08/01/2014 10:00:27 at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:414) 08/01/2014 10:00:27 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:710) 08/01/2014 10:00:27 at hudson.model.Run.execute(Run.java:1702) 08/01/2014 10:00:27 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) 08/01/2014 10:00:27 at hudson.model.ResourceController.execute(ResourceController.java:88) 08/01/2014 10:00:27 at hudson.model.Executor.run(Executor.java:231) I have checked the git-plugin code and I think the id of the commit is not well retrieved. 506fc54deb5c89c43450dc60a05415198b0a is a valid SHA1 but the id retrieved is 506fc54deb5c89c43450dc60a05415198b0atree , so the tree suffix is too much. The issue might be in the parseCommit method or maybe it can be linked to a specific git version (like the issue of maven release plugin with git 1.8.5). I'm using : git 1.7.9.5. Jenkins GIT client plugin 1.6.0 Jenkins GIT plugin 2.0 I'm not sure about the scenario to reproduce this error but there is the git log of the commit : commit 506fc54deb5c89c43450dc60a05415198b0a Author: JENKINS Date: Wed Jan 8 01:13:06 2014 +0100 release Langs Change-Id: I157faff2efffdb369933958dfb15842f0e9c4ff7 commit f25811f05aeb812bdf4a1c2c50d251f0e088f9f5 Author: JENKINS Date: Fri Jan 3 01:12:26 2014 +0100 release Langs Change-Id: I82be648aaa25dcbc81c2ace3ac2dea91eba6d425 commit 3be79c86892135e7f0d4a40642cd2710cd7013c2 Author: JENKINS Date: Fri Dec 27 01:13:28 2013 +0100 release Langs Change-Id: I42fbc4d166161d467602f7b3c6ef6621c9512545 I don't have a Jenkins Plug-in dev ready environment so I can't go further right now. I hope the details I gave could help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15737) MultiJob plugin does not take account current parameters
Greg BOUGEARD created JENKINS-15737 MultiJob plugin does not take account current parameters Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 06/Nov/12 10:24 AM Description: since 1.6, multijob plugin does not pass current parameters to nested jobs. in 1.5 it was not possible to add in a phase job twice the same job (with different parameters), now it's fixed in 1.6 but the disability to pass current parameters is a really a show stopper for me. Project: Jenkins Priority: Critical Reporter: Greg BOUGEARD This message is automatically generated by JIRA. 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-15313) Trigger on Updated Change does not fetch the last commit
Greg BOUGEARD commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit I shoud precise I'm using gerrit 2.4.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-15313) Trigger on Updated Change does not fetch the last commit
Greg BOUGEARD commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit I made some tests : First job : Triggered on Change Merged Git config : Refspec = $GERRIT_REFSPEC , Branch to build = $GERRIT_BRANCH Second job : Triggered on Update Refs Git config : Refspec = null, branch to build = $GERRIT_REFNAME 1 test : git push bypassing code review. Second job is well triggered. It checks out the right code (I checked it on the jenkins job workspace with a git log). => Test success, that it is exactly what I expected 2 test : git push to code review then submit First job is well triggered. It DOES NOT check out the right code. (I checked it on the jenkins job workspace with a git log) In my case it's 3 commits late. Second job is triggered too (NOT EXPECTED!) but it checks out the right code. => Test failed. First job is well triggered but does not checks out the right code, second job is triggered but I did not want to. Was I wrong on some config? I can give you the parameters for each test & job if it can help 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-15313) Trigger on Updated Change does not fetch the last commit
Greg BOUGEARD commented on JENKINS-15313 Trigger on Updated Change does not fetch the last commit When I saw the 2.6.0 announcement I was happy because I was going to refactor some jobs into in a single one. But if I well understand you, I still have to have : 1 job triggered on Refs Updated (without any params) 1 job triggerd on Change Merged (without any params) 1 job manually triggerd (with REFSPEC and BRANCH params) The three jobs will do the same thing (mvn deploy), but because the trigger is different, I have to keep three jobs. (Maybe I can merge the two first ones?) This message is automatically generated by JIRA. 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-15313) Trigger on Updated Change does not fetch the last commit
Greg BOUGEARD created JENKINS-15313 Trigger on Updated Change does not fetch the last commit Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 26/Sep/12 9:14 AM Description: I made a job with the following config : parameters : GERRIT_REFSPEC default value refs/heads/release GERRIT_BRANCH default value $GERRIT_REFNAME Git plugin config : Url of repo : a right url Refspec : $GERRIT_REFSPEC Name or Repository : origin Branch specifier : origin/$GERRIT_BRANCH Gerrit Trigger config : Trigger on Change Merged , Ref Updated Dynamic config (..) (should be right) My issue is on Ref Updated trigger, the log prints it fetches the origin/release (if I pushed directly on release) but in facts it does not get the checkout the last version. eg : I updated an artifact version in a pom.xml, I push it by-passing gerrit, the refs updated triggers works and trigger my job but it does not take in account my pom.xml modification . 26/09/2012 11:08:48 Last Built Revision: Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:48 Fetching changes from 1 remote Git repository 26/09/2012 11:08:48 Fetching upstream changes from ssh://gerrit.it.int/it-lang 26/09/2012 11:08:49 Commencing build of Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:49 Checking out Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) and the git history : 26/09/2012 11:08:48 Last Built Revision: Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:48 Fetching changes from 1 remote Git repository 26/09/2012 11:08:48 Fetching upstream changes from ssh://gerrit.it.int/it-lang 26/09/2012 11:08:49 Commencing build of Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) 26/09/2012 11:08:49 Checking out Revision c436e2f4e5f92400b8011fe1579bc2e80ca11c07 (origin/release) Environment: jenkins 1.482 Gerrit Trigger 2.6.0 Project: Jenkins Priority: Major Reporter: Greg BOUGEARD This message is automatically generated by JIRA. 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-15244) Gerrit Trigger - 405 Method not allowed when a build is launched manually
Greg BOUGEARD commented on JENKINS-15244 Gerrit Trigger - 405 Method not allowed when a build is launched manually I found that when the Refs Updated trigger is used, there is no $GERRIT_BRANCH parameter but only a $GERRIT_REFNAME. As my Refs Updated triggered builds were failing too, adding a GERRIT_BRANCH parameter with default value $GERRIT_REFNAME fixed them. And to build a specific branch like origin/master, there is just to set the GERRIT_BRANCH to master and the GERRIT_REFSPEC to rfs/heads/master . This message is automatically generated by JIRA. 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-15244) Gerrit Trigger - 405 Method not allowed when a build is launched manually
Greg BOUGEARD commented on JENKINS-15244 Gerrit Trigger - 405 Method not allowed when a build is launched manually Hi, I configured the same way but I have a different fail message : 20/09/2012 11:08:48 Started by user gbougeard 20/09/2012 11:08:48 [EnvInject] - Loading node environment variables. 20/09/2012 11:08:48 Building on master in workspace /var/lib/jenkins/jobs/CI-components-ALL_BRANCHES/workspace 20/09/2012 11:08:48 Checkout:workspace / /var/lib/jenkins/jobs/CI-components-ALL_BRANCHES/workspace - hudson.remoting.LocalChannel@2bacfa90 20/09/2012 11:08:48 Using strategy: Default 20/09/2012 11:08:48 Last Built Revision: Revision 535685321e0a8183296fedb7a9feded6a5b4b206 (origin/release) 20/09/2012 11:08:48 Fetching changes from 1 remote Git repository 20/09/2012 11:08:48 Fetching upstream changes from ssh://gerrit.it.int/components 20/09/2012 11:08:49 No candidate revisions 20/09/2012 11:08:49 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. This message is automatically generated by JIRA. 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-13720) The manifest branch, file & other parameters should evaluate input parameters
Greg BOUGEARD created JENKINS-13720:
---
Summary: The manifest branch, file & other parameters should
evaluate input parameters
Key: JENKINS-13720
URL: https://issues.jenkins-ci.org/browse/JENKINS-13720
Project: Jenkins
Issue Type: Bug
Components: repo
Reporter: Greg BOUGEARD
I added a String parameter BRANCH_NAME to my job.
I'd like to use it as manifest branch manifest file and it's not evaluated when
the repo init is done :
fatal: manifest '${BRANCH_NAME}.xml' not available
fatal: manifest ${BRANCH_NAME}.xml not found
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12466) Jobs using repo plugin do not persist
[ https://issues.jenkins-ci.org/browse/JENKINS-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161887#comment-161887 ] Greg BOUGEARD commented on JENKINS-12466: - Any planned date for 1.2.1? This issue is really a show stoppper for repo plugin. > Jobs using repo plugin do not persist > - > > Key: JENKINS-12466 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12466 > Project: Jenkins > Issue Type: Bug > Components: repo >Affects Versions: current > Environment: Ubuntu 10.04, Jenkins 1.448, repo plugin 1.2 >Reporter: Senthil Natarajan >Assignee: Arnaud Héritier >Priority: Minor > > I lost a job that used the repo plugin, after restarting Jenkins. I checked > the jenkins log, and this is the error shown in the log: > Jan 18, 2012 4:43:28 PM jenkins.InitReactorRunner$1 onTaskFailed > SEVERE: Failed Loading job Manifest_Monitor > java.lang.NullPointerException > at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139) > at java.lang.Object.toString(Object.java:219) > at java.lang.String.valueOf(String.java:2826) > at java.util.Arrays.toString(Arrays.java:4071) > at > java.util.concurrent.CopyOnWriteArrayList.toString(CopyOnWriteArrayList.java:860) > at java.lang.String.valueOf(String.java:2826) > at java.lang.StringBuilder.append(StringBuilder.java:115) > at > org.jvnet.hudson.plugins.DownStreamProjectActionFactory.createFor(DownStreamProjectActionFactory.java:69) > at > hudson.model.AbstractProject.createTransientActions(AbstractProject.java:612) > at hudson.model.Project.createTransientActions(Project.java:203) > at > hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602) > at hudson.model.AbstractProject.onLoad(AbstractProject.java:272) > at hudson.model.Project.onLoad(Project.java:88) > at hudson.model.Items.load(Items.java:115) > at jenkins.model.Jenkins$14.run(Jenkins.java:2372) > at > org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$5.runTask(Jenkins.java:812) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > 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) > Jan 18, 2012 4:43:28 PM > org.jvnet.hudson.plugins.DownStreamProjectActionFactory createFor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12466) Jobs using repo plugin do not persist
[ https://issues.jenkins-ci.org/browse/JENKINS-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159743#comment-159743 ] Greg BOUGEARD commented on JENKINS-12466: - Would be nice if it could be quickly integrated because the plugin is not usable in this state. Each time my jenkins server reboot (each night) the REPO jobs are not reloaded. > Jobs using repo plugin do not persist > - > > Key: JENKINS-12466 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12466 > Project: Jenkins > Issue Type: Bug > Components: repo >Affects Versions: current > Environment: Ubuntu 10.04, Jenkins 1.448, repo plugin 1.2 >Reporter: Senthil Natarajan >Priority: Minor > > I lost a job that used the repo plugin, after restarting Jenkins. I checked > the jenkins log, and this is the error shown in the log: > Jan 18, 2012 4:43:28 PM jenkins.InitReactorRunner$1 onTaskFailed > SEVERE: Failed Loading job Manifest_Monitor > java.lang.NullPointerException > at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139) > at java.lang.Object.toString(Object.java:219) > at java.lang.String.valueOf(String.java:2826) > at java.util.Arrays.toString(Arrays.java:4071) > at > java.util.concurrent.CopyOnWriteArrayList.toString(CopyOnWriteArrayList.java:860) > at java.lang.String.valueOf(String.java:2826) > at java.lang.StringBuilder.append(StringBuilder.java:115) > at > org.jvnet.hudson.plugins.DownStreamProjectActionFactory.createFor(DownStreamProjectActionFactory.java:69) > at > hudson.model.AbstractProject.createTransientActions(AbstractProject.java:612) > at hudson.model.Project.createTransientActions(Project.java:203) > at > hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602) > at hudson.model.AbstractProject.onLoad(AbstractProject.java:272) > at hudson.model.Project.onLoad(Project.java:88) > at hudson.model.Items.load(Items.java:115) > at jenkins.model.Jenkins$14.run(Jenkins.java:2372) > at > org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$5.runTask(Jenkins.java:812) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > 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) > Jan 18, 2012 4:43:28 PM > org.jvnet.hudson.plugins.DownStreamProjectActionFactory createFor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12466) Jobs using repo plugin do not persist
[ https://issues.jenkins-ci.org/browse/JENKINS-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159329#comment-159329 ] Greg BOUGEARD commented on JENKINS-12466: - I made a job using Repo plugin and I changed it ot use Git instead. I have the same exception : Feb 20 09:34:25 jenkins.it.int s_src@jenkins jenkins: SEVERE: Failed Loading job REPO-NEW-US Feb 20 09:34:25 jenkins.it.int s_src@jenkins jenkins: java.lang.NullPointerException Feb 20 09:34:25 jenkins.it.int s_src@jenkins jenkins: #011at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139) > Jobs using repo plugin do not persist > - > > Key: JENKINS-12466 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12466 > Project: Jenkins > Issue Type: Bug > Components: repo >Affects Versions: current > Environment: Ubuntu 10.04, Jenkins 1.448, repo plugin 1.2 >Reporter: Senthil Natarajan >Priority: Minor > > I lost a job that used the repo plugin, after restarting Jenkins. I checked > the jenkins log, and this is the error shown in the log: > Jan 18, 2012 4:43:28 PM jenkins.InitReactorRunner$1 onTaskFailed > SEVERE: Failed Loading job Manifest_Monitor > java.lang.NullPointerException > at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139) > at java.lang.Object.toString(Object.java:219) > at java.lang.String.valueOf(String.java:2826) > at java.util.Arrays.toString(Arrays.java:4071) > at > java.util.concurrent.CopyOnWriteArrayList.toString(CopyOnWriteArrayList.java:860) > at java.lang.String.valueOf(String.java:2826) > at java.lang.StringBuilder.append(StringBuilder.java:115) > at > org.jvnet.hudson.plugins.DownStreamProjectActionFactory.createFor(DownStreamProjectActionFactory.java:69) > at > hudson.model.AbstractProject.createTransientActions(AbstractProject.java:612) > at hudson.model.Project.createTransientActions(Project.java:203) > at > hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602) > at hudson.model.AbstractProject.onLoad(AbstractProject.java:272) > at hudson.model.Project.onLoad(Project.java:88) > at hudson.model.Items.load(Items.java:115) > at jenkins.model.Jenkins$14.run(Jenkins.java:2372) > at > org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$5.runTask(Jenkins.java:812) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > 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) > Jan 18, 2012 4:43:28 PM > org.jvnet.hudson.plugins.DownStreamProjectActionFactory createFor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
