Booz Allen's lean manufacturing approach for holistically designing, developing and fielding AI solutions across the engineering lifecycle from data processing to model building, tuning, and training to secure operational deployment
While migrating to the ghcr.io as aissemble's new helm repository, we encountered some cyclic tests in the the test-mda-models module. The core issue is the test-chart execution of maven-exec-plugin, which generally looks like:
Of course in the process of migrating to a new helm repo, no charts have been deployed here yet, which uncovered the cycle. We should likely do the following:
update to use the local version of the chart
refactor to at least pull this up to a common pluginDependency definition in test-mda-models so it isn't repeated almost verbatim in four different modules. More ideally, we'd eliminate the use of the maven-exec-plugin for this altogether as it is a generally a pretty good sign we have a workaround in place. Since we've forked the helm-maven-plugin, why not support this with it?
This impacts the following four modules:
test-mda-data-delivery-model
test-mda-data-delivery-model-basic
aissemble-test-data-delivery-pyspark-model
aissemble-test-data-delivery-pyspark-model-basic
In the meantime, the test-chart execution has been disabled by pulling up the existing skip-test profile in those four modules into a common profile in test-mda-models and making it active by default. There is a link to this issue on that block as well as each test-chart execution to help folks that might encounter it until it is fixed.
While migrating to the ghcr.io as aissemble's new helm repository, we encountered some cyclic tests in the the
test-mda-models
module. The core issue is thetest-chart
execution ofmaven-exec-plugin
, which generally looks like:In this block, we reference a remote helm repo:
Of course in the process of migrating to a new helm repo, no charts have been deployed here yet, which uncovered the cycle. We should likely do the following:
pluginDependency
definition intest-mda-models
so it isn't repeated almost verbatim in four different modules. More ideally, we'd eliminate the use of themaven-exec-plugin
for this altogether as it is a generally a pretty good sign we have a workaround in place. Since we've forked thehelm-maven-plugin
, why not support this with it?This impacts the following four modules:
test-mda-data-delivery-model
test-mda-data-delivery-model-basic
aissemble-test-data-delivery-pyspark-model
aissemble-test-data-delivery-pyspark-model-basic
In the meantime, the
test-chart
execution has been disabled by pulling up the existingskip-test
profile in those four modules into a common profile intest-mda-models
and making it active by default. There is a link to this issue on that block as well as eachtest-chart
execution to help folks that might encounter it until it is fixed.