此内容没有您所选择的语言版本。
Chapter 12. Repository Notifications
Quay supports adding notifications to a repository for various events that occur in the repository’s lifecycle. To add notifications, click the Settings tab while viewing a repository and select Create Notification
. From the When this event occurs
field, select the items for which you want to receive notifications:
After selecting an event, further configure it by adding how you will be notified of that event.
Adding notifications requires repository admin permission.
The following are examples of repository events.
12.1. Repository Events 复制链接链接已复制到粘贴板!
12.1.1. Repository Push 复制链接链接已复制到粘贴板!
A successful push of one or more images was made to the repository:
12.1.2. Dockerfile Build Queued 复制链接链接已复制到粘贴板!
Here is a sample response for a Dockerfile build has been queued into the build system. The response can differ based on the use of optional attributes.
12.1.3. Dockerfile Build Started 复制链接链接已复制到粘贴板!
Here is an example of a Dockerfile build being started by the build system. The response can differ based on some attributes being optional.
12.1.4. Dockerfile Build Successfully Completed 复制链接链接已复制到粘贴板!
Here is a sample response of a Dockerfile build that has been successfully completed by the build system.
This event will occur simultaneously with a Repository Push event for the built image(s)
12.1.5. Dockerfile Build Failed 复制链接链接已复制到粘贴板!
A Dockerfile build has failed
12.1.6. Dockerfile Build Cancelled 复制链接链接已复制到粘贴板!
A Dockerfile build was cancelled
12.1.7. Vulnerability Detected 复制链接链接已复制到粘贴板!
A vulnerability was detected in the repository
12.2. Notification Actions 复制链接链接已复制到粘贴板!
12.2.1. Quay Notification 复制链接链接已复制到粘贴板!
A notification will be added to the Quay.io notification area. The notification area can be found by clicking on the bell icon in the top right of any Quay.io page.
Quay.io notifications can be setup to be sent to a User, Team, or the organization as a whole.
12.2.2. E-mail 复制链接链接已复制到粘贴板!
An e-mail will be sent to the specified address describing the event that occurred.
All e-mail addresses will have to be verified on a per-repository basis
12.2.3. Webhook POST 复制链接链接已复制到粘贴板!
An HTTP POST call will be made to the specified URL with the event’s data (see above for each event’s data format).
When the URL is HTTPS, the call will have an SSL client certificate set from Quay.io. Verification of this certificate will prove the call originated from Quay.io. Responses with status codes in the 2xx range are considered successful. Responses with any other status codes will be considered failures and result in a retry of the webhook notification.
12.2.4. Flowdock Notification 复制链接链接已复制到粘贴板!
Posts a message to Flowdock.
12.2.5. Hipchat Notification 复制链接链接已复制到粘贴板!
Posts a message to HipChat.
12.2.6. Slack Notification 复制链接链接已复制到粘贴板!
Posts a message to Slack.