You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered: