Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix one issue at the time.
The pull request must update the test suite to demonstrate the changed functionality.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.
What does this PR do?
Adds fallback behaviour to the logic that populates job name, job base name and build tag:
If job name could not be populated, JOB_NAME is used to fill it
If job base name could not be populated, JOB_BASE_NAME (or JOB_NAME if base name is not available) is used to fill it
If build tag could not be populated, concatenation of jenkins-${JOB_NAME}-${BUILD_NUMBER} is used to fill it
CI Visibility backend requires these values to be non-empty. If any of them is not provided, corresponding events will be dropped.
Description of the Change
Alternate Designs
Possible Drawbacks
Verification Process
The new logic is covered with unit tests.
Additional Notes
Release Notes
Review checklist (to be filled by reviewers)
[ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[ ] PR should not have do-not-merge/ label attached.
[ ] If Applicable, issue must have kind/ and severity/ labels attached at least.
Requirements for Contributing to this repository
What does this PR do?
Adds fallback behaviour to the logic that populates job name, job base name and build tag:
JOB_NAMEis used to fill itJOB_BASE_NAME(orJOB_NAMEif base name is not available) is used to fill itjenkins-${JOB_NAME}-${BUILD_NUMBER}is used to fill itCI Visibility backend requires these values to be non-empty. If any of them is not provided, corresponding events will be dropped.
Description of the Change
Alternate Designs
Possible Drawbacks
Verification Process
The new logic is covered with unit tests.
Additional Notes
Release Notes
Review checklist (to be filled by reviewers)
changelog/label attached. If applicable it should have thebackward-incompatiblelabel attached.do-not-merge/label attached.kind/andseverity/labels attached at least.