Details

    • Type: Task
    • Status: Done
    • Resolution: Done
    • Affects Version/s: trunk
    • Fix Version/s: None
    • Component/s: Other

      Description

      CI has been disabled in the trunk for quite some time now due to problems running zookeeper under CI. While those problems have been resolved within the QUADS_QUERY_BRANCH, zookeeper processes are not properly terminated in CI for the trunk. This leads to instability in the trunk for CI.

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        I am enabling CI in the trunk by disabling the service start/stop logic in build.xml and commenting out the logic to run the CI tests for services having a dependency on zookeeper and jini.

        Show
        bryanthompson bryanthompson added a comment - I am enabling CI in the trunk by disabling the service start/stop logic in build.xml and commenting out the logic to run the CI tests for services having a dependency on zookeeper and jini.
        Hide
        bryanthompson bryanthompson added a comment -

        CI is looking good for the trunk. There are a few (4) well known tests which experience spurious failures, but everthing else is fine. However, CI results are not being propagated to http://www.bigdata.com/hudson/lastSuccessful/report/index.html. I am looking into this now. It could be that builds on CI nodes other than the master are not propagated correctly or that rsync is not being invoked correctly for the trunk.

        Show
        bryanthompson bryanthompson added a comment - CI is looking good for the trunk. There are a few (4) well known tests which experience spurious failures, but everthing else is fine. However, CI results are not being propagated to http://www.bigdata.com/hudson/lastSuccessful/report/index.html . I am looking into this now. It could be that builds on CI nodes other than the master are not propagated correctly or that rsync is not being invoked correctly for the trunk.
        Hide
        bryanthompson bryanthompson added a comment -

        Ok. CI was not invoking rsync, which has been fixed, and the URL for the CI trunk builds has changed. It is now [1]. I have updated the blog to point at the correct CI trunk builds as well and changed the label on the blog to reflect the Hudson / Jenkins debate.

        I have also enabled the javadoc builds for the trunk. I still need to verify that those are propagated correctly.

        [1] http://www.bigdata.com/hudson-trunk/lastSuccessful/archive/trunk/ant-build/classes/test/test-results/report/index.html

        Show
        bryanthompson bryanthompson added a comment - Ok. CI was not invoking rsync, which has been fixed, and the URL for the CI trunk builds has changed. It is now [1] . I have updated the blog to point at the correct CI trunk builds as well and changed the label on the blog to reflect the Hudson / Jenkins debate. I have also enabled the javadoc builds for the trunk. I still need to verify that those are propagated correctly. [1] http://www.bigdata.com/hudson-trunk/lastSuccessful/archive/trunk/ant-build/classes/test/test-results/report/index.html

          People

          • Assignee:
            bryanthompson bryanthompson
            Reporter:
            bryanthompson bryanthompson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: