Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove redundant deploy steps #1377

Closed
ElijahLynn opened this issue Apr 1, 2020 · 6 comments
Closed

Remove redundant deploy steps #1377

ElijahLynn opened this issue Apr 1, 2020 · 6 comments
Labels
DevOps CMS team practice area

Comments

@ElijahLynn
Copy link
Contributor

Follow up of #1303

Remove redundant deploy steps (cache:rebuild, updatedb, config:import) from ansible/deployment/config/cms/tasks/post-init-tasks.yml and ansible/deployment/config/cms/tasks/post-init-tasks-prod.yml because it is being run twice now, the second time being in the deploy/* section of tests.yaml.
@ElijahLynn ElijahLynn added the DevOps CMS team practice area label Apr 1, 2020
@jonpugh jonpugh mentioned this issue Apr 1, 2020
Closed
5 tasks
@cmaeng cmaeng added Infrastructure Objective 1 2020: Develop CMS infrastructure for evolving API, e2e testing and demo needs. and removed Infrastructure Objective 1 2020: Develop CMS infrastructure for evolving API, e2e testing and demo needs. labels Sep 15, 2020
@indytechcook
Copy link
Contributor

@ElijahLynn @olivereri is this still an issue with the #2494

@ElijahLynn
Copy link
Contributor Author

I think it is still run twice, and we need to update the BRD test run now to pass a filter to not run those for the yaml-tests.

@ElijahLynn
Copy link
Contributor Author

ElijahLynn commented Dec 15, 2020 •
edited by oksana-c

Now that we are half moved off of DevShop I think this should be updated to run drush deploy once we upgrade to Drush 10, #3868 .

@ElijahLynn
Copy link
Contributor Author

We should do #3904 first and see if this is still needed.

@oksana-c
Copy link
Contributor

@ElijahLynn what was the conclusion after completing #3904 ^^? Do we still need to keep this story open?

@ElijahLynn
Copy link
Contributor Author

Yeah, this is done now, in #3904.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
DevOps CMS team practice area
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@indytechcook @ElijahLynn @oksana-c @cmaeng