Inheritance methods of Metadata is not intuitive

[yakanechi]

What happened:
If there are multiple trigger sources for the current metadata, the value of the job that completed first takes precedence.
In the following example, the value is set in job1 and then reset in job3, but job2 is completed before job3, so the value of x is 1 in job4.
It seems strange that values set later are not used.

What you expected to happen:
Consider adding a timestamp-like feature for each metadata, with the newly added ones taking precedence.

How to reproduce it:

jobs:
  Job1:
    requires: [ ~commit ]
    steps:
      - meta set x "1"

  Job2:
    requires: [ ~Job1 ]
    steps:
      - echo "nothing"

  Job3:
    requires: [ ~Job1 ]
    steps:
      - sleep 60
      - meta set x "2"

  Job4:
    requires: [ Job2, Job3 ]
    steps:
      - echo $(meta get x)

[VonnyJap]

@sagar1312 @tkyi - do you guys have any thoughts on how to solve this issue? Basically this looks like a bug, x should be seen as 2 in Job4, but users are seeing the old value 1 returned.

[tkyi]

Yeah that sounds like a bug. Should be the more recently finished build that takes precedence.