Ability to show new repo commits after last build?

[Kevin]

may be overlooking something simple but is there a way to display in a Jenkins project any new commits made to a Github repo (that the Jenkins project is configured to use) since the last build was run? 

My users are hoping to be able to go into Jenkins, select a project and see somewhere a list of the newest commits to the repo since the last successfully completed build.

[Mark Waite]

There is no way that I know to show commits to the repository since the last build.

The usual pattern is to start a build as soon as new commits are detected.

Mark Waite

On Tue, Mar 22, 2016 at 1:33 PM Kevin <kevinj...@gmail.com> wrote:

may be overlooking something simple but is there a way to display in a Jenkins project any new commits made to a Github repo (that the Jenkins project is configured to use) since the last build was run? 

My users are hoping to be able to go into Jenkins, select a project and see somewhere a list of the newest commits to the repo since the last successfully completed build.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/08b94e33-6e25-4099-b650-8c362a733537%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kevin]

bummer. I have been slowing migrating our projects over from TeamCity and found out today that this was a feature that my devs really liked in TeamCity. 

thanks for the quick response.

[Baptiste Mathus]

Hi Kevin,

What was your build frequency before? Because indeed like Mark said, most of us here would just become nervous if Jenkins hadn't started building new commits either immediately a build after a code push (with a hook on the SCM side), or at least in the next few minutes after using polling (with a low value, like 5 minutes max).

But also note that Jenkins is designed to be very extensible. So if this is really a big issue for you, you could consider writing a small plugin to add that to a job page. 

Cheers

--

You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b8259f6c-5f27-4d1e-af93-2139aa88376d%40googlegroups.com.

[Kevin]

Hi Baptiste,

at the moment, the devs are manually triggering builds when they are ready (probably once every couple of hours). I agree that it should be happening much more often than that and am going to start getting them used to the idea that as soon as they make a commit, that code will be checked out and tested by Jenkins. You guys are right - once we start doing this, there should be no need for that other feature I initially posted about.