Planned Outage: Taskotron Production - 2017-04-25 @ 19:00
by Tim Flink
There there will be an outage starting at 2017-04-25 19:00 UTC, which
will last approximately 2 hours.
This is less notice than I would like but we're going to have some
downtime for Taskotron later today. I suspect that the actual outage
will be less than 2 hours but for the sake of safety, we've left it
that long.
The primary purpose of this outage is to get the production resultsdb
database off of the common host that most of the rest of the QA apps
are using. There have been some performance issues as of late and we
want to start narrowing down what could be causing the problem.
Tim
7 years
Re-Scheduling Jobs for Taskotron as a User
by Tim Flink
One of the things that seems like it is and will be a pain point for
folks writing package-specific tasks is how to work through the times
when there was an issue in the task and things didn't run well. At the
moment, the only solution we have is to re-build the affected package
or to pester an admin to re-run the trigger - neither of which is an
ideal answer.
I was thinking about how to improve this in the near future and am
wondering about adding a "reschedule" button to execdb jobs:
1. authenticated user clicks on "reschedule" button
2. execdb makes an api call to the buildmaster to find the parameters
which were used for that task
3. using the data from 2), execdb starts a new job for just that
item and item type
I'm not thrilled at the idea of code duplication here between trigger
and execdb but compared to figuring out a web interface for trigger,
this seems like a more tractable solution for the short/medium term.
Thoughts?
Tim
7 years
Proposal to CANCEL: 2017-04-17 QA Devel Meeting
by Tim Flink
It's a holiday for many of the usual suspects and seeing as how
attendance will likely be low, I'm proposing that we cancel the usual
QA Devel meeting.
If there are topics that you think need to be discussed this week,
reply to this thread and we can un-cancel.
Tim
7 years