Works perfectly!  Thanks, Esmond!

@

Andrew,

I changed the provided template as specified in the manual (for the screensaver svn repo only). Let me know if its what you requested, by default it allows log editing only.

Esmond

One hack at a time please Andrew!

I'll get to this over the weekend, please respond if its urgent and I will find time today.

Yup, exactly, retroactive update of a commit log, and definitely am interested in trying the hook out.  I end up needing this correction ability at least a few times a year, and I feel commit log accuracy to be more important than audit log accuracy.  (Of course the audit log should log the commit log change, ideally, right?!  But I doubt GForge has that sophistication.  And while I'm daydreaming...if only tickets' commit associations would be upated on commit log correction...but I know that's too much to hope for! :)  Perhaps I should submit a GForge feature request...

thx,

@

Hi Andrew,

To clarify, you're trying to retro-actively update a commit log for a previous revision?

This is not enabled by default as it will compromise the integrity of the audit log. That said, it looks to be as simple as you indicate, see here as an example. Want me to try the log-hook in that link for your repo?

Esmond

Hi Phil,

gForge are "strongly encouraging" we wait for the 5.6 release for better Git support. Stay tuned to the home-page, I will post an update when they announce 5.6 is production ready.

Thank you for your patience!

Esmond

Inevitably, I've run into the unfortunate situation of making a Subversion commit with an incomplete or incorrect log message.  In the past (pre-ABCD Forge? previous version of ABCD Forge?), I've been able to update the log message for a given revision.  Attempting this now, I get an error message, as detailed here:

$ svn propset --username atolopko -r 3056 --revprop svn:log "what i really meant to say"
Authentication realm: <http://forge.abcd.harvard.edu:80> Document repository
Password for 'atolopko':
svn: DAV request failed; it's possible that the repository's pre-revprop-change hook either failed or is non-existent
svn: At least one property change failed; repository is unchanged
svn: Error setting property 'log':
Repository has not been enabled to accept revision propchanges;
ask the administrator to create a pre-revprop-change hook

So, might it be possible to install a pre-revprop-change hook that would allow this operation to succeed (and to save us fallible developers from recording erroneous logs in perpetuity)?

thanks,

@

No Git SCM user being automatically-granted ssh access (similar to other SCM repos)  is a facet of the partial Git and Forge integration. I can change all the files and database tables manually but am waiting for the vendors input. We are still discussing our options and I will update you when I have a definitive answer.

Thanks for being patient, its always best to work with the vendors recommendation on a production server!

I tried "git clone ssh://forge.abcd.harvard.edu/gf/project/pdurbin/scmgit" but I'm getting "Permission denied, please try again" as if my password is wrong (I'm pretty sure it isn't).

Under My Stuff -> My Account -> Edit SSH Keys I see "The user is not set for using unix shell accounts."  Maybe that's the problem. . .

I'd like to use SSH keys anyway, with any version control system, to avoid having to type a password.

Thanks for all of your help, Esmond.  No big deal on this, by the way.  I just thought I'd try out your git offering, since it's new.  I can wait for gForge Advanced Server 5.6 with the better git integration, as you mentioned in another post in this thread.

Phil

Philip,

Still working with the vendor to get specifics on the upstream integration.

In the interim, please try the following command over ssh:

"git clone ssh://username@gforge.machine/gf/project/project_name/scmgit"

That or we could try the git->svn transparency?

Esmond

Philip,

The release of gForge Advanced Server 5.6 is due real-soon-now and will include git integration on par with SVN and CVS. As currently implemented, the Forge production version of gFAS5.5 and Git is what the vendor describes as "basic" and not wholly integrated into the Forge UI. 

I am talking to the vendor tomorrow to discuss the backport potential with the upstream scmgit plugin. Please stand by.

Esmond

The "test" access info wasn't descriptive enough? ;D

For security purposes, we enable features on request. The Git SCM for GFAS is a plugin and its not currently enabled. I will start the integration and update you later today or tomorrow when its live.

Hello, I just created a project called pdurbin and chose git.  Now I'd like to do something like:

git clone git://forge.abcd.harvard.edu/pdurbin.git

Can someone tell me what the proper URL should be?  Perhaps I missed a step. . .

Thanks,

Phil

The cruise control might work.  I am interested to test it out.