[cle-release-team] 2.9.x build failures

[Matthew Jones]

I no longer see 2.9.0-rc03 in mailsender base.
There is about a 2-3 minute window in every tool while the release is
actually happening that the wrong version is in the pom.

https://source.sakaiproject.org/viewsvn/mailsender/branches/1.7/pom.xml

The only workaround for this was to have a process
- Copy the branch to a temporary branch
- Update the scm block
- Update Jenkins to point to that temp directory (or have a separate job
for reach tool to release)
- Run Jenkins from this directory
- Remove temporary directory

I never got the time to automate writing this, so there a window for a few
hours every few weeks (always late in the US evening) while all indies are
releasing where the branch will not work correctly as the process updates
the versions in place, then commits them back.

The build last night started at
*00:41:51 2012 UTC*
and ended at
*02:53:49 2012 UTC**
*

There shouldn't be a Maven version limitation. Maven 2.x will print
warnings about checksum errors because the format of the metadata changed
and was incompatible and I was never able to find any way to consistently
fix that. Maven 3.x does not have that problem.

Most likely I'm not going to spend time on this change for the 2.10
release. Most of the "indies" which the CLE Team works on and
are versioned the same as Sakai will just be moved back and released as
part of the core build (not assemblies). The few true indies can remain.
I'm seeing less of an advantage to this process when the same small group
of people are the only ones working on everything. But this likely won't
happen for at least a few months and with release team discussion.

On Fri, Nov 2, 2012 at 11:31 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> Assuming the persona of a first-time dev interested in downloading and
> installing 2.9.x I blew away my local .m2 repo (all of it) and then checked
> out 2.9.x.  I then attempted to build it with Maven 3.0.4 but encountered
> core-deploy build failures.  I then checked Confluence and the 2.9.x
> release notes but there is no mention of a Maven version limitation
> (2.2.1).  Nor are there at present any 2.9 installation instructions (I'll
> assume that they are on the way and are simply not in place yet).  So I
> checked Nightly2 (which is cheating), reverted to 2.2.1 and commenced a new
> build.
>
> The build failed again on the mailsender assembly.   The 1.7.1-SNAPSHOT
> assembly inherits org.sakaiproject.master version 2.9.0-rc03 via its
> mailsender-base-pom <parent>.  rc03 has yet to be deployed to Maven Central
> and it ain't in the snapshot repo (expected), hence the build failure.[3]
>
> I suspect my 2.2.1 build issue is because I tried to perform a build as
> Matt is deploying rc03 but I thought I'd bring my experience to your
> attention--particularly as regards the install guide which is at present
> not newbie friendly.
>
> Cheers,
>
> Anth
>
>
> [1] [INFO] Unable to find resource
> 'org.sakaiproject:master:pom:2.9.0-rc03' in repository
> sakai-maven2-snapshots (http://source.sakaiproject.org/maven2-snapshots)
> Downloading:
> http://repo1.maven.org/maven2/org/sakaiproject/master/2.9.0-rc03/master-2.9.0-rc03.pom
>
> [2]
> https://oss.sonatype.org/content/repositories/snapshots/org/sakaiproject/mailsender/mailsender-base/1.7.1-SNAPSHOT/mailsender-base-1.7.1-20121102.024725-17.pom
>
> [3]
> http://search.maven.org/#search|gav|1|g%3A%22org.sakaiproject%22%20AND%20a%3A%22master%22
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20121102/e0736589/attachment-0006.html