[Building Sakai] Snapshots in Sonatype repo

[David Horwitz]

Ideally we should use the jenkins post build step to upload the 
snapshots. This stops a partial build being deployed (e.g the API builds 
but the impl is broken)

We stopped using it because of jenkin's problem deploying the artefacts 
to the sakai repo ...

D



On 06/22/2012 04:59 PM, Matthew Jones wrote:
> Okay, well that sounds like a good plan then,
>
> I filed this jira as:
> https://jira.sakaiproject.org/browse/SAK-22321
>
> We'll need to go into every tool's base pom and add
>
> <relativePath>../master/pom.xml</relativePath>
>
> to the parents where the parent is master and it has no relativePath. 
> This will ensure local builds are still successful and it uses the 
> correct master.  I'd guess this would take 30-60 minutes depending on 
> how quick someone is. :)
>
> We may also want to add the sonatype snapshot repository to every 
> indie so it can build completely standalone. This is something that 
> for sure should be in contrib projects 2.9+. .And it works in 
> 2.9-SNAPSHOT master, though not needed at ALL with a fixed 2.9.0-b05 
> version since that's in maven central.
>
> <repositories>
> <repository>
> <id>sonatype-nexus-snapshots</id>
> <name>Sonatype Nexus Snapshots</name>
> <url>
> https://oss.sonatype.org/content/repositories/snapshots
> </url>
> <releases>
> <enabled>false</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> </repositories>
>
> Then I can go to jenkins and add deploy:deploy to every task for trunk 
> and rebuild it. The actual work to do this is about 30 minutes, but 
> will take Jenkins hours to actually get them deployed.
>
> During this cleanup every project should also be edited to:
>
> - Discard old artifacts instead of old builds. Every project is set to 
> get rid of old builds, when it can be nice having the build history 
> and build history is small, artifacts are the things that take up the 
> space, so we only need to keep at most 1 old artifacts and all old builds.
>
> - Not poll the SCM as often. We're looking into moving to cloud bees. 
> If we do go there, we don't want to build as often because it will be 
> expensive. Right now snapshots are checked and possibly built every 15 
> minutes and/or when another dependency is built. I feel like just 
> checking and building every hour should be sufficient.
>
> On Fri, Jun 22, 2012 at 3:54 AM, David Horwitz 
> <david.horwitz at uct.ac.za <mailto:david.horwitz at uct.ac.za>> wrote:
>
>     This is also a big problem for automated builds...
>
>     D
>
>
>     On 06/22/2012 12:50 AM, Steve Swinsburg wrote:
>>     Hi all,
>>
>>     I know we discussed using sakai-trunk-all (not just sakai trunk)
>>     for builds to resolve the missing snapshot issue, however there
>>     is still an issue when you want to use a tool that binds to a
>>     newer snapshot artifact in an older version of Sakai, and that
>>     snapshot is not in a repo.
>>
>>     For example running the dashboard in Sakai 2.8 or 2.9. It
>>     declares a parent of:
>>     <parent>
>>     	<groupId>org.sakaiproject</groupId>
>>     	<artifactId>master</artifactId>
>>     	<version>2.10-SNAPSHOT</version>
>>     </parent>
>>
>>     So unless I have:
>>     1. Built 2.10 on my local machine, or
>>     2. Changed the pom and therefore mucked up the version of
>>     dependencies that are inherited
>>
>>     I cannot build.
>>
>>     This would be resolved if the snapshots could be deployed to the
>>     sonatype snapshots repo and the repo listed in the projects.
>>
>>     thanks,
>>     Steve
>>
>>
>>     _______________________________________________
>>     sakai-dev mailing list
>>     sakai-dev at collab.sakaiproject.org  <mailto: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  <mailto:sakai-dev-unsubscribe at collab.sakaiproject.org>  with a subject of "unsubscribe"
>
>     _______________________________________________
>     sakai-dev mailing list
>     sakai-dev at collab.sakaiproject.org
>     <mailto: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
>     <mailto: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/20120622/12a93d55/attachment.html