Project update scripts (was: Re: Zone for hosting git clones at Apache)

[Grzegorz Kossakowski <gk...@apache.org>]

Jukka Zitting pisze:
>> Is it possible to subscribe to some notification list that notifies about
>> any commit made into public part of our svn? If so I would like to
>> subscribe to it and then I could experiment with writing such a script.
> 
> I don't think we have that, but the existing per-project commit
> mailing lists should be a good a source of example notifications.

Yep. Good idea.

The problem is that there is no 1-1 mapping between per-project notification list and actual projects in SVN. What I
mean here is (for example) situation with Cocoon where we have standard layout for 2.1 and 2.2 versions of Cocoon but
Cocoon 3.0 that is written from scratch is subproject with its own branches/tags/trunk layout.

Thus we would have to either:
1. Update all projects associated with given e-mail address
2. extract the path of modified  files and try to scan all .git/config files for matching paths

The second way is totally automatic so no mapping between repositories and e-mail addresses has to be maintained but
this way is much more tricky.

Do we need this trickery or we are fine with first option?

-- 
Best regards,
Grzegorz Kossakowski

Re: Project update scripts

[Grzegorz Kossakowski <gk...@apache.org>]

Jukka Zitting pisze:
> Hi,
> 
> On Sat, Feb 28, 2009 at 12:31 AM, Grzegorz Kossakowski
> <gk...@apache.org> wrote:
>> Paul Querna pisze:
>>> Can't we can figure out what needs to be done, and just add another
>>> notification method to the post-commit hook?
>> In my opinion we need to figure out how to deal with mismatch that we will face.
>> The problem is that we have one big svn repository mapped into several smaller
>> Git repositories.
> 
> That's no big problem, as the Git mirrors already include enough
> git-svn metadata for an update script to determine whether a
> particular commit affects the mirror. All you need is a list of paths
> affected in the svn commit and a script that matches those paths to
> the relevant Git mirrors.

Yep, that was my idea as well but I still think this won't be just a few lines of scripting but we'll see what I'll come
up with.

BTW. I'll fork your scripts hosted on GitHub. Since they were not updated for a few months I guess they are out-dated.
Could you upload the latest version?

-- 
Best regards,
Grzegorz Kossakowski

Re: Project update scripts

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Sat, Feb 28, 2009 at 12:31 AM, Grzegorz Kossakowski
<gk...@apache.org> wrote:
> Paul Querna pisze:
>> Can't we can figure out what needs to be done, and just add another
>> notification method to the post-commit hook?
>
> In my opinion we need to figure out how to deal with mismatch that we will face.
> The problem is that we have one big svn repository mapped into several smaller
> Git repositories.

That's no big problem, as the Git mirrors already include enough
git-svn metadata for an update script to determine whether a
particular commit affects the mirror. All you need is a list of paths
affected in the svn commit and a script that matches those paths to
the relevant Git mirrors.

BR,

Jukka Zitting

Re: Project update scripts

[Grzegorz Kossakowski <gk...@apache.org>]

Paul Querna pisze:
> Can't we can figure out what needs to be done, and just add another
> notification method to the post-commit hook?

In my opinion we need to figure out how to deal with mismatch that we will face. The problem is that we have one big svn
repository mapped into several smaller Git repositories.

If big repository is being modified by commit we have to find out which Git repositories are affected by that commit. I
don't know how replacing monitoring e-mail notifications with post-commit hook will help us with this particular problem.

-- 
Best regards,
Grzegorz Kossakowski

Re: Project update scripts

[Paul Querna <pq...@apache.org>]

Grzegorz Kossakowski wrote:
> Jukka Zitting pisze:
>>> Is it possible to subscribe to some notification list that notifies about
>>> any commit made into public part of our svn? If so I would like to
>>> subscribe to it and then I could experiment with writing such a script.
>> I don't think we have that, but the existing per-project commit
>> mailing lists should be a good a source of example notifications.
> 
> Yep. Good idea.
> 
> The problem is that there is no 1-1 mapping between per-project notification list and actual projects in SVN. What I
> mean here is (for example) situation with Cocoon where we have standard layout for 2.1 and 2.2 versions of Cocoon but
> Cocoon 3.0 that is written from scratch is subproject with its own branches/tags/trunk layout.
> 
> Thus we would have to either:
> 1. Update all projects associated with given e-mail address
> 2. extract the path of modified  files and try to scan all .git/config files for matching paths
> 
> The second way is totally automatic so no mapping between repositories and e-mail addresses has to be maintained but
> this way is much more tricky.
> 
> Do we need this trickery or we are fine with first option?
> 

Can't we can figure out what needs to be done, and just add another 
notification method to the post-commit hook?