[Building Sakai] Trunk build broken
Neal Caidin
neal.caidin at apereo.org
Tue Mar 10 11:11:33 PDT 2015
Would this make a good discussion/agenda item for our Thursday Sakai Core
team meeting?
-- Neal
On Tue, Mar 10, 2015 at 6:57 AM, Matthew Buckett <
matthew.buckett at it.ox.ac.uk> wrote:
>
>
> On 9 March 2015 at 16:17, Matthew Jones <matthew at longsight.com> wrote:
>
>> Okay this should be fixed after
>> https://github.com/sakaiproject/sakai/pull/265
>>
>> I'm not sure why travis didn't notice it after the first run, it only
>> failed after I actually merged it. ;) Maybe because it still had the old
>> directories?
>>
>
> Yep, travis currently keeps the ~/.m2/repository between builds to speed
> them up. I think I saw about a 5 minute speed improvement in builds by
> caching ~/.m2/repository, and it also increases the reliability of builds
> as temporary networking failures in contacting repositories don't fail
> builds as easily.
>
> Possibly clearing out all SNAPSHOTS would allow us to keep the speed
> increase but catch problems like this. But we'd need to add this cleanout
> to the builds script.
>
> The other alternative is just not to cache the ~/.m2/repository at all and
> have slower builds again.
>
> --
> Matthew Buckett, VLE Developer, IT Services, University of Oxford
>
> _______________________________________________
> 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/20150310/cf0b5a44/attachment.html
More information about the sakai-dev
mailing list