On this page:


Installing on Linux, MacOS, and Windows desktops

The MacOS desktop UI is shown in the illustrations below.

  1. Download and launch the installer for your OS (Linux , MacOS, or Windows).

  2. Click “Next” once you have read the welcome message from Bob Swift




  3. Accept the End User License Agreement (EULA) and click “Next”.
    If you do not wish to accept the EULA select “I do not accept the agreement” and click “Next” or click “Cancel”.



  4. Select where you wish to install the Bob Swift CLI. This defaults to the folder “ACLI” underneath your user directory.



  5. Optionally enroll in a getting started email newsletter subscription. Clear the checkbox to decline enrollment.



  6. If your installation directory contains a Bob Swift CLI installation prior to 9.2, then you will be prompted to confirm whether to overwrite it and given the option for the installer to make backups of user modifiable files.



  7. Choose how you would like to initially configure the Bob Swift CLI installation and then click “Next”. Based on your selection the installer may prompt you for additional connection properties:



    1. Configure CLI connections for:

      1. Atlassian’s Cloud (Jira + Confluence)
        Configure the CLI to connect to an Atlassian hosted instance of Jira (and Confluence if subscribed).

      2. Self hosted server(s)
        Choose this option if you self-host (in your own data center or in a private cloud) the Server or Data Center editions of Jira and/or Confluence.

      3. None (skip this configuration)
        The installer will configure example CLI connections, but will not prompt for any additional connection properties.

    2. Add your installation directory to the user path…
      The installer will configure your environment to make it easier to launch the Bob Swift CLI from any location on your desktop.

    3. Run a simple test of the CLI to verify it is working.
      The installer will use the configuration information from this dialog to create a test script to verify the CLI installed correctly.

  8. The next installer dialogs will vary based on your CLI connections selection in the previous dialog:

    1. Atlassian’s Cloud (Jira + Confluence)



      1. Jira URL: The web address of your Atlassian hosted Jira instance.

      2. Connection name (no spaces): A nickname for this connection for easy reference when issuing CLI commands to be executed using this connection.

      3. Login required…: Indicates if the Jira instance requires a user email and API token to connect or not (aka anonymous access).

        1. User Email: The email address of the user account with which the CLI should connect.

        2. API token: The API token of the user account with which the CLI should connect. API tokens are required by the Atlassian cloud to connect (login) when not using a web browser.

    2. Self hosted server(s)
      This applies to both Jira and Confluence although Jira is used in the example below.



      1. Jira URL: The web address of your self hosted instance.

      2. Connection name (no spaces): A nickname for this connection for easy reference when issue CLI commands to be executed using this connection.

      3. Login required…: Indicates if the Jira instance requires a user name and password to connect or not (aka anonymous access).

        1. User Name: The user account name with which the CLI should connect.

        2. Password: The password for the user.

  9. The installer is now to ready to install the Bob Swift CLI and apply your configuration preferences.



  10. The Installer will show progress of setup.

  11. If you chose “Run a simple test of the CLI to verify it is working” earlier you will see the results of the test. The test results will vary based on your earlier configuration selections.



  12. Once concluded, the Installer presents an option to view the readme file for the installed release.



  13. You can now launch the Bob Swift CLI:

    1. From the Desktop shortcut or Start menu in Windows

    2. The Launchpad on MacOS.

    3. The console command: acli in Linux, MacOS, and Windows.

Installing on Linux servers

Note: This applies to Linux servers without a graphical desktop environment. The Linux installer will not run in the MacOS terminal.

Previous versions