I don't have such a sample, need to duplicate some way the exclusion filter
used by SCM plugin
build flow don't us SCM triggers, so can't benefit advanced feature they
provide
2013/7/14 Thomas Fields
> Thanks for the reply.
>
> >> is you have to exclude some jobs based on scm commit, do it BEFO
Thanks for the reply.
>> is you have to exclude some jobs based on scm commit, do it BEFORE you call
>> build("job")
How would I do that - any ideas? Can you give me an example?
Cheers
Tom
Sent from my iPhone
On 13 Jul 2013, at 21:32, Thomas Fields wrote:
> Hi there,
>
> The build flow pl
Having never used the tool, just a guess, but would logging into the slave
machine as the user you specified in the Jenkins slave config and running
the scripts do what you want?
Richard.
On Saturday, July 13, 2013, Phuong Do wrote:
> I installed dimensions on slave. One thing that before runnin
On Sun, 14 Jul 2013 12:07:25 +0200, Jean-Louis Boudart
wrote:
[FATAL] Non-resolvable parent POM: Failure to find
org.jenkins-ci.plugins:plugin:pom:1.456 in
https://repository-jenkins.forge.cloudbees.com/release was cached in
the local repository, resolution will not be reattempted until the
u
See my answer in the dev-list:
> Von: Ulli Hafner
> Betreff: Aw: EasyAnt plugin
> Datum: 14. Juli 2013 12:16:53 MESZ
> An: "jenkinsci-...@googlegroups.com"
>
> It might work if you would use an LTS release as parent pom. I'm using 1.424
> for my plug-ins and that works perfectly…
> These are v
CI build [1] is broken. It fails with the following message :
[FATAL] Non-resolvable parent POM: Failure to find
org.jenkins-ci.plugins:plugin:pom:1.456 in
https://repository-jenkins.forge.cloudbees.com/release was cached in
the local repository, resolution will not be reattempted until the
update
It works, thanks for you help.
2013/7/14 Ulli Hafner
> A good, that makes things easy. You should have commit rights now. Can you
> please check?
>
> Ulli
>
> Am 13.07.2013 um 17:50 schrieb Jean-Louis Boudart <
> jeanlouis.boud...@gmail.com>:
>
> The plugin source was there
> https://svn.jenkin
Can you please check if there is already an issue in Jira? If not please create
a new one. Does the problem occur in Jenkins 1.522?
Ulli
Am 13.07.2013 um 18:25 schrieb Maurice van der Pot :
> We're experiencing failures in all our builds with the below error in console
> output.
> I've been lo
A good, that makes things easy. You should have commit rights now. Can you
please check?
Ulli
Am 13.07.2013 um 17:50 schrieb Jean-Louis Boudart :
> The plugin source was there
> https://svn.jenkins-ci.org/trunk/hudson/plugins/easyant
> But it seems already mirrored /moved on github :
> https:
build flow orchestrate job execution, it don't handle scm-triggers. When
flow is started, all builds involved will run
is you have to exclude some jobs based on scm commit, do it BEFORE you call
build("job")
2013/7/13 Thomas Fields
> Hi there,
>
> The build flow plugin looks really powerful but
10 matches
Mail list logo