Feature/email jenkins results

[chrisveilleux]

Description

Add steps to Jenkinsfile to email the results of integration tests on success or failure

How to test

• Make a branch off of this one and create local version of it
• add the branch name to the "when" clause in the integration test stage
• push change to origin

Contributor license agreement signed?

CLA [yes]

[forslund]

Should we send success-emails? I'd say it's better to only send things when there is something worth noting.

[krisgesling]

I'm guessing this will be a personal preference thing.

For me, I prefer to get something either way. If I don't get any email I don't know if the job succeeded or the system just failed to email me.

[forslund]

Well Github shows the jobs that have finished and their status so I think that information is available and only really of interest to the one reviewing a PR. since a contributor won't have the possibility to access the Jenkins job and restart it afaik.

[krisgesling]

I assumed the allure report would be accessible to anyone with the link so they can't restart the job but they could see why their build failed.

[forslund]

Yeah exactly, for a failure that's useful but for a success it's redundant imho.

[forslund]

I realize now that the results can't be viewed at all except from the link in the e-mail. So maybe it's good to have for now. In the long term I do think we should try to get the report returned to the PR instead if the build is successful.

[forslund]

I noted a couple of minor issues. The big issue is that I don't seem to be getting the e-mail to my personal mail account despite Jenkins warning that the mail is sent to an unregistered address...

[forslund]

This also sends to devs instead of dev.

[forslund]

The non-breaking space doesn't render correctly in the e-mail

[chrisveilleux]

Could you be more specific? I noticed a space in the link after the text but not sure how to get rid of it.

[devops-mycroft]

Voight Kampff Integration Test Succeeded (Results)