Fix deploy job; use absolute path for HOME #175
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pulled out the smaller changes from #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.