Skip to content

Pull request build validation for core environment templates #32

Closed
@charleszipp

Description

@charleszipp

Description

As an engineer, I would like to automate the testing of my infrastructure deployment for a pull request, so that reviewers do not need to manually run the automated tests locally

Acceptance Criteria

scenario 1: new pull request triggers test run

when a new pull request is created
then a ci build that executes the automated tests should be triggered
and the ci build should use the pr branch (/refs/pull/99/merge)

scenario 2: new commits on existing pull request triggers test run

given a pull request exists
when new commits are pushed to the pull request source branch
then a ci build check that executes the automated tests should be triggered
and the ci build should use the pr branch (/refs/pull/99/merge)

scenario 4: ci build in progress blocks pull request merge

when a ci build has been triggered for a pull request
then the pull request merge is blocked

scenario 5: ci build failure blocks pull request merge

when the ci build fails
then the pull request merge is blocked

scenario 6: ci build completes and tests pass

given all other pull request conditions have been met (cla check, reviewers approved)
when the ci build completes successfully
then the pull request can be merged to master

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions