Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[6.15.z] - preserving PRT result as part of github comment & PRT pass/fail label… #14057

Conversation

omkarkhatavkar
Copy link

Cherrypick of PR: #13979

Problem Statement

Currently, the PRT result gets clean after a new commit and there is no way for PR to know what happened with the result. PRT passed/failed labels also need to be added automatically this helps in reviewing the PR quickly and merging them

Solution

Add the dispatch workflow that takes care of this thing from the Jenkins CI update the GitHub comment with all details and apply the filter.

Testing

I was able to test this on the my fork of robottelo here https://github.com/omkarkhatavkar/robottelo/actions/runs/7755989443/job/21152444058

…SatelliteQE#13979)

preserving the PRT result as part of github comment & PRT pass/fail label
@omkarkhatavkar omkarkhatavkar requested a review from a team as a code owner February 13, 2024 12:29
@omkarkhatavkar omkarkhatavkar added No-CherryPick PR doesnt need CherryPick to previous branches 6.15.z Introduced in or relating directly to Satellite 6.15 labels Feb 13, 2024
@omkarkhatavkar omkarkhatavkar changed the title preserving PRT result as part of github comment & PRT pass/fail label… [6.15.z] - preserving PRT result as part of github comment & PRT pass/fail label… Feb 13, 2024
@Gauravtalreja1 Gauravtalreja1 merged commit 276a1fc into SatelliteQE:6.15.z Feb 13, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.15.z Introduced in or relating directly to Satellite 6.15 No-CherryPick PR doesnt need CherryPick to previous branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants