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

githubWorkflowUseSbtThinClient should default to false due to current issues #74

Closed
mdedetrich opened this issue Jul 13, 2021 · 6 comments

Comments

@mdedetrich
Copy link
Contributor

mdedetrich commented Jul 13, 2021

This is more of a suggestion but it seems like a lot of people are having problems with sbt's thin client mode (see sbt/sbt#6468). An issue I just found is that currently when SBT runs with --client it ignores all environment variables which makes the env field for WorkflowStep.Sbt not even work (you can see the PR at iheartradio/ficus#155 where I had to set this to false because sbt-coveralls cannot even pick up the env vars)

My suggestion would be to set it completely to false until the problems with a new SBT release.

@armanbilge
Copy link
Contributor

@mdedetrich
Copy link
Contributor Author

@djspiewak Shall I close the issue or do you want me to leave it open?

@armanbilge
Copy link
Contributor

@mdedetrich pretty sure this will be addressed, lots of projects are making this change including typelevel/cats-effect#2150 (comment).

@djspiewak
Copy link
Collaborator

Ah, didn't realize it wasn't linked. This is fixed in main and will be released soon

@yanns
Copy link

yanns commented Oct 27, 2021

https://github.com/djspiewak/sbt-github-actions still documents the following:

githubWorkflowUseSbtThinClient : Boolean – [...] (default: true for sbt ≥ 1.4, false otherwise)

Is it still true?

@mdedetrich
Copy link
Contributor Author

@yanns I think you are right, just made a PR for it here #101

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

No branches or pull requests

4 participants