Skip to the main content.

Using GitHub with ScriptRunner

What is GitHub?

GitHub is a software version control system in the cloud. So developers can develop scripts and store them in GitHub. GitHub only supports version management and version history of scripts and therefore only covers a very small part of the ScriptRunner functions.


Post Featured Image

There are always inquiries from customers and ambiguities about GitHub. Some of them say “we already have GitHub, so we don’t need ScriptRunner”. What is GitHub?

What can’t GitHub do?

The functions in ScriptRunner for managing, executing, monitoring and delegating cannot be covered with GitHub.


Can you use GitHub with ScriptRunner?

A resounding YES. The way GitHub works dictates that valid scripts are checked out to a directory. So you put a GitHub checkout directory on the ScriptRunner backend. Using ScriptRunner’s global settings, this directory is configured as the script directory for ScriptRunner.

With this, scripts from GitHub will now appear in ScriptRunner. In addition, ScriptRunner actively monitors this directory and notices when new or modified scripts are made available by GitHub. Replicating versioned scripts stored in GitHub, Gitlab, etc. can also be automated using a small PowerShell script and a timed action from ScriptRunner. This way, the ScriptRunner backend always has the latest scripts of a branch – advantage of this is that you can use all the logic and features of ScriptRunner seamlessly integrated with GitHub.


Script Synchronization with Git

If you want to synchronize your ScriptRunner library with an external repository via Git, you can find a suitable PowerShell script for this on the ScriptRunner GitHub repository:
ScriptRunner Tools “Script Synchronization” on GitHub >

Related posts

About the author: