gt;
>
>
> HTH Reinhold
>
>
>
> *From:* jenkins...@googlegroups.com <
> jenkins...@googlegroups.com > *On Behalf Of *Mike Craig
> *Sent:* Montag, 11. März 2019 23:33
> *To:* Jenkins Users >
> *Subject:* Jenkins Pipeline: Variable expansion issues
>
>
Hello,
The following snippet from my pipeline is acting very strangely, the values
from the print statements are correct
print "asgName: $asgName"
print "asgMax: $asgMax"
print "asgMin: $asgMin"
asgIncrease = (asgMax * 2)
print
Hello,
For clear text data entry I'd like to be able to enable a 'trim' feature.
This page doesn't document one:
https://jenkins.io/doc/book/pipeline/syntax/#parameters
I would like something like this, does it exist? I couldn't get the below
to work for me.
parameters {
string(name:
gt;
>
>
> ---- Ursprüngliche Nachricht
> Von: Mike Craig
> Datum: 27.02.19 23:12 (GMT+01:00)
> An: Jenkins Users
> Betreff: Pipeline: How to modify Build History status monitor
>
> Hello,
>
> Prior to using declarative pipeline, we were able to modify t
Perfect, thank you for the reference! Having a "how-to" question, and
mapping that to a documentation section is the hardest part for me. :)
On Wed, Feb 27, 2019 at 10:55 PM Andreas Magnusson <
andreas.ch.magnus...@gmail.com> wrote:
> Not quite sure what you want to do, but we modify
Hello,
Prior to using declarative pipeline, we were able to modify the Build
History to indicate information we wanted to see.
We are using a shared "terraform-deploy" pipeline now and would like to
modify this build history to display which project (aka component) was
built in that run.
Hello,
I am using the Jenkins CLI to pull down a list of 'template' jobs, search
and replace for our release version, then create a job using the job XML
which I have pulled from Jenkins.
The template job uses promoted builds plugin to have CI, Directed
Build, ReleaseCandidate,
Hello,
I'm trying to make the Perforce Plugin's view spec more dynamic by
including an Environment variable in the spec, but it doesn't' seem to work
the way I would expect.
Our specs usually include the Release name:
//base/products/branch/v1.Main/... //VMWIN2K801/products/branch/v1.Main/...
I use a batch process using this project:
https://configgen.codeplex.com/
On Tuesday, April 8, 2014 10:40:09 AM UTC-7, award wrote:
I apologize if this has already been discussed or resolved in advance;
however, I can't seem to find the answer i'm looking for. Maybe I'm not
asking it
