Prepare fresh deployment for automated tests #93
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Logs: ``` [W 2020-11-04 03:57:37.582 JupyterHub auth:413] User 'authtest' in blacklist. Stop authentication [W 2020-11-04 03:57:37.582 JupyterHub base:670] Failed login for authtest ```
…nt-for-automated-tests
…ample EXTRA_CONF_DIRS
…eployments Due to difference in existing data on Thredds, previously this query only works on production deployment (Boreas). The new query targets minimal data in bootstrap-testdata which should exist on all deployments needing to run the Jenkins testsuite at https://github.com/Ouranosinc/PAVICS-e2e-workflow-tests.
|
LGTM |
matprov
approved these changes
Nov 6, 2020
|
@moulab88 Can you check if the Nagios monitoring on https://medus.ouranos.ca/canarie/node/service/stats (Medus, not Boreas) is working? Normally we should receive a mail if the link reponse code goes back to 200, I didn't receive it. Basically same behavior as Boreas. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@matprov is building an automated pipeline that will provision and deploy a full PAVICS stack and run our Jenkins test suite for each PR here.
So each time his new fresh instance comes up, there are a few steps to perform for the Jenkins test suite to pass. Those steps are captured in
scripts/bootstrap-instance-for-testsuite. @matprov please call this script, do not perform each steps yourself so any future changes to those steps will be transparent to your pipeline. A new optional components was also required, done in PR #92.For security reasons, Jupyterhub will block the test user to login since its password is known publicly.
Each step are also in their own script so can be assembled differently to prepare the fresh instance if desired.
Solr query in the canarie monitoring also updated to target the minimal dataset from
bootstrap-testdataso the canarie monitoring page works on all PAVICS deployment (fixes #6). @matprov you can use this canarie monitoring page (ex: https://pavics.ouranos.ca/canarie/node/service/status) to confirm the fresh instance is ready to run the Jenkins test suite.