[Building Sakai] trunk again

[Kevin Chan]

Thanks David, your suggestion did the trick.

Oddly, I checked the org/sakaiproject/kernel directory before deleting 
it and the 1.0.9-SNAPSHOT was in place...

   Kevin Chan

   Operations Team
   Educational Technology Services
   University of California, Berkeley


On 5/30/09 1:27 AM, David Horwitz wrote:
> Hi Guys:
>
> Trunk: I have for the moment commented out OSP from the main build 
> profile in the base pom. This should mean the next build at 8am should 
> work (jut missed the 4am one)
>
> Kevin: that 2-6-x build failure looks like bamboo hasn't fetched the 
> updated 1.0.9-SNAPSHOT kernel .mvn should do so automaticaly but if 
> you blast out org/sakaiproject/kernel in the repo that should do it ...
>
>
> David
> Kevin Chan wrote:
>> Also, a quick question:
>>
>> Are the nightly builds being executed with "-Dmaven.skip.test= true"? I
>> noticed in our automated builds (by Atlassian Bamboo) that the 2.6.x
>> build started to fail yesterday morning (May 28) at revision 63004. I
>> see that the nightly 2.6.x build happened without incident, so this is
>> just a guess with the nightly builds are happening with the
>> "-Dmaven.skip.test=true" flag.
>>
>> Here is a link to the various Sakai builds that I am running via Bamboo:
>> http://bamboo.media.berkeley.edu/bamboo/browse/SAK
>>
>> You can see the error for the 2.6.x build at:
>> http://bamboo.media.berkeley.edu/bamboo/browse/SAK-26X-46
>>
>>     Kevin Chan
>>
>>     Operations Team
>>     Educational Technology Services
>>     University of California, Berkeley
>>
>>
>> On 5/29/09 3:01 PM, Charles Hedrick wrote:
>>    
>>> Well, it looks like no recent trunk version works. In case someone
>>> wants to know: I just checked code into dav, in both 2.6.x and trunk.
>>> I tested both, but I tested trunk by loading the trunk version of dav
>>> into 2.6.x. A purist might say that I should check it in an actual
>>> trunk build. Unfortunately I can't get one to build and start.
>>>
>>> Perhaps we could modify the 4 hour build scripts so that if it
>>> actually starts it saves the svn revision number someplace. Then I
>>> could check someplace in source.sakaiproject.org and see the most
>>> recent version that is known to build and start.
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email tosakai-dev-unsubscribe at collab.sakaiproject.org  with a subject of "unsubscribe"
>>>
>>>      
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email tosakai-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/20090530/bdb48d71/attachment.html