On Mon, Dec 3, 2018 at 8:11 AM domi wrote:
> Thanks James, thats an interesting path, but it does look like we would
> have to build quite a lot around this to make it a good replacement of our
> current infrastructure. We also did have a look at jenkins-x, but to be
> honest, it is just way to m
Thanks for the explanation Jesse! I created an issue for the
workflow-cps-plugin at https://issues.jenkins-ci.org/browse/JENKINS-54996
/Domi
> On 3 Dec 2018, at 15:25, Jesse Glick wrote:
>
> On Mon, Dec 3, 2018 at 7:49 AM Tony Noble wrote:
>> Would it not make sense to for Jenkins to at least
On Mon, Dec 3, 2018 at 7:49 AM Tony Noble wrote:
> Would it not make sense to for Jenkins to at least attempt to parse the
> pipeline script when the job is created / amended? Even if it ignores
> 'stages' and just looks at 'parameters' and 'triggers', that would at least
> get round not only
Yes, I do the exact same thing, there is not trigger config in the pipeline
script - but for me this does not work the way you describe it - the job at
least has to run once. But you seem to use the cps block instead of the cpsScm
block for you job-dsl configuration, not sure abut this...
pipel
This is something that can be annoying at times.
Would it not make sense to for Jenkins to at least attempt to parse the
pipeline script when the job is created / amended? Even if it ignores
'stages' and just looks at 'parameters' and 'triggers', that would at least
get round not only this issue
But I don't configure the trigger part with a pipeline script.
I use Job DSL to create a pipeline job. In that pipeline job I configure
the triggering-part with Job DSL and only keep the build process in the
pipeline script.
Then I don't have to run the pipeline script once before it all works.
Hi Tomas,
I do this too, but this does not mean I don’t have to start the build at least
once to make the webhooks work.
/Domi
> On 3 Dec 2018, at 09:25, Tomas Bjerre wrote:
>
> Regarding configuration of webhooks with pipelines. This is why I always
> configure that with Job DSL. I configure
Regarding configuration of webhooks with pipelines. This is why I always
configure that with Job DSL. I configure the Jenkins job and the Git
service (usually some rest-call) in the same Groovy (Job DSL) script.
Den måndag 3 december 2018 kl. 09:15:05 UTC+1 skrev domi:
>
> Thanks Jesse, it proba
Thanks Jesse, it probably is, but even though - do you see a chance to fix the
issues I mentioned?
e.g. why do I need to run a pipeline once before it accepts webhooks from
GitHub or Bitbucket? I do understand that I can configure additional SCM
sources from within a pipeline, but why does it n
Thanks James, thats an interesting path, but it does look like we would have to
build quite a lot around this to make it a good replacement of our current
infrastructure. We also did have a look at jenkins-x, but to be honest, it is
just way to much for us: first of all we don’t use k8s (we use
The simplest approach, starting from what you are doing now, would be
to keep the build records and other state files from your Jenkins
installation, recreating only the configuration files from Git.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers
we solved this in Jenkins X through the use of Prow for handling webhooks &
orchestrating the serverless jenkins pod and then using kubernetes custom
resources to maintain state (pipeline activities, environments, teams,
releases etc)
https://jenkins-x.io/news/serverless-jenkins/
we then use an im
Hi,
Since we now have JCasC and the job-dsl plugin it is easier then ever to treat
jenkins as a disposable resource and just recreate it from scratch whenever you
feel the need for it.
We do have build everything around this idea and reinstall our whole build
infrastructure every time we need t
13 matches
Mail list logo
