...
- Go to the CLI installation directory.
- Rename the example properties file (acli-cloud or acli-server) to acli.properties appropriately as per your environment.
Update the acli.properties file, as shown below:
To work with multiple Cloud sites and/or Server sites, you need to update the acli.properties file as shown in the below example where different environments like Prod,Stage, QA etc., are targeted:
Code Block language bash title Example: acli.properties linenumbers true # Example Cloud configuration - customize and rename this file to acli.properties # Cloud requires an email address and a corresponding API token from Atlassian. # Use an existing token or create one at https://id.atlassian.com/manage/api-tokens (requires an Atlassian account login). cloudcredentials cloudcredentials = --user automation@example.com --token xxxxxxxxxxxxxxxxxxxxxxxx myjira = jiracloud -s https://issues.example.com ${cloudcredentials} myconfluence = confluencecloud -s https://mydocs.example.com ${cloudcredentials} # Example Server configuration: prodservercredentials = --user admin --password admin jiraserver = jira -s https://prodjira.examplegear.com ${prodservercredentials} confluenceserver = confluence -s https://prodconfluence.examplegear.com ${prodservercredentials} qacredentials = --user qauser --password qapass qajira = jira -s https://qajira.example.com ${qacredentials} qaconfluence = confluence -s https://qaconfluence.example.com ${qacredentials} # This defines the default client for actions, choose the most likely used client default = ${myjira}
Save the file and run the below commands as per your requirement:
Code Block language bash acli qajira --action getServerInfo acli myconfluence --action addPage --space "demo" --title "This is title" --parent "@home" acli myjira --action cloneIssue --issue "JIRACLI-4" --summary "clone summary" --comment "comment for cloned issue"
| Info | ||
|---|---|---|
You can also use -a instead of --action for all CLI actions. For example:
|
...
| Info |
|---|
|
...