Skip to content
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.

Sign up for GitHub

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

feat(STONEINTG-1002): Multi arch build requirements #222

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(STONEINTG-1002): Multi arch build requirements #222

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/modules/ROOT/pages/how-tos/testing/integration/adding.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@

In {ProductName}, you can add integration tests to verify that the individual components of your application integrate correctly, forming a complete and functional application. {ProductName} runs these integration tests on the container images of components before their release.

+
NOTE: Starting an integration test is dependant on the results of a successful build pipeline providing some required information about an image, details on these requirements can be found link:https://github.com/konflux-ci/architecture/blob/main/architecture/integration-service.md#image-extraction-details[here]. In the case of multi-arch builds, an OCI index that maps to the relevant artifacts is used.

.Prerequisites

* You have created an application in {ProductName}.
Expand Down
2 changes: 1 addition & 1 deletion docs/modules/ROOT/pages/how-tos/testing/integration/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ This document covers the integration tests that {ProductName} triggers after com

Integration tests ensure that all built components conform to some set of requirements. xref:how-tos/testing/integration/adding.adoc[Adding an integration test] is as simple as providing a reference to a git repository and the path to the Tekton pipeline that defines the test.

After a successful build pipeline, a snapshot is created with the just-produced component and the remaining component references from the application's Global Candidate List. The configured integration test scenarios are then run against this snapshot. If you need to run the snapshots through custom checks, you can also xref:how-tos/testing/integration/creating.adoc[create your own integration tests].
After a successful build pipeline, a snapshot is created with the just-produced component and the remaining component references from the application's Global Candidate List. The configured integration test scenarios are then run against this snapshot. Note that in order for integration tests to successfully run, the service requires a valid pullspec for the components. If you need to run the snapshots through custom checks, you can also xref:how-tos/testing/integration/creating.adoc[create your own integration tests].

The integration service provides users with the ability to reset their component’s Global Candidate List to a desired state with a manually created `override`. You can xref:how-tos/testing/integration/creating.adoc[create an override snapshot] and provide a valid container image for a component to reset the component’s Global Candidate List.

Expand Down
Loading