Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the webhook endpoint URL configurable #146

Merged
merged 2 commits into from
May 8, 2024

Conversation

antifuchs
Copy link
Contributor

In some CI setups (especially those where the CI server is reachable over a VPN with split-horizon DNS), the URL to access the CI server differs from the URL that the (external) webhook endpoint listens on.

This change introduces an option webhookBaseUrl that allows setting that URL independently from the buildbot installation URL.

In some CI setups, the URL to access the CI server differs from the
URL that the (external) webhook endpoint listens on. This change
introduces an option webhookBaseUrl that allows setting that URL
independently from the buildbot installation URL.
nix/master.nix Outdated Show resolved Hide resolved
@amnnku
Copy link

amnnku commented May 8, 2024

Out of interest, does setting the webhook url manually change the need for the user to be an admin in gitea?

Or do you still set the url automatically, just with this revised url.

@antifuchs
Copy link
Contributor Author

You still have to have permissions to set the webhook endpoint on each repo. This only alters the URL that the buildbot-nix code sets using those permissions.

@Mic92
Copy link
Member

Mic92 commented May 8, 2024

@mergify queue

Copy link

mergify bot commented May 8, 2024

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 2f38900

@mergify mergify bot merged commit 2f38900 into nix-community:main May 8, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants