On 4 January 2018 at 7:19:53pm, Stephen Connolly (
stephen.alan.conno...@gmail.com) wrote:
* the multibranch plugin (which I use already) is pretty flaky. I find it
> will sometimes reset all the branches to be enabled even though I try to
> disable old branches to get them out of the view
>
You
On Thu 4 Jan 2018 at 06:57, Ari Maniatis
wrote:
> I think that's a great idea. The main downsides I see are:
>
> * the multibranch plugin (which I use already) is pretty flaky. I find it
> will sometimes reset all the branches to be enabled even though I try to
> disable old branches to get them
I think that's a great idea. The main downsides I see are:
* the multibranch plugin (which I use already) is pretty flaky. I find it
will sometimes reset all the branches to be enabled even though I try to
disable old branches to get them out of the view
* if you create a lot of branches you end
I am using Git though, I'm not sure about the current availability of this
functionality for SVN
--
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 jenkinsci-user
I have been using the multibranch project's tag build functionality to
achieve this. An environment variable is provided when running a tag build,
so the pipeline can have a stage which checks for the presence of that
variable.
Using multibranch to build a single branch seems a little counter
i
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 injec
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 simil
I’m not really sure how to read that. I tried
pipeline {
release { }
}
But got an error. Maybe it needs to contain steps? Or stages?
Ari
On 4 January 2018 at 1:54:02am, Victor Martinez (
victormartinezru...@gmail.com) wrote:
I've not used that plugin in the past, but there are a couple of ex
I've not used that plugin in the past, but there are a couple of examples
in the below test:
-
https://github.com/jenkinsci/release-plugin/blob/master/src/test/java/hudson/plugins/release/pipeline/ReleaseStepTest.java
--
You received this message because you are subscribed to the Google Groups
Thanks Victor,
Do you have any pointers or examples of the docs for declaration
configuration of the release plugin?
Ari
On Thursday, 4 January 2018 01:23:34 UTC+11, Victor Martinez wrote:
>
> Hi Ari,
>
> AFAIK, the release plugin is supported with pipelines:
> https://issues.jenkins-ci.org/br
Hi Ari,
AFAIK, the release plugin is supported with
pipelines: https://issues.jenkins-ci.org/browse/JENKINS-40765 (release
2.7+). Regarding the promoted build plugin, I'm afraid it's still an open
topic: https://issues.jenkins-ci.org/browse/JENKINS-36089
Input command is the one I used in the
OK, I've made a small amount of progress. I've learned that:
1. The release plugin doesn't work with pipeline
2. The promoted build plugin doesn't work with pipeline
3. Some users are using the "input" command to cause the build to hang for
a few days, and then be able to make a release. This mos
I'm starting to experiment with Jenkinsfile configuration and its mostly
coming together. Probably the hardest thing is sorting out which
instructions are for the old script syntax and which for the new
declarative syntax. Probably a few years from now stackoverflow will have
more correct answe
13 matches
Mail list logo
