Git commit during build tricks scm scheduller

[Diego Oliveira]

Hello,

    I'm having trouble configuring my project build in jenkins. The build script is part of my project and trigged by jenkins in the build phase. The problem is that my script do some changes, a commit, and then push upstream, this makes that the next SCM pool finds a new commit (that one the script made in the last run) and then starts a new build, indefinitely. I think the problem is happening because Jenkins fetchs the commit hash in the start of the build, and never refresh that after the build, when the new commit happens.

    Is there a way to make jenkins refresh the commit hash after the build?

      --
      Diego

[Mark Waite]

You didn't mention which SCM you're using, but you do reference "commit hash", so I assume you're using one of the distributed SCM plugins (git, mercurial, etc.).

If you are using the git plugin, then you may be able to use the additional behaviour "ignore commits from certain users" so that commits from the continuous integration server user do not trigger another build of the job.  Look at the "git log" output from those commits and paste the name of the user as written in "git log" in the exclusion list.

Thanks,

Mark Waite

--
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/57c0528d-5638-4476-8fff-19b39fc7c6b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.