Project

General

Profile

Actions

Bug #3831

closed

[Crunch] inconsistent find_or_create behavior in pipeline runner vs job

Added by Ward Vandewege over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
0.5

Description

The pipeline runner automatically adds a find_or_create = true field for jobs in the pipeline, if one does not exist. This inverts the documented default behavior at the job level (which is find_or_create = false).

Either we need to change the pipeline runner behavior, or we need to explicitly document this. It's very confusing to have a different default at different layers in our stack, though.

Actions #1

Updated by Ward Vandewege over 9 years ago

  • Description updated (diff)
Actions #2

Updated by Ward Vandewege over 9 years ago

  • Subject changed from [Crunch] inconsistent find_or_create behavior in pipeline runner vs jobs to [Crunch] inconsistent find_or_create behavior in pipeline runner vs job
Actions #3

Updated by Ward Vandewege over 9 years ago

  • Target version set to Arvados Future Sprints
Actions #4

Updated by Tom Clegg over 9 years ago

  • Status changed from New to In Progress
  • Story points set to 0.5
Actions #5

Updated by Tom Clegg about 7 years ago

  • Status changed from In Progress to Closed
Actions #6

Updated by Tom Clegg about 7 years ago

  • Target version deleted (Arvados Future Sprints)
Actions

Also available in: Atom PDF