I see you have multiple branches in the repo. When you set the branches to
build to a wildcard, Jenkins will build once every matching branch and then sit
and wait for any branch to receive new commits.
-- Sami
Pete Long kirjoitti 13.5.2012 kello 23.22:
> Hi Sami
>
> Basically I followed th
Hi Sami
Basically I followed the instructions as per the book
Repository URL=>
git://github.com/PeteLong/game-of-life.git
Branch Specifier (blank for default):=> **
I trust this is the info you wanted.
Pete
On May 13, 7:15 pm, Sami Tikka wrote:
> Wh
Which branch did you configure in your job?
-- Sami
Pete Long kirjoitti 13.5.2012 kello 19.11:
> Hi
>
> I going through the “Jenkins – The Definitive Guide” to basically
> learn about this tool. I am finally able to configure a new maven job
> to build the project,
>
> git://github.com/PeteLo
Build is now being triggered by detection of changes in the repositiry
BUT I can't explain why it is working now and not before as I have no
changes. Maybe small gremlins at work that will surface sometime
later .. but for now all is good,
Pete
On May 13, 5:11 pm, Pete Long wrote:
> Hi
>
> I goi
Hi
I going through the “Jenkins – The Definitive Guide” to basically
learn about this tool. I am finally able to configure a new maven job
to build the project,
git://github.com/PeteLong/game-of-life.git
I have configured the job to monitor the repository for changes every
5 mins and only to per
