Update to add possibilty to have same container in the same site.yml #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My 3 modifications in run.ymal.j2
1°) To have the possibility of having the same container several times, I added the “num” field.
This field makes it possible to distinguish each container.
The field value is used in the name of the jobs and can therefore be used to identify the function of the job.
In the attached file, a job that launches the onboarding of several packages
Excerpt from this job:
- container: eri_5gc_vnf-onboard
db_project: eri_5gc_vnf-onboard
number: CCRC1.1
docker_args:
approx:
TARGET: CCRC
VNF_VERSION: V1.1
In this example, I put num: CCRC1.1 which allows me by reading the name of the jobs concerned to see that it concerns CCRC V1.1.
This gives as job name: 22_PACKAGE_ONBOARDING-CCRC1.1-127.0.0.1-eri_5gc_vnf-onboard-1.0.2-check_not_onboarded-run
2°) I also added in the template, the fact of having for each suite, the docker_args variables of the common part added to the docker_args of the suite
For your information, before in Cédric's template, only the docker_args of the suite are taken if existing, otherwise it is only those of the common part.
With my modifications, the variables below from the common part of my example are propagated in each job
docker_args:
approx:
VERBOSE: _OFF
PLATFORM: VIAAS
EVNFM_NAME: EVNFM1
3°) To be able to position the following options in multijob of jenkins, I added the management of test_properties.
tests_properties:
abort-all-job: true
aggregate-results: true
kill-phase-on: UNSTABLE
These options of a jenkins multijob are useful to determine the behavior of a scenario in case of error
Thanks
Dominique