We'd like some easier to process data from Milo.BuildInfo cbuildbot stages, as we are depending more on the API to fill in our build details page.

Here is an example for a current build stage in the API result:

"step": {
  "name": "VMTest (attempt 1) : [SKIPPED]",
  "status": "SUCCESS",
  "stdoutStream": {
     "name": "recipes/steps/VMTest__attempt_1__:__SKIPPED_/0/stdout"
   },
   "started": "2017-07-24T01:02:49.097813829Z",
   "ended": "2017-07-24T01:02:49.098639964Z"
}

(for more example, see http://shortn/_O8k3d6RA8V)

The proposed changes are: 
1. Put only the stage name in the name field. In the above example, that is getting rid of the (attemp 1) : [SKIPPED]",
2. Stage name should either be the same as they are in CIDB, or stage should have a field that tells us the CIDB id for the stage, so that we can easily cross-reference to get more accurate time.
2. We should being able to use stage name as an id for a build stage for our UI purpose, so they should be unique (e.g, no two CommitQueueSync stages for the same build)

3. Status should reflect the real status of the stage. In the above example, it should be "skipped" as opposed to "success". 

Let me know how this sound :-) 
 

We'd like some easier to process data from Milo.BuildInfo cbuildbot stages, as we are depending more on the API to fill in our build details page.

Here is an example for a current build stage in the API result:

"step": {
  "name": "VMTest (attempt 1) : [SKIPPED]",
  "status": "SUCCESS",
  "stdoutStream": {
     "name": "recipes/steps/VMTest__attempt_1__:__SKIPPED_/0/stdout"
   },
   "started": "2017-07-24T01:02:49.097813829Z",
   "ended": "2017-07-24T01:02:49.098639964Z"
}

(for more example, see http://shortn/_O8k3d6RA8V)

The proposed changes are: 
1. Put only the stage name in the name field. In the above example, that is getting rid of the (attemp 1) : [SKIPPED]",
2. Stage name should either be the same as they are in CIDB, or stage should have a field that tells us the CIDB id for the stage, so that we can easily cross-reference to get more accurate time.
2. We should be able to use stage name as an id for a build stage for our UI purpose, so they should be unique (e.g, no two CommitQueueSync stages for the same build)

3. Status should reflect the real status of the stage. In the above example, it should be "skipped" as opposed to "success". 

Let me know how this sound :-)