Hi,
Trying to figure out a way to configure jenkins via groovy init.d scripts
so it will
auto-download mvn and java versions.
I found http://javadoc.jenkins-ci.org/hudson/model/JDK.html but it seems to
require a full path to a JDK - I would prefer it
used whatever is needed for auto downloadin
Hi,
I just recently become aware of `/pluginManager/prevalidateConfig` which
can let me upload a config.xml and have jenkins automatically install any
missing plugins.
In that context I got two questions:
1) is there a way to specify in config.xml I just want the latest version
of the plugin
I take this back.
${FILE,path="PATH"} worked. Environment variables does not.
I've updated https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
to actually state recipient list also honors email tokens.
--
You received this message because you are subscribed to the Google Groups
"J
p
> that in mind.
>
so this means there is no way for the build to affect the list of
recipients of mail ?
I tried using tokens but they seem to only work for subject and body.
Is this somehow intentional ?
/max
On Apr 1, 2014 4:43 AM, "Max Rydahl Andersen"
>
> wro
No, the ${ENV style does not work in the body nor recipient list.
I guess I could try the groovy script approach - but would be simpler if
mail-ext actually supported the env variables as claimed. Maybe it was
added very late and I don't have latest update ?
/max
On Mar 31, 2014
I found this issue: https://issues.jenkins-ci.org/browse/JENKINS-5942
it was closed as incomplete but as far as I can see it is exactly the
problem - not possible to access environment variables set by the build in
the actual mail.
On Monday, March 31, 2014 8:16:41 AM UTC+2, Max Rydahl
Hey,
Background:
I got a little script (https://github.com/maxandersen/jiralint) which is
used to take queries against Jira locating stale jiras or jiras with
missing/wrong information on them
and then generate a junit test xml report which then in turn makes jenkins
generate a build failure re
#x27;m mainly interested of having a recording of the builds tags to
easily check them out.
/max
>
> slide
>
>
> On Tue, Nov 12, 2013 at 11:43 AM, Max Rydahl Andersen
>
> > wrote:
>
>> Yeah, i dont want to have the Master repo littered with Jenkins build
>>
Yeah, i dont want to have the Master repo littered with Jenkins build tags and
I also don't want to give the Jenkins user push access to github master ( just
see the recent Jenkins push force incident ;)
If could have a way to have the initial repository be kept uptodate with master
repo that
Hey,
I'm trying to figure out the easiest way to have jenkins push tags for each
build for a master repository to a "ci" repository but for now it seems to
me like the SCM plugins and Git Publisher plugin does not allow for such
setup.
Is the only option to do a shell script at the end which p
10 matches
Mail list logo