Set HOME to an absolute path, env.WORKSPACE, rather than a relative ., which is needed for both the docker bind mounting to work correctly, and the serverless-python-requirements plugin correctly include Python packages in the zip file.
Add docs for how the deploy job works
Add verbose logging since the plugin hides the actual error on failures. Now you should be able to see the docker run command:
Pulled out the smaller changes from https://github.com/rstudio/r-builds/pull/171 to fix the deploy job with the existing docker inside docker packager:
env.WORKSPACE
, rather than a relative.
, which is needed for both the docker bind mounting to work correctly, and the serverless-python-requirements plugin correctly include Python packages in the zip file..cache
/.npm
generated files that didn't need to be in the serverless packageI just tested this again to be sure at https://build.posit.it/blue/organizations/jenkins/r-builds%2Fdeploy-r-builds/detail/deploy-r-builds/202/pipeline/, and confirmed that staging builds still work.