On Wed, Oct 24, 2018 at 10:13 AM Christian wrote:

Am 25.05.18 um 07:50 schrieb Adrian Schröter:

...

Yes, we are aware of it and will look into it.

(The CLA blocked me on working on github integration in the past, but might not be a problem anymore with webhooks).

Hi Adrian,

any news on this ? Cause since Oct. 1st you are unable to setup a new GitHub Service. This feature got disbaled. Hence you are already forced to make use of webhooks.

Existing Services will work until Jan 31, 2019 Thank you very much ...

Webhooks support for GitHub and Pagure was merged into OBS back in July: https://github.com/openSUSE/open-build-service/commit/7d4a4eef5e647704b39833... These are active on the build service today, there's just no documentation for them... -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Am 24.10.18 um 16:37 schrieb Christian:

Am 24.10.18 um 16:15 schrieb Neal Gompa:

...

These are active on the build service today, there's just no documentation for them... Hi Neal,

thank you for info. How should the 'Payload URL' look alike ? I guess it is the <API URL> + <PRJ> + <PKG> + trigger/service ?

The URL is https://build.opensuse.org/trigger/webhook?id=$TOKEN_ID The token_id is listed on osc tokens and you have to put the token itself as secret Greetings, Stephan -- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Am 25.10.18 um 09:23 schrieb Christian:

...

The URL is https://build.opensuse.org/trigger/webhook?id=$TOKEN_ID

The token_id is listed on osc tokens and you have to put the token itself as secret

Am 24.10.18 um 21:00 schrieb Stephan Kulow: the webhook config on GitHub is split up into two config parts .. 1) Payload URL: 2) secret

did you test it that way ?

coolo@cleopatra#~>osc token --create home:coolo demopac Create a new token <status code="ok"> <summary>Ok</summary> <data name="token">aWup8hf2dzF8c2GPfoKn1BpV</data> <data name="id">1920</data> </status> And then paste aWup... into the secret: https://pasteboard.co/HK3ry5c.png Greetings, Stephan -- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Am 25.10.18 um 10:13 schrieb Andreas Schwab:

On Okt 25 2018, Stephan Kulow wrote:

...

Am 25.10.18 um 09:23 schrieb Christian:

...

...

The URL is https://build.opensuse.org/trigger/webhook?id=$TOKEN_ID

The token_id is listed on osc tokens and you have to put the token itself as secret

Am 24.10.18 um 21:00 schrieb Stephan Kulow: the webhook config on GitHub is split up into two config parts .. 1) Payload URL: 2) secret

did you test it that way ?

coolo@cleopatra#~>osc token --create home:coolo demopac Create a new token <status code="ok"> <summary>Ok</summary> <data name="token">aWup8hf2dzF8c2GPfoKn1BpV</data> <data name="id">1920</data> </status>

And then paste aWup... into the secret: https://pasteboard.co/HK3ry5c.png

Are you sure it's the token id and not the token string that you need to use? osc token --trigger also uses the token string.

Well, you need both - don't ask me why. But it's in the code: https://bit.ly/2yzK1kx Greetings, Stephan -- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Hi, everyone! I successfully integrated OBS and GitHub after reading previous messages on this mailing list: https://lists.opensuse.org/opensuse-buildservice/2018-05/msg00042.html https://lists.opensuse.org/opensuse-buildservice/2018-10/msg00034.html I made a begin-to-end how-to and published it: https://kamarada.github.io/en/2019/03/19/integrating-the-open-build-service-... It starts with an existing GitHub repository and an empty OBS package and ends with an integrated setup so that any git push to GitHub triggers a package rebuild in OBS. Please feel free to copy and paste it as is to an official place (maybe a wiki or the OBS blog), change the example to a more appropriate one if you want, I can also help if given the proper permissions and instructions. Only later I realized the OBS documentation has been updated with instructions on how to use GitHub webhooks: https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.source_serv... But all the necessary information is fragmented across the OBS guides. My how-to references Adrian's and Frank's texts, so I carbon copy them and again thank them for sharing information. Antonio The Linux Kamarada Project http://kamarada.github.io/ Em seg, 29 de out de 2018 às 09:22, Christian Bruckmayer escreveu:

And yes, we should document this :)

Christian

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org