Cyntech’s Tech Blog

Peter Knoop gave me a cool little script to run to gather Jira tags from Sakai’s SVN log.

Read the rest of this entry »

I need to generate a report on Jira issues resolved between two revisions in Sakai’s Subversion repository, but after investigating Jira’s SVN report, it seems it only displays the last 20 revisions for a particular version.

After speaking with Michigan University’s Peter Knoop, his suggestion was a manual grab of the SVN logs, grepped into a readable format to obtain the Jira issue keys.

I’ll post up the results a bit later.

For the last three weeks, I’ve been struggling to get our SVN repository set up in a way that would enable us to merge new versions of Sakai into our vendor branch. The problem originated when we set it up last year in a way similar to the Sakai Foundation’s repository was set up (using multiple projects and a build directory with externals). However, when it came to merging in new vendor code, it was practically impossible.

So, for the last three weeks, I’ve been trying to recreate our repository in a more traditional vendor branch configuration, and finally, only today, have I been able to get some measure of success. The sheer size of Sakai doesn’t help either.

The trick, we’ve found, is that we need to use the svn_load_dirs script that the Subversion authors wrote to maintain the vendor drops, otherwise when you merge you get nothing but conflicts.

Another cool little thing I found was that if you need to delete all unversioned files, use this command:

svn status --no-ignore | grep '^\?' | sed 's/^\?      //'  | xargs rm -rf

Very helpful.