[Building Sakai] trunk build status?

[Matthew Jones]

Yea I fixed the builds server *right* before the noon build and it deployed
updated artifacts.

This particular issue is something related to the artifact deployment and
is either something incorrect with Jenkins, nexus/sonatype or the maven
deployment plugin. I'm not sure what yet.

Matthew Buckett filed an issue against sonatype here:
https://issues.sonatype.org/browse/OSSRH-3161 and we've been discussing it
on the release list.
http://collab.sakaiproject.org/pipermail/cle-release-team/2012-March/000366.html

Apparently there's some elements in the maven metadata that are generated
in maven3 that maven2 can't recognize for some reason.

I *think* it was all related back to this issue in Jenkins where it
assigned unique versions to the artifacts.

https://issues.jenkins-ci.org/browse/JENKINS-2593

This was checked by default on all of the jobs and certain combinations of
maven and Jenkins caused some problem. We've upgraded both maven and
Jenkins on the build server in the last week but haven't cleaned out the
repository or done full snapshot builds. I also believe I've looked at
every job to confirm this unique version option isn't checked but I can't
say with 100% certainty that it isn't. I'd like to write a script to check
it but getting the 2.9.0-b03 finished is my top priority at the moment now
that at least nightly is running.

-Matthew

On Mon, Mar 19, 2012 at 12:47 PM, Jim Eng <jimeng at umich.edu> wrote:

> BTW, the noon build on nightly2 succeeded.
>
> Jim
>
>
>
> On Mar 19, 2012, at 12:43 PM, Jim Eng wrote:
>
> If it works with maven-3, does that mean that someone introduced maven-3
> syntax into sone or more pom files? Just curious.
>
> Jim
>
>
> On Mar 19, 2012, at 11:29 AM, Matthew Jones wrote:
>
> We're working on it, the server (builds.sakaiproject.org) went down over
> the weekend (not sure why) and it doesn't come up correctly (also not sure
> why) . . . Well I'm sure WHY it doesn't come up correctly (the /dev devices
> aren't created in the open vz container) but I'm not sure why they aren't
> created. I've done everything here [1]
>
> Anyway, there are a lot of related problems not now, and there's no actual
> commit that can be backed out to fix this. Aaron said an offline build can
> fix it, and I've heard building with Maven 3 instead of Maven 2 will fix it
> as well.
>
> [1]  http://wiki.openvz.org/Physical_to_container#.2Fdev
>
> On Mon, Mar 19, 2012 at 11:08 AM, Jim Eng <jimeng at umich.edu> wrote:
>
>> It looks like the last successful build of trunk was noon Eastern US time
>> on Saturday (roughly 47 hours ago).  There was discussion of the problem
>> yesterday with no conclusion.  Is anybody working on this?  If not, could
>> we back out the recent changes so the trunk build is not broken?
>>
>> Thanks.
>>
>> Jim
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120319/aa0324eb/attachment.html