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
Describe what should be investigated or refactored
Currently the make file builds lots of binaries needed for end to end tests. Instead of rebuilding binaries or zarf packages on each subsequent run we simply check if they are there. This saves time but can lead to testing on old binaries or packages if they have changed. It would be better if we dynamically recreated binaries or packages within make if anything changed.
For example:
any go code changes should lead to re-build on make
any changes to the init package or zarf agent should lead to a rebuild of the init package on make init-package
any change to any of the example packages should lead to rebuild - ideally this could be done dynamically but if that's not doable I still believe hard coding the paths is worth it.
The text was updated successfully, but these errors were encountered:
Describe what should be investigated or refactored
Currently the make file builds lots of binaries needed for end to end tests. Instead of rebuilding binaries or zarf packages on each subsequent run we simply check if they are there. This saves time but can lead to testing on old binaries or packages if they have changed. It would be better if we dynamically recreated binaries or packages within make if anything changed.
For example:
make
make init-package
The text was updated successfully, but these errors were encountered: