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

Should the single ci command alias be split into multiple workflow steps? #60

Closed
armanbilge opened this issue Jan 9, 2022 · 1 comment · Fixed by #65
Closed

Should the single ci command alias be split into multiple workflow steps? #60

armanbilge opened this issue Jan 9, 2022 · 1 comment · Fixed by #65
Labels
Milestone

Comments

@armanbilge
Copy link
Member

Spinning out of http4s/sbt-http4s-org#120 (comment).

This is a pattern I adopted from sbt-spiewak, but it obviously has tradeoffs.

Pros:

  • a single command, that in theory you can run locally to emulate CI
  • works well when split into ciJVM, ciJS, etc.
  • doesn't have to restart sbt for each step

Cons:

  • harder to see on what step a build fails
  • difficult to progressively build up the commands in the alias, or remove stuff
  • sometimes, restarting sbt is actually a good thing
@armanbilge
Copy link
Member Author

I think fixing #61 would make it feasible to split CI into separate steps while being friendly to platform-crossed-matrices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant