Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Div
stylepadding: 0 0.5em 0.5em 0.5em


Excerpt


Div
stylemargin: 0 1em 0.8em 0

14 May 2020

The Utoolity team is pleased to present Automation with AWS 1.8 – this release introduces remote conditions with AWS for Jira Service Desk automation, Jira workflow transitions, and Bamboo builds and deployments.

You can now use the Invoke Lambda Function action to evaluate remote conditions so that you can control Jira Service Desk automation rules via the Automate with AWS if condition, control Jira workflow transitions via the Automate with AWS workflow condition and Automate with AWS workflow validator, and fail or succeed Bamboo builds and deployments via the Automate with AWS task.





Panel
borderColor#bbb
bgColor#fff


Div
stylefloat: left; margin: 0
Learn more and try it for free in: Bamboo | Jira



Panel
borderColor#bbb
bgColor#eeeeee

On this page:

Table of Contents
maxLevel3
exclude(Popular|Recent).*


Highlights (Core)

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1

Evaluate remote conditions with the Invoke Lambda Function action

You can now use the Invoke Lambda Function action in applicable integrations to evaluate arbitrary remote conditions by returning a JSON result shape that adheres to the action response format schema:

Code Block
{
        'result': false,
        'errorMessage': "Deployment blocked due to service being in alarm state"
}

This allows you to call AWS services and third-party REST APIs to ensure that any prerequisites for your workflows are automatically checked right before dependent steps are initiated.

Supported integrations are the Jira Service Desk Automate with AWS if condition, the Jira Automate with AWS workflow condition and Automate with AWS workflow validator, and the Bamboo Automate with AWS task.

Highlights (Jira)

Panel
borderColor#F3F3F3
bgColor#FFFFFF
borderWidth1

Evaluate remote conditions to

conditionally run

control Jira Service Desk automation rules

Image Added

You can now use the Automate with AWS if condition to conditionally run Jira Service Desk automation rules based on the response returned from the Invoke Lambda Function action.


Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1

Evaluate remote conditions to control Jira workflow transitions

Image Added

You can now use the Automate with AWS workflow condition and Automate with AWS workflow validator to control Jira workflow transitions based on the response returned from the Invoke Lambda Function action.

Highlights (Bamboo)

Panel
borderColor#F3F3F3
bgColor#FFFFFF
borderWidth1

Evaluate remote conditions to fail or succeed Bamboo builds and deployments

You can now check Evaluate as condition within the Automate with AWS task to conditionally fail or succeed Bamboo builds and deployments based on the response returned from the Invoke Lambda Function action .

Resolved issues

Release 1.8.1

2020-06-30

This release addresses the following issues:

Core

  • Improvements
    • AAWS-752 – Surface new AWS region Africa (Cape Town) / af-south-1
    • AAWS-754 – Surface new AWS region Europe (Milan) / eu-south-1
  • Security
    • AAWS-772 – Fix vulnerable dependencies

Bamboo

  • Bugs
    • AAWS-711 – Fix NoSuchMethodError exception in Bamboo 7.0: com.atlassian.bamboo.variable.CustomVariableContext.setCommonContext()
    • AAWS-712 – Fix missing connector ID clipboard copy JavaScript resources

Release 1.8.0

2020-05-14

This release addresses the following issues:

Core

  • Stories
    • AAWS-738 – As a user, I want to invoke a Lambda function so that I can check remote conditions

Jira

  • Stories
    • AAWS-123 – As a user, I want to gate Jira workflow transitions so that I can transition conditionally
    • AAWS-124 – As a user, I want to gate Jira Service Desk rules so that I can automate conditionally
  • Improvements
    • AAWS-726 – Use configured AWS action as display name of Jira Service Desk rule components
  • Tasks
    • AAWS-654 – Drop support for Jira 7.5
    • AAWS-682 – Drop support for Jira 7.6
    • AAWS-698 – Drop support for Jira 7.7
    • AAWS-706 – Drop support for Jira 7.8

Bamboo

  • Stories
    • AAWS-255 – As a user, I want to gate Bamboo jobs via a task so that I can succeed jobs conditionally
  • Bugs
    • AAWS-649 – Fix Bamboo 6.10 elastic agent RuntimeException: Provider for class javax.xml.stream.XMLInputFactory cannot be created
  • Tasks
    • AAWS-650 – Drop support for Bamboo 6.2
    • AAWS-696 – Drop support for Bamboo 6.3
    • AAWS-705 – Drop support for Bamboo 6.4