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-32476: Import from Git allow users to import an app with Build option Pipeline also when no Pipeline is available #13853

Merged

Conversation

lokanandaprabhu
Copy link
Contributor

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

Analysis / Root cause:
Validation was not added to check if any pipeline template is selected if user choose Pipeline from the cluster

Solution Description:
Added the validation to check if build type is Pipeline and pipeline type is not PAC to check whether pipeline template is selected or not. If not create button will be disabled

Screen shots / Gifs for design review:

----When Just after Pipeline operator is installed---

Screen.Recording.2024-05-15.at.11.00.54.AM.mov

--- Import from Git form---
https://github.com/openshift/console/assets/102503482/ef7d7127-795a-4ff8-bdbf-4563f78ccfed

---Adding serverless function without Pipeline template created---
https://github.com/openshift/console/assets/102503482/f87d01e6-32e9-4aa8-b5c2-835b16b50462

---Create serverless function form---
https://github.com/openshift/console/assets/102503482/e7c4ce2a-e4b8-4b2c-9542-15f6cd048ab2

Unit test coverage report:
NA

Test setup:

  1. Install OpenShift Local
  2. Install Pipelines Opeartor
  3. Import from Git and select Pipeline as option

Browser conformance:

  • Chrome
  • Firefox
  • Safari
  • Edge

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 15, 2024
@openshift-ci-robot
Copy link
Contributor

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-32476, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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-32476

Analysis / Root cause:
Validation was not added to check if any pipeline template is selected if user choose Pipeline from the cluster

Solution Description:
Added the validation to check if build type is Pipeline and pipeline type is not PAC to check whether pipeline template is selected or not. If not create button will be disabled

Screen shots / Gifs for design review:

----When Just after Pipeline operator is installed---

Screen.Recording.2024-05-15.at.11.00.54.AM.mov

--- Import from Git form---
https://github.com/openshift/console/assets/102503482/ef7d7127-795a-4ff8-bdbf-4563f78ccfed

---Adding serverless function without Pipeline template created---
https://github.com/openshift/console/assets/102503482/f87d01e6-32e9-4aa8-b5c2-835b16b50462

---Create serverless function form---
https://github.com/openshift/console/assets/102503482/e7c4ce2a-e4b8-4b2c-9542-15f6cd048ab2

Unit test coverage report:
NA

Test setup:

  1. Install OpenShift Local
  2. Install Pipelines Opeartor
  3. Import from Git and select Pipeline as option

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 component/pipelines Related to pipelines-plugin approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 15, 2024
@lokanandaprabhu
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 15, 2024
@openshift-ci-robot
Copy link
Contributor

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-32476, 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.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sanketpathak

In response to this:

/jira refresh

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 requested a review from sanketpathak May 15, 2024 06:27
@lokanandaprabhu
Copy link
Contributor Author

/cc @vikram-raj

@openshift-ci openshift-ci bot requested a review from vikram-raj May 15, 2024 06:27
Copy link
Member

@vikram-raj vikram-raj left a comment

Choose a reason for hiding this comment

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

/lgtm

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

openshift-ci bot commented May 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lokanandaprabhu, vikram-raj

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

@lokanandaprabhu
Copy link
Contributor Author

/retest

@openshift-merge-bot openshift-merge-bot bot merged commit 86e3115 into openshift:master May 21, 2024
5 of 6 checks passed
@openshift-ci-robot
Copy link
Contributor

@lokanandaprabhu: Jira Issue OCPBUGS-32476: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-32476 has been moved to the MODIFIED state.

In response to this:

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

Analysis / Root cause:
Validation was not added to check if any pipeline template is selected if user choose Pipeline from the cluster

Solution Description:
Added the validation to check if build type is Pipeline and pipeline type is not PAC to check whether pipeline template is selected or not. If not create button will be disabled

Screen shots / Gifs for design review:

----When Just after Pipeline operator is installed---

Screen.Recording.2024-05-15.at.11.00.54.AM.mov

--- Import from Git form---
https://github.com/openshift/console/assets/102503482/ef7d7127-795a-4ff8-bdbf-4563f78ccfed

---Adding serverless function without Pipeline template created---
https://github.com/openshift/console/assets/102503482/f87d01e6-32e9-4aa8-b5c2-835b16b50462

---Create serverless function form---
https://github.com/openshift/console/assets/102503482/e7c4ce2a-e4b8-4b2c-9542-15f6cd048ab2

Unit test coverage report:
NA

Test setup:

  1. Install OpenShift Local
  2. Install Pipelines Opeartor
  3. Import from Git and select Pipeline as option

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.

@lokanandaprabhu
Copy link
Contributor Author

/cherrypick release-4.16

@openshift-cherrypick-robot

@lokanandaprabhu: new pull request created: #13884

In response to this:

/cherrypick release-4.16

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.

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 component/pipelines Related to pipelines-plugin jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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.

None yet

4 participants