-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Committing CI artifacts
- Loading branch information
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
title: Committing CI artifacts | ||
date: 2024-07-03 | ||
permalink: daily/2024/07/03/committing-ci-artifacts | ||
tags: | ||
- software-development | ||
- git | ||
cta: ~ | ||
snippet: | | ||
Do you commit artifacts from your CI pipeline? | ||
--- | ||
|
||
One of the main uses for [a CI pipeline][0] is to build artifacts for your application, such as installing your dependencies using Composer or npm, or using build tools to perform tasks such as building your CSS and JavaScript assets. | ||
|
||
Performing these tasks in a CI pipeline means the resulting files can be ignored from your code repository and not committed - making your commits smaller and easier to review, and less likely for you to encounter merge conflicts. | ||
|
||
The alternative approach is to not use a CI pipline and to perform the tasks manually and commit them to your repository. | ||
|
||
This introduces a separate set of challenges, but people like having the files in their repository and not worrying about failures in their pipeline. | ||
|
||
Which do you prefer? | ||
|
||
[0]: {{site.url}}/daily/2024/07/02/ci-not-ci-pipeline |