Skip to content

Commit

Permalink
Update ships/0031-shipwright-trigger.md
Browse files Browse the repository at this point in the history
Co-authored-by: Gabe Montero <gmontero@redhat.com>
  • Loading branch information
otaviof and gabemontero authored Mar 22, 2022
1 parent 4e43966 commit ec85ff8
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion ships/0031-shipwright-trigger.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,11 @@ Shipwright Trigger

Shipwright's project goal is to automate and greatly simplify the container image building process, and currently, users can only initiate the build process by issuing a new `BuildRun` object.

This enhancement proposal describes how Shipwright will react upon WebHook events coming from Git service providers like GitHub, how it will be incorporated into Tekton Pipelines via Custom Task, and how it will react upon Tekton Pipelines resources.
This enhancement proposal describes how Shipwright will react to:
- WebHooks: Handles WebHook requests from Git service providers, like GitHub, in order to activate a Build
- Tekton Pipelines: Integration between Tekton Pipelines and Shipwright, Builds will be triggered when a given Pipeline has reach the desired status
- Tekton [Custom-Tasks](https://github.com/tektoncd/community/blob/main/teps/0002-custom-tasks.md) (Run): A new Custom Task will allow users to call out Shipwright Builds directly from Pipelines
Images: Integration with the new Shipwright [Image project](https://github.com/shipwright-io/image), changes to any Images managed by that project that serve as input into a Shipwright Build will initiate new BuildRuns when any of those images change.

# Motivation

Expand Down

0 comments on commit ec85ff8

Please sign in to comment.