# These path variables are used by the pytest calls.
# They can be overwritten in the job templates to e.g. only test encoder or decoder in the chain
### These path variables are used by the pytest calls.
### They can be overwritten in the job definitions in the variables: section to e.g. only test encoder or decoder in the chain
### E.g. a job that tests the BASOP encoder against the float ref via MLD etc. would overwrite DUT_DECODER_PATH with REF_DECODER_PATH in its variables: section
# "DUT_" - used in merge request pipelines for the branch build (Device Under Test)
DUT_ENCODER_PATH:"./IVAS_cod_dut"
DUT_DECODER_PATH:"./IVAS_dec_dut"
DUT_RENDERER_PATH:"./IVAS_rend_dut"
DUT_POST_RENDERER_PATH:"./ISAR_post_rend_dut"
# "REF_" - used in merge request regression jobs for the floating-point ref (ivas-codec main)
REF_ENCODER_PATH:"./IVAS_cod_ref"
REF_DECODER_PATH:"./IVAS_dec_ref"
REF_RENDERER_PATH:"./IVAS_rend_ref"
REF_POST_RENDERER_PATH:"./ISAR_post_rend_ref"
# "MERGE_TARGET_" - used in merge request jobs to denote the build from the target branch (mostly main)
# "MERGE_SOURCE_FLOAT_REF_" - used for the respective float reference branch of an MR. Can be main or the respective companion branch in ivas-codec repo