build-deploy documentation #273
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nilsgstrabo
requested review from
satr,
Richard87,
emirgens,
sveinpj and
sondresjolyst
emirgens
reviewed
Nov 10, 2023
Comment on lines
97
to
100
| - Pipelines created manually from `Radix Web Console` or `Radix CLI` will always build all components and jobs. | ||
| - When pipelines are created from a `Github webhook`, Radix will only build components and jobs that affected by the changes, and reuse images from the active deployment for unchanged components/jobs. | ||
| - When Radix detects that `radixconfig.yaml` is modified, all components and jobs are built. | ||
| - When `build secret` values are updated, the next pipeline job will build all components and jobs. |
There was a problem hiding this comment.
Put this on top, this is the main thing
emirgens
reviewed
Nov 10, 2023
satr
reviewed
Nov 10, 2023
|
|
||
| There are few options how the code can be located in the GitHub repository for a Radix application: | ||
| For manually created pipeline jobs, Radix will always build all components and jobs. When a pipeline job is created from a Github webhook, Radix compares the commit ID from the webhook request body with the commit ID of the active deployment to detect which directories have changed. The list of changed directories are then compared to the `src` property for each component and job, and if any of the changed directories are equal to, or a child of `src`, a new image is built for the component/job. Radix will reuse the image from the current active deployment for components and jobs that have not changed. |
There was a problem hiding this comment.
Suggested change
| For manually created pipeline jobs, Radix will always build all components and jobs. When a pipeline job is created from a Github webhook, Radix compares the commit ID from the webhook request body with the commit ID of the active deployment to detect which directories have changed. The list of changed directories are then compared to the `src` property for each component and job, and if any of the changed directories are equal to, or a child of `src`, a new image is built for the component/job. Radix will reuse the image from the current active deployment for components and jobs that have not changed. | |
| For manually created pipeline jobs, Radix will always build all components and jobs without defined property `image`. When a pipeline job is created by a Github webhook, Radix compares the commit ID from the webhook request body with the commit ID of the active deployment to detect which directories have changed. The list of changed directories are then compared to the `src` property for each component and job: | |
| * If any of the changed directories are within the directory, defined in `src` or are its sub-directories, a new image is built for the component and job. | |
| * if no such changes detected, Radix will reuse the image from the current active deployment for components and jobs. |
There was a problem hiding this comment.
This is described in the previous paragraph. I don't think there is a need to describe it one more time.
Richard87
requested changes
Nov 13, 2023
satr
previously approved these changes
Nov 13, 2023
satr
approved these changes
Nov 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.