Hi,
On Sun, Aug 26, 2012 at 9:56 AM, Sami Tikka wrote:
>> I always thought you have to specify polling schedule if you check the
>> polling box... but you can make the polling cycle very long, e.g. once a
>> week.
On 26/08/2012, at 4:52 PM, Richard Bywater wrote:
> Nope - just ticking the bo
Nope - just ticking the box and leaving the schedule blank works a
charm. No need to have that build for no reason :)
Richard.
On Sun, Aug 26, 2012 at 9:56 AM, Sami Tikka wrote:
> Neither Jenkins or Git really support having multiple projects in one Git
> repository (at least not yet). The diff
Neither Jenkins or Git really support having multiple projects in one Git
repository (at least not yet). The difficulties you are experiencing are a
result of that.
I always thought you have to specify polling schedule if you check the polling
box... but you can make the polling cycle very lon
Hello,
I'm using Jenkins 1.464. I have a Bitbucket repository that contains
several top-level directories, each of which represent a single Jenkins
job. I'm using the Git plugin and its "Included Regions" attribute to
detect just those changes that are relevant to each job. [1] The Bitbucket
