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.

Sign up for GitHub

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

Jump to bottom

Tests: Fix discovery test #1695

Merged
merged 1 commit into from
Sep 11, 2023
Merged

Tests: Fix discovery test #1695

merged 1 commit into from
Sep 11, 2023

Conversation

radtriste
Copy link
Contributor

Many thanks for submitting your Pull Request ❤️!

Please make sure your PR meets the following requirements:

  • You have read the contributors guide
  • Pull Request title is properly formatted: [KOGITO|RHPAM-XYZ] Subject
  • Pull Request contains link to the JIRA issue
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
  • Your feature/bug fix has a testcase that verifies it
  • You've tested the new feature/bug fix in an actual OpenShift cluster
  • You've added a RELEASE_NOTES.md entry regarding this change
How to retest this PR or trigger a specific build:

  • (Re)run Jenkins tests
    Please add comment: Jenkins [test|retest] this

  • Prod tests
    Please add comment: Jenkins (re)run [prod|Prod|PROD]

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@radtriste radtriste marked this pull request as ready for review September 8, 2023 08:47
@radtriste radtriste requested a review from spolti September 8, 2023 08:47
@radtriste
Copy link
Contributor Author

continuous-integration/jenkins/pr-merge and continuous-integration/jenkins/branch can be ignored for now

@spolti spolti merged commit ee5de39 into main Sep 11, 2023
@spolti spolti deleted the fix_discovery_test branch September 11, 2023 14:51
github-actions bot pushed a commit that referenced this pull request Sep 11, 2023
@radtriste
Tests: Fix discovery test (#1695)
48e69f0
@github-actions github-actions bot mentioned this pull request Sep 11, 2023
Closed
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@spolti spolti spolti approved these changes

Assignees
No one assigned
Labels
backport-1.44.x
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@radtriste @spolti