fierce-plastic-71129
03/23/2021, 7:17 PM--changed-parent
and --changed-include-dependees
). Is there a way to compute precisely the targets that have been impacted by a change?witty-crayon-22786
03/23/2021, 7:28 PM--changed
flags will report those targets as potentially changed.witty-crayon-22786
03/23/2021, 7:29 PMwitty-crayon-22786
03/23/2021, 7:36 PMhundreds-father-404
03/23/2021, 7:41 PM./pants tailor
. See https://www.pantsbuild.org/docs/targets#target-granularity-for-first-party-code for the guidance there (to be clear, not required to do)fierce-plastic-71129
03/23/2021, 8:38 PM1.11
) so we’re not using dependency inference. For local tests, it’s indeed not much of a problem since those are cached. But on a build server, you can’t always assume that the test cache will be warm. More generally speaking, I think there is a need to know exactly what targets have changed as a result of a change. For example, we have a custom target type for a service and we want to detect exactly what services need to be redeployed after a change is landed. We were hoping to implement this logic using the pants but due to the false positive, it looks we’re going to have to re-implement all of this ourselves.witty-crayon-22786
03/23/2021, 8:38 PMwitty-crayon-22786
03/23/2021, 8:41 PMFor example, we have a custom target type for a service and we want to detect exactly what services need to be redeployed after a change is landed.one way to approach this is to use the digest of the output binary to skip work. that still relies on caching though.
witty-crayon-22786
03/23/2021, 8:42 PMwitty-crayon-22786
03/23/2021, 8:43 PM--changed
flags: https://github.com/pantsbuild/pants/issues/11206 … but we’re unlikely to be able to start that until later this year.fierce-plastic-71129
03/23/2021, 8:48 PMhundreds-father-404
03/23/2021, 8:49 PMfierce-plastic-71129
03/23/2021, 8:56 PMwitty-crayon-22786
03/23/2021, 10:09 PMwitty-crayon-22786
03/23/2021, 10:11 PMwitty-crayon-22786
03/23/2021, 10:12 PM