Automate Atlassian Add-on Management Part Two


Continue with Part One, let me list some requirements that I would like to keep in the scope:

Must Have

  • Plugins metadata (application, version, desired_state…) is source controlled.
  • Can query plugins information (version, license, expiry date…) from servers.
  • Can query plugins information from Atlassian Market place.
  • Can enable/disable plugins.
  • Can install/uninstall plugins.
  • Can update plugins.
  • Can check compatibility.

Should Have

  • Can support dry run mode.
  • Can generate report.
  • Can be distributed by docker image.

Better Have

  • Can send notification to Slack (e.g new versions are available, license expiry warning).
  • Can raise Jira ticket (e.g new versions are available, license expiry warning).
  • Can update Confluence page (e.g Plugins report).
  • Can upload/download plugin binary to/from artifact repository.
  • Can renew plugin license.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s