In all likelihood, this is something that Acorn UI build (Gradle plugin or homegrown build task) should not own. However, it will serve as a pattern by example that they can use. This is because we don't know where they will want to deploy and the mechanisms needed to deploy.
Make sure there's a deploy task that will only run when a CI build is triggered, but does nothing and is disable it by default. Most consumers will want to modify, delete, or disable this task.
In all likelihood, this is something that Acorn UI build (Gradle plugin or homegrown build task) should not own. However, it will serve as a pattern by example that they can use. This is because we don't know where they will want to deploy and the mechanisms needed to deploy.
Make sure there's a
deploy
task that will only run when a CI build is triggered, but does nothing and is disable it by default. Most consumers will want to modify, delete, or disable this task.