git-workflow/autogits
SHA256
21
2
Fork 13
Code Issues 47 Pull Requests 14 Actions Projects 2 Activity

obs-staging-bot: allow build-disabling repositories in the QA projects #116

Manually merged
epaolantonio merged 1 commits from epaolantonio/autogits:epaolantonio/builddisable into main 2026-01-22 13:53:33 +01:00
Conversation 1 Commits 1 Files Changed 3 +29 -6
epaolantonio commented 2026-01-21 19:14:43 +01:00
Contributor
Copy Link

Using the BuildDisableRepos configuration, it is now possible to
define which repositories to build-disable in the QA project meta.

This is for example useful for the SLES development workflow, where
the product repository should only be enabled after the packagelist
definitions have been built - so it is not desirable to have them
built as soon as the QA project is created.

Example:

{
  "ObsProject": "SUSE:SLFO:Main",
  "StagingProject": "SUSE:SLFO:Main:PullRequest",
  "QA": [
    {
      "Name": "SLES",
      "Origin": "SUSE:SLFO:Products:SLES:16.1",
      "BuildDisableRepos": ["product"]
    }
  ]
}

Signed-off-by: Eugenio Paolantonio eugenio.paolantonio@suse.com

Using the BuildDisableRepos configuration, it is now possible to define which repositories to build-disable in the QA project meta. This is for example useful for the SLES development workflow, where the product repository should only be enabled after the packagelist definitions have been built - so it is not desirable to have them built as soon as the QA project is created. Example: { "ObsProject": "SUSE:SLFO:Main", "StagingProject": "SUSE:SLFO:Main:PullRequest", "QA": [ { "Name": "SLES", "Origin": "SUSE:SLFO:Products:SLES:16.1", "BuildDisableRepos": ["product"] } ] } Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
epaolantonio added 1 commit 2026-01-21 19:14:43 +01:00
obs-staging-bot: allow build-disabling repositories in the QA projects
Some checks failed
go-generate-check / go-generate-check (push) Failing after 25s
Details
go-generate-check / go-generate-check (pull_request) Has been cancelled
Details
edd8c67fc9 
Using the BuildDisableRepos configuration, it is now possible to
define which repositories to build-disable in the QA project meta.

This is for example useful for the SLES development workflow, where
the product repository should only be enabled after the packagelist
definitions have been built - so it is not desirable to have them
built as soon as the QA project is created.

Example:

    {
      "ObsProject": "SUSE:SLFO:Main",
      "StagingProject": "SUSE:SLFO:Main:PullRequest",
      "QA": [
        {
          "Name": "SLES",
          "Origin": "SUSE:SLFO:Products:SLES:16.1",
          "BuildDisableRepos": ["product"]
        }
      ]
    }

Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
adamm approved these changes 2026-01-22 13:52:09 +01:00
epaolantonio manually merged commit edd8c67fc9 into main 2026-01-22 13:53:33 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
adamm
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
M0ses adamm adamm_super adrianSuSE andriinikitin atartamo bigironman dancermak darix dirkmueller dmach eroca jdsn jzerebecki mstrigl oertel smithfarm
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: git-workflow/autogits#116
Delete Branch "epaolantonio/autogits:epaolantonio/builddisable"

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?