Skip to content
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.

Commit

Permalink
Add information on PR images expiring
Browse files Browse the repository at this point in the history
Signed-off-by: arewm <[email protected]>
  • Loading branch information
arewm committed Sep 29, 2023
1 parent 98d11a6 commit 527c5a6
Showing 1 changed file with 12 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ However, there are three reasons you might want to upgrade your build pipeline t

* Customize: Upgrading the build pipeline enables you to tailor the build process that {ProductName} uses for the components of your application, to better meet your specific needs.
* Reinforce security: When you upgrade, {ProductName} adds a variety of security checks and scans on your pipeline that get run on each build.
* Continuous integration: Upgraded build pipelines automatically rebuild your components every time a new commit is merged into the main branch of their repositories.
* Continuous integration: Upgraded build pipelines automatically rebuild your components every time a new commit is added to a pull request or merged into the configured branch of their repositories.
.Prerequisites

Expand Down Expand Up @@ -38,6 +38,17 @@ Confirm that most of the build pipeline tasks that {ProductName} previously skip
. Select the most recent *PipelineRun*.
. View the build pipeline tasks and scroll down to view the vulnerabilities scan, which summarizes the results of the `clair-scan`.

.Continuous Integration

After upgrading the build pipeline, PipelineRuns will be started to build and test commits in pull requests. The status of the completed PipelineRuns will be visible in the pull requests.

[NOTE]
====
{ProductName} sets an expiration date for images produced from pull request commits. The produced images will be deleted from
quay.io after a week. In order to prevent an image reference from becoming invalid, the image should either be copied to an external
location or the pull request should be merged, triggering a new image build without an expiration set.
====

.Updates

If you upgrade your build pipeline for a component, then whenever we release a new `build-definition` for upgraded pipelines, the {ProductName} bot submits a pull request (PR) to the git repository of your component. These PRs only change the `.tekton` directory of the component repository; they do not alter the source code specific to your component in any way.
Expand Down

0 comments on commit 527c5a6

Please sign in to comment.