+++ This bug was initially created as a clone of Bug #1340787 +++ Repeating bug 1340787 comment #13: (Yesterday) I tried on comm-beta and it didn't work. I've just tried on comm-central and it hasn't worked there either. No confirmation (and no error message) and no job was triggered. I haven't tried C-A or C-esr52 so far. More information/analysis in bug 1340787 comment #14.
There are problems with C-C treeherder. For a while I haven't been able to add job. Today I noticed that I can also not re-run jobs. The request is accepted and then nothing happens. Tom, another job for you ;-)
Have you looked at the buildapi to see if there are pending builds? https://secure.pub.build.mozilla.org/buildapi/self-serve/comm-central is currently showing a number of pending builds. Looking at https://secure.pub.build.mozilla.org/buildapi/pending , windows buildbots are having a bad day.
Hi! Comment 1 and 2 are likely unrelated to comment 0 - it also sounds like there's a backlog, which isn't anything to do with Treeherder. The trigger jobs feature is working now for Firefox repos (was broken for a few weeks), so either this should all be working for you, or it's a C-C specific issue, in which case we don't really have the resources to fix it (there are now only two people working on Treeherder). Fingers crossed the builds complete and all is working anyway :-)
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → INCOMPLETE
OK, the repeated jobs were pending, but the "Add Job" function is broken since bug 1340787, actually no, it worked for a while and then broke again. It's broken now, try it, you get Error fetching runnable jobs: Failed to fetch task ID (No decision task)
As I said, triggering new jobs doesn't work, so maybe Tom can look into that.
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
6 months ago
Status: REOPENED → NEW
(In reply to Jorg K (GMT+2) from comment #4) > OK, the repeated jobs were pending, but the "Add Job" function is broken > since bug 1340787, actually no, it worked for a while and then broke again. > It's broken now, try it, you get > Error fetching runnable jobs: Failed to fetch task ID (No decision task) I suspect the treeherder code now has the assumption that there is a decision task for a push, which would only be the case if there were taskcluster jobs -- almost certainly not the case for C-C. This might be fixable, but it's a bit of a losing battle -- as buildbot becomes rarer, it's going to become increasingly less of a priority for treeherder and Mozilla generally and I would expect more breakage in the future (which people are going to be ever-slower to respond to). If you want to continue using Mozilla infra, I would suggest looking at moving to taskcluster.
Component: Treeherder → Treeherder: Job Triggering & Cancellation
Looks like this is fixed now that c-c has a decision task.
Status: NEW → RESOLVED
Last Resolved: 6 months ago → 3 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.