search

SAP / project-piper-action

CI/CD tooling for the SAP Ecosystem, integrated with GitHub Actions
39 stars 15 forks source link

Make the piper binary location an input parameter #206

Open blackhatcrazy opened 1 month ago

blackhatcrazy commented 1 month ago

Currently the piper binary is downloaded to the fixed location ${process.cwd()}/${version}/${piperBinaryName} as seen here.

This causes problems when using this action in combination with act to run a piper-step locally.

Please allow for an alternative path configuration input for the action.

milkotodorov commented 1 month ago

I've made a PR for the same purpose: https://github.com/SAP/project-piper-action/pull/204 This way it should work locally. Waiting to be merged.

milkotodorov commented 1 month ago

You can use as follows in your github actions yaml to do a local compilation of piper:

with:
  piper-version: 'devel:SAP:jenkins-library:<version_or_commit_hash>'

That works as workaround too.