Skip to content

[release-4.19] MCO-1703: Using OpenShift Pipeline as a way to build MC in OCL#5103

Closed
pablintino wants to merge 34 commits intoopenshift:release-4.19from
pablintino:pipeline-4.19
Closed

[release-4.19] MCO-1703: Using OpenShift Pipeline as a way to build MC in OCL#5103
pablintino wants to merge 34 commits intoopenshift:release-4.19from
pablintino:pipeline-4.19

Conversation

@pablintino
Copy link
Copy Markdown
Contributor

@pablintino pablintino commented Jun 4, 2025

- What I did

- How to verify it

- Description for the changelog

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jun 4, 2025 •
edited by openshift-ci bot
Loading

@pablintino: This pull request references MCO-1465 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

- What I did

- How to verify it

- Description for the changelog

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 4, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 4, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jun 4, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jun 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pablintino

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

The pull request process is described here

Details 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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 4, 2025
@RishabhSaini @pablintino
creating basic pipeline structure
3a128dd
@RishabhSaini @pablintino
add RBAC policy for querying tekton resources
83a007f
@RishabhSaini @pablintino
switching to tektonV1beta1 for clusterTaskKind
c7d61d3
@RishabhSaini @pablintino
fixing errors on already exists subscription and tektonConfig in wait
b8eb7c4
@RishabhSaini @pablintino
fix paramValye for v1beta1
783d1d1
@RishabhSaini @pablintino
trying loggin
a190549
@RishabhSaini @pablintino
fix pipelineresultstype
074d85b
@RishabhSaini @pablintino
fix authfilePush param
be845a6
@RishabhSaini @pablintino
missing tektonclient add
119376f
@RishabhSaini @pablintino
fix param value of pipelineRun
523f83b
@RishabhSaini @pablintino
fix proxy values default
e9d5dbe
@RishabhSaini @pablintino
from clustertask to resolverref
c323e94
@RishabhSaini @pablintino
fix srviceacc and workspace
adb9838
@RishabhSaini @pablintino
fix rolebingds
b8ca9ed
@RishabhSaini @pablintino
fix scc add to operator sync manifest
c23effa
@RishabhSaini @pablintino
adding support for machineconfig and trustbundle
2eef9b4
@RishabhSaini @pablintino
revert deployment required-scc
a59b5da
@RishabhSaini @pablintino
checkAndInstallPipeline when syncing mosc and mosb
abce9e8
@RishabhSaini @pablintino
remove unecessary loggin
6eea58e
@RishabhSaini @pablintino
fix echoing script
30f6bb4
@RishabhSaini @pablintino
fix DOCKERFILE to path
7c068d7
@RishabhSaini @pablintino
make custom task
63a102c
@RishabhSaini @pablintino
fixing authfile issues for build and push
715e6f3
@pablintino pablintino changed the title [release-4.19] MCO-1465: Using OpenShift Pipeline as a way to build MC in OCL [release-4.19] MCO-1703: Using OpenShift Pipeline as a way to build MC in OCL Jun 18, 2025
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented Jun 18, 2025 •
edited by openshift-ci bot
Loading

@pablintino: This pull request references MCO-1703 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

- What I did

- How to verify it

- Description for the changelog

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

openshift-ci bot commented Jun 26, 2025

@pablintino: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Sep 25, 2025

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 25, 2025
@openshift-merge-robot
Copy link
Copy Markdown
Contributor

openshift-merge-robot commented Sep 25, 2025

PR needs rebase.

Details

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.

@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Oct 25, 2025

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 25, 2025
@openshift-bot
Copy link
Copy Markdown
Contributor

openshift-bot commented Nov 25, 2025

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Nov 25, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Nov 25, 2025

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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

Reviewers

No reviews

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@pablintino @openshift-ci-robot @openshift-bot @openshift-merge-robot @RishabhSaini