How to Set Up Your Forked Repo in Git

When it comes to extracting code into utility classes, there's only one option that makes it possible: setting up your forked repo in Git. This approach provides a sandbox environment where malicious code cannot be executed, reducing the risk of potential dangers.

To set up your forked repo in Git, you'll need to configure Jenkins to download scripts from the repository. You can do this by installing the necessary plugins, including Authorize Project, Git, Groovy, and DSL. Once these plugins are installed, you can create a Jenkins DSL seed job and configure it to run as an admin user.

By doing so, you'll be able to extract shared code into utility classes and prevent potentially dangerous scripts from being executed. This approach is more secure than simply unlocking the scripts via the validation queue or disabling script security altogether.

In addition, configuring Jenkins to download scripts from the Git repository provides another layer of protection against malicious code. By default, downloaded scripts are not executable by regular users or the 'SYSTEM' user, reducing the risk of potential dangers.

To get started with setting up your forked repo in Git, follow these steps:

1. Install the necessary plugins: Authorize Project, Git, Groovy, and DSL.

2. Create a Jenkins DSL seed job.

3. Configure the job to run as an admin user.

4. Set up the security system so that the seed job always runs as an admin.

By following these steps, you'll be able to set up your forked repo in Git and extract code into utility classes while ensuring the security of your Jenkins environment.

Git set upstream to forked repo