As a user, I would like to run different pipelines depending on what branch
my commit happens on.
In Declarative Pipelines there is support for doing conditional stages,
however, using this conditional logic has 2 issues:
- You cannot re-order stages based on the branches
- It makes the p
x27;m trying to find a way that post can run w/o being on a node.
I'm also trying to find a way to have multiple steps run inside a stage but
on different nodes.
On Wednesday, April 12, 2017 at 4:08:39 PM UTC-4, Kenneth Brooks wrote:
>
> When I specify an agent inside a stage, it then
simply call that method from with each
> pipeline.
>
> 3. You can define your steps in a configuration file as a property or yaml
> and load those files using the Pipeline utility steps plugin.
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin
>
Created a bug for it with evidence and jenkins plugin
info: https://issues.jenkins-ci.org/browse/JENKINS-43576
On Wednesday, April 12, 2017 at 6:48:06 PM UTC-4, Kenneth Brooks wrote:
>
> Quickly trying out your suggestion of pipeline directly inside the if. It
> sees the stages, but
hose files using the Pipeline utility steps plugin.
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin
>
> To sum up, I think having different stages is worth discussing (it is not
> going to be implemented in the short term) but there are already many
> e
and simply call that method from with each
> pipeline.
>
> 3. You can define your steps in a configuration file as a property or yaml
> and load those files using the Pipeline utility steps plugin.
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Utility+Steps+Plugin
>
&
eploy-utility-1.0') {
// do some deployment using our homegrown deployment binaries on this
node
}
}
-k
On Wednesday, April 12, 2017 at 4:25:51 PM UTC-4, Andrew Bayer wrote:
>
> Are you wanting to use the same node for most, if not all, of the
> pipeline? If so, just use the
As a user, I want to run multiple stages inside a single agent.
Today we use the mesos plugin and spin up and spin down an agent on demand.
I want to have 3 stages all run on that same agent before it spins down.
That way all stages can leverage that workspace before it is trashed.
Current abili
When I specify an agent inside a stage, it then also applies to everything
in the 'post' section.
I'm not sure that is alway the behavior I want.
Is there a way around this?
Specifically, we have the ability to take a checkpoint (similar to the
enterprise edition checkpoint feature) but that s
TL;DR up front:
*As a user, I want to have a pipeline that performs specific pipeline
stages based on the branch. Recommendation: Put the when{} condition
outside the pipeline{} tag.*
*As a user, I want to declare my stages but have the implementation be
separate so that I can reuse them in mult
10 matches
Mail list logo
