-
Notifications
You must be signed in to change notification settings - Fork 70
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.
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
[DOCS] Updates README with information about content-build #15961
Conversation
7702949
to
9f61c23
Compare
@@ -124,7 +124,7 @@ The production instance of the CMS is utilized in two main ways: | |||
|
|||
#### Build and Release Process | |||
|
|||
In a continuous integration context, the `content-build` project is managed as a dependency of the CMS project; the build script is executed targeting the local instance and runs all of the content queries performed as part of the normal content release process, to ensure no changes have been introduced to the CMS codebase that break compatibility. A full content build happens at the conclusion of the testing pipeline on our [Tugboat](https://tugboat.qa/) preview environments. | |||
In a continuous integration context, the `content-build` project is managed as a dependency of the CMS project; the build script is executed targeting the local instance--the database and code of which is from the day before--and runs all of the content queries performed as part of the normal content release process, to ensure no changes have been introduced to the CMS codebase that break compatibility. A full content build happens at the conclusion of the testing pipeline on our [Tugboat](https://tugboat.qa/) preview environments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't correct. The database and code are current at the time the build script is run in a CI context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ndouglas Perhaps I misinterpreted Steve's comment here: https://dsva.slack.com/archives/C0FQSS30V/p1698873014936379?thread_ts=1698852721.440479&cid=C0FQSS30V
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Steve's comment is referring to the content-build
repository's CI process. This section is referring to the va.gov-cms
repository's CI process.
In the content-build
repository's CI process, the build script is not managed as a dependency of the CMS project and is not executed targeting the local instance of the CMS; there is no local instance.
Unclear where to add information about the content-build using yesterday's CMS code and db. |
Description
Relates to #15960
Testing done
N/A
Screenshots
N/A
QA steps
Definition of Done
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing