Hello,
I suspect that there is a mistake in the example Rebuild a Package for Every Change in a Branch in the OBS official documentation:
https://openbuildservice.org/help/manuals/obs-user-guide/cha-obs-scm-ci-workflow-integration#sec-obs-obs-scm-ci-workflow-integration-use-cases-rebuild-package-for-every-change
In it, it's said that using a workflow involving rebuild_packages step would trigger rebuild of a package with newest changes introduced by new commits in a PR. As far as I know, though, rebuild_packages doesn't execute services, thus no changes would be picked up, meaning a redundant build would be made.
I suspect, this example is supposed to present trigger_services step, instead. With it, the services would be triggered, new changes picked up by OBS, and a new build would follow.
Hello,
I suspect that there is a mistake in the example
Rebuild a Package for Every Change in a Branchin the OBS official documentation:https://openbuildservice.org/help/manuals/obs-user-guide/cha-obs-scm-ci-workflow-integration#sec-obs-obs-scm-ci-workflow-integration-use-cases-rebuild-package-for-every-change
In it, it's said that using a workflow involving
rebuild_packagesstep would trigger rebuild of a package with newest changes introduced by new commits in a PR. As far as I know, though,rebuild_packagesdoesn't execute services, thus no changes would be picked up, meaning a redundant build would be made.I suspect, this example is supposed to present
trigger_servicesstep, instead. With it, the services would be triggered, new changes picked up by OBS, and a new build would follow.