Cloudbees has some templating type products out there.

Honestly I think every and all build should just be sh("./runs.h") or
sh("make")

I can't help more than that though, i think freestyle, while huge, might be
a good place to look at how its done.

Gavin

On Thu, Aug 6, 2020 at 7:07 PM Michael Carter <mikeycarter1...@gmail.com>
wrote:

> Guess you could say what I'm investigating is to create is a few "secure"
> templates.   That is create a job type where the "builder" and/or
> "publishers" are basically locked in and the people using them have only a
> few of the "freestyle" options.
>
> Partly on one server as a way to open up people having some control over
> their job without a free run on the system... other side of this is a
> "turn-key" solution for those who keep saying to me, "It's unreasonble for
> me to expect developers to know how to write scripts"
>
> That last one these people tend to get overwhelmed with too many options
> so want to limit the options to only the things they need to choose from.
>
> At the moment just fact finding to see what I can and can't do.  When I
> noticed the Ivy/Maven templates had everything embedded with options turned
> off... I started looking at them as a template to make my own.
>
>
> On Thursday, August 6, 2020 at 6:54:24 PM UTC-4, Gavin Mogan wrote:
>>
>> I would take a look at FreeStyleProject. You'd need @Extension and some
>> templates at the very least.
>>
>> https://javadoc.jenkins.io/hudson/model/FreeStyleProject.html
>>
>> Maven project type is pretty much abandoned because of how integrated it
>> was with the java version your running jenkins with.
>>
>> But why would you want a new job type, does pipeline or multibranch
>> pipeline not work for you?
>>
>> On Thu, Aug 6, 2020 at 3:09 PM Michael Carter <mikeyca...@gmail.com>
>> wrote:
>>
>>> Was trying to reverse engineer the Ivy/Maven project to figure out how
>>> to create my own type of job.
>>>
>>> Is there a basic Hello World type template I could grab and expand off
>>> of?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/0e8388c7-751f-4c23-96d8-21efcfabf428o%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/0e8388c7-751f-4c23-96d8-21efcfabf428o%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/33e8d7c0-9f19-4559-aab2-d9ce7d6fddd2o%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/33e8d7c0-9f19-4559-aab2-d9ce7d6fddd2o%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuMHbnhbg_X_G3TpAHDbu3QJxoJFMA_DRoKwVTWtGDYGQ%40mail.gmail.com.

Reply via email to