-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downstream testing trial #744
base: dev
Are you sure you want to change the base?
Conversation
18170d6
to
d40d72f
Compare
…sonal access token this will fail
…ondition ("if pullrequest") for testing. revert this later
a010e82
to
3177a48
Compare
3177a48
to
ede8780
Compare
I think we can merge this, the largest change are the docker-compose files but a restructuring here is probably needed for the ory change because this will add a number of components that need to be launched to run MP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and one comment added.
Also, I know this falls outside this PR's scope but probably worth noting: Postgres 11 has reached its EOL.
managementportal-postgresql: | ||
extends: | ||
file: ../postgresql.yml | ||
service: managementportal-postgresql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The service has been renamed to postgresql
in ../postgresql.yml
.
Is this "non_mp" compose file intended for all devs? If yes, it would be nicer to have an example showing how to use it.
The most important changes here are the ones in main.yml, the rest is probably redundant when you update the base |
Description: Added a github action which, on merging a branch into dev/master triggers downstream tests agains the built docker image
An alternative way to do this would be to pull the downstream repo and run the tests, but this seems more messy. It does however keep any failing pipelines close to the source (in this case, the changes to management portal)
Checklist: