-
Notifications
You must be signed in to change notification settings - Fork 14
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
Speed up ci:reset by passing along a pre-built DB. #1629
Conversation
9868b68
to
2eb1770
Compare
2eb1770
to
262d9f3
Compare
d1af573
to
bfc848e
Compare
bfc848e
to
70aa795
Compare
70aa795
to
21428b9
Compare
21428b9
to
a466ef2
Compare
a466ef2
to
5c688e2
Compare
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.
It is a bit difficult to wrap my head around what is happening here.
I get the concept of resusing af prebulit db, but dont undestand how it is effectuated here.
A have some more questions that it would be nice if you take a look at.
@@ -382,7 +386,9 @@ tasks: | |||
ci:reset: | |||
desc: Create CI setup in a clean state | |||
cmds: | |||
- task dev:reset | |||
- task dev:reset:common | |||
- task dev:cli -- drush sqlq --file=../tools/site-reset.sql.gz |
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.
What is contained in site-reset.sql.gz?
It would be nice if it was documented somewhere what is happening here
@@ -125,8 +125,8 @@ tasks: | |||
cmds: | |||
- docker compose {{ .DOCKER_COMPOSE_FILES }} pull | |||
|
|||
dev:reset: | |||
desc: Create local development setup in a clean state | |||
dev:reset:common: |
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.
What is the purpose of dev:reset:common? Would be nice to have in the description what the intention is.
Also consider which of the newly introduced dev:rest* cmds private so it is clear what is meant to be run as seprate task cmds and what is used internally
This speeds up the CI actions, spending ~2 minute instead of ~4 minutes on just setting up the basic site.
Ideally, we could speed it up even more by somehow caching the result of
docker compose {{ .DOCKER_COMPOSE_FILES }} pull
, but I could not get it working.If we managed to get that working, I think we could get it all the way down to 30 seconds.