Closed clbarrell closed 6 months ago
Hi @clbarrell I created a PR https://github.com/buildkite/templates/pull/39 to make this Gatsby template scoped to CI only. The commit suggestions I was making are becoming unwieldy so a PR into this branch would be easier.
In #39 I kept the focus on CI, removed the build command and running only Jest and ESLint.
Secondly, I added the cache plugin and updated the README with more config steps.
Why no build command?
The user's cloud provider will run build during deployment. A good step to make it real for the user would be a deployment workflow to a cloud provider.
If we want to introduce CD, a good use case would be to integrate with the most popular cloud provider option like Netlify, Gatsby's preferred provider.
For this PR I think it's preferable to keep the scope to CI only, and explore other potential options after v1.
As discussed this morning, let's park Gatsby for now and focus on CI for languages first, because the nodejs-ci covers Gatsby's CI use cases.
When you come back to this one, hit me up and we can look at rebasing this branch to clean up the history a little.
As per comments above, I'm going to close this one and we can come back to it later.
Needs checking and editing.
Anyone is free to take this over and complete it.