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

[STAGING][QA-003] Trigger multiple QA builds from different origins #78

New Issue
Open
opened 2026-03-04 17:50:45 +01:00 by atartamo · 0 comments
atartamo commented 2026-03-04 17:50:45 +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 multiple QA entries with different Origin projects (e.g., openSUSE:Factory:Rings:0-Bootstrap and openSUSE:Factory:Rings:1-MinimalX).
  5. Wait for the initial staging project to be created in OBS.
  6. Add both corresponding labels (e.g., QA-0Bootstrap and QA-1MinimalX) to the project PR.
  7. Trigger the staging bot to process the PR.

Expected Results

  1. The staging bot identifies both labels and creates two corresponding OBS sub-projects.
  2. Each sub-project name follows the format: <StagingProject>:<PR_NUMBER>:<QA_NAME>.
  3. The bot correctly fetches and applies the unique metadata from each respective Origin project to the corresponding sub-project.
  4. Repositories in each QA project that previously pointed to the base ObsProject are updated to point to the current PR's staging project.
  5. The staging bot adds a comment listing both newly created QA projects.
**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 multiple `QA` entries with **different** `Origin` projects (e.g., `openSUSE:Factory:Rings:0-Bootstrap` and `openSUSE:Factory:Rings:1-MinimalX`). 5. Wait for the initial staging project to be created in OBS. 6. Add both corresponding labels (e.g., `QA-0Bootstrap` and `QA-1MinimalX`) to the project PR. 7. Trigger the staging bot to process the PR. **Expected Results** 1. The staging bot identifies both labels and creates two corresponding OBS sub-projects. 2. Each sub-project name follows the format: `<StagingProject>:<PR_NUMBER>:<QA_NAME>`. 3. The bot correctly fetches and applies the unique metadata from **each respective** `Origin` project to the corresponding sub-project. 4. Repositories in each QA project that previously pointed to the base `ObsProject` are updated to point to the current PR's staging project. 5. The staging bot adds a comment listing both newly created QA projects.
atartamo added the
bot
staging
status
todo
 labels 2026-03-04 17:50:45 +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#78
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?