feat(ci): change the env variables for AMF (MR 169)
Thinh changed the way NRF is handled in AMF
See https://gitlab.eurecom.fr/oai/cn5g/oai-cn5g-amf/-/merge_requests/169
Merge request reports
Activity
requested review from @tien-thinh.nguyen
assigned to @arora
added 1 commit
- 86ea42a4 - fix(ci): testing a mounted strategy for AMF in slicing scenario
mentioned in merge request oai-cn5g-amf!169 (closed)
- Resolved by Raphael Defosseux
@defosseu This will create confusion for readers. I say either we mount for all or none.
I understand if we start mounting for every tutorial we will have hundreds of configuration files. So we need to fix the docker-compose parameters.
added 3 commits
-
86ea42a4...f34dc0ee - 2 commits from branch
master
- 5287370f - Merge remote-tracking branch 'origin/master' into ci-amf-pr-169-fixes
-
86ea42a4...f34dc0ee - 2 commits from branch
added 1 commit
- 4248365c - feat(ci): change the env variables for AMF (MR 169)
Passing now:
https://jenkins-oai.eurecom.fr/job/OAI-CN5G-Tutorials-Check-Dev/13/artifact/test_results_oai_cn5g_tutorials.html
181 181 - OPERATOR_KEY=63bfa50ee6523365ff14c1f45f88737d @defosseu Can we remove the
OPERATOR_KEY
field from all the docker-compose files. It is not useful anymore. @tien-thinh.nguyen Correct me if I am wrong.Edited by Sagar Arora
removed v1.5 label
added v2.0 label