1 Reply Latest reply: Jul 7, 2010 11:39 PM by Alejandro Guizar Branched from an earlier discussion. RSS

jbpm4 hudson jobs

Sebastian Schneider Master

Hello Alejandro,

 

why are jbpm4-tomcat and jbpm4-jboss still deactivated, the same for jbpm4-enterprise? And why is jbpm4-cfg instable and parsers, upgrade and spring are marked as failed?

 

Sebastian

  • 1. Re: jbpm4 hudson jobs
    Alejandro Guizar Master

    why are jbpm4-tomcat and jbpm4-jboss still deactivated, the same for jbpm4-enterprise? And why is jbpm4-cfg instable and parsers, upgrade and spring are marked as failed?

    If you must know, the jbpm4 hudson jobs were in pretty bad shape, all red, when I started to work on them. Hence the claim they look better than ever. The enterprise, tomcat and jboss jobs all assume they can bind on localhost, which is generally not allowed in the nodes available to our Hudson installations. I've spent at least a full day trying to fix these jobs but the assumption has deep roots.

     

    Jobs jbpm-cfg, parsers and spring have been victims of temporary network failures, e.g. java.net.UnknownHostException: anonsvn.jboss.org. The spring job also had a recurrent failure in AssignmentHandlerTest that Hui Sheng fixed today.

     

    The upgrade job is just broken and I don't know why. In my view it is not critical because there are no database schema changed between 4.3 and 4.4.

     

    UPDATE: all jbpm4 hudson jobs are back to work. Check the public Hudson instance for the latest results.