Skip to content

[Metax][CI]Change Jenkins trigger group from APPROVAL to GZ_BD-CPU#7918

Merged
plusNew001 merged 1 commit into
PaddlePaddle:developfrom
plusNew001:0525-ci-update
May 25, 2026
Merged

[Metax][CI]Change Jenkins trigger group from APPROVAL to GZ_BD-CPU#7918
plusNew001 merged 1 commit into
PaddlePaddle:developfrom
plusNew001:0525-ci-update

Conversation

@plusNew001
Copy link
Copy Markdown
Collaborator

Motivation

💡 If this PR is a Cherry Pick, the PR title needs to follow the format by adding the [Cherry-Pick] label at the very beginning and appending the original PR ID at the end. For example, [Cherry-Pick][CI] Add check trigger and logic(#5191)

💡 如若此PR是Cherry Pick,PR标题需遵循格式,在最开始加上[Cherry-Pick]标签,以及最后面加上原PR ID,例如[Cherry-Pick][CI] Add check trigger and logic(#5191)

Modifications

Usage or Command

Accuracy Tests

Checklist

  • Add at least a tag in the PR title.
    • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
    • You can add new tags based on the PR content, but the semantics must be clear.
  • Format your code, run pre-commit before commit.
  • Add unit tests. Please write the reason in this PR if no unit tests.
  • Provide accuracy results.
  • If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

Copilot AI review requested due to automatic review settings May 25, 2026 09:05
@paddle-bot
Copy link
Copy Markdown

paddle-bot Bot commented May 25, 2026

Thanks for your contribution!

@paddle-bot paddle-bot Bot added the contributor External developers label May 25, 2026
@plusNew001
Copy link
Copy Markdown
Collaborator Author

/skip all

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

该 PR 调整 Metax 相关的 GitHub Actions 工作流,使其在触发 Jenkins 任务时不再使用 APPROVAL runner group,而改为使用 GZ_BD-CPU,以匹配新的 CI 运行资源/权限分组。

Changes:

  • .github/workflows/ci_metax.ymlruns-on.groupAPPROVAL 修改为 GZ_BD-CPU,影响 Metax PR 的 Jenkins 触发作业运行位置。

补充提醒:该 PR 当前描述信息基本未填写(Motivation/Modifications/Tests 等),建议补充变更原因与验证方式;另外标题建议在最后一个 tag 后增加空格以贴合模板示例格式。此变更一般不需要面向用户的文档更新,但如果仓库/团队内部有 CI runner group 说明文档,建议同步更新。

Comment on lines 21 to 23
runs-on:
group: APPROVAL
group: GZ_BD-CPU
environment: Metax_ci
Comment on lines 19 to +22
trigger-jenkins:
name: Trigger Jenkins for PR
runs-on:
group: APPROVAL
group: GZ_BD-CPU
@plusNew001 plusNew001 closed this May 25, 2026
@plusNew001 plusNew001 reopened this May 25, 2026
@plusNew001 plusNew001 merged commit cc413e0 into PaddlePaddle:develop May 25, 2026
32 of 40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor External developers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants