Too many ways to start dev pieces

[tiberiuichim]

[tiberiuichim]

We have to do something, it's annoying.

Some ideas:

• split into multiple flavours of makefile: some that use only dockers, some that use only buildout / "real plone"
• use better names. "plone" instead of "backend", "cypress", "volto" rather then frontend
• ...

[stevepiercy]

@tiberiuichim the Makefile has grown.

$ make help
build-backend                  Build Plone 5.2
docs-clean                     Clean current and legacy docs build directories, and Python virtual environment
docs-html                      Build html
docs-linkcheck                 Run linkcheck
docs-linkcheckbroken           Run linkcheck and show only broken links
docs-livehtml                  Rebuild Sphinx documentation on changes, with live-reload in the browser
docs-news                      Create or update the symlink from docs to volto package
docs-test                      Clean docs build, then run linkcheckbroken, vale
docs-vale                      Install (once) and run Vale style, grammar, and spell checks
full-test-acceptance-coresandbox Runs CoreSandbox Full Acceptance Testing in headless mode
full-test-acceptance-guillotina Runs the Guillotina Full Acceptance Testing in headless mode
full-test-acceptance-multilingual Runs Multilingual Full Acceptance Testing in headless mode
full-test-acceptance-seamless-multilingual Runs Seamless Multilingual Full Acceptance Testing in headless mode
full-test-acceptance-seamless  Runs Seamless Core Full Acceptance Testing in headless mode
full-test-acceptance-workingcopy Runs WorkingCopy Full Acceptance Testing in headless mode
full-test-acceptance           Runs Core Full Acceptance Testing in headless mode
help                           This help message
start-backend                  Start Plone Backend
start-test-acceptance-frontend-coresandbox-dev Start the CoreSandbox Acceptance Frontend Fixture in dev mode
start-test-acceptance-frontend-coresandbox Start the CoreSandbox Acceptance Frontend Fixture
start-test-acceptance-frontend-dev Start the Core Acceptance Frontend Fixture in dev mode
start-test-acceptance-frontend-guillotina Start the Guillotina Acceptance Frontend Fixture
start-test-acceptance-frontend-multilingual Start the Multilingual Acceptance Frontend Fixture
start-test-acceptance-frontend-project Start the Project Acceptance Frontend Fixture
start-test-acceptance-frontend-seamless-multilingual Start the Seamless Multilingual Acceptance Frontend Fixture
start-test-acceptance-frontend-seamless Start the Seamless Core Acceptance Frontend Fixture
start-test-acceptance-frontend-workingcopy Start the WorkingCopy Acceptance Frontend Fixture
start-test-acceptance-frontend Start the Core Acceptance Frontend Fixture
start-test-acceptance-server-detached Start Test Acceptance Server Main Fixture (docker container) in a detached (daemon) mode
start-test-acceptance-server-guillotina Start Guillotina Test Acceptance Server (docker container)
start-test-acceptance-webserver-seamless Start the seamless webserver
test-acceptance-coresandbox-headless Start CoreSandbox Cypress Acceptance Tests in headless mode
test-acceptance-coresandbox    Start CoreSandbox Cypress Acceptance Tests
test-acceptance-guillotina-headless Start the Guillotina Cypress Acceptance Tests in headless mode
test-acceptance-guillotina     Start the Guillotina Cypress Acceptance Tests
test-acceptance-headless       Start Core Cypress Acceptance Tests in headless mode
test-acceptance-multilingual-headless Start Multilingual Cypress Acceptance Tests in headless mode
test-acceptance-multilingual   Start Multilingual Cypress Acceptance Tests
test-acceptance-seamless-multilingual-headless Start Seamless Multilingual Cypress Acceptance Tests in headless mode
test-acceptance-seamless-multilingual Start Seamless Multilingual Cypress Acceptance Tests
test-acceptance-seamless       Start Seamless Cypress Acceptance Tests
test-acceptance-workingcopy-headless Start WorkingCopy Cypress Acceptance Tests in headless mode
test-acceptance-workingcopy    Start WorkingCopy Cypress Acceptance Tests
test-acceptance                Start Core Cypress Acceptance Tests

docs-* are good.

I don't know about the rest. What do you suggest?

[davisagli]

The main problem here seems to be the proliferation of commands for starting different variations of the acceptance tests. Maybe it would help to create a wrapper script so there is one command that can be called with different parameters to start the acceptance tests? In a way that would just be hiding the complexity that still remains, but at least it would be organized a bit more clearly?