Details

    • Type: Task Task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Testing
    • Labels:
      None

      Description

      Use this issue to record changes to the Hudson continuous environment setup at http://hudson.zones.apache.org/hudson/view/Sling/

        Issue Links

          Activity

          Hide
          Robert Munteanu added a comment -

          Tried to cut down the number of spurious builds by updating the Ignored Patterns for the sling-trunk-1.

          {6,7}

          builds to be

          /trunk/tooling/ide/.*
          /trunk/contrib/.*
          /trunk/samples/.*

          The previous exclusions did not work.

          Show
          Robert Munteanu added a comment - Tried to cut down the number of spurious builds by updating the Ignored Patterns for the sling-trunk-1. {6,7} builds to be /trunk/tooling/ide/.* /trunk/contrib/.* /trunk/samples/.* The previous exclusions did not work.
          Hide
          Robert Munteanu added a comment -

          Disabled tests in the sling-ide-1.6 build since most of them require an X server available and fail the build.

          Show
          Robert Munteanu added a comment - Disabled tests in the sling-ide-1.6 build since most of them require an X server available and fail the build.
          Hide
          Antonio Sanso added a comment -

          I am out of office, back on June 22.

          regards

          antonio

          Show
          Antonio Sanso added a comment - I am out of office, back on June 22. regards antonio
          Hide
          Robert Munteanu added a comment -

          Updated sling-ide-1.6 build

          • Checkout the tooling/ide directory straightaway, since we no longer need to build the tooling bundle
          • Remove the extra step to build the tooling bundle
          • Increase timeout to 15 minutes, to account for extra tests
          Show
          Robert Munteanu added a comment - Updated sling-ide-1.6 build Checkout the tooling/ide directory straightaway, since we no longer need to build the tooling bundle Remove the extra step to build the tooling bundle Increase timeout to 15 minutes, to account for extra tests
          Hide
          Robert Munteanu added a comment -

          Updated all Sling jobs to use Maven 3.0.5 . This seems to fix SVN polling for now ( see INFRA-7536 ).

          Show
          Robert Munteanu added a comment - Updated all Sling jobs to use Maven 3.0.5 . This seems to fix SVN polling for now ( see INFRA-7536 ).
          Hide
          Robert Munteanu added a comment -

          Also updated sling-contrib-1.6, sling-oak-it-1.6, sling-samples-1.6 and sling-healthcheck-1.6 to use Maven 3.x (latest ).

          Show
          Robert Munteanu added a comment - Also updated sling-contrib-1.6, sling-oak-it-1.6, sling-samples-1.6 and sling-healthcheck-1.6 to use Maven 3.x (latest ).
          Hide
          Robert Munteanu added a comment -

          Updated sling-trunk-1.6 and sling-trunk-1.7 to fix job execution. Previously, they would fail with

          FATAL: Failed to install http://archive.apache.org/dist/maven/binaries/apache-maven-3.0.4-bin.zip to /home/hudson/tools/maven/apache-maven-3.0.4

          This was previously discussed on builds@apache.org, but I don't have the link at hand.

          Show
          Robert Munteanu added a comment - Updated sling-trunk-1.6 and sling-trunk-1.7 to fix job execution. Previously, they would fail with FATAL: Failed to install http: //archive.apache.org/dist/maven/binaries/apache-maven-3.0.4-bin.zip to /home/hudson/tools/maven/apache-maven-3.0.4 This was previously discussed on builds@apache.org, but I don't have the link at hand.
          Hide
          Robert Munteanu added a comment -

          Updated sling-samples-1.6:

          • run on only the ubuntu slaves which were recently updated to OpenJDK 7 - see INFRA-6218
          • changes lifecycles phases to clean install instead of clean deploy, since we don't rely on those snapshots being deployed
          Show
          Robert Munteanu added a comment - Updated sling-samples-1.6: run on only the ubuntu slaves which were recently updated to OpenJDK 7 - see INFRA-6218 changes lifecycles phases to clean install instead of clean deploy, since we don't rely on those snapshots being deployed
          Hide
          Robert Munteanu added a comment - - edited

          Updated sling-trunk-1.6, and sling-trunk-1.7:

          • run on only the ubuntu slaves which were recently updated to OpenJDK 7 - see INFRA-6218
          • temporarily disabled the war integration tests since that module consistently ( and unexplainably ) fails the build . The jobs don't run on Buildbot either, so this should give us a baseline in terms of how jobs perform on the two CI platforms
          Show
          Robert Munteanu added a comment - - edited Updated sling-trunk-1.6, and sling-trunk-1.7: run on only the ubuntu slaves which were recently updated to OpenJDK 7 - see INFRA-6218 temporarily disabled the war integration tests since that module consistently ( and unexplainably ) fails the build . The jobs don't run on Buildbot either, so this should give us a baseline in terms of how jobs perform on the two CI platforms
          Hide
          Bertrand Delacretaz added a comment -

          As the Jenkins builds are still very flaky, I have asked for Buildbot jobs to be setup, see SLING-3234

          Show
          Bertrand Delacretaz added a comment - As the Jenkins builds are still very flaky, I have asked for Buildbot jobs to be setup, see SLING-3234
          Hide
          Bertrand Delacretaz added a comment -

          I have added info about some recent Jenkins failures to INFRA-6218 - still way too many unexplained issues for Jenkins to be of any use.

          Show
          Bertrand Delacretaz added a comment - I have added info about some recent Jenkins failures to INFRA-6218 - still way too many unexplained issues for Jenkins to be of any use.
          Hide
          Robert Munteanu added a comment -

          Updated sling-healthcheck-1.6 to use the 'clean install' goals instead of the default 'install' goal. I hope this will clear the CI failures, as the build passes locally for me, and perhaps it's picking up stale local artifacts.

          Show
          Robert Munteanu added a comment - Updated sling-healthcheck-1.6 to use the 'clean install' goals instead of the default 'install' goal. I hope this will clear the CI failures, as the build passes locally for me, and perhaps it's picking up stale local artifacts.
          Hide
          Robert Munteanu added a comment -

          Added .travis.yml file in http://svn.apache.org/viewvc?view=revision&revision=1511240 and also filed INFRA-6643 to activate the Travis hook on Github.

          Show
          Robert Munteanu added a comment - Added .travis.yml file in http://svn.apache.org/viewvc?view=revision&revision=1511240 and also filed INFRA-6643 to activate the Travis hook on Github.
          Hide
          Robert Munteanu added a comment -

          Added sling-ide-1.6 job, set to build hourly.

          Show
          Robert Munteanu added a comment - Added sling-ide-1.6 job, set to build hourly.
          Hide
          Robert Munteanu added a comment -

          Updated sling-trunk-

          {1.6,1.7}

          to ignore changes on /repos/asf/sling/trunk/contrib/tooling/ide.* , to prevent triggering builds which don't include any real changes.

          Show
          Robert Munteanu added a comment - Updated sling-trunk- {1.6,1.7} to ignore changes on /repos/asf/sling/trunk/contrib/tooling/ide.* , to prevent triggering builds which don't include any real changes.
          Hide
          Robert Munteanu added a comment -

          Updated all jobs to only build on ubuntu&&Unable to render embedded object: File ((ubuntu5)&&) not found.(ubuntu4) , since I saw spurious failures on ubuntu4 as well.

          Show
          Robert Munteanu added a comment - Updated all jobs to only build on ubuntu&& Unable to render embedded object: File ((ubuntu5)&&) not found. (ubuntu4) , since I saw spurious failures on ubuntu4 as well.
          Hide
          Robert Munteanu added a comment -

          Changed the sling-contrib-1.6 job to use install instead of deploy, since we don't depend on the deployed contrib artifacts and this speeds up the build a little.

          Show
          Robert Munteanu added a comment - Changed the sling-contrib-1.6 job to use install instead of deploy, since we don't depend on the deployed contrib artifacts and this speeds up the build a little.
          Hide
          Robert Munteanu added a comment -

          Applied the changes from the above message to sling-samples-1.6 as well, since it was affected by CI failures.

          Show
          Robert Munteanu added a comment - Applied the changes from the above message to sling-samples-1.6 as well, since it was affected by CI failures.
          Hide
          Robert Munteanu added a comment -

          Updated the sling-trunk-1.

          {6,7}

          config jobs to

          • keep latest 10 builds, to ease debugging of CI failures
          • build on ubuntu && !(ubuntu5) , since as I noted in INFRA-6218 , most CI failures seem to happen on ubuntu5
          Show
          Robert Munteanu added a comment - Updated the sling-trunk-1. {6,7} config jobs to keep latest 10 builds, to ease debugging of CI failures build on ubuntu && !(ubuntu5) , since as I noted in INFRA-6218 , most CI failures seem to happen on ubuntu5
          Hide
          Robert Munteanu added a comment -

          Disabled automatic artifact archiving for sling-contrib-1.6

          Show
          Robert Munteanu added a comment - Disabled automatic artifact archiving for sling-contrib-1.6
          Hide
          Robert Munteanu added a comment -

          Updated all sling jobs to be restricted on the ubuntu label. This currently expands to all ubuntu slaves, so we should have enough processing power. I did this because builds on solaris slaves fail, with the typical root cause being

          Caused by: java.io.IOException: error=12, Not enough space
          at java.lang.UNIXProcess.forkAndExec(Native Method)
          at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
          at java.lang.ProcessImpl.start(ProcessImpl.java:65)
          at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
          ... 41 more

          Show
          Robert Munteanu added a comment - Updated all sling jobs to be restricted on the ubuntu label. This currently expands to all ubuntu slaves, so we should have enough processing power. I did this because builds on solaris slaves fail, with the typical root cause being Caused by: java.io.IOException: error=12, Not enough space at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:53) at java.lang.ProcessImpl.start(ProcessImpl.java:65) at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) ... 41 more
          Hide
          Bertrand Delacretaz added a comment -

          The sling-trunk.1.6 and 1.7 jobs were tied to the ubuntu6 slave, I have removed this restriction to see if that helps.

          Also removed the "Sling" lock on those jobs, if they execute on different slaves it's not needed, and even on the same slave that should not be a problem.

          Show
          Bertrand Delacretaz added a comment - The sling-trunk.1.6 and 1.7 jobs were tied to the ubuntu6 slave, I have removed this restriction to see if that helps. Also removed the "Sling" lock on those jobs, if they execute on different slaves it's not needed, and even on the same slave that should not be a problem.
          Hide
          Bertrand Delacretaz added a comment -

          Done for all 4 jobs found under https://builds.apache.org/view/S-Z/view/Sling/

          Show
          Bertrand Delacretaz added a comment - Done for all 4 jobs found under https://builds.apache.org/view/S-Z/view/Sling/
          Hide
          rmuntean added a comment -

          As discussed on http://sling.markmail.org/thread/qc53zsaia2gsurhi , can someone please disable artifact archival for the Sling jobs?

          Show
          rmuntean added a comment - As discussed on http://sling.markmail.org/thread/qc53zsaia2gsurhi , can someone please disable artifact archival for the Sling jobs?
          Hide
          Bertrand Delacretaz added a comment -

          I have added a sling-trunk-1.7 job by copying the 1.6 one and setting JDK 1.7 - visible at https://builds.apache.org/view/S-Z/view/Sling/

          Show
          Bertrand Delacretaz added a comment - I have added a sling-trunk-1.7 job by copying the 1.6 one and setting JDK 1.7 - visible at https://builds.apache.org/view/S-Z/view/Sling/
          Hide
          Bertrand Delacretaz added a comment -

          The sling-trunk-1.6 build was failing since I added the new test-fragment bundle, as -PwarIntegrationTests was set, so the integrationTests profile was not enabled anymore and the new launchpad/test-fragment bundle was not built.

          I have added -PintegrationTests so that both profiles are activated, the Launchpad Testing Fragment Bundle is now correctly built.

          Show
          Bertrand Delacretaz added a comment - The sling-trunk-1.6 build was failing since I added the new test-fragment bundle, as -PwarIntegrationTests was set, so the integrationTests profile was not enabled anymore and the new launchpad/test-fragment bundle was not built. I have added -PintegrationTests so that both profiles are activated, the Launchpad Testing Fragment Bundle is now correctly built.
          Show
          Carsten Ziegeler added a comment - Done: https://builds.apache.org/view/Sling/
          Hide
          Antonio Sanso added a comment -

          somebody with the right karma might also add a global view for sling as for https://builds.apache.org/user/asanso/my-views/view/Sling/

          Show
          Antonio Sanso added a comment - somebody with the right karma might also add a global view for sling as for https://builds.apache.org/user/asanso/my-views/view/Sling/
          Hide
          Carsten Ziegeler added a comment -

          The url for the Jenkins server is: https://builds.apache.org/

          I've removed the old 1.5 trunk project, switched the samples-1.5 project to samples-1.6 and updated the Maven version to 3.0.4 for all three builds.

          Show
          Carsten Ziegeler added a comment - The url for the Jenkins server is: https://builds.apache.org/ I've removed the old 1.5 trunk project, switched the samples-1.5 project to samples-1.6 and updated the Maven version to 3.0.4 for all three builds.
          Hide
          Carsten Ziegeler added a comment -

          Switched contrib-1.5 to contrib-1.6 as we have a module requiring Java 6

          Show
          Carsten Ziegeler added a comment - Switched contrib-1.5 to contrib-1.6 as we have a module requiring Java 6
          Hide
          Carsten Ziegeler added a comment -

          Changed 1.5 contrib and samples to build with Maven 3.0.3 (it still was Maven 2.2.1)

          Show
          Carsten Ziegeler added a comment - Changed 1.5 contrib and samples to build with Maven 3.0.3 (it still was Maven 2.2.1)
          Hide
          Justin Edelson added a comment -

          with SLING-2281, we'll need a 1.7 build as well.

          Show
          Justin Edelson added a comment - with SLING-2281 , we'll need a 1.7 build as well.
          Hide
          Bertrand Delacretaz added a comment -

          Increased the timeouts on the sling-trunk-1.5 and 1.6 builds to 100 minutes (from 75 and 60 previously).

          The builds often take around an hour on ubuntu1 (haven't checked why), so if the build slave is a bit slower than usual they would often fail.

          Show
          Bertrand Delacretaz added a comment - Increased the timeouts on the sling-trunk-1.5 and 1.6 builds to 100 minutes (from 75 and 60 previously). The builds often take around an hour on ubuntu1 (haven't checked why), so if the build slave is a bit slower than usual they would often fail.
          Hide
          Bertrand Delacretaz added a comment - - edited

          Changed the sling-trunk-1.5 and 1.6 builds to use Maven 3.0.3 as we were getting this error with 2.2.1 :

          > [INFO] The projects in the reactor contain a cyclic reference: Edge between 'Vertex

          {label='org.apache.sling:org.apache.sling.commons.testing'}

          ' and 'Vertex

          {label='org.apache.sling:org.apache.sling.api'}

          ' introduces to cycle in the graph org.apache.sling:org.apache.sling.api --> org.apache.sling:org.apache.sling.commons.testing --> org.apache.sling:org.apache.sling.api

          But there's no actual cycle if you take the version numbers into account, as the API module depends on a released version of Commons Testing (SLING-2127).

          Show
          Bertrand Delacretaz added a comment - - edited Changed the sling-trunk-1.5 and 1.6 builds to use Maven 3.0.3 as we were getting this error with 2.2.1 : > [INFO] The projects in the reactor contain a cyclic reference: Edge between 'Vertex {label='org.apache.sling:org.apache.sling.commons.testing'} ' and 'Vertex {label='org.apache.sling:org.apache.sling.api'} ' introduces to cycle in the graph org.apache.sling:org.apache.sling.api --> org.apache.sling:org.apache.sling.commons.testing --> org.apache.sling:org.apache.sling.api But there's no actual cycle if you take the version numbers into account, as the API module depends on a released version of Commons Testing ( SLING-2127 ).
          Hide
          Bertrand Delacretaz added a comment -

          Added -PwarIntegrationTests to both sling-trunk-1.5 and sling-trunk-1.6 jobs.

          Show
          Bertrand Delacretaz added a comment - Added -PwarIntegrationTests to both sling-trunk-1.5 and sling-trunk-1.6 jobs.
          Hide
          Felix Meschberger added a comment -

          Disabling trying to install the bundle in the local OBR repository.xml file for the hudson builder machines
          by setting the build flag

          -DobrRepository=false

          on all builds.

          Every now and then builds have failures/problems/nusances due to the local repository.xml file on the hudson build machines being corrupt. Since we do not use those repository.xml at all, we just as well can omit filling it.

          Show
          Felix Meschberger added a comment - Disabling trying to install the bundle in the local OBR repository.xml file for the hudson builder machines by setting the build flag -DobrRepository=false on all builds. Every now and then builds have failures/problems/nusances due to the local repository.xml file on the hudson build machines being corrupt. Since we do not use those repository.xml at all, we just as well can omit filling it.
          Hide
          Bertrand Delacretaz added a comment - - edited

          Removed the https://hudson.apache.org/hudson/view/Sling/job/sling-installer-1.5/ build from Hudson, as the installer is now included in the trunk build.

          Show
          Bertrand Delacretaz added a comment - - edited Removed the https://hudson.apache.org/hudson/view/Sling/job/sling-installer-1.5/ build from Hudson, as the installer is now included in the trunk build.
          Hide
          Bertrand Delacretaz added a comment -

          Added -enableassertions to all our build jobs at http://hudson.zones.apache.org/hudson/view/Sling/ , thanks for the suggestion.

          Show
          Bertrand Delacretaz added a comment - Added -enableassertions to all our build jobs at http://hudson.zones.apache.org/hudson/view/Sling/ , thanks for the suggestion.
          Hide
          Justin Edelson added a comment -

          -enableassertions should be added to MAVEN_OPTS - see SLING-1577

          Show
          Justin Edelson added a comment - -enableassertions should be added to MAVEN_OPTS - see SLING-1577
          Hide
          Bertrand Delacretaz added a comment -

          http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/ build got stuck due to an our of PermGen error, added

          -XX:MaxPermSize=128M

          to its MAVEN_OPTS

          Show
          Bertrand Delacretaz added a comment - http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/ build got stuck due to an our of PermGen error, added -XX:MaxPermSize=128M to its MAVEN_OPTS
          Hide
          Bertrand Delacretaz added a comment -

          Added -DHttpTestBase.readyTimeoutSeconds=300 to the Maven build options of both 1.5 and 1.6 builds after implementing SLING-1439.

          Also increased memory for Maven, -Xmx512M -XX:MaxPermSize=256M for both builds, as they seemed slow lately, let's see if this helps.

          Show
          Bertrand Delacretaz added a comment - Added -DHttpTestBase.readyTimeoutSeconds=300 to the Maven build options of both 1.5 and 1.6 builds after implementing SLING-1439 . Also increased memory for Maven, -Xmx512M -XX:MaxPermSize=256M for both builds, as they seemed slow lately, let's see if this helps.
          Hide
          Bertrand Delacretaz added a comment -

          The 1.6 build was only started if the 1.5 build was successful - the problem is that this hides cases where the 1.5 build fails but the 1.6 would succeed (like SLING-1424).

          I have changed this, both builds are now triggered independently by watching svn commits hourly.

          Show
          Bertrand Delacretaz added a comment - The 1.6 build was only started if the 1.5 build was successful - the problem is that this hides cases where the 1.5 build fails but the 1.6 would succeed (like SLING-1424 ). I have changed this, both builds are now triggered independently by watching svn commits hourly.
          Hide
          Bertrand Delacretaz added a comment -

          Removed the -Dhttp.port settings from both 1.5 and 1.6 builds now that SLING-1404 selects them dynamically

          Show
          Bertrand Delacretaz added a comment - Removed the -Dhttp.port settings from both 1.5 and 1.6 builds now that SLING-1404 selects them dynamically
          Hide
          Bertrand Delacretaz added a comment -

          sling-trunk-1.5 build was failing with "out of memory error - PermGen space", I have added MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=128M" to the 1.5 build (1.6 had them already)

          Show
          Bertrand Delacretaz added a comment - sling-trunk-1.5 build was failing with "out of memory error - PermGen space", I have added MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=128M" to the 1.5 build (1.6 had them already)
          Hide
          Justin Edelson added a comment -

          Did the Port Allocator plugin get installed? I know there's some doubt that it would help, but it can't hurt (and from looking at the code, it will help)

          Show
          Justin Edelson added a comment - Did the Port Allocator plugin get installed? I know there's some doubt that it would help, but it can't hurt (and from looking at the code, it will help)
          Hide
          Bertrand Delacretaz added a comment -

          Changed the http.port number in the sling-trunk-1.5 setup to 9366, there was another port number collision.
          Might just be transient with an older execution of the same build, didn't check.

          Show
          Bertrand Delacretaz added a comment - Changed the http.port number in the sling-trunk-1.5 setup to 9366, there was another port number collision. Might just be transient with an older execution of the same build, didn't check.
          Hide
          Felix Meschberger added a comment -

          Configured following builds to use Maven 2.2.1: sling-samples-1.5, sling-contrib-1.5, sling-installer-1.5

          Show
          Felix Meschberger added a comment - Configured following builds to use Maven 2.2.1: sling-samples-1.5, sling-contrib-1.5, sling-installer-1.5
          Hide
          Felix Meschberger added a comment -

          Changed the http.port number in the sling-trunk-1.6 setup to 9364 to prevent another port number collision causing the 1.6 build to break ...

          Show
          Felix Meschberger added a comment - Changed the http.port number in the sling-trunk-1.6 setup to 9364 to prevent another port number collision causing the 1.6 build to break ...
          Hide
          Felix Meschberger added a comment -

          Another change to the sling-trunk-1.6 is required: Set MAVEN_OPTS to "-Xmx256M -XX:MaxPermSize=128M" to prevent a PermGen OutOfMemoryError during integration tests.

          Show
          Felix Meschberger added a comment - Another change to the sling-trunk-1.6 is required: Set MAVEN_OPTS to "-Xmx256M -XX:MaxPermSize=128M" to prevent a PermGen OutOfMemoryError during integration tests.
          Hide
          Felix Meschberger added a comment -

          I have switched the sling-trunk-1.[56] builds to use Maven 2.2.1.

          Now, all builds succeed again ...

          It looks like there is a problem when doing a reactor build with Maven 2.0.9 (see also SLING-1252)

          Enabled sling-trunk-1.6 build again-

          Show
          Felix Meschberger added a comment - I have switched the sling-trunk-1. [56] builds to use Maven 2.2.1. Now, all builds succeed again ... It looks like there is a problem when doing a reactor build with Maven 2.0.9 (see also SLING-1252 ) Enabled sling-trunk-1.6 build again-
          Hide
          Felix Meschberger added a comment - - edited

          The sling-trunk-1.5 is failing due to JSP Scripting build errors.

          Carsten found out, that doing "mvn clean install deploy" actualls runs the phases up to install twice and since maven does not clean up the project properties, the serviceComponents.xml file is added twice to the Service-Components header which in turn causes the second entry to be modified and flagged by bnd.

          I have modified the sling-trunk-1.5 build to just to "mvn clean deploy" and now everything runs fine – except the integration tests.

          The other builds don't have "duplicate" build phases.

          Show
          Felix Meschberger added a comment - - edited The sling-trunk-1.5 is failing due to JSP Scripting build errors. Carsten found out, that doing "mvn clean install deploy" actualls runs the phases up to install twice and since maven does not clean up the project properties, the serviceComponents.xml file is added twice to the Service-Components header which in turn causes the second entry to be modified and flagged by bnd. I have modified the sling-trunk-1.5 build to just to "mvn clean deploy" and now everything runs fine – except the integration tests. The other builds don't have "duplicate" build phases.
          Hide
          Ian Boston added a comment -

          Added deploy to the mvn clean install of the root config, so that all artifacts get deployed to the snapshot repo.

          I see the launchpad base app.jar appearing in the snapshot nexus group, but not in the repo yet, I assume there is a staging pending.

          Show
          Ian Boston added a comment - Added deploy to the mvn clean install of the root config, so that all artifacts get deployed to the snapshot repo. I see the launchpad base app.jar appearing in the snapshot nexus group, but not in the repo yet, I assume there is a staging pending.
          Hide
          Bertrand Delacretaz added a comment -

          Activated the "Abort the build if it's stuck" option (60 minutes, fail the build) on all Sling build projects to avoid hogging up build instances if our builds get stuck, which seems to happen if the selected port is unavailable.

          Show
          Bertrand Delacretaz added a comment - Activated the "Abort the build if it's stuck" option (60 minutes, fail the build) on all Sling build projects to avoid hogging up build instances if our builds get stuck, which seems to happen if the selected port is unavailable.
          Hide
          Bertrand Delacretaz added a comment -

          Nigel Daley says the port allocator plugin would only help if everybody uses it, which is not likely [1]. I guess for now we'll just stick to "carefully" selected port numbers, and if needed build in a simple port selection mechanism (calling new ServerSocket(0).getLocalPort() selects an available port, for example).

          [1] http://mail-archives.apache.org/mod_mbox/www-builds/200910.mbox/%3C48CAC9D4-C09E-4BFF-B27F-1352FA02D6FE@apache.org%3E

          Show
          Bertrand Delacretaz added a comment - Nigel Daley says the port allocator plugin would only help if everybody uses it, which is not likely [1] . I guess for now we'll just stick to "carefully" selected port numbers, and if needed build in a simple port selection mechanism (calling new ServerSocket(0).getLocalPort() selects an available port, for example). [1] http://mail-archives.apache.org/mod_mbox/www-builds/200910.mbox/%3C48CAC9D4-C09E-4BFF-B27F-1352FA02D6FE@apache.org%3E
          Hide
          Bertrand Delacretaz added a comment -

          Moved sling-trunk-1.6 build to port 9363 as the 1.5 and 1.6 builds do run at the same time sometimes.

          Show
          Bertrand Delacretaz added a comment - Moved sling-trunk-1.6 build to port 9363 as the 1.5 and 1.6 builds do run at the same time sometimes.
          Hide
          Bertrand Delacretaz added a comment -

          I have asked on <builds@apache.org> about installing the Port Allocator plugin.

          Show
          Bertrand Delacretaz added a comment - I have asked on <builds@apache.org> about installing the Port Allocator plugin.
          Hide
          Justin Edelson added a comment -

          if there's already support for passing in http.port as a system property, then the pain I was mentioning is non-existant. You just need to configure the Port Allocator plugin (assuming it is installed) and then do -Dhttp.port=$HTTP_PORT (assuming that HTTP_PORT is the allocated port environment variable).

          Show
          Justin Edelson added a comment - if there's already support for passing in http.port as a system property, then the pain I was mentioning is non-existant. You just need to configure the Port Allocator plugin (assuming it is installed) and then do -Dhttp.port=$HTTP_PORT (assuming that HTTP_PORT is the allocated port environment variable).
          Hide
          Bertrand Delacretaz added a comment -

          Added "-Dhttp.port=9362" to the maven build options of both the sling-trunk-1.6 and sling-trunk-1.5 projects, as port 8888 was in use on the Hudson build machines.

          On the sling-dev list, Justin Edelson says "is it possible to use the Port Allocator plugin (http://wiki.hudson-ci.org/display/HUDSON/Port+Allocator+Plugin)? It's a bit of PITA in that your code (primarily test cases in my experience) needs to do an environment variable lookup, I've found it to be worthwhile to avoid port contention problems."

          Show
          Bertrand Delacretaz added a comment - Added "-Dhttp.port=9362" to the maven build options of both the sling-trunk-1.6 and sling-trunk-1.5 projects, as port 8888 was in use on the Hudson build machines. On the sling-dev list, Justin Edelson says "is it possible to use the Port Allocator plugin ( http://wiki.hudson-ci.org/display/HUDSON/Port+Allocator+Plugin)? It's a bit of PITA in that your code (primarily test cases in my experience) needs to do an environment variable lookup, I've found it to be worthwhile to avoid port contention problems."
          Hide
          Bertrand Delacretaz added a comment -

          Added new job http://hudson.zones.apache.org/hudson/view/Sling/job/sling-installer-1.5/ while working on SLING-1078. Might be merged with another job later on.

          Show
          Bertrand Delacretaz added a comment - Added new job http://hudson.zones.apache.org/hudson/view/Sling/job/sling-installer-1.5/ while working on SLING-1078 . Might be merged with another job later on.
          Hide
          Bertrand Delacretaz added a comment -

          Added new job http://hudson.zones.apache.org/hudson/job/sling-samples-1.5/ as the sling-contrib modules was missing the org.apache.sling.samples.path-based.rtp dependency

          Show
          Bertrand Delacretaz added a comment - Added new job http://hudson.zones.apache.org/hudson/job/sling-samples-1.5/ as the sling-contrib modules was missing the org.apache.sling.samples.path-based.rtp dependency
          Hide
          Felix Meschberger added a comment -
          • Reconfigured the Sling projects to access the TLP SVN location instead of the previous incubator/sling location.
          • Changed notification address to dev@sling.apache.org
          • Re-enabled 1.5 builds
          Show
          Felix Meschberger added a comment - Reconfigured the Sling projects to access the TLP SVN location instead of the previous incubator/sling location. Changed notification address to dev@sling.apache.org Re-enabled 1.5 builds
          Hide
          Jukka Zitting added a comment -

          One more change

          • The sling-trunk-1.6 job is now only build after a successful sling-trunk-1.5. This way we won't get duplicate warnings (separately for 1.5 and 1.6) about broken builds.
          Show
          Jukka Zitting added a comment - One more change The sling-trunk-1.6 job is now only build after a successful sling-trunk-1.5. This way we won't get duplicate warnings (separately for 1.5 and 1.6) about broken builds.
          Hide
          Bertrand Delacretaz added a comment -

          Jukka says, on sling-dev:

          I've changed the Hudson settings a bit:

          • Changed the svn poll interval from 15 minutes to 1 hour based on infra recommendation
          • Removed the timed nightly build option, as the build jobs are already executed whenever there are code or dependency changes. Extra nightly builds serve little purpose and only produce the "still broken" notifications that people find annoying.
          • Disabled the "Send e-mail for every unstable build" option for sling-contrib-1.5, though in light of the above changes I think it could (should?) be re-enabled. A "still broken" notification is IMHO quite useful when it's bound to actual changes that people commit.
          Show
          Bertrand Delacretaz added a comment - Jukka says, on sling-dev: I've changed the Hudson settings a bit: Changed the svn poll interval from 15 minutes to 1 hour based on infra recommendation Removed the timed nightly build option, as the build jobs are already executed whenever there are code or dependency changes. Extra nightly builds serve little purpose and only produce the "still broken" notifications that people find annoying. Disabled the "Send e-mail for every unstable build" option for sling-contrib-1.5, though in light of the above changes I think it could (should?) be re-enabled. A "still broken" notification is IMHO quite useful when it's bound to actual changes that people commit.
          Hide
          Bertrand Delacretaz added a comment -

          Added new sling-contrib-1.5 job to build what's under sling/contrib, including the jcrinstall integration tests

          Show
          Bertrand Delacretaz added a comment - Added new sling-contrib-1.5 job to build what's under sling/contrib, including the jcrinstall integration tests
          Hide
          Bertrand Delacretaz added a comment -

          Another cool thing about Hudson: the new launchpad/test-services module that I created today has been included in the build automatically, I don't think continuum does that (or at least not our continuum setup)

          Show
          Bertrand Delacretaz added a comment - Another cool thing about Hudson: the new launchpad/test-services module that I created today has been included in the build automatically, I don't think continuum does that (or at least not our continuum setup)
          Hide
          Bertrand Delacretaz added a comment - - edited

          Added info about Hudson setup at http://incubator.apache.org/sling/site/project-information.html , will be published in a few hours.

          Show
          Bertrand Delacretaz added a comment - - edited Added info about Hudson setup at http://incubator.apache.org/sling/site/project-information.html , will be published in a few hours.
          Hide
          Felix Meschberger added a comment -

          I have modified both build configurations by adding mvn goals "clean install". This forces to clean the target (and other files) before building and testing the bundles. The default is just to run "install" which in the end fails for the launchpad/testing bundle because hudson thinks test output has not changed and thus fails the build.

          Show
          Felix Meschberger added a comment - I have modified both build configurations by adding mvn goals "clean install". This forces to clean the target (and other files) before building and testing the bundles. The default is just to run "install" which in the end fails for the launchpad/testing bundle because hudson thinks test output has not changed and thus fails the build.
          Hide
          Bertrand Delacretaz added a comment -

          I have created the sling-trunk-1.5 and 1.6 jobs, to build the Sling trunk (from the top-level pom.xml) with JDK 1.5 and 1.6

          The 1.5 build is configured to deploy the snapshots under
          https://repository.apache.org/content/repositories/snapshots/org/apache/sling/

          Tied to Ubuntu build systems, and polling svn at 15 minutes interval, so builds should be triggered automatically by svn changes. A daily build is also configured.

          Notifications go to sling-commits@incubator.apache.org .

          The first build took about 50 minutes, later ones might be faster if Maven keeps artifacts around.

          The jobs use a lock named "Sling" to avoid running them at the same time, so as to be good Hudson citizens.

          The Hudson Sling view (http://hudson.zones.apache.org/hudson/view/Sling/) shows all jobs having name that start with "sling", so if we add more jobs they should start with this prefix.

          See http://wiki.apache.org/general/Hudson for more general info about that build server.

          Show
          Bertrand Delacretaz added a comment - I have created the sling-trunk-1.5 and 1.6 jobs, to build the Sling trunk (from the top-level pom.xml) with JDK 1.5 and 1.6 The 1.5 build is configured to deploy the snapshots under https://repository.apache.org/content/repositories/snapshots/org/apache/sling/ Tied to Ubuntu build systems, and polling svn at 15 minutes interval, so builds should be triggered automatically by svn changes. A daily build is also configured. Notifications go to sling-commits@incubator.apache.org . The first build took about 50 minutes, later ones might be faster if Maven keeps artifacts around. The jobs use a lock named "Sling" to avoid running them at the same time, so as to be good Hudson citizens. The Hudson Sling view ( http://hudson.zones.apache.org/hudson/view/Sling/ ) shows all jobs having name that start with "sling", so if we add more jobs they should start with this prefix. See http://wiki.apache.org/general/Hudson for more general info about that build server.

            People

            • Assignee:
              Unassigned
              Reporter:
              Bertrand Delacretaz
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development