o/

Usually the best way to implement something is to look at how other plugins
are doing it. The easiest way to find these existing implems is using
https://www.jenkins.io/doc/developer/extensions/jenkins-core/#toolinstallation

Then, beware to read a few examples of ideally well-known plugins (theory
being that there's greater chance to see idiomatic Jenkins code in a plugin
installed 100k times, than one installed 10 :)).

Cheers

Le dim. 3 mars 2024 à 08:46, Stéphane BOBIN <stephane.bobin...@gmail.com> a
écrit :

> Hi Daniel!
>
> I like the idea. Do you have some more guidance, please? I found this:
> https://javadoc.jenkins.io/hudson/tools/ToolInstallation.html. But it
> does not explain a lot. Can you point me to the doc for the various items
> you suggest? A big thanks for your help!
>
> -- Stéphane BOBIN
>
> Le sam. 2 mars 2024 à 00:40, 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> a écrit :
>
>>
>>
>> On Fri, Mar 1, 2024 at 11:43 PM Stéphane BOBIN <
>> stephane.bobin...@gmail.com> wrote:
>>
>>> - What is the recommended and secure way to have scripts on agents to
>>> call utilities from the plugin?
>>>
>>
>> It's not a common enough use case to have a general recommendation.
>>
>> Some ideas: publish the utilities separately rather than as part of the
>> plugin, integrate them as tools into Jenkins (ToolInstallation /
>> ToolInstaller), implement their functionality as build step(s), provide a
>> build step to copy them to the workspace, or make them available for
>> download from Jenkins like the agent.jar (with some care to not allow
>> downloading anything else).
>>
>> --
>> 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/CAMo7PtJ%2BvW36L2Qhf4gqc2ebO09UQV7WweWByduxgpsXwhT9Pg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJ%2BvW36L2Qhf4gqc2ebO09UQV7WweWByduxgpsXwhT9Pg%40mail.gmail.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/CAMQQ2smfvD2JnTjCFrFWP4sSXgZgf9cOsQ_WPPTQ5S_m-tS3Jw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMQQ2smfvD2JnTjCFrFWP4sSXgZgf9cOsQ_WPPTQ5S_m-tS3Jw%40mail.gmail.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/CANWgJS6f%2Bye6cet4G2PG%3DH0cyaykJiAcmQzOn-Bi_fD9SzSwMg%40mail.gmail.com.

Reply via email to