I also pointed out to CB that what I really wanted was to be able to apply
parameters specified in the SCM to a template (via literate builds).
So instead of
Environment
==========
· jdk1.6.0_64, RedHat_6
Build
====
* mvn random command.
I would like a way in source to describe the CB template I want and its
parameters
Template
=======
* Standard Code review build
* Standard Commit build
* Standard Documentation build
Parameters
=========
* Java:jdk1.6.0_64
* Label:RedHat_6
Now in reality I would also like to go one step further – and be able to assume
the template (or at least set it in a the literate job)
e.g.
Parameters
=========
* Java:jdk1.6.0_64
* Label:RedHat_6
* email: [email protected]
Such that I have a foobar_commit job (using the “commit” template) – that takes
the parameters for the template from the parameters in the source code, a
foobar_doc (suing the “documentation” template) etc etc..
Any values not specified optionally would fail the build, or use defaults.
It sounds like I am not quite alone in this request – although Stephen will
probably shoot me when I mention the maven project type (or its new
replacement)…
/James
From: [email protected]
[mailto:[email protected]] On Behalf Of Christian Willman
Sent: 11 March 2014 15:52
To: [email protected]
Subject: Re: Is it possible to have non editable execute shell for users?
Stephen,
I'm really interested in the Literate plugin! Like I mentioned to you and Jesse
before (through Cloudbees support vis-a-vis my work), it's futile for us unless
we can keep devs from creating FreestyleBuilds.
--
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 it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
