OutOfMemory in Github Actions run

[pjfanning]

Thanks for the work on this great project. I'm using sbt-ci-release alongside sbt-github-actions.

I have an issue where the Github Actions publish step that runs sbt ci-release runs out of memory. I'd appreciate some advice on how to solve this. Github Actions seems to be running in a VM that allows sbt about 1Gb heap and this doesn't appear to be enough for my use case.

https://github.com/FasterXML/jackson-module-scala/runs/3673951099?check_suite_focus=true

https://github.com/FasterXML/jackson-module-scala/blob/2.13/.github/workflows/ci.yml#L66 (generated publish step)

• the publish step retrieves the previously built jars (from the build steps) - there are 4 scala versions supported
• sbt ci-release still tries to rebuild the jars that need publishing - 2.11 and 2.12 are built but the OOM happens during the 2.13 build
• is there any way to get sbt-ci-release to just use the jars from the tgz files that it has retrieved to avoid the expensive rebuild of the jars?
• I suspect that I should hand edit the generated ci.yml to do 4 separate sbt ci-release calls, 1 per scala version supported
• is it worth trying to set SBT_OPTS with higher Xmx in the hope that this might work?
• any other suggestions would be appreciated

[pjfanning]

I added this to my build.sbt - ThisBuild / githubWorkflowSbtCommand := "sbt -J-Xmx2G" and this fixed the issue.

I suspect the reason that ci-release needs to rebuild the jars is to sign them - the ci-release job was not failing for snapshot release - only for full releases.