Skip to content

add support for specifying alternate cvmfs-config package to install via $INPUT_CVMFS_CONFIG_PACKAGE #1

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

Merged
merged 3 commits into from
Dec 15, 2020

Conversation

boegel
Copy link
Contributor

@boegel boegel commented Nov 10, 2020

@wdconinc I didn't test this, but I expect this to work since it's very similar to the other ${INPUT_CVMFS...} input variables.

This should allow use to install our own cvmfs-config-eessi package (see https://github.com/EESSI/filesystem-layer/releases).

@boegel
Copy link
Contributor Author

boegel commented Nov 10, 2020

@wdconinc If you would like to see this change covered by a test, let me know, I can look into that (using cvmfs-config-eessi, I guess).

@boegel
Copy link
Contributor Author

boegel commented Nov 10, 2020

@wdconinc I'm not sure why the test I added is failing... Am I overlooking something?

@bedroge
Copy link

bedroge commented Nov 11, 2020

@boegel it looks like the INPUT_* variables are still set to their default values. Maybe it's related to this issue: actions/runner#665?

@wdconinc wdconinc merged commit 7fe2558 into cvmfs-contrib:main Dec 15, 2020
@boegel boegel deleted the INPUT_CVMFS_CONFIG_PACKAGE branch December 15, 2020 18:09
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

Successfully merging this pull request may close these issues.

3 participants