You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature/ELI-262 regression tests ci integration (#351)
* stashing
* trigger for the regression tests now in place
* commit workflow to test integration
* using a different workflow to test the integration
* using a different workflow to test the integration
* returned missing steps that are required
* asdf version bump
* comment out the docker line that asdf does not support
* added python to .tool-versions
* added python to .tool-versions
* added test tag value of main
* added the parameters to the run_regression_tests.py call
* removed Azure authentication method from run_regression_tests.py
* removed Azure authentication method from run_regression_tests.py
* force lowercase env name
* use PAT token for now
* use PAT token for now
* Try to use standard GITHUB_TOKEN again
* Go back to PAT
* script works once the token issue is resolved
* try access token directly instead of exporting to variable
* rename env variable to TESTS_TOKEN
* print out TESTS_TOKEN
* use default github token
* try PAT again
* testing if i can retrieve a different secret
* using with: instead of env:
* using with: instead of env:
* call secret in workflow_call:
* inherit secrets
* attempt at caching of poetry packages
* remove inputs from workflow temporarily to avoid confusion
* remove requirement for review to deploy
* rename
* rename
* revert everything back to normal behaviour
* comment out deployment of test to test the workflow still works with venv caching
* fixed pr_label NoneType error
* use the Python version from .tool-versions
* use the Python version from .tool-versions. rename to take out the redundant word "run"
* take out ==
* fix the python version grab
* restored deploy to test workflow to its former glory
* remove stated permissions (not sure if they're needed)
* remove stated permissions (not sure if they're needed)
* moved the regression tests from a separate job to a step of the deploy job
* Maybe we don't need to inherit secrets if it's not a separate job?
* move regression tests from being a separate job to being a step in the deploy process
* returned secrets: {} to base-deploy.yml
0 commit comments