1

I have a Jenkins Shared Library which supports functions to checkout, build, etc. Is it possible to convert the entire library into a plugin making it more portable and also protect the code?

Or any other ways by which I might not expose the code but give users the ability to access all the functionalities by calling the functions?

Arghya
  • 240
  • 1
  • 16

1 Answers1

2

Shared library logic doesn't translate directly to a plugin.

Usually Jenkins admins are looking for a solution the other way around: how to convert a plugin to a shared library. A plugin has to be installed by an admin, requires a restart every time there is an update to the code, can potentially bring your whole master down in case of an error.

You probably have good reasons to want to hide the library code from your users. Maybe you can put your library in a repo where users don't have read access. In order to use the library in a build, only credentials stored in Jenkins have to be able to access the repository.

Mzzl
  • 3,926
  • 28
  • 39
  • I am having a similar requirement. In my scenario, I want to distribute a container that has the Jenkins setup with shared libraries. I want to protect this library code as it has plain text source files written in groovy. Configuring with Git repo also leads to same issue- I think Jenkins is copying the library content to the job workspace folder as it checkouts on every build, so user who has read access to workspace or slave logins, he can grab the code. Is there a way to obfuscate groovy code by any means and that can be understood easily by groovy engine in the Jenkins core system? – Srinivas Sep 08 '20 at 16:06