com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Manual Artifact Update Workflow

Owned by Former user (Deleted)
Last updated: Sept 01, 2014 by Former user (Deleted)
1 min read

The workflow involved in uploading an artifact to a cartridge instance manually is illustrated in the diagram below:

The workflow involved in uploading an artifact to a cartridge instance manually will be as follows:

  1.  When a tenant user needs to upload an artifact, they will initially issue a git commit to update their local repository and then they will push the artifact into their remote Git repository by issuing a git push. 
  2. Thereafter, the tenant user will carryout the deployment  synchronization process manually using one of the following methods: CLI tool, Web UI or REST API. 
  3. This will trigger the "Artifact Update" event to be published to the "Instance Notifier" topic, which is within the Message Broker. 
  4. Thereafter, the relevant cartridge instances will subscribe to the "Artifact Update" event and update its artifacts by  issuing a git pull to the tenant user's remote Git repository.
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.