* add glean to treeherder for measuring failure outcomes
* add glean to treeherder for measuring failure outcomes
* allow for notification of glean metrics and ability to turn on/off glean
* add data review bug
* add updatePinnedJobs function to failureSummaryTab
* Update Node.js to v19
* adjust node in package.json as well
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Joel Maher <joel.maher@gmail.com>
* Update position of global celery parameters
* Update celery to 5.2.6
* Reference directly cached-property
* Use shared_task instead of task
* Update env for celery
* Check rabbitmq is up in dev entrypoint
* Setup HOME in dev Dockerfile to avoid mozci crash
* Use INFO log level for celery to see what is going on
* Fix lint on docker/entrypoint.sh
* Update retryable unit test
* Listen to mozci classification pulse messages and save results in Treeherder database
* Nits and suggestions
* Fix tests
* Revert changes
* Add unit tests + Fix review related code snippets
* Nit
* Add a dedicated command to listen to mozci classification pulse messages
Co-authored-by: Eva Bardou <ebardou@teklia.com>
Support for filing issues as security bugs got added in bug 1369067. Having the
security group hardcoded and not matching the default one for the component
causes bugs to get missed during triage.
* Add model for file-to-bugzilla-component relation and its ingestion process
* add API endpoint to get Bugzilla product and component for source file path/search term
* bug filer: identify bugzilla product and component to use based on file path
* First stab at dockerflow support
* Add dockerfile and entrypoint for production builds
* Add docker build to circle
* Add stub version.json file
* Fix linting issues
* Add entrypoints for cronjobs
* Bump python to 3.7.10 to try to fix issues with typing module
* Remove requirement on typing again
* Remove bigquery and activedata references (#7051)
* Remove activedata and bigquery again
* Add importlib-metadata to dev requirements
* Remove remnants of selenium tests from setup.cfg
* Don't call taskcluster.aio.createSession outside of async functions (it's not allowed)
* Disable newrelic linters to fix issue with imp module
See https://discuss.newrelic.com/t/python-warnings-during-pytest/114897
* Fix linting errors
* Use pytest-xdist to speed up tests
* Properly ignore newrelic warnings
* Disable django.contrib.staticfiles in tests, because it breaks everything
* Set TREEHERDER_DEBUG=False for unit tests, because it breaks some tests
* Fix linting issues
* Docker: Bug 1630293 - Increase max MySql connections
* docs: Set a concurrency of 1
* docs: Remove the usage of -B for Docker set up
Using -B in more than one instance will cause the remaining celery beats to
execute in more than one container.
* Reduce unsupported known failure line while still reporting to New Relic
This makes sure that serving the documentation via poetry does not regress
and we have a single way of generating them.
Setting the build backend in `pyproject.toml` makes `pip` to use `poetry` to install the dependencies. By doing so, readthedocs will be able to install the required dependencies to generate the docs (since they don't support poetry directly).
The recent addition of Celery workers consumption has increased the usage
of number of connections to the database.
In certain cases like loading a large number of pushes we can hit the maximum
limit of connections.
This change increases the default `max_connections` to 300 (about double).
* Add Travis job to run Python tests outside of Docker
* `runtests.sh` is renamed to `runchecks.sh` and it does not run Python tests
* `manage.py check --deploy` was duplicated in Travis
* Update testing documentation
* Remove `-bb` since it is not needed since Python 3.5
* Development Docker container to initialize data
`docker-compose up` will now initialize the data for the local database.
This will also include initializing SETA's data.
* Change SETA's logging level and preseed information
The preseed information was all for Buildbot
The logging level changes is in preparation for when production switching to INFO messages instead of WARNING
* Docker container to log INFO messages instead of DEBUG messages
`LOGGING_LEVEL` is now set for the Docker container and it sets the logging
to `INFO` instead of `DEBUG`. The Django app will still be initialize in
debug mode but the default logging will be informative messages.
You can still log debugging messages by setting `LOGGING_LEVEL=DEBUG` before
initializing the Docker container.
* Change permissions for docker/entrypoint.sh
* Allow using Django in localhost
* Documentation changes
Allow running shellcheck tests
Use docker-compose for the Selenium tests
Install docs updates
Switch to yarn cache instead of npm
Install UI dependencies
* Add ability to override DATABASE_URL and use a .env file
We will likely switch to a Docker based solution in the future, however
for now the configs are unused and out of date (fig has been replaced
with docker-compose, we no longer generate per-repo credentials etc).
In addition, there are tools that can convert the Heroku Procfile into
Docker configs, so we may end up using a solution based on that instead.
As such, let's remove the configs (they'll always be available in
version control history) to reduce the maintenance burden and clutter in
the repo.
EvaBardou
Joel Maher
Sebastian Hengst
renovate[bot]
Bastien Abadie
EvaBardou
Sarah Clements
beatrice-acasandrei
Renovate Bot
Ben Hearsum (he/him)
Jeremiah Orem
Cameron Dawson
Armen Zambrano
Armen Zambrano G
Sarah Clements
Ed Morley
Mauro Doglio