Fix #8809

[aspiringmind-code]

See #8809

• Remove CHECK_TEST_RESULT variable to make it easier to understand and streamlining
• Make the pipeline more robust using rules like skip_check and skip_submit
• Now we only need to set three variables: SUBMIT_STATUS_TRACKING, CLIENT_CONFIGURATION_VALIDATION and CLIENT_VALIDATION_SUITE for both task submission and checking of their respective actions. By default, they are all set to true.
• We additionally have three skip variables SKIP_BUILD, SKIP_DEPLOY and SKIP_SUBMIT which can be used if so desired. By default they are all set to false.

[cmsdmwmbot]

Jenkins results:

• Python3 Pylint check: succeeded
• Pycodestyle check: succeeded

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-CRABServer-PR-test/2321/artifact/artifacts/PullRequestReport.html

[belforte]

Now we only need to set three variables: SUBMIT_STATUS_TRACKING, CLIENT_CONFIGURATION_VALIDATION and CLIENT_VALIDATION_SUIT

should SUBMIT_ be removed from the name of the first variable then, for consistency ? Same for _SUIT in the last.

[belforte]

thanks Vijay, I agree with plan in the top bullet list, but am not able to relate it to the code. Can we have a sort of walk-through ?

[aspiringmind-code]

Yes, sure

[cmsdmwmbot]

Jenkins results:

• Python3 Pylint check: succeeded
• Pycodestyle check: succeeded

Details at https://cmssdt.cern.ch/dmwm-jenkins/view/All/job/DMWM-CRABServer-PR-test/2322/artifact/artifacts/PullRequestReport.html

[sinonkt]

It's looks good to me! Thanks!

[belforte]

very good