Commit c9f8271c authored by Jan Kiene's avatar Jan Kiene
Browse files

change strict mode on scripts

parent 131f6fa9

snippets/basop/branch-follows-porting-naming-convention.sh

+2 −0
Original line number Diff line number Diff line
@@ -28,6 +28,8 @@ 
# accordance with the laws of the Federal Republic of Germany excluding its conflict of law rules and

# the United Nations Convention on Contracts on the International Sales of Goods.



set -euo pipefail



BASOP_PATTERN="^[0-9]+[_-]basop[_-].*"

MSG_DOES_NOT_MATCH="Your branch name %s does not match the template '<issue_number>_basop_<description>', e.g. '123_basop_fix_this_one_bug-2'.

If this branch is porting a float MR with a corresponding float part, then

snippets/basop/check-float-ref-companion-branch-exists-for-porting-merge-requests.sh

+2 −2
Original line number Diff line number Diff line
@@ -28,7 +28,7 @@ 
# accordance with the laws of the Federal Republic of Germany excluding its conflict of law rules and

# the United Nations Convention on Contracts on the International Sales of Goods.



set -uxo pipefail

set -euo pipefail



MSG_NO_FLOAT_REF_BRANCH_FOUND="Your branch name %s looks like it is a porting MR, but there is no corresponding float merge request (%s).

If this is intended (nothing to port to ivas-float-update), simply ignore this warning.
@@ -38,7 +38,7 @@ If there should be a float ref branch for this MR, please check your spelling on 


bash "${CI_PROJECT_DIR}"/ivas-codec-ci/snippets/basop/update-scripts-repo.sh

exit_code_is_porting_mr=0

bash "${CI_PROJECT_DIR}"/ivas-codec-ci/snippets/basop/branch-follows-porting-naming-convention.sh $CI_COMMIT_REF_NAME | exit_code_is_porting_mr=$?

bash "${CI_PROJECT_DIR}"/ivas-codec-ci/snippets/basop/branch-follows-porting-naming-convention.sh "$CI_COMMIT_REF_NAME" | exit_code_is_porting_mr=$?



# if this does not look like a porting branch, finish with success here - no need to check for a float companion

if [ "$exit_code_is_porting_mr" == "1" ]; then