Server Hook Plugin Management

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

As a GitLab self hosted administrator I want to enforce process using server hooks on certain reposiories and want to be able to administer from the UI that the functionality is activated. I want to manage versions of the server hook that are visible in the UI and from a support bundle.

Intended users

System Administrator

User experience goal

Custom plugin is uploaded through the UI (or from a marketplace), at instance admin level.

The Repository admin has a configuration option to turn on the server hook for the repo (and option of passing parameters)

Proposal

Example of how this works is how Atlassian manage plugins https://developer.atlassian.com/server/bitbucket/how-tos/beginner-guide-to-bitbucket-server-plugin-development/

Further details

N/A

Permissions and Security

Server hook enablement and configuration only available for administrators

Documentation

N/A internal to GitLab processes

Available Tier

Premium

Feature Usage Metrics

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this feature?

Links / references

https://developer.atlassian.com/server/bitbucket/how-tos/beginner-guide-to-bitbucket-server-plugin-development/