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.

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

Decide on CircleCI template features #24

Open
benlinton opened this issue Jul 31, 2018 · 0 comments
Open

Decide on CircleCI template features #24

benlinton opened this issue Jul 31, 2018 · 0 comments

Comments

@benlinton
Copy link
Contributor

benlinton commented Jul 31, 2018

We should come to a consensus on features that we want to support for our default default CircleCI v2 template.

Options include

  • ruby
  • mysql
  • postgres
  • redis
  • yarn / node
  • default end-to-end testing framework (cypress, teaspoon, or other)
  • imagemagick
  • ...more

Additional questions

  • Do we want to support optional workflows?
  • What is the easiest way to maintain this over time?
  • How do we avoid conditional spaghetti code in our template?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant