Skip to content

Run the community build CI with the correct sbt wrapper #6187

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

Merged
merged 3 commits into from
Mar 29, 2019

Conversation

smarter
Copy link
Member

@smarter smarter commented Mar 28, 2019

In particular, this avoids situations where the JVM goes into
interpreter-only mode because CodeCache is full.

.drone.yml Outdated
@@ -41,7 +41,7 @@ pipeline:
- cp -R . /tmp/3/ && cd /tmp/3/
- git submodule update --init --recursive --jobs 7
- export PATH=/tmp/4/project/scripts:$PATH
Copy link
Contributor

Choose a reason for hiding this comment

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

I thought this export would be enough for drone to pick ./project/scripts/sbt over the default.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah I don't know why that doesn't work.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah, it's the wrong /tmp folder

Copy link
Contributor

Choose a reason for hiding this comment

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

🤦‍♂️

In particular, this avoids situations where the JVM goes into
interpreter-only mode because CodeCache is full.
@smarter smarter force-pushed the community-build-cmd branch from f933576 to 733f84d Compare March 28, 2019 16:14
@smarter smarter force-pushed the community-build-cmd branch 3 times, most recently from 6ef431b to 2730c9a Compare March 28, 2019 17:17
- It didn't work because it looked into /tmp/4/ instead of /tmp/3/
- Fixing that doesn't help, because project/scripts/sbt is not meant to
  be in the PATH: the script will try to run `sbt` to find the real sbt
  launcher, so if it is itself in the PATH we end up with an infinite loop.
@smarter smarter force-pushed the community-build-cmd branch from 2730c9a to 17e78ad Compare March 28, 2019 17:17
@OlivierBlanvillain OlivierBlanvillain merged commit 2a2de2d into scala:master Mar 29, 2019
@allanrenucci allanrenucci deleted the community-build-cmd branch March 29, 2019 10:41
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