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

NO-ISSUE: Add support with marking failed steps #35

Merged

Conversation

eliorerz
Copy link

@eliorerz eliorerz commented May 30, 2024

Sometimes failures are related to the steps they are present in and not related to some specific file or string(e.g. equinix failure or conformance-tests).
This PR added the option to add BugMater actions when step is marked as failed.
After this PR we will need to update the configuration file in openshift-assisted/bugmaster-configurations#16

/cc @gamli75 @danmanor

@openshift-ci openshift-ci bot requested review from danmanor and gamli75 May 30, 2024 10:01
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 30, 2024
@openshift-ci-robot
Copy link

@eliorerz: This pull request explicitly references no jira issue.

In response to this:

Sometimes failures are related to the steps they are present in and not related to some specific file or string(e.g. equinix failure or conformance-tests).
This PR added the option to add BugMater actions when step is marked as failed.
After this PR we will need to update the configuration file

/cc @gamli75 @danmanor

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link

openshift-ci bot commented May 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eliorerz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 30, 2024
@danmanor
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 30, 2024
@danmanor
Copy link

/lgtm

@openshift-merge-bot openshift-merge-bot bot merged commit 036f9a5 into main May 30, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants