I see this at the end of my job logs: [ci-game] evaluating rule: Build result [ci-game] evaluating rule: Increased number of failed tests [ci-game] evaluating rule: Increased number of passed tests [ci-game] evaluating rule: Decreased number of failed tests [ci-game] evaluating rule: Decreased number of passed tests [ci-game] evaluating rule: Open HIGH priority tasks [ci-game] evaluating rule: Open NORMAL priority tasks [ci-game] evaluating rule: Open LOW priority tasks [ci-game] evaluating rule: PMD violation [ci-game] evaluating rule: pylint violation [ci-game] evaluating rule: CPD violation [ci-game] evaluating rule: Checkstyle violation [ci-game] evaluating rule: FindBugs violation [ci-game] evaluating rule: FXCop violation [ci-game] evaluating rule: Simian violation [ci-game] evaluating rule: StyleCop violation [ci-game] evaluating rule: HIGH priority PMD warnings [ci-game] evaluating rule: NORMAL priority PMD warnings [ci-game] evaluating rule: LOW priority PMD warnings [ci-game] evaluating rule: New HIGH priority Findbugs warnings [ci-game] evaluating rule: New NORMAL priority Findbugs warnings [ci-game] evaluating rule: New LOW priority Findbugs warnings [ci-game] evaluating rule: Fixed HIGH priority Findbugs warnings [ci-game] evaluating rule: Fixed NORMAL priority Findbugs warnings [ci-game] evaluating rule: Fixed LOW priority Findbugs warnings [ci-game] evaluating rule: Changed number of compiler warnings [ci-game] evaluating rule: Changed number of checkstyle warnings Finished: SUCCESS
But it never assigns a score. Well, the only time is assigns a score is when someone breaks the build - other than that I never see the line "[ci-game] scored: 1.0". I also checked the server logs and the only message I see during a build is this: [#|2012-06-22T08:15:49.766-0400|INFO|glassfish3.1.2|hudson.model.Run|_ThreadID=26;_ThreadName=Thread-2;|PCS Master #102 main build action completed: SUCCESS|#] Probably unrelated, but I'm seeing a lot of these when I navigate around the jenkins web pages: [#|2012-06-22T08:19:48.988-0400|WARNING|glassfish3.1.2|hudson.ExpressionFactory2$JexlExpression|_ThreadID=22;_ThreadName=Thread-2;|Caught exception evaluating: job.buildHealth. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException --Ryan On Friday, 22 June 2012 02:41:10 UTC-4, Ulli Hafner wrote: > > On 06/22/2012 04:00 AM, RShoemaker wrote: > > I just installed Jenkins 1.466 and ci-game 1.18. All the other plugins I > installed are more recent than what's listed in the requirements, but every > build says it's worth 0 points and that there were no players. I > configured my job to run all the plugins (mvn install checkstyle:checkstyle > pmd:pmd findbugs:findbugs) and publish all the results. I include ci-game > as a post-build action. The job is currently setup to poll our git repo > and it only builds when it notices changes. Jenkins publishes the changes > and shows who committed them, so it seems like ci-game should have that > info as well. The project is a multi-module maven project. > > I'm assuming user error on my part - any suggestions? > > Is there a message from the plug-in in the console log of your job? This > is a typical output in our jobs: > > *21:48:03* [ci-game] evaluating rule: Build result*21:48:03* [ci-game] > scored: 1.0*21:48:03* [ci-game] evaluating rule: Increased number of failed > tests*21:48:03* [ci-game] evaluating rule: Increased number of passed > tests*21:48:03* [ci-game] evaluating rule: Decreased number of failed > tests*21:48:03* [ci-game] evaluating rule: Decreased number of passed > tests*21:48:03* [ci-game] evaluating rule: Open HIGH priority > tasks*21:48:03* [ci-game] evaluating rule: Open NORMAL priority > tasks*21:48:03* [ci-game] evaluating rule: Open LOW priority tasks*21:48:03* > [ci-game] evaluating rule: HIGH priority PMD warnings*21:48:03* [ci-game] > evaluating rule: NORMAL priority PMD warnings*21:48:03* [ci-game] evaluating > rule: LOW priority PMD warnings*21:48:03* [ci-game] evaluating rule: New > HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New > NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New > LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Changed > number of compiler warnings*21:48:03* [ci-game] evaluating rule: Changed > number of checkstyle warnings* > Ulli* > > > On Friday, 22 June 2012 02:41:10 UTC-4, Ulli Hafner wrote: > > On 06/22/2012 04:00 AM, RShoemaker wrote: > > I just installed Jenkins 1.466 and ci-game 1.18. All the other plugins I > installed are more recent than what's listed in the requirements, but every > build says it's worth 0 points and that there were no players. I > configured my job to run all the plugins (mvn install checkstyle:checkstyle > pmd:pmd findbugs:findbugs) and publish all the results. I include ci-game > as a post-build action. The job is currently setup to poll our git repo > and it only builds when it notices changes. Jenkins publishes the changes > and shows who committed them, so it seems like ci-game should have that > info as well. The project is a multi-module maven project. > > I'm assuming user error on my part - any suggestions? > > Is there a message from the plug-in in the console log of your job? This > is a typical output in our jobs: > > *21:48:03* [ci-game] evaluating rule: Build result*21:48:03* [ci-game] > scored: 1.0*21:48:03* [ci-game] evaluating rule: Increased number of failed > tests*21:48:03* [ci-game] evaluating rule: Increased number of passed > tests*21:48:03* [ci-game] evaluating rule: Decreased number of failed > tests*21:48:03* [ci-game] evaluating rule: Decreased number of passed > tests*21:48:03* [ci-game] evaluating rule: Open HIGH priority > tasks*21:48:03* [ci-game] evaluating rule: Open NORMAL priority > tasks*21:48:03* [ci-game] evaluating rule: Open LOW priority tasks*21:48:03* > [ci-game] evaluating rule: HIGH priority PMD warnings*21:48:03* [ci-game] > evaluating rule: NORMAL priority PMD warnings*21:48:03* [ci-game] evaluating > rule: LOW priority PMD warnings*21:48:03* [ci-game] evaluating rule: New > HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New > NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New > LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Changed > number of compiler warnings*21:48:03* [ci-game] evaluating rule: Changed > number of checkstyle warnings* > Ulli* > > > On Friday, 22 June 2012 02:41:10 UTC-4, Ulli Hafner wrote: > > On 06/22/2012 04:00 AM, RShoemaker wrote: > > I just installed Jenkins 1.466 and ci-game 1.18. All the other plugins I > installed are more recent than what's listed in the requirements, but every > build says it's worth 0 points and that there were no players. I > configured my job to run all the plugins (mvn install checkstyle:checkstyle > pmd:pmd findbugs:findbugs) and publish all the results. I include ci-game > as a post-build action. The job is currently setup to poll our git repo > and it only builds when it notices changes. Jenkins publishes the changes > and shows who committed them, so it seems like ci-game should have that > info as well. The project is a multi-module maven project. > > I'm assuming user error on my part - any suggestions? > > Is there a message from the plug-in in the console log of your job? This > is a typical output in our jobs: > > *21:48:03* [ci-game] evaluating rule: Build result*21:48:03* [ci-game] > scored: 1.0*21:48:03* [ci-game] evaluating rule: Increased number of failed > tests*21:48:03* [ci-game] evaluating rule: Increased number of passed > tests*21:48:03* [ci-game] evaluating rule: Decreased number of failed > tests*21:48:03* [ci-game] evaluating rule: Decreased number of passed > tests*21:48:03* [ci-game] evaluating rule: Open HIGH priority > tasks*21:48:03* [ci-game] evaluating rule: Open NORMAL priority > tasks*21:48:03* [ci-game] evaluating rule: Open LOW priority tasks*21:48:03* > [ci-game] evaluating rule: HIGH priority PMD warnings*21:48:03* [ci-game] > evaluating rule: NORMAL priority PMD warnings*21:48:03* [ci-game] evaluating > rule: LOW priority PMD warnings*21:48:03* [ci-game] evaluating rule: New > HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New > NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: New > LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > HIGH priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > NORMAL priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Fixed > LOW priority Findbugs warnings*21:48:03* [ci-game] evaluating rule: Changed > number of compiler warnings*21:48:03* [ci-game] evaluating rule: Changed > number of checkstyle warnings* > Ulli* > > >
