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

OCPBUGS-43925: BuildConfig form breaks on manually enter the Git URL #14449

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lokanandaprabhu
Copy link
Contributor

Fixes:
https://issues.redhat.com/browse/OCPBUGS-43925

Analysis / Root cause:
While getting git type value from fromik value fieldPrefix was not considered

Solution Description:
Updated GitTypeSelector component to consider fieldPrefix while fetching git type

Screen shots / Gifs for design review:

-------- BuildConfig form-----

Screen.Recording.2024-10-30.at.11.11.30.AM.mov

-------- Import from git form-----

Screen.Recording.2024-10-30.at.11.13.24.AM.mov

-------- Create serverless form-----

Screen.Recording.2024-10-30.at.11.14.27.AM.mov

Unit test coverage report:
NA

Test setup:

1. Navigate to Create BuildConfig form page
2. Select source type as Git
3. Enter the git url by typing manually do not paste or select from the suggestion

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 30, 2024
@openshift-ci-robot
Copy link
Contributor

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-43925, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sanketpathak

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Fixes:
https://issues.redhat.com/browse/OCPBUGS-43925

Analysis / Root cause:
While getting git type value from fromik value fieldPrefix was not considered

Solution Description:
Updated GitTypeSelector component to consider fieldPrefix while fetching git type

Screen shots / Gifs for design review:

-------- BuildConfig form-----

Screen.Recording.2024-10-30.at.11.11.30.AM.mov

-------- Import from git form-----

Screen.Recording.2024-10-30.at.11.13.24.AM.mov

-------- Create serverless form-----

Screen.Recording.2024-10-30.at.11.14.27.AM.mov

Unit test coverage report:
NA

Test setup:

  1. Navigate to Create BuildConfig form page
  2. Select source type as Git
  3. Enter the git url by typing manually do not paste or select from the suggestion

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

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.

@openshift-ci openshift-ci bot added component/dev-console Related to dev-console approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 30, 2024
@lokanandaprabhu
Copy link
Contributor Author

/retest

Copy link
Contributor

@Lucifergene Lucifergene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fix works as expected.
I've added some more edits to this file to ensure consistency. I've adjusted the formatting to match the pattern observed in the other files.

Copy link
Contributor

@Lucifergene Lucifergene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the revision

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 6, 2024
Copy link
Contributor

openshift-ci bot commented Nov 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lokanandaprabhu, Lucifergene

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-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1533f64 and 2 for PR HEAD fa253e2 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2bce638 and 1 for PR HEAD fa253e2 in total

@lokanandaprabhu
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2c069cb and 2 for PR HEAD fa253e2 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 02adeca and 1 for PR HEAD fa253e2 in total

Copy link
Contributor

openshift-ci bot commented Nov 8, 2024

@lokanandaprabhu: all tests passed!

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

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. component/dev-console Related to dev-console jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants