Cannot get tag-release working properly with obs workflows
Hey all, I was trying to get a tag-release workflow working with the new OBS workflows feature for one of my projects: obsctl[1], but the tag-push hook returns errors and GitLab winds up disabling the hook. When it *does* run, it branches the package and doesn't put anything in there, making it kind of useless. The workflow definition is here: https://gitlab.com/datto/engineering/DevOps/obsctl/-/blob/main/.obs/workflow... I don't understand what I'm doing wrong, and the documentation is no help. :( Can someone please help? [1]: https://gitlab.com/datto/engineering/DevOps/obsctl -- 真実はいつも一つ！/ Always, there's only one truth!
On Sat, Dec 31, 2022 at 12:15 AM Neal Gompa <ngompa13@gmail.com> wrote:
Hey all,
I was trying to get a tag-release workflow working with the new OBS workflows feature for one of my projects: obsctl[1], but the tag-push hook returns errors and GitLab winds up disabling the hook. When it *does* run, it branches the package and doesn't put anything in there, making it kind of useless.
The workflow definition is here: https://gitlab.com/datto/engineering/DevOps/obsctl/-/blob/main/.obs/workflow...
I don't understand what I'm doing wrong, and the documentation is no help. :(
Can someone please help?
Ping for help! Also, CentOS Stream 9 on AArch64 is stuck on blocked: https://build.opensuse.org/project/monitor/isv:Datto:Utilities:OBSCtl:Mainline?arch_aarch64=1&blocked=1&defaults=0&repo_CentOS_9=1 -- 真実はいつも一つ！/ Always, there's only one truth!
On 2022-12-31 06 h 15, Neal Gompa wrote:
Hey all,
I was trying to get a tag-release workflow working with the new OBS workflows feature for one of my projects: obsctl[1], but the tag-push hook returns errors and GitLab winds up disabling the hook. When it *does* run, it branches the package and doesn't put anything in there, making it kind of useless.
The workflow definition is here: https://gitlab.com/datto/engineering/DevOps/obsctl/-/blob/main/.obs/workflow...
I don't understand what I'm doing wrong, and the documentation is no help. :(
Can someone please help?
[1]: https://gitlab.com/datto/engineering/DevOps/obsctl
-- 真実はいつも一つ！/ Always, there's only one truth!
Hey Neal, I am leading the development of the SCM/CI integration feature on OBS. I'll do my best to help you out in solving this issue. What is the error you are getting? Do you have logs of the CI runs? I cannot see them in your project somehow... Thank you -- Dany Marcoux Senior Full Stack Web Developer - Open Build Service SUSE Software Solutions Germany GmbH dmarcoux@suse.com Frankenstraße 146 90461 Nürnberg Germany Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman (HRB 36809, AG Nürnberg) www.suse.com
On Wed, Jan 11, 2023 at 4:32 AM Dany Marcoux <dmarcoux@suse.de> wrote:
On 2022-12-31 06 h 15, Neal Gompa wrote:
Hey all,
I was trying to get a tag-release workflow working with the new OBS workflows feature for one of my projects: obsctl[1], but the tag-push hook returns errors and GitLab winds up disabling the hook. When it *does* run, it branches the package and doesn't put anything in there, making it kind of useless.
The workflow definition is here: https://gitlab.com/datto/engineering/DevOps/obsctl/-/blob/main/.obs/workflow...
I don't understand what I'm doing wrong, and the documentation is no help. :(
Can someone please help?
[1]: https://gitlab.com/datto/engineering/DevOps/obsctl
-- 真実はいつも一つ！/ Always, there's only one truth!
Hey Neal,
I am leading the development of the SCM/CI integration feature on OBS. I'll do my best to help you out in solving this issue.
What is the error you are getting? Do you have logs of the CI runs? I cannot see them in your project somehow...
Well, it worked once, but there were several issues occurring: 1. OBS returns 400 errors whenever it's doing stuff (source services, etc.) 2. OBS doesn't handle the case where a tag is updated and throws a 400 error 3. OBS doesn't reliably populate branched packages for the tag-push workflow (the branched package is empty) The first two cases means that GitLab automatically disables the webhook because of "errors", which makes debugging issues really hard. There was also a period of time where it was returning errors saying things like "invalid name" and stuff when nothing had changed. Also, because these are webhooks and not CI runs, I don't have logs to give you. And finally, there's no status reporting back to GitLab. :( -- 真実はいつも一つ！/ Always, there's only one truth!
On 2023-01-11 10 h 54, Neal Gompa wrote:
On Wed, Jan 11, 2023 at 4:32 AM Dany Marcoux <dmarcoux@suse.de> wrote:
On 2022-12-31 06 h 15, Neal Gompa wrote:
Hey all,
I was trying to get a tag-release workflow working with the new OBS workflows feature for one of my projects: obsctl[1], but the tag-push hook returns errors and GitLab winds up disabling the hook. When it *does* run, it branches the package and doesn't put anything in there, making it kind of useless.
The workflow definition is here: https://gitlab.com/datto/engineering/DevOps/obsctl/-/blob/main/.obs/workflow...
I don't understand what I'm doing wrong, and the documentation is no help. :(
Can someone please help?
[1]: https://gitlab.com/datto/engineering/DevOps/obsctl
-- 真実はいつも一つ！/ Always, there's only one truth!
Hey Neal,
I am leading the development of the SCM/CI integration feature on OBS. I'll do my best to help you out in solving this issue.
What is the error you are getting? Do you have logs of the CI runs? I cannot see them in your project somehow...
Well, it worked once, but there were several issues occurring:
1. OBS returns 400 errors whenever it's doing stuff (source services, etc.) 2. OBS doesn't handle the case where a tag is updated and throws a 400 error 3. OBS doesn't reliably populate branched packages for the tag-push workflow (the branched package is empty)
The first two cases means that GitLab automatically disables the webhook because of "errors", which makes debugging issues really hard.
There was also a period of time where it was returning errors saying things like "invalid name" and stuff when nothing had changed.
Also, because these are webhooks and not CI runs, I don't have logs to give you.
And finally, there's no status reporting back to GitLab. :(
-- 真実はいつも一つ！/ Always, there's only one truth!
It's true that OBS doesn't handle the case where a tag is updated. This is a known limitation. As for the other errors, it's quite hard to help if I don't get anything to look at... And with the missing status reports back to GitLab, this shouldn't be the case even if there are errors in the workflow runs. Except if those errors aren't caught by our code, then this happens. -- Dany Marcoux Senior Full Stack Web Developer - Open Build Service SUSE Software Solutions Germany GmbH dmarcoux@suse.com Frankenstraße 146 90461 Nürnberg Germany Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman (HRB 36809, AG Nürnberg) www.suse.com
participants (2)
-
Dany Marcoux -
Neal Gompa