Django rest framework can't handle model view sets which don't have a model
for this case. Since the job-log-url endpoint isn't really a model viewset,
let's give it the correct class name.
The admin.js file has es6 templating syntax which is not considered
valid in our Karma tests. This moves the admin controller to the
/admin folder where it should be anyway, so that the UI tests stop
failing.
This moves the Sheriff panel out to a full-page app. The functionality
is basically the same, however. Much of the logic and HTML were just
copied from the Sheriff panel.
This also introduces ReactJS to the repo. This was used to speed up
the rendering of the reference data lists in the Exclusions detail
editor. The ``reactselect`` component is defined as normal JavaScript.
We decided not to introduce using JSX at this time.
We need to update the template value on angular digest cycles, because
we can't count on the "raw log url" being available when we first render the
template (the job may still be loading).
Upcoming changes in bug 1295380 will change log output for many tests
in TaskCluster resulting in lines being prefixed with a timestamp and
the task step name. Unless these line prefixes are handled, it
confuses the error parser.
This commit detects logs as coming from TaskCluster and strips their
line prefix accordingly.
This changes ingestion, the API endpoints, and the frontend to match
the new structure. For now we continue to store text_log_summary artifacts,
though they don't do anything anymore.
Upcoming changes in bug 1295380 will change log output for many tests
in TaskCluster resulting in lines being prefixed with a timestamp and
the task step name. Unless these line prefixes are handled, it
confuses the error parser.
This commit detects logs as coming from TaskCluster and strips their
line prefix accordingly.
When you select a single job and then press the cancel all jobs button,
the behavior of the cancel all jobs button so it cancels just the selected
job.
Prior to this patch, the selected job can be canceled no matter which
cancel all jobs button is clicked, even if the selected job is from a
different push. This push only activates the selected job behavior when
the selected job is from the push where the cancel all jobs button was
pressed.
Previously `<site-root>/revision.txt` would 404 if `SERVE_MINIFIED_UI`
was unset on Heroku, which would then cause the next deploy to fail.
It's now made available in both the `ui/` and `dist/` directories, so
it can be found regardless of the value of `SERVE_MINIFIED_UI`.