Upgrade

Upgrade ScriptRunner for Confluence

There are two ways to update ScriptRunner for Confluence: 

Version History on the Atlassian Marketplace

To upgrade ScriptRunner for Confluence, navigate to Version History. From there, you can select a version to Download. 

You can also click Watch in the upper right-hand corner to be notified when new versions are released. 

Manage Apps in Confluence Instance

If you navigate to General Configuration > Manage Apps, you can update by selecting Update. 

Upgrade Confluence

Confluence 8

Compatibility with Confluence 8

Only those versions marked as compatible in the Atlassian Marketplace will work with Confluence 8.

Some of your scripts may fail if you upgrade without modifications.

If you have been through the Confluence 6 → 7 upgrade, you have little to fear in upgrading to Confluence 8.

You may not need to make any changes to your own scripts. The major areas of change are listed below.

For further reference, see Atlassian's Preparing for Confluence 8 documentation. The information here is focused on the areas of change likely to affect script writers.

Please manually review your configured scripts for each feature.

Upgrades and staging Environments

If you do not have a staging environment, you should invest the time it takes to create one. You should be able to reliably clone your production instance to the staging environment, so you can test plugins and upgrades.

A good strategy to follow is to:

  1. Make changes to remove all deprecated code while you are using Confluence 8. If you remove deprecated code, then your code has the best chance of working unchanged with Confluence 8.

    Deprecated code is shown as a warning.

  2. Upgrade your staging instance to Confluence 8.

  3. Review your scripts to make sure you don’t have any type checking errors, and Test.

  4. Record changes, if needed.

  5. When upgrading your production instance using inline scripts some changes are necessary. For files, you can update your Scripts Directory, e.g. by merging from a branch.

Changes to Confluence Java API

You can review changes to the Confluence Java API on Atlassian's Deprecated Code Paths Removed in 8.0.

Anything else?

Did we miss something important that script authors should take into account when upgrading? Please let us know.

If it’s likely to affect more than a couple of users we will add it to this documentation.

On this page