Lucene - Core
  1. Lucene - Core
  2. LUCENE-2974

the hudson nightly for lucene should check out lucene by itself

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 4.0, Trunk
    • Component/s: general/build
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Currently its too easy to break the lucene-only packaging and build.

      the hudson job for lucene should check out lucene by itself, this will
      prevent it from being broken.

        Activity

        Hide
        Robert Muir added a comment -

        bulk move 3.2 -> 3.3

        Show
        Robert Muir added a comment - bulk move 3.2 -> 3.3
        Hide
        Steve Rowe added a comment -

        This issue is about excluding the top-level dev-tools/ dir from the Lucene-only nightly build checkouts, right?

        Show
        Steve Rowe added a comment - This issue is about excluding the top-level dev-tools/ dir from the Lucene-only nightly build checkouts, right?
        Hide
        Robert Muir added a comment -

        and solr and modules, too?

        Currently, when issuing releases, people want lucene to compile/javadocs/etc by itself, and the release manager has to test this (and fix any issues before creating an RC, or fix and respin). This is because the lucene src distribution is rooted at the lucene/ folder.

        So it would be better if hudson tested this continuously rather than it being on the RM?

        Show
        Robert Muir added a comment - and solr and modules, too? Currently, when issuing releases, people want lucene to compile/javadocs/etc by itself, and the release manager has to test this (and fix any issues before creating an RC, or fix and respin). This is because the lucene src distribution is rooted at the lucene/ folder. So it would be better if hudson tested this continuously rather than it being on the RM?
        Hide
        Steve Rowe added a comment -

        Currently trunk modules/ is also tested by the Jenkins nightly build. You think this should change? (If so, I guess a new build for modules/ is in order.)

        Show
        Steve Rowe added a comment - Currently trunk modules/ is also tested by the Jenkins nightly build. You think this should change? (If so, I guess a new build for modules/ is in order.)
        Hide
        Robert Muir added a comment -

        I think it should all be tested!

        But I think we should try to test what we actually release. Maybe the nightly build should even build release artifacts, untar them, and run javadocs/tests this way?

        And this is also related to the packaging issue (LUCENE-2999) !

        Show
        Robert Muir added a comment - I think it should all be tested! But I think we should try to test what we actually release. Maybe the nightly build should even build release artifacts, untar them, and run javadocs/tests this way? And this is also related to the packaging issue ( LUCENE-2999 ) !
        Hide
        Steve Rowe added a comment -

        http://builds.flonkings.com/ currently runs Lucene-only builds, but it checks out the top-level. Maybe it could simply be switched to checking out lucene/ only?

        But I think we should try to test what we actually release. Maybe the nightly build should even build release artifacts, untar them, and run javadocs/tests this way?

        This is already happening, right?

        Show
        Steve Rowe added a comment - http://builds.flonkings.com/ currently runs Lucene-only builds, but it checks out the top-level. Maybe it could simply be switched to checking out lucene/ only? But I think we should try to test what we actually release. Maybe the nightly build should even build release artifacts, untar them, and run javadocs/tests this way? This is already happening, right?
        Hide
        Robert Muir added a comment -

        There is now a jenkins task doing this actually:
        https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/
        and https://builds.apache.org/job/Lucene-Solr-SmokeRelease-4.x/

        these build actual releases, and run the smoketester against them.

        So my concerns about it being too easy to break packaging are resolved.

        Show
        Robert Muir added a comment - There is now a jenkins task doing this actually: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/ and https://builds.apache.org/job/Lucene-Solr-SmokeRelease-4.x/ these build actual releases, and run the smoketester against them. So my concerns about it being too easy to break packaging are resolved.
        Hide
        Robert Muir added a comment -

        Fixed in LUCENE-4295

        Show
        Robert Muir added a comment - Fixed in LUCENE-4295
        Hide
        Uwe Schindler added a comment -

        Closed after release.

        Show
        Uwe Schindler added a comment - Closed after release.

          People

          • Assignee:
            Unassigned
            Reporter:
            Robert Muir
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development