Storing pipeline script "as-is", in config.xml?

Hello, setting up a Jenkins 2 pipeline script, it will be stored with special chars in config.xml. Example: stage('Setup') Is it possible to force Jenkins to store the snippet as it was insert into the build job, in this example: stage('Setup') thank you. Best regards, Michael -- Yo

Re: Jenkins User Conference 2014

Hi, Fred's question is a very good one. Best regards Michael > Alyssa Tong hat am 1. Februar 2014 um 17:14 geschrieben: > > > Hi Fred, > > The date may change :o) > > The thought is that Berlin is easily accessible for those coming from > outside of the city. > > Where would you say has the b

polling for changes; where are credentials stored

Hello, for polling the version control system (e.g. Subversion) for changes, the Jenkins master is used, right? Where on the file system are the credentials stored, which are used to connect to Subversion to poll for existence of changes? Thank you. Michael -- You received this message b

Publish JUnit results in Maven 2/3 build

Hello, having a Maven 2/3 build job, how/where can I configure *additional* JUnit test result files to be picked up and published by Jenkins, after the build? My freestyle build has a post build action where I can add inclusion paths, but how to proceed with a Maven build job? Thank you. Mich

Re: EnvInject plugin not passing environment variable to post build action

Generally, a plugin that has more releases than a core component, this does not sound too bad for me. Am Dienstag, den 01.01.2013, 10:59 +0100 schrieb domi : The idea of the envinject plugin is really nice, but It sounds more and more like not a good idea to use it - it seems very unstable a

Execution order post steps and post-build actions

Hello, given a Maven 3 build job, what is the specified order of Jenkins "Post Steps" and "Post-build Actions", which I can rely on? What I observe is that in at least one case the order is a bit "strange": given one post step and two post-build actions, I get the following execution order: 1. a

Re: Email-ext: access job entry parameter

Hello, sometimes it is already a big help just writing the question. :) Found it, thanks. Michael > Hello, > > my build job is parameterized with $variable. > > The default content of the mail is: > ${JELLY_SCRIPT,template="template"} > > What do I have to write inside the Jelly template t

Email-ext: access job entry parameter

Hello, my build job is parameterized with $variable. The default content of the mail is: ${JELLY_SCRIPT,template="template"} What do I have to write inside the Jelly template to output $variable? I've read the docs, and I'm aware of the tokens approach, but unfortunately I'm not able to print th

Re: parameterize downstream job with user prompt

Am Mittwoch, den 29.08.2012, 14:54 +0200 schrieb Christopher Orr : On 08/29/2012 08:46 AM, Michael Hüttermann wrote: can I somehow parameterize a downstream build job with a String where I offer a default value and the user gets a prompt to commit the value or can enter a different one

parameterize downstream job with user prompt

Hello, can I somehow parameterize a downstream build job with a String where I offer a default value and the user gets a prompt to commit the value or can enter a different one? Thanks. Michael

SVN credentials re-use in shell script, later in the build job

Hello, is there a way to re-use the Subversion account (password), stored via Jenkins, for further access to Subversion, later, via shell build step, in the same build job? In my Jenkins build job, I connect to and checkout out sources from Subversion. Auth is done with via once entering username

SVN changes/commit messages, and env variable

Hello, with Subversion, how can I get the SCM changes that triggered that Jenkins build (the change log, or part of it) and assign that to an environment variable for further usage, if not already present in an env variable somehow? The question with slightly another direction: where in a build j

DevOps book, call for contribution: team building -- We want your story!

Hello fellows, one chapter of my upcoming "DevOps for Developers" book covers team building. I'm looking for success stories how you've set up a team of devs and ops, how the team grew together, how the team collaborate successfully, how you've aligned incentives of devs and ops, how you've addres

parameterized build on other projects

Hello, I'd like to conditionally trigger downstream jobs: depending on some input parameters that a current job receives, a job A is triggered, or a job B. Is there any smart way to do that? The "parameterized trigger plugin" would be a good candidate but it can only put in relation downstream job