git-workflow/tests
SHA256
16
0
Code Issues 30 Packages Projects Wiki

[STAGING][QA-001] Trigger QA build via single label #76

New Issue
Open
opened 2026-03-04 17:50:24 +01:00 by atartamo · 0 comments
atartamo commented 2026-03-04 17:50:24 +01:00
Owner
Copy Link

Test Steps

  1. Create a package PR.
  2. Wait for the workflow-pr bot to create the related project PR.
  3. Wait for staging-bot to be added as a reviewer and ensure it is listed in the required reviewers for the project PR.
  4. Ensure the staging.config in the PR includes a QA entry with a specific Label (e.g., QA-SLES-Full) and an Origin project.
  5. Wait for the initial staging project (the one for "onlybuild" packages) to be created in OBS.
  6. Add the label QA-SLES-Full to the project PR.
  7. Trigger the staging bot to process the PR.

Expected Results

  1. The staging bot identifies the label and creates a new OBS sub-project.
  2. The new project name follows the format: <StagingProject>:<PR_NUMBER>:<QA_NAME> (e.g., SUSE:SLFO:Main:PullRequest:123:SLES).
  3. The bot fetches the metadata (ProjectMeta) from the Origin project and applies it to the new QA project.
  4. Repositories in the new QA project that previously pointed to the base ObsProject are updated to point to the PR's main staging project.
  5. The staging bot adds a comment to the project PR: "QA Project added: https://<OBS_URL>/project/show/<QA_PROJECT_FULL_NAME>".
**Test Steps** 1. Create a package PR. 2. Wait for the `workflow-pr` bot to create the related project PR. 3. Wait for `staging-bot` to be added as a reviewer and ensure it is listed in the required reviewers for the project PR. 4. Ensure the `staging.config` in the PR includes a `QA` entry with a specific `Label` (e.g., `QA-SLES-Full`) and an `Origin` project. 5. Wait for the initial staging project (the one for "onlybuild" packages) to be created in OBS. 6. Add the label `QA-SLES-Full` to the project PR. 7. Trigger the staging bot to process the PR. **Expected Results** 1. The staging bot identifies the label and creates a new OBS sub-project. 2. The new project name follows the format: `<StagingProject>:<PR_NUMBER>:<QA_NAME>` (e.g., `SUSE:SLFO:Main:PullRequest:123:SLES`). 3. The bot fetches the metadata (`ProjectMeta`) from the `Origin` project and applies it to the new QA project. 4. Repositories in the new QA project that previously pointed to the base `ObsProject` are updated to point to the PR's main staging project. 5. The staging bot adds a comment to the project PR: "QA Project added: `https://<OBS_URL>/project/show/<QA_PROJECT_FULL_NAME>`".
atartamo added the
bot
staging
status
todo
 labels 2026-03-04 17:50:24 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority
High
Priority
Medium
bot
staging
bot
workflow-pr
not-implemented
status
done
status
in-progress
status
todo
No Label
bot
staging
status
todo
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
M0ses adamm adrianSuSE andriinikitin atartamo bigironman dancermak darix dirkmueller dmach eroca jdsn jzerebecki mstrigl oertel smithfarm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: git-workflow/tests#76
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?