Skip to content

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