You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting BUILD_ARGUMENTS works for developer-oriented builds, such as:
$ DEMO=r-d-r-roofit EXCLUDE_COMPONENTS=r-ui,r-m-broker BUILD_ARGUMENTS="COMPUTE_BACKENDS=htcondorcern,slurmcern,kubernetes" make ci
However it does not work for release builds, so images such as reanahub/reana-job-controller-htcondorcern-slurmcern:0.6.0-31-g35c4fc8 are not having Condor installed.
Three solutions:
manually, as a quick fix, one can do reana-dev docker-build -c r-j-controller -b COMPUTE_BACKENDS=htcondorcern,slurmcern,kubernetes and push this image over the created one;
one permanent solution would be to improve Makefile to make it aware of BUILD_ARGUMENTS to make the fix permanent;
The build arguments have been moved to shell scripts. What remains to be done is the naming of the docker image. This is related to issues #370 and #363. I'll add a comment there and close the issue here.
Setting
BUILD_ARGUMENTS
works for developer-oriented builds, such as:$ DEMO=r-d-r-roofit EXCLUDE_COMPONENTS=r-ui,r-m-broker BUILD_ARGUMENTS="COMPUTE_BACKENDS=htcondorcern,slurmcern,kubernetes" make ci
However it does not work for release builds, so images such as
reanahub/reana-job-controller-htcondorcern-slurmcern:0.6.0-31-g35c4fc8
are not having Condor installed.Three solutions:
manually, as a quick fix, one can do
reana-dev docker-build -c r-j-controller -b COMPUTE_BACKENDS=htcondorcern,slurmcern,kubernetes
and push this image over the created one;one permanent solution would be to improve
Makefile
to make it aware ofBUILD_ARGUMENTS
to make the fix permanent;the other permanent solution would be to address this as part of make: move to shell scripts #304.
The text was updated successfully, but these errors were encountered: