this implements the approach suggested by @boegel in the issue: if the filter is specified in a comment, file bot/export_vars.sh is created and sourced before running the bot/build.sh script
notes:
as is the case with other filters, spaces or colons cannot be used
variables have to be specified one by one, which was easier to implement and avoids having to specify another delimiter, which then also cannot be used
i used filter name exportvariable instead of the suggested build_env to avoid confusion with other uses of build_env in the code.
added an allowlist of name-value pairs (allowed_exportvars) to app.cfg for increased security. each name-value pair specified in a PR comment must be listed in the allowlist in order to run a build job.
fixes https://github.com/EESSI/eessi-bot-software-layer/issues/281
this implements the approach suggested by @boegel in the issue: if the filter is specified in a comment, file
bot/export_vars.shis created and sourced before running thebot/build.shscriptnotes:
exportvariableinstead of the suggestedbuild_envto avoid confusion with other uses of build_env in the code.example usage:
UPDATE 2024-11-23
allowed_exportvars) toapp.cfgfor increased security. each name-value pair specified in a PR comment must be listed in the allowlist in order to run a build job.export_vars.shscript to thecfgdir