Christian Schweikert
Christian Schweikert
Hm, builds are failing. Doesn't find all of the dependencies yet. Maybe because Node.js 18 was released only a week ago. I'll try again later and keep you posted.
@braisvq1996 good point. Does anything speak against moving on to Centos/RHEL 8? Like already mentioned in one of the discussions above I have no clue about the implications of this...
@braisvq1996 thanks finishing this one ❤️
I like the idea :) What I'm not so sure of is the way the ``userParams`` parameter can be stored and made accessible on the ``context`` object during both situations:...
Just on more thought on this: If we keep the param config as part of the QS code, the QS remains "portable". What do I mean by portability? Let's imagine...
LGTM One more thought on the proposed solution: What is holding us back from actually using those images directly from dockerhub instead of building them into the respective image streams...
Ah, nice. Will have a look. @stitakis When I get you correctly the plan for publishing on dockerhub is not just for running the ODS e2e tests, but to also...
@ManuelFeller : big thanks for bringing light into this topic regarding `.npmrc` files with environment variables or the yarn issue: what about (re-)creating the ``.npmrc`` file during builds like this:...
Will a ``.env`` file be taken into consideration by ``npm`` or ``sh`` automatically? When it comes to nodejs you usually need to read out a ``.env`` file with an explicit...