Skip to content

Please support openshift build webhooks #7488

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

Closed
5 of 7 tasks
bzed opened this issue Jul 16, 2019 · 3 comments
Closed
5 of 7 tasks

Please support openshift build webhooks #7488

bzed opened this issue Jul 16, 2019 · 3 comments
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@bzed
Copy link

bzed commented Jul 16, 2019

  • Gitea version (or commit ref): master
  • Git version: HEAD
  • Operating system: Debian
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist: not relevant

Description

Please support openshift build webhooks. See the generic webhook part in
https://docs.openshift.com/container-platform/4.1/builds/triggering-builds-build-hooks.html

  • the POST request needs a formatted yaml file as data.

Thanks,

Bernd

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jul 16, 2019
@titou10titou10
Copy link

titou10titou10 commented Aug 4, 2019

+1
The specs of the webhook trigger for OpenShift v3.11 are here: https://docs.openshift.com/container-platform/3.11/dev_guide/builds/triggering_builds.html

It has to be an HTTPPOSTrequest with a"Content-Type" header of "application/yaml" or "application/json" and the following payload (Shown as yaml):

git:
  uri: "<url to gitea repository>"
  ref: "<optional git reference>"
  commit: "<commit hash identifying a specific git commit>"
  author:
    name: "<author name>"
    email: "<author e-mail>"
  committer:
    name: "<committer name>"
    email: "<committer e-mail>"
  message: "<commit message>"
env: 
   - name: "<variable name>"
     value: "<variable value>"

@scorbin
Copy link

scorbin commented Sep 19, 2019

+1
Don't want to use gitlab with openshift

@lunny
Copy link
Member

lunny commented Sep 19, 2019

PR is welcome for those who are familiar with openshift.

@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

5 participants