On Fri, Nov 26, 2010 at 7:50 AM, Luciano Resende <[email protected]> wrote: > On Thu, Nov 25, 2010 at 7:20 AM, <[email protected]> wrote: >> Author: antelder >> Date: Thu Nov 25 15:20:38 2010 >> New Revision: 1039071 >> >> URL: http://svn.apache.org/viewvc?rev=1039071&view=rev >> Log: >> Add a build profile to build all thats necessary for the all distro as >> quickly as possible, so no tests get run, intended mainly for Hudson to try >> to get some nightly builds published more often >> >> Modified: >> tuscany/sca-java-2.x/trunk/pom.xml >> >> Modified: tuscany/sca-java-2.x/trunk/pom.xml >> URL: >> http://svn.apache.org/viewvc/tuscany/sca-java-2.x/trunk/pom.xml?rev=1039071&r1=1039070&r2=1039071&view=diff >> ============================================================================== >> --- tuscany/sca-java-2.x/trunk/pom.xml (original) >> +++ tuscany/sca-java-2.x/trunk/pom.xml Thu Nov 25 15:20:38 2010 >> @@ -669,6 +669,23 @@ org.apache.tuscany.sca.assembly:org.apac >> </profile> >> >> <profile> >> + <id>all-distro</id> >> + <properties> >> + <skipTests>true</skipTests> >> + <buildZips>true</buildZips> >> + </properties> >> + <modules> >> + <module>maven/maven-tuscany-plugin</module> >> + <module>modules</module> >> + <module>features</module> >> + <module>distribution/all</module> >> + </modules> >> + <build> >> + <defaultGoal>install</defaultGoal> >> + </build> >> + </profile> >> + >> + <profile> >> <id>base</id> >> <modules> >> <module>modules/assembly</module> >> >> >> > > > The 2.x code base has been growing and the time to perform a full > build has grown as well, and I know some of us are relying on Hudson > to perform a full build with all tests to make sure the code is stable > and no regressions have been introduced. > > From the comments on this commit, it seems that we are going to start > skipping tests in Hudson builds. I don't think it's a good idea to > start building AND publishing snapshots of modules that are not even > tested. > > Thoughts ? >
Luciano, the Hudson builds aren't very successful and most of the time they don't complete. When i say "most" of the time i mean that without manual intervention we can go for months without getting a Hudson build through. Often the fails are not due to any problem in the Tuscany code but some unrelated Hudson problem such as timeouts or port conflicts. Most Tuscany devs don't seem to have time to do anything when Hudson fails so I'm a little skeptical people are relying much on the results. I've spent way too much time on this now with its current setup so I've started looking at different approaches, and one of those is trying splitting things up so the testing runs separately. I'd like to get the nightly build section at http://tuscany.apache.org/sca-java-releases.html being more reliable and perhaps with a separate status line showing things like the status of the different sets of things like itests, compliance tests, module builds etc. ...ant
