You will have to confirm that the plugins you use are compatible with the newer
version of Jenkins. I would recommend backing up, creating a test server from
the. backup then upgrading all the plugins on the backup Jenkins to see what
breaks.
--
You received this message because you are
You will need to customize the Blue Ocean image to contain the cf executable
and use your new image instead of the one we provide.
--
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
Dear All,
This weekend I'm planning to upgrade my Jenkins as per below Migration plan:
1.585 -> LTS 2.32.1
Request all of you to please advise if I'm able to directly upgrade 1.585
to LTS 2.32.1
Regards
Vikrant
--
You received this message because you are subscribed to the Google Groups
So I now have a handful of pipeline scripts all reusing some global
methods, all of which I pasted into each script, so I've started to set up
a shared library to avoid duplication.
I'm using https://jenkins.io/doc/book/pipeline/shared-libraries/ as my
implementation guide.
My questions have
Hmmm, of course I found https://issues.jenkins-ci.org/browse/JENKINS-41668
a couple of minutes later...
On Sunday, 5 February 2017 20:50:16 UTC+1, Staffan Forsell wrote:
>
> I have an normal pipeline that looks like this:
>
> #!groovy
> node('docker_host') {
> stage("checkout") {
> p4sync
I have an normal pipeline that looks like this:
#!groovy
node('docker_host') {
stage("checkout") {
p4sync credential: 'superSecretCred', depotPath: '//path'
}
def myEnv
stage("docker build") {
myEnv = docker.build("mytag", "utils/docker")
}
myEnv.inside {
stage("build") {
