...@gmail.com
javascript: wrote:
On 2015-04-13 22:19, Konrad Slepoy wrote:
Isn't this a really standard behavior though? Who wants all of their
branches to build when they push to one even if they have never been built
before?
For us this is exactly what we need. We have a project
and will continue as a git plugin feature for a long time because
many users depend on that behavior.
Mark Waite
On Mon, Apr 13, 2015 at 9:44 AM, Konrad Slepoy ksl...@terpmail.umd.edu
javascript: wrote:
Hi, I set branches to build to be empty. It works fine, just for some
reason on the first run
Hi, I set branches to build to be empty. It works fine, just for some
reason on the first run of the jenkins job(as in the very first time Build
#1 is executed) it assumes that all branches have been changed even when I
only push to one branch. How do I fix that? I only want it to build changed
Hi, I set branches to build to be empty. It works fine, just for some
reason on the first run of the jenkins job(as in the very first time Build
#1 is executed) it assumes that all branches have been changed even when I
only push to one branch. How do I fix that? I only want it to build changed
HELP!
On Monday, April 6, 2015 at 12:14:52 PM UTC-4, Konrad Slepoy wrote:
I am configuring our system to build when a change is pushed to github.
However, on the first push made by a user, all branches build. Is there a
way to make only changed branches build? I don't want every branch
I am configuring our system to build when a change is pushed to github.
However, on the first push made by a user, all branches build. Is there a
way to make only changed branches build? I don't want every branch to build
on a user's first connection between their github and their jenkins.
--
