Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CICD] Tests run even if a prior build/release stage has failed #309

Open
nmiodice opened this issue Sep 23, 2019 · 0 comments
Open

[CICD] Tests run even if a prior build/release stage has failed #309

nmiodice opened this issue Sep 23, 2019 · 0 comments
Labels
bug Something isn't working effort - small 1 day effort pri-Low Low priority issue

Comments

@nmiodice
Copy link

As a developer, I don't want the tests to run in the case that a previous stage has failed because it wastes time.

Acceptance Criteria

  • This line needs to take into account the success of the prior stages

  • This line also needs to be fixed.

Example of build where integration tests ran but the deployment failed

https://dev.azure.com/csedallascrew/project-cobalt/_build/results?buildId=1085&view=logs&s=d4a977ca-786e-5ca4-015f-d6b8c18a860e&j=1a08d14b-2493-53ec-cabc-8e3308a58870
@nmiodice nmiodice added the bug Something isn't working label Sep 23, 2019
@nmiodice nmiodice changed the title Tests run even if a prior build/release stage has failed [CICD] Tests run even if a prior build/release stage has failed Sep 23, 2019
@nmiodice nmiodice added the effort - small 1 day effort label Sep 23, 2019
@ianphil ianphil added the pri-Low Low priority issue label Sep 23, 2019
@nmiodice nmiodice mentioned this issue Sep 26, 2019
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working effort - small 1 day effort pri-Low Low priority issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nmiodice @ianphil