Closed a-t-0 closed 2 years ago
[x] Improve verbosity of functions.
[x] Check where the build status is retrieved.
[x] Check what the timeout is.
[x] Check whether build statusses should be pushed.
[x] CHeck whether the build statusses are pushed.
Next up: improve verbosity of: push_commit_build_status_in_github_status_repo_to_github
(push_commit_build_status_in_github_status_repo_to_github)
works properly.Write:
#######################################
# Loops over all the commit build status txts in the GitHub repository with the
# GitLab build statusses, and deletes all the txts with invalid build statusses.
# Then removes those from BOTH evaluated lists. And adds them to a "erroneous"
# list.
#
# Local variables:
#
# Globals:
#
# Arguments:
#
# Returns:
# 0 If function was evaluated succesfull.
# Outputs:
#
#######################################
# Run with:
# bash -c "source src/import.sh src/CI/call_CI/verify_build_statusses_are_valid.sh && assert_commit_build_status_txt_is_valid
delete_invalid_commit_txts(){
echo "pass"
}
And then complete the remainder of the asserts, and implement those asserts to throw an error on invalid build statusses.
The code seems to not take enough time to wait until a CI build result is obtained.
Make sure it does wait and ensure the results are passed to the build status correctly.