But why is it building branches that aren't changed??? I am only changing
one branch, yet on the first build-- it thinks all branches were built and
builds all branches??
On Monday, April 13, 2015 at 7:23:29 PM UTC-4, Mark Waite wrote:
On Mon, Apr 13, 2015 at 3:03 PM, felix schwitzer
I think your concept of changed and the plugin concept of changed are
different.
The plugin considers the transition from never been built tobuilt while
I think your model only includes the transition from previous build to new
build
Mark Waite
On Apr 14, 2015 8:25 AM, Konrad Slepoy
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?
On Monday, April 13, 2015 at 12:35:10 PM UTC-4, Mark Waite wrote:
I think that the empty field means monitor all branches. If you don't
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 that is
multi-platform and developer can
On Mon, Apr 13, 2015 at 3:03 PM, felix schwitzer flx107...@gmail.com
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
I think that the empty field means monitor all branches. If you don't
want to monitor all branches, then you need to define branches to build to
match the specific branches you want to monitor.
The specific description you gave, , is not implemented in the git plugin
as far as I know. If a
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
