Jenkins and git notes

[Jon Schewe]

Has anyone thought about attaching a git note onto commits that have run through Jenkins and then pushing those notes back to the repository?

--
Jon Schewe | http://mtu.net/~jpschewe

[Mark Waite]

I don't know what you mean by a "git note".  Can you describe further what you are trying to do?

 

One of the steps in our build increments the version number of the build.  In order to have repeatable builds for a point in time, we commit that version increment and then we push it to the central git repository.  Is that similar to what you're trying to do, or are you trying to do something different?

 

Mark Waite

From: Jon Schewe <[hidden email]>
To: [hidden email]
Sent: Monday, January 23, 2012 7:47 PM
Subject: Jenkins and git notes

Has anyone thought about attaching a git note onto commits that have run through Jenkins and then pushing those notes back to the repository?

--
Jon Schewe | http://mtu.net/~jpschewe

[Sebastian Bergmann-2]

On 01/24/2012 09:25 AM, Mark Waite wrote:
> I don't know what you mean by a "git note".

  http://progit.org/2010/08/25/notes.html

--
Sebastian Bergmann                    Co-Founder and Principal Consultant
http://sebastian-bergmann.de/                           http://thePHP.cc/

[Mark Waite]

Thanks for the pointer.  Considering the difficulties involved in sharing, merging, and maintaining notes (at least as described at that link), I definitely would like to know more about the use model envisioned by the user. 

 

Are they trying create something like a tag of a specific commit, but they want more text associated with the tag?  Since tags can have a message associated with them, I'm not sure how a note is better than a tag.

 

Mark Waite

From: Sebastian Bergmann <[hidden email]>
To: [hidden email]
Sent: Tuesday, January 24, 2012 7:28 AM
Subject: Re: Jenkins and git notes

On 01/24/2012 09:25 AM, Mark Waite wrote:
> I don't know what you mean by a "git note".

http://progit.org/2010/08/25/notes.html

-- Sebastian Bergmann                    Co-Founder and Principal Consultant
http://sebastian-bergmann.de/                          http://thePHP.cc/

[Jon Schewe]

I suppose one could just use a tag with the status of the build in the
commit message as well.

On Tue, Jan 24, 2012 at 8:49 AM, Mark Waite <[hidden email]> wrote:

> Thanks for the pointer.  Considering the difficulties involved in sharing,
> merging, and maintaining notes (at least as described at that link), I
> definitely would like to know more about the use model envisioned by the
> user.
>
> Are they trying create something like a tag of a specific commit, but they
> want more text associated with the tag?  Since tags can have a message
> associated with them, I'm not sure how a note is better than a tag.
>
> Mark Waite
>
> From: Sebastian Bergmann <[hidden email]>
> To: [hidden email]
> Sent: Tuesday, January 24, 2012 7:28 AM
> Subject: Re: Jenkins and git notes
>
> On 01/24/2012 09:25 AM, Mark Waite wrote:
>> I don't know what you mean by a "git note".
>
> http://progit.org/2010/08/25/notes.html
>
> -- Sebastian Bergmann                    Co-Founder and Principal Consultant
> http://sebastian-bergmann.de/                          http://thePHP.cc/
>
>

--
Jon Schewe | http://mtu.net/~jpschewe

[Nigel Magnay]

If you use gerrit with Jenkins, you get this for free.

My git logs contain entries like:

Commit comment Blah

    

    Signed-off-by: Blah <[hidden email]>

    Change-Id: I9f5388753a1f33fe5ae6d6f48cc54d859e5cb195

    Reviewed-on: http://gerrit/r/96

    Reviewed-by: Mr Person <[hidden email]>    

    Tested-by: Jenkins <[hidden email]>

Following the gerrit link gives you the full comment from Jenkins, which includes the URL to the build that it tested.

On Tue, Jan 24, 2012 at 3:11 PM, Jon Schewe <[hidden email]> wrote:

I suppose one could just use a tag with the status of the build in the
commit message as well.

On Tue, Jan 24, 2012 at 8:49 AM, Mark Waite <[hidden email]> wrote:
> Thanks for the pointer.  Considering the difficulties involved in sharing,
> merging, and maintaining notes (at least as described at that link), I
> definitely would like to know more about the use model envisioned by the
> user.
>
> Are they trying create something like a tag of a specific commit, but they
> want more text associated with the tag?  Since tags can have a message
> associated with them, I'm not sure how a note is better than a tag.
>
> Mark Waite
>
> From: Sebastian Bergmann <[hidden email]>
> To: [hidden email]
> Sent: Tuesday, January 24, 2012 7:28 AM
> Subject: Re: Jenkins and git notes
>
> On 01/24/2012 09:25 AM, Mark Waite wrote:
>> I don't know what you mean by a "git note".
>
> http://progit.org/2010/08/25/notes.html
>
> -- Sebastian Bergmann                    Co-Founder and Principal Consultant
> http://sebastian-bergmann.de/                          http://thePHP.cc/
>
>

--
Jon Schewe | http://mtu.net/~jpschewe