A current workflow that we have is that make is us...
# generalp
purple-plastic-57801
03/04/2023, 7:40 PMA current workflow that we have is that make is used to download several artifacts that are required to test.
In bazel land, I have a written rules that will grab external dependencies, and associate them as dependencies for whichever label I’m building as needed.
Is there a way to do the same thing in pants?
e
enough-analyst-54434
03/04/2023, 7:41 PMPants subsets the lock for each test file executed.
enough-analyst-54434
03/04/2023, 7:41 PMEach test runs with exactly and only its real deps IOW.
enough-analyst-54434
03/04/2023, 7:41 PMIs that what you mean?
enough-analyst-54434
03/04/2023, 7:42 PMOr by artifact do you mean blob - not Python package dependency artifact? Like a text file or something.
p
purple-plastic-57801
03/04/2023, 7:43 PMCorrect. An external resource that is required for the test to run. Test data.
purple-plastic-57801
03/04/2023, 7:44 PMSo is there a way to specify this external HTTP endpoint and checksum are dependencies for this test target?
e
enough-analyst-54434
03/04/2023, 7:44 PMSee `resource`: https://www.pantsbuild.org/docs/reference-resource#codesourcecode
You would depend on a resource.
enough-analyst-54434
03/04/2023, 7:45 PMThose sorts of deps are ~obviously not inferrable. You have to go old school and edit the
python_testsdependenciesBUILDenough-analyst-54434
03/04/2023, 7:46 PMSo, you just add 1 dependency entry. The rest of the Python import deps 1st and 3rd party are still inferred. That manual addition is just added in.
👍 1
3 Views