Dear Sebastian,
I solved this issue doing this because i think that versioning for
configurations is the big issue in Jenkins:
1) put your settings file in the scm you're using (in my case svn).
2) create a Jenkins job and allow only jenkins administrator to see it (i
use matrix project configura
There's a config-file-provider plugin that does what you're looking for:
https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin
Seems like a horrible idea to put a settings file in a source tree
though
There's really no way to use properties like env. or w/e and
leverage t
On 26 April 2012 09:33, sebastian.st...@softwareag.com <
sebastian.st...@softwareag.com> wrote:
> Hi,
>
>
> I wonder how to best use Maven profiles on Jenkins. Our profile is
> stored in a settings.xml file, which is contained in our source tree.
>
Smells like an anti-pattern... how goes the figh
Hi,
I wonder how to best use Maven profiles on Jenkins. Our profile is
stored in a settings.xml file, which is contained in our source tree.
We can include this profile in Jenkins using -s path/to/settings.xml
option.
Usually, a developer would need to alter this file and adapt it to his
working
