Post-landing CI goals #17541
-
|
I've read the pants CI guide https://www.pantsbuild.org/docs/using-pants-in-ci and understand how to only run the tests on transitive set of tests that differ from trunk. That's great! But I'm a unsure what the typical thing to do is once the code has landed in trunk: Package everything? Package only what has "changed" with some elaborate variant of HEAD^1? Package everything and if you are using a fine grained cache that actually only packages things that have changed? (Same question for "deploy", but I know that's alpha.) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Great question. It really depends on your org's practices of course, but if you have a lot of services, and don't want to redeploy them constantly, then you can use something like, e.g., This assumes your deploys are tagged in git, which is very good practice. |
Beta Was this translation helpful? Give feedback.
Great question. It really depends on your org's practices of course, but if you have a lot of services, and don't want to redeploy them constantly, then you can use something like, e.g.,
./pants list --filter-target-type=pex_binary --changed-since=release_branch --changed-dependents=transitiveto find all the pex_binary targets affected by changes since the release_branch.This assumes your deploys are tagged in git, which is very good practice.