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

Run SBT in batch mode #126

Merged
merged 1 commit into from
Sep 4, 2023
Merged

Run SBT in batch mode #126

merged 1 commit into from
Sep 4, 2023

Conversation

rossabaker
Copy link
Contributor

If an SBT project definition doesn't load, the build hangs on the SBT retry prompt, until it times out after a default six hours. cli.exec doesn't detect that SBT isn't running in an interactive terminal, so we explicitly set it to --batch mode.

Copy link
Member

@adpi2 adpi2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@rossabaker
Copy link
Contributor Author

I'm not sure why so many tests failed. I have a green build in my fork that I'd be happy to cherry-pick into more PRs. I think the only "bad" commit on my branch is 3262895.

@adpi2
Copy link
Member

adpi2 commented Sep 4, 2023

I'm not sure why so many tests failed.

The tests fail because your Github profile does not have the right to submit dependencies in this repo. (I should probably deactivate those tests in PRs).

Let's see if they pass after merging.

@adpi2 adpi2 merged commit dc1a36e into scalacenter:main Sep 4, 2023
1 of 13 checks passed
@rossabaker
Copy link
Contributor Author

I got past the dynver handshake issue that's still failing by upgrading sbt-ci-release: rossabaker@f66d97b. I didn't pursue the Windows error.

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

Successfully merging this pull request may close these issues.

2 participants