- Issue created by @alexdmccabe
- πΊπΈUnited States jdleonard Austin, TX, USA
Would it make sense to parallelize the "test" stage next to the "build" stage (and have "deploy" stage dependent on the other two)? Won't make much difference for a while, but in theory? Also wonder whether "build" should be "build-docs" and "deploy" should be "deploy-docs" given we will eventually have other tasks that could probably be performed in parallel. I'm undoubtedly over-optimizing...
- πΊπΈUnited States bluegeek9
I updated the pipeline to use the Drupal template. If mkdocs.yml exists pages will be built and deployed, but only when the branch is the default. MR will not build or deploy pages.
- πΊπΈUnited States jdleonard Austin, TX, USA
Thanks for this @bluegeek9!
Two notes:
- Work was previously done to explicitly build mkdocs pages in MRs so that changes to docs can be QA'd. Is there a way to restore that capability with your changes?
- This is a meta issue so work should be performed in child issues, but not here. Would you please create a new child issue to capture the changes you are proposing?
Setting status to Active for this meta issue.
- πΊπΈUnited States jdleonard Austin, TX, USA
jdleonard β changed the visibility of the branch 3515999-meta-improve-cicd to hidden.