"build time" includes time waiting in a queue

[jaredly]

It seems there ought to be a duration field stored in the database. Because finished-created doesn't quite capture it.

[niallo]

we could add another field like "start_timestamp" which is set to the moment the simple-worker actually begins processing. thoughts?

on a related note, the "-1" duration on the job dashboard should be fixable with client-side code?

[jaredly]

yeah I like the idea of a "start_timestamp".
Yeah, that will eventually have the same running counter you see on the
build page.

On Sun, Jul 21, 2013 at 11:44 PM, niallo notifications@github.com wrote:

we could add another field like "start_timestamp" which is set to the
moment the simple-worker actually begins processing. thoughts?

on a related note, the "-1" duration on the job dashboard should be
fixable with client-side code?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/133#issuecomment-21325687
.

[niallo]

for start_timestamp, we just need to add an additional property on "update_status" events. when this is included, Strider can save it to the job document.

[jaredly]

yup. sounds great.

On Sun, Jul 21, 2013 at 11:47 PM, niallo notifications@github.com wrote:

for start_timestamp, we just need to add an additional property on
"update_status" events. when this is included, Strider can save it to the
job document.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/133#issuecomment-21325742
.

[jaredly]

I'd also like to separate out "deploy time". Because deploying to heroku
can add on another 5-10 minutes to the overall build time ... and I don't
know that I'm as much interested in that as in the time it takes to build &
run tests.

On Sun, Jul 21, 2013 at 11:48 PM, Jared Forsyth jabapyth@gmail.com wrote:

yup. sounds great.

On Sun, Jul 21, 2013 at 11:47 PM, niallo notifications@github.com wrote:

for start_timestamp, we just need to add an additional property on
"update_status" events. when this is included, Strider can save it to the
job document.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/133#issuecomment-21325742
.

[niallo]

Looks like this is done in master.