Executing a General Workflow in CDA from a Post-build Action in Jenkins

  1. Go to the main page and create a new build job (New Item) or use an existing one.
  2. If you are creating a new build job , enter the necessary information in the General, Source Code Management, Build Triggers, and Build sections.
  3. At the bottom of the page, click the Add post-build action button in the Post-build Actions section.
  4. Add Execute General Workflow in Continuous Delivery Automation as a post-build action.
  5. Do one of the following:
    • Select the Use Centralized CDA Connection Parameters checkbox to authenticate with the centralized connection details . See: Configuring CDA Centralized Connection Details).
    • Enter the connection details:

      • Server

        Example:

        http://192.000.000.00/cda

      • Full Username

        Examples:

        • 1000/USER/DEP
        • AUTOMIC/1000/USER/DEP

      • Password

  6. Click Test connection to ensure that the connection succeeds.
  7. Once the connection has been checked, review or edit the other fields as follows:

    1. Enter the name of an existing CDA workflow.

      Notes:

      • This value can also contain variables. Variables must start with $.
      • Archived workflows are not supported.
    2. Select the execution start time:
      • Now
      • At: if selected, you have to specify the planned start time (yyyy-MM-dd HH:mm). Date-time values must be in the future and in UTC format.

        Note: This field can also contain variables (for example: Build environment variable). Variables must start with $. For example: $date_time.

      • Queue: if selected, specify the queue (the container for workflow executions) where you want to add the execution

        Notes:

        • This value can also contain variables. Variables must start with $.
        • Inactive Queues are not supported.
    3. Manual Confirmation: select if manual confirmation is required for the execution.
    4. User/Group: if manual confirmation is needed, you have to define either a user or a group to confirm the execution.

      Notes:

      • Inactive users/ user groups are not supported.
      • This value can also contain variables. Variables must start with $.
    5. Dynamic Properties: optionally, click Check for Dynamic Properties to know whether dynamic properties for the selected Workflow are required or not.

      Click Set Dynamic Property and manually enter the name and value of the dynamic properties to apply them to the execution Workflow and override the existing ones.

      Example: $Dynamic_Key = $Value

  8. You can create multiple ARA general Workflow executions by clicking Add another CDA General Workflow Execution as many times as needed.
  9. Click Save.

As of now, after each successful build the general deployment Workflows configured in the CDA Execute General Workflow in Continuous Delivery Automation post-build action is automatically triggered in CDA.