Skip to content
This repository was archived by the owner on Sep 15, 2021. It is now read-only.

Run integration tests every day #10

Open
semistrict opened this issue Mar 20, 2018 · 2 comments
Open

Run integration tests every day #10

semistrict opened this issue Mar 20, 2018 · 2 comments

Comments

@semistrict
Copy link
Contributor

Set up the integration tests to run in TravisCI every day.

@odeke-em
Copy link
Contributor

Cool idea @Ramonza, I believe you are referring to cron jobs on Travis-CI https://docs.travis-ci.com/user/cron-jobs/

Perhaps we need to define the yaml file for our language dependencies then figure out how to notify everyone of test failures, perhaps we can make an email that forwards to all of us(or those that'd like to know) when things break.

odeke-em added a commit that referenced this issue Mar 28, 2018
Updates #10

A helper to get us closer to integration tests that are triggered
say on every push to a repository.

The helper when run will run the tests by `make test` and if
there is any failure, it'll upload all the output to GCS, grab
a link and then compose an email that'll be sent to everyone
that needs to be notified.

It uses postmark for emailing

```shell
$ go run run+notify.go -gcp-project census-demos \
-postmark-account-token "dbfb2fd0-9c33-42cf-85ee-6d234ebca614" \
-postmark-server-token "85d8e1b7-52a1-41fb-8ac9-4eb5d450996e"
```

```shell
2018/03/28 00:25:13 Failed to run `make test` error: exit status 2
output: protoc -I src/main/proto/ src/main/proto/defs.proto
--go_out=plugins=grpc:src/main/proto
 # To use a different OpenCensus and gRPC version, use
 # -PopencensusVersion= and -PgrpcVersion=.
./gradlew installDist

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine java version from '9.0.4'.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or
--debug option to get more log output.
make: *** [gradlew_install] Error 1
exit status 1
```
@odeke-em
Copy link
Contributor

I just wrote up this #20 which might be a nicer step towards adding webhooks per repo that'll trigger integration tests and email everyone involved as they please.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants