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.

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

Next Build application injection #575

Closed
2 tasks
mreed101 opened this issue Jun 27, 2024 · 0 comments
Closed
2 tasks

Next Build application injection #575

mreed101 opened this issue Jun 27, 2024 · 0 comments
Labels
epic A collection of user stories spanning multiple repositories

Comments

@mreed101
Copy link
Contributor

mreed101 commented Jun 27, 2024

Description

Next build needs the ability to mimic the behavior of Content Build by pulling in vets-website applications and being able to test those applications locally.

Currently there is a problem that exist in content-build that we want to avoid in next-build, if an application is removed from vets-website but not updated in registry.json (inside of content-build) this will cause content-build to fail during it's continuous deployment build.

It would be a good idea if we can grab registry.json directly out of the vets-website repo. We already are pulling the vets-website asset directly from their s3 bucket so this may be simple enough to achieve.

Supporting Details

The following guide walks through how applications currently work in content-build

Task

@mreed101 mreed101 mentioned this issue Jul 3, 2024
11 tasks
@mreed101 mreed101 added the epic A collection of user stories spanning multiple repositories label Aug 19, 2024
@mreed101 mreed101 closed this as completed Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic A collection of user stories spanning multiple repositories
Projects
None yet
Development

No branches or pull requests

1 participant