Before actions were generated by triggering hooks, treeherder generated action
tasks directly. When doing this, the calling code generated the task id, and
then used that to link to the task. Now that things are generated via hooks,
refactor things so the calling code gets the task id from the code triggering
the hook.
It seems that Heroku Review apps have regressed and they are not being added to ALLOWED_HOSTS, thus,
making the web deployment have lost of errors (one of them below):
> ERROR [django.security.DisallowedHost:77] Invalid HTTP_HOST header: 'treeherder-pulse-lsiten-afvimm.herokuapp.com'. You may need to add 'treeherder-pulse-lsiten-afvimm.herokuapp.com' to ALLOWED_HOSTS.
This change can be manually tested like this:
```shell
% export HEROKU_REVIEW_APP=1
% export HEROKU_APP_NAME=treeherder-foo
% python -c "from treeherder.config import settings; print(settings.ALLOWED_HOSTS)"
['https://treeherder-foo.herokuapp.com']
```
* Configuration for black
* changes congiguration
* change pyproject's directory
* add files to be excluded and skip string normalization
* removed isort from pre-commit
* remove version locks for black
* fix
* remove all isort
* update requirements
Co-authored-by: SuyashSalampuria <suyash546@gmail.com>
Co-authored-by: Kyle Lahnakoski <kyle@lahnakoski.com>
This permits setting up the complete ingestion pipeline with a single command.
It only ingests from autoland and tries to use minimal resources on a localhost.
Co-authored-by: Armen Zambrano <armenzg@users.noreply.github.com>
* fixed bug Redirecting to correct url on changing the status or framework filter
* Changed the updated filter logic from status and frameworks to not pages in AlertsView.js
* Kyles recommended changes
The most common issue with failed tasks except intermittent failures are
check-in related issues. Until now, the tasks in 'Similar Jobs' were ordered by
the task's start time which was confusing if tasks had been requested to run
again ("retrigger") because the list jumped between pushes. With the new order
by pushes, issues can be more easily associated with a push/check-in.
The downside is that infrastructure related issues are harder to spot but in
general these don't affect only one kind of task (which the 'Similar Jobs' tab
focuses on).
This is part 1 of this bug and only makes changes to how JobDetails API
is used in the UI to retrieve uploaded artifacts. It updates ReplicatesGraph,
DetailsPanel, UnsupportedJob and LogViewer App. Adds helpers and updates tests.
* Bug 1626914 - Make Review Apps use Pulse credentials secret
In the beginning of the Heroku Review Apps it made sense to create a user/password that was shared accross apps and be publicly available (since each app would generate their own random queue names).
Unfortunately, last night, I saw a lot of alerts for queues that were overgrowing. We recently
landed some code that should be deleting queues once there are no consumers (which was not happening). This could be because we had a Review app from a long time ago create lots of queues that were not auto-deleted or someone locally is doing development with the shared credentials unknowingly creating many queues.
Either way, the new Heroku Review apps allow defining config variables (secrets) at the pipeline level and are injected in the Review apps upon creation.
I've reset the treeherder-shared-pulse-user password and created a PULSE_URL config var with the new password.
* Checking for NEW_RELIC_INSIGHTS_API_KEY prevents review apps from releasing
Kyle Lahnakoski
Shubhank Saxena
Cameron Dawson
Sebastian Hengst
Tom Prince
ionutgoldan
esanuandra
alexandru-io
Armen Zambrano
Sarah Clements
dependabot[bot]
PIGNOSE
Shubham Kumar
octavian-negru
Suyash Salampuria
Armen Zambrano G
Ishita Kumar
KWierso
Simon Sapin
Alexandru Irimovici
Edwin Takahashi
ssalarda