If we feel we're courageos enough, we could schedule Fennec 53.0b2 via the releasetasks. All the tasks are contained within a single graph now, sans few builders that are still known to have issues.
I've updated the docs steps here but I wouldn't rush into merging the PR until we've successfully tested this method against a release to see it works (well, I mean a real release, I've alredy played with a staging one). Alternatively, we have the hook + tweaking the graph to only do the second graph.
Since the Go-to-build is coming most likely late on PST timezone, I thought you might give this a try and if it works, please merge the PR. If it doesn't, we can use the hook.
@escapewindow
I'll go ahead and merge this as I also included the fall-back steps from before. We should use this new approach for the next beta to test our graph limitations.
@escapewindow
If we feel we're courageos enough, we could schedule Fennec 53.0b2 via the releasetasks. All the tasks are contained within a single graph now, sans few builders that are still known to have issues.
I've updated the docs steps here but I wouldn't rush into merging the PR until we've successfully tested this method against a release to see it works (well, I mean a real release, I've alredy played with a staging one). Alternatively, we have the hook + tweaking the graph to only do the second graph.
Since the Go-to-build is coming most likely late on PST timezone, I thought you might give this a try and if it works, please merge the PR. If it doesn't, we can use the hook.