Connecting with CI/CD - Jenkins

The Jenkins plugin allows you to download the Uleska Plugin where you can set up the host where you have Uleska running on site or in the cloud.

To download the Uleska plugin for Jenkins, go here: https://plugins.jenkins.io/uleska/ 

You can add the Application ID and Version ID for the Application you want to run.

Getting the Application and Version GUIDs

To get the GUID value for your application or version to be tested, you can either get this from your user interface or the Uleska CLI.

• To get the GUIDs from the user interface, click on the application and version you want to test, and click on the 'Edit' or 'Results' button or icon. This will take you to a page with more details about your version, but will also include the application and version GUID in the URL bar

• Another way to get the GUID values for application and version is to run the Uleska CLI. Use the '--get_ids' command, passing in the application name and version name. This will return the GUIDs.

Running the Uleska CLI from Jenkins

You can also run the Uleska CLI from Jenkins as you would run any Python command, see the Python example at https://www.jenkins.io/doc/pipeline/tour/hello-world/ for more details.

The Uleska CLI will receive updates ahead of the Jenkins plugin so you may find more ability to control your security testing and view results through the Uleska CLI.  You can find out more about the Uleska CLI here.

Change your security testing without affecting your JENKINS CONFIGURATION

Now you have the Uleska CLI hook into your project's Jenkins jobs, that's all you will need to change.  Now if you want to change or add new security tools, modify profiles, etc, you can do that all from within the Uleska UI, giving you more flexibility around security testing, without constantly needing to update CI/CD code.