search

Ouranosinc / PAVICS-e2e-workflow-tests

Test user-level workflow.
Apache License 2.0
0 stars 2 forks source link

output-sanitize.cfg: try to make notebooks work on both Travis-CI and Jenkins #38

Closed tlvu closed 4 years ago

tlvu commented 4 years ago

Add regex sanitize for WPS output url.

Both production Jenkins (https://pavics.ouranos.ca/wpsoutputs/) and and non-production Travis-CI (http://localhost:5000/outputs/) WPS output url are accepted. This means non-production url in notebooks won't be caught by Jenkins. Don't like this, but no easy solution yet.

For Finch PR https://github.com/bird-house/finch/pull/112

Tested on Jenkins but un-tested on Travis-CI.

Passed Jenkins run http://jenkins.ouranos.ca/job/PAVICS-e2e-workflow-tests/job/add-regex-to-output-sanitize-cfg-for-Travis-CI/5/console.

@davidcaron Can you help test this one on Travis-CI?

davidcaron commented 4 years ago

@tlvu can you restart this travis build when this PR gets merged? https://travis-ci.org/github/bird-house/finch/builds/663502163?utm_source=github_status&utm_medium=notification

tlvu commented 4 years ago

@davidcaron It's Trevor that takes care of Travis so I don't even have a Travis login. Can you retrigger the build for me?

huard commented 4 years ago

@davidcaron @tlvu Builds are automatically started each new commit into a PR.

tlvu commented 4 years ago

Builds are automatically started each new commit into a PR.

I think both DavidC and I do not want to create bogus commits just to trigger Travis-CI. Looks like DavidC has a way to re-trigger existing build without new commits.

davidcaron commented 4 years ago

Sure, there is a button in Travis ci for restarting a build when you have the proper permissions.

tlvu commented 4 years ago

Sure, there is a button in Travis ci for restarting a build when you have the proper permissions.

@Zeitsperre FYI, no need to pollute with bogus commit anymore to re-trigger Travis-CI.