Skip to content

feat: add new github action for tidb-operator-release v1.x#6606

Merged
ti-chi-bot[bot] merged 7 commits intopingcap:mainfrom
lybcodes:featrue/migrate-tidb-operator-release-publish-job
Dec 16, 2025
Merged

feat: add new github action for tidb-operator-release v1.x#6606
ti-chi-bot[bot] merged 7 commits intopingcap:mainfrom
lybcodes:featrue/migrate-tidb-operator-release-publish-job

Conversation

@lybcodes
Copy link
Contributor

This PR migrate tidb-operator-release job on CD.pingcap.net to GitHub action job style to make it own easy feedback and triggers, also improving maintainability.

original jenkins job:

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Dec 15, 2025

Hi @lybcodes. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Dec 15, 2025

Welcome @lybcodes! It looks like this is your first PR to pingcap/tidb-operator 🎉

@pingcap-cla-assistant
Copy link

pingcap-cla-assistant bot commented Dec 15, 2025

CLA assistant check
All committers have signed the CLA.

@ti-chi-bot ti-chi-bot bot added the size/M label Dec 15, 2025
@ti-chi-bot ti-chi-bot bot added size/L and removed size/M labels Dec 15, 2025
@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.47%. Comparing base (2dc570f) to head (55eba1f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6606   +/-   ##
=======================================
  Coverage   41.47%   41.47%           
=======================================
  Files         349      349           
  Lines       20043    20043           
=======================================
  Hits         8313     8313           
  Misses      11730    11730           
Flag Coverage Δ
unittest 41.47% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ti-chi-bot ti-chi-bot bot added the lgtm label Dec 16, 2025
@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Dec 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csuzhangxc

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

@ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Dec 16, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-12-16 10:20:41.755483954 +0000 UTC m=+1554786.569261526: ☑️ agreed by csuzhangxc.

@ti-chi-bot ti-chi-bot bot added the approved label Dec 16, 2025
@ti-chi-bot ti-chi-bot bot merged commit b2e036e into pingcap:main Dec 16, 2025
4 checks passed
@wuhuizuo
Copy link
Contributor

/cherrypick release-1.x release-1.6

@wuhuizuo
Copy link
Contributor

/cherrypick release-1.x

@ti-chi-bot
Copy link
Member

@wuhuizuo: cannot checkout release-1.x release-1.6: error checking out release-1.x release-1.6: exit status 1. output: error: pathspec 'release-1.x release-1.6' did not match any file(s) known to git

Details

In response to this:

/cherrypick release-1.x release-1.6

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 ti-community-infra/tichi repository.

@wuhuizuo
Copy link
Contributor

/cherrypick release-1.6

@ti-chi-bot
Copy link
Member

@wuhuizuo: new pull request created to branch release-1.x: #6609.
But this PR has conflicts, please resolve them!

Details

In response to this:

/cherrypick release-1.x

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 ti-community-infra/tichi repository.

ti-chi-bot pushed a commit to ti-chi-bot/tidb-operator that referenced this pull request Dec 16, 2025
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
ti-chi-bot pushed a commit to ti-chi-bot/tidb-operator that referenced this pull request Dec 16, 2025
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

@wuhuizuo: new pull request created to branch release-1.6: #6610.
But this PR has conflicts, please resolve them!

Details

In response to this:

/cherrypick release-1.6

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 ti-community-infra/tichi repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants