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.

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

investigate incremental improvement for incorporating integration tests in development #4332

Closed
pameyer opened this issue Dec 1, 2017 · 1 comment
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure"

Comments

@pameyer
Copy link
Contributor

pameyer commented Dec 1, 2017

Related #4329 (and probably earlier versions); failed integration tests are not easily visible in GitHub/waffle (aka - they require someone remembering to check https://build.hmdc.harvard.edu:8443/ and notice the failure).

It should be possible to configure jenkins to notify GitHub when integrations tests fail (https://plugins.jenkins.io/pipeline-githubnotify-step ? others?). While the ideal state would be having these failure notifications integrated with the other "checks" automatically performed on pull requests (travis and coveralls); "done" for this issue would be having a comment showing up in the PR if an integration test fails (or a comment on the PR that integration tests have run, with success/failure).

@pdurbin
Copy link
Member

pdurbin commented Oct 8, 2022

configure jenkins to notify GitHub when integrations tests fail

We've had this working for years at this point thanks to @donsizemore

Closing.

There's more to do around automated testing, of course, but we should create new issues for those efforts.

@pdurbin pdurbin closed this as completed Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure"
Projects
None yet
Development

No branches or pull requests

2 participants