[Building Sakai] How to checkout the 2.9.0 tag source including all tagged indie source?

[Gast, Cynthia (cmw6s)]

Matthew, I missed your comments when I was checking this morning, but thank you for this information.  My thought is to include the indie '../tags/' branches in the externals, to indicate which specific tags versions were released along with 2.9.0 tag.  Agreed that any subsequent indie tag releases would be my responsibility to discover and acquire separately.

Thanks,
Cindy @ UVa

________________________________
From: Matthew Jones [matthew at longsight.com]
Sent: Tuesday, November 27, 2012 8:19 PM
To: Gast, Cynthia (cmw6s)
Cc: sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] How to checkout the 2.9.0 tag source including all tagged indie source?

I'd just use the 2.9.x-all branch. If you used 2.9.0 you'd have to mess around too much with the core-deploy and change too many other versions.

If you wanted to lock it down to specific revisions, you'd want to have an msub in svn and make a copy of the 2.9.x-all branch, then either manually or with some script go down each external and set it to the revision which was tagged for 2.9.0

#Pseudocode
foreach external in 2.9.x-all {
do a regex of 2.9.x to 2.9.0
svn info on the 2.9.0 revision
print back revision number in the external
}
svn propset external
svn commit

I had a script that *kind of* did this for Michigan, but it set the latest 2.9.x revision, and I had to manually bump it back if we didn't want that version.
https://source.sakaiproject.org/svn/msub/umich.edu/ctools/builds/trunk/tools/versionSetter.pl

I didn't think it would take more than an hour to write this script, it ended up taking a little more than 2 hours because the poms are pretty inconsistent. The names of the artifactId don't always match the names of the directory they're in, not all poms have version tags in them (so they inherit from the master, this is mostly true for the ones in core) and the core is still on a 2 digit version.

However the versions for core and indies for 2.9.0 should be correct in this externals
https://source.sakaiproject.org/contrib/cle-release/scripts/externals/

Then if you did want some newer version you could just update it.

What was your suggestion, Chris?


On Tue, Nov 27, 2012 at 2:45 PM, Gast, Cynthia (cmw6s) <cmw6s at eservices.virginia.edu<mailto:cmw6s at eservices.virginia.edu>> wrote:
Hello:

We are setting up for our 2.9.0 upgrade.  We need source for all the projects.  First, I exported the 2.9.0 tag, but this only provides source for some projects (as has been discussed); all indie project tagged source would have to be acquired still.  I took a look at the checkout using the 2.9.x-all branches (svn export https://source.sakaiproject.org/svn/sakai/branches/sakai-2.9.x-all/ ./2.9.x-all).  I see the externals is set to the trunk branches.  So while it does allow me to acquire source for all the core + indie projects, it is source from trunk (with pom files referring to SNAPSHOT versions).

Has anyone created an externals that allows one to export the source for the 2.9.0 tag plus the tag versions of the indies that make it up? ... a  2.9.0-all ?  This would be a huge help to those of us who do build all source.

If not, would it help if I created the externals file to allow us to do this?  Otherwise, I'll go get each indie's source one-by-one according to the version tag.

Thanks for considering this,
Cynthia Gast
UVa Sakai development team
cmw6s at virginia.edu<mailto:cmw6s at virginia.edu>

_______________________________________________
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/20121128/cc08daeb/attachment.html