Version 2.36 seems to have fixed it.
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
Regards,
--
Ahmed Mubbashir Khan
"I don't make Software, I make it better"
http://about.me/mubbashir
On Wed, Oct 23, 2013 at 5:18 PM, Ulli Hafner wr
I tried the same after posting to the mailing list, didn't help :(
Regards,
--
Ahmed Mubbashir Khan
"I don't make Software, I make it better"
http://about.me/mubbashir
On Tue, Oct 22, 2013 at 6:09 PM, Daniel Beck wrote:
> I think we had t
Hi All,
Which branch is build if there are multiple branches in a job and job has
been configured for all jobs?
What is the workflow? How jenkins determine what to build?
Similarly:
If a job was initially configured for master, and then we switch it to
monitor all branches. It seems like its
above list all
branches as it should.
Any idea what might be happening here?
p.s. following is the branch config:
Branches to build
Branch Specifier (blank for default):
On Sunday, 27 January 2013 16:19:45 UTC+4, Ahmed Mubbashir Khan wrote:
>
> Plus on executing 'git branch -a
Plus on executing 'git branch -a'
It doesn't list any of the other remote branch, see:
$ git branch -a
* (no branch)
master
remotes/origin/HEAD -> origin/master
remotes/origin/master
On Sunday, 27 January 2013 16:13:09 UTC+4, Ahmed Mubbashir Khan wrote:
>
> H
Hi All,
I configured a porject with a specific branch, then instead of specifiying
a branch I though it would be better if I go with the default behaviour
that is build every branch.
I removed the the branch name from 'Branches to build' but on polling it
seems like that it is still looking for
