Ah OK. That doesn't seem terribly useful since the other job then cannot be
a pipeline because it doesn't support a release stage.
What's really needed here is simpler: the ability to put a button in the
Jenkins UI with an arbitrary name (like "release") and which triggers the
build while injecting some parameter. Maybe parameterised builds are the
closest solution.
Ari
On Thursday, 4 January 2018 03:19:12 UTC+11, Victor Martinez wrote:
>
> I just ran a raw example and it basically triggers another job with some
> arguments.
>
> stage("Build") {
> node {
> sh 'echo mvn'
> }
> }
> stage("Release") {
> release 'archive'
> }
>
>
> Where archive is just a basic job with some basic hello world in the
> release section
>
> It looks like a kind of similar step like the build DSL one
> <https://jenkins.io/doc/pipeline/steps/pipeline-build-step/>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/063acf54-f8a9-4bf1-a878-b72dccea4182%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
