no longer using path name in artifact name for bazel project

Summary: Turns out this is no longer necessary if we save the relative path properly - it is exactly equivalent in terms of uniqueness.

Test Plan: N/A

Reviewers: anupc

Reviewed By: anupc

Subscribers: changesbot, kylec

Differential Revision: https://tails.corp.dropbox.com/D225216

changes/models/jobplan.py

@@ -236,7 +236,6 @@ def get_build_step_for_job(cls, job_id):
                 cpus=bazel_cpus,
                 memory=bazel_memory,
                 max_executors=bazel_max_executors,
-                use_path_in_artifact_name=True,
             )
             return jobplan, implementation
 

tests/changes/models/test_job.py

@@ -78,8 +78,6 @@ def test_autogenerated_commands(self, get_config):
         assert implementation.artifacts == []
         assert implementation.artifact_suffix == '.bazel'
 
-        assert implementation.use_path_in_artifact_name is True
-
         assert implementation.commands[0].type == CommandType.setup
         assert implementation.commands[0].script == bazel_setup_expected
 
@@ -126,7 +124,6 @@ def test_autogenerated_commands_with_exclusions(self, get_config):
 
         assert implementation.max_executors == 3
 
-        assert implementation.use_path_in_artifact_name is True
         assert implementation.artifacts == []
         assert implementation.artifact_suffix == '.bazel'