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
After switching over to kubecf, we feel there is a need to build a tool for developers which would make changing, building, deploying and testing changes in BOSH releases consumed by kubecf.
The anatomy of the current process is as follows:
Clone the target BOSH release and make changes locally or push it to feature branch.
Create a BOSH release using bosh create-release...
Build its release image using fissile build release-images...
Load that image into target system e.g: minikube or kind.
Test the changes.
If there are any issues then repeat step 1 through 6.
We have created a script to automate the aforementioned steps in the attached script - rebuild-brains.sh.txt, however its not generic and easily configurable. It would be great to see if this use-case can be accomodated in catapult.
The text was updated successfully, but these errors were encountered:
I would just approach this the following way, but it's just a suggestion:
add a make bosh that checkouts the code if not present into the buildfolder and builds bosh.
add a make fissile (there's is already a target like that, maybe needs to be rewritten or a different name) that takes the artifacts inside a know path in the buildfolder and builds a fislle image, and uploads it
By making the targets idempotent, you can call them several times, and even like make bosh fissile of course.
This maybe should go in modules/scf/* or modules/extra/* for now, we can change it later.
After switching over to kubecf, we feel there is a need to build a tool for developers which would make changing, building, deploying and testing changes in BOSH releases consumed by kubecf.
The anatomy of the current process is as follows:
bosh create-release...
fissile build release-images...
minikube
orkind
.We have created a script to automate the aforementioned steps in the attached script - rebuild-brains.sh.txt, however its not generic and easily configurable. It would be great to see if this use-case can be accomodated in catapult.
The text was updated successfully, but these errors were encountered: