Skip to content

Commit ec85ff8

Browse files
otaviofgabemontero
andauthored
Update ships/0031-shipwright-trigger.md
Co-authored-by: Gabe Montero <[email protected]>
1 parent 4e43966 commit ec85ff8

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

ships/0031-shipwright-trigger.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,11 @@ Shipwright Trigger
55

66
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.
77

8-
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.
8+
This enhancement proposal describes how Shipwright will react to:
9+
- WebHooks: Handles WebHook requests from Git service providers, like GitHub, in order to activate a Build
10+
- Tekton Pipelines: Integration between Tekton Pipelines and Shipwright, Builds will be triggered when a given Pipeline has reach the desired status
11+
- 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
12+
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.
913

1014
# Motivation
1115

0 commit comments

Comments
 (0)