On 5 June 2013 12:27, Emmanuel Bernard wrote:
> For now I cloned a search job, created a Personal runs view, added a
> GitHub notification from my personal fork and pushed results as IRC
> private messages.
+1
> Not too bad so far after the initial phase where Jenkins decided to run
> build on a
For now I cloned a search job, created a Personal runs view, added a
GitHub notification from my personal fork and pushed results as IRC
private messages.
Not too bad so far after the initial phase where Jenkins decided to run
build on all my already existing branches :)
Question, is this config
I also was thinking of creating a personal job there which would
monitor a specific branch name on my personal github fork, maybe
"toTest" or "forJenkins".
Another option is to use parametric jobs: you have to trigger them
from the UI and the wizard will ask you to fill in a couple of
parameters w
Lol, was just going to say this ;)
You can clone the Jenkins job and point it at your branch. Not so sure
I want this to happen automatically for all my branches.
On 06/04/2013 05:36 PM, Gunnar Morling wrote:
> If you just want an ad-hoc solution, you could create a copy of the HSEARCH
> job a
If you just want an ad-hoc solution, you could create a copy of the HSEARCH
job and change it to let it build your branch. I'm doing it like that every
once in a while.
--Gunnar
2013/6/5 Emmanuel Bernard
> With the CI slowly getting in place. Would there be a way to test a
> branch of mine wit
