Bugzilla

(In reply to Cameron Dawson [:camd] from comment #13)

> Yeah, I agree with you here, Sarah.  wrt those TinderboxPrintlines, I wonder how we can determine if they give any value to folks.  It's possible nobody cares about them.  I remember some conversations we had with Ed way back when (as you mentioned).  We could add a little badge in the ui next to the printlines of `deprecated` or something and see if someone files a bug asking to keep them.  Or remove them and see if anybody screams.  :D.

I was planning to send an email out on Monday to dev-platform mailing list about the plan to stop ingesting uploaded artifacts at (roughly) end of month. So, I could also mention that we are thinking of not processing those TinderboxPrint lines at a later date and solicit feedback on it. They'd still be in the logs for people to look at, but we wouldn't be parsing it to add to the JobDetail table. Maybe we'd get some feedback that way.

I know that Tom.Prince finds value in the "Built by... " urls parsed from TinderboxPrint and he suggested he could create a structured artifact (I'm actually realizing I'm not clear on what that means, but could it then be retrieved from the taskcluster public artifacts API instead?). 

> can you hide them behind a + button- keep metrics whenever the + button is expanded to show the data? I would say 45 days of collecting data would be enough data to make an informed decision.

I don't think how they're displayed is the issue, just a question of if we're ingesting them and no one really looks at that data in the job details or log viewer panels.

(In reply to Cameron Dawson [:camd] from comment #13)

> Yeah, I agree with you here, Sarah.  wrt those TinderboxPrintlines, I wonder how we can determine if they give any value to folks.  It's possible nobody cares about them.  I remember some conversations we had with Ed way back when (as you mentioned).  We could add a little badge in the ui next to the printlines of `deprecated` or something and see if someone files a bug asking to keep them.  Or remove them and see if anybody screams.  :D.

I was planning to send an email out on Monday to dev-platform mailing list about the plan to stop ingesting uploaded artifacts at (roughly) end of month. So, I could also mention that we are thinking of not processing those TinderboxPrint lines at a later date and solicit feedback on it. They'd still be in the logs for people to look at, but we wouldn't be parsing it to add to the JobDetail table. Maybe we'd get some feedback that way.

I know that Tom.Prince finds value in the "Built by... " urls parsed from TinderboxPrint and he suggested he could create a structured artifact - see bug 1625033. (I'm actually realizing I'm not clear on what that means, but could it then be retrieved from the taskcluster public artifacts API instead?)

> can you hide them behind a + button- keep metrics whenever the + button is expanded to show the data? I would say 45 days of collecting data would be enough data to make an informed decision.

I don't think how they're displayed is the issue, just a question of if we're ingesting them and no one really looks at that data in the job details or log viewer panels.