Option to disable launch of jenkins job with pipeline

[Charles Moulliard]

Hi,

Is there an option that we can configure to avoid that the jenkins job is started when the piepline has been created ? Otherwise, I can't use & demonstrate gerrit as commit have already been pushed into the gogs repo. And we have to make  change within the git repo before the process start to allow to push a commit with a commit-id

Regards,

--

Charles Moulliard

Apache Committer & PMC / Architect @RedHat

Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

[James Strachan]

On 22 October 2015 at 19:21, Charles Moulliard <ch0...@gmail.com> wrote:

Hi,

Is there an option that we can configure to avoid that the jenkins job is started when the piepline has been created ? Otherwise, I can't use & demonstrate gerrit as commit have already been pushed into the gogs repo.

I don't follow. How are we to create projects & set them up without committing to a git repo?

When should a build start?

And we have to make  change within the git repo before the process start to allow to push a commit with a commit-id

Regards,

--

Charles Moulliard

Apache Committer & PMC / Architect @RedHat

Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

--
You received this message because you are subscribed to the Google Groups "fabric8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

James
-------
Red Hat

Twitter: @jstrachan
Email: james.s...@gmail.com

Medium: https://medium.com/@jstrachan/
Blog: http://macstrac.blogspot.com/

fabric8: http://fabric8.io/

hawtio: http://hawt.io/

Open Source DevOps and Integration

[Charles Moulliard]

What I'm saying is the following. When we have finished to create a CD Pipeline project, it will appear under the view Develop >> Default >> Projects >> gogsadmin-xxx. Within this view, under pipelines tab, it appears that the job(s) defined according to the groovy - canary release file are started.

I think that instead of starting automatically the jobs in jenkins we offer the possibility to the user to start it manually (maybe using the trigger button or a start button). Why: Maybe after the creation of the git repo in Gogs, it will be interested to make some commits, to add the commit-msg required to send commits to gerrit, ... before that the jobs are started.

Make sense ?