Skip to content
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

Make the piper binary location an input parameter #206

Open
blackhatcrazy opened this issue Jul 11, 2024 · 2 comments
Open

Make the piper binary location an input parameter #206

blackhatcrazy opened this issue Jul 11, 2024 · 2 comments

Comments

@blackhatcrazy
Copy link

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
Copy link

I've made a PR for the same purpose: #204
This way it should work locally.
Waiting to be merged.

@milkotodorov
Copy link

milkotodorov commented Jul 12, 2024

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.

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

No branches or pull requests

2 participants