Using GitHub with ScriptRunner

Author: | |Reading time: 2 minutes Category: Development

This article has been translated automatically.

There are always inquiries from customers and uncertainties about GitHub. Some interested people say “We have GitHub and therefore don’t need a ScriptRunner”.
What is GitHub?

GitHub is a software version management in the cloud. So developers can develop scripts and save them in GitHub. So GitHub only supports the functions version management and version history of scripts and only overlaps in a very small part with the ScriptRunner functions.
What can’t GitHub do?

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

A clear YES. The way GitHub works is that valid scripts are checked out to a directory. So you put a GitHub check out directory on the ScriptRunner backend. The global settings of ScriptRunner configure this directory as a script directory for ScriptRunner.
Now the scripts from GitHub appear in ScriptRunner.
In addition, ScriptRunner actively monitors this directory and will be notified when new or changed scripts are made available by GitHub. The replication of the versioned scripts stored in GitHub, Gitlab, etc. can also be automated with a small PowerShell script and a scheduled action of ScriptRunner. So the ScriptRunner backend always has the latest scripts of a branch – advantage of this is that you can use all the logic and functions of ScriptRunner seamlessly integrated with GitHub.

These posts might also be interesting for you:

PowerShell Script Code, PowerShell Parameter und ihre grafische Darstellung in ScriptRunner
PowerShell-Script Header und Parameter, ScriptRunner, PowerShell-Script Code