CHANGELOG.md

1.89

This 1.89 release comes with quite several changes:

• api/rest.py: check if callback exception has messages attribute
• ci:
  • backend/lava.py:
    • add sanity check in job_name
    • fix cases for empty job_name in definition
  • ci/tasks.py:
    • check if job exists before fetching
    • do not fetch jobs without job_id
• core/models.py: prevend malformed yaml to be saved
• core/callback.py: handle requests exceptions
• core/history.py: check for empty projects
• frontend/comparison.py: sanity check project slug
• plugins/linux_log_parser:
  • Add support for test name regex
  • Move test name regex to higher level

1.88

This 1.88 release adds a neat feature that gives the user the exact log link of a LAVA test.

1.87

This 1.87 release does a bit of Python updates. The github actions have stopped working for a while and needed a set of commits to go back working. Part of these changes are related to new Python versions. Newer SQUAD releases should start supportting Python > 3.10, as older versions are going to be deprecated soon.

The release also fetches build metadata for jobs coming from Tuxsuite backend and lastly it changes log-parser plugin to optionally fetch kernel panics without square braces around cut-here (thanks Anders!).

1.86.3

This 1.86.3 release fixes deprecation warnings regarding imp module

1.86.2

This 1.86.2 release fixes tuxsuite backend to mark jobs as canceled when requested.

1.86.1

This 1.86.1 release adds support for filtering testjobs by created_at attribute

1.86

This 1.86 release adds an extension of DRF's UserRateThrottle by allowing throttling users registered via social accounts.

1.85

This 1.85 release changes the test jobs page to only display resubmit and cancel buttons when backend really supports it.

1.84

This 1.84 release has a new way to run SQUAD via docker-compose, thanks to @swvanbuuren!

The release also counts with a few improvements on the REST API and CI module.

Complete list of changes going in:

• api: rest:
  • register only one build endpoint
  • add skip filter
• ci:
  • fetch LAVA job definition for watchjobs
  • fix variable naming of get_job_definition methods
  • add test for getting job definitions to testing backend
  • account for backends without job definition
• docs:
  • .readthedocs.yml: bump Python to 3.10
  • update authorization token header in SQUAD docs
  • make docker compose definition generic
  • add docker compose example incl. documentation
  • change localhost port behavior

1.83

This 1.83 release improves documentation and how to run SQUAD.

1.82

This 1.82 release improves performance of release 1.81 and also adds title to all pages in SQUAD.

1.81.1

This 1.81.1 release uses the most recent release of plugins

1.81

This 1.81 release reverts part of 1.80 regarding plugin postprocessing.

It still uses the queue ci_fetch_postprocess, but instead of waiting for plugin subtasks on the main thread, it relies on plugins to invoke a SQUAD task that updates testjob status. This should increase overall consistency in SQUAD.

1.80

This 1.80 release adds Tuxsuite new metadata when fetching tests.

The release also changes a bit how SQUAD does postprocessing of testjobs. There was a bug in SQUAD that would cause inconsistencies if SQUAD was deployed in a auto-scalable environment. The bug is resolved by creating a separate queue called "ci_fetch_postprocess" to be consumed by a persistent worker.

1.79

This 1.79 release expands the Tuxsuite backend regex to accept groups and projects with the dot ('.') character in it.

1.78

This 1.78 release adds a tiny bit of per-user confiuration of the UI. When viewing a build, a user can opt to see only failures or a summary of all tests. This setting was set to failures only before, but now can be customized per user under user menu "User Preferences".

1.77

This 1.77 release adds two little features in SQUAD api. First one is when using /api/submit/, SQUAD will now return the id of the test run just created. The second feature is a new flag ?delay_fetch when passed to /api/watchjob/ which tells SQUAD not to schedule the jobs to be fetched right away.

1.76.2

This 1.76.2 release fixes job status when fetching jobs.

1.76.1

This 1.76.1 release adds download_url attribute to attachments block. It is better if the client already knows the url to download such attachments.

1.76

This 1.76 release adds REST API endpoints to download TestRun attachments.

1.75.1

This 1.75.1 release fixes 2 small bugs from past release.

First one is to avoid getting build_name from oe builds and the second bug fix is related to loading projects with builds without status objects associated.

The latter would only happen on SQUAD instances older than 2018.

1.75

This 1.75 release fixes an important bug that has been around unnoticed for quite some time.

The bug is basically a race condition when a build is marked as finished too early, before all testjobs results are actually done processing. The fix should address that issue.

The release also allows listing projects in group's home page by active in last N days. Within project settings one can determine N.

There has been added support for accepting OE builds from Tuxsuite and support for squad-client will come soon.

Complete list of changes going in:

• api/rest.py: re-add suite to failures with confidence endpoint
• ci/backend/tuxsuite.py: support oe builds
• ci/models.py: bring pending function to TestJob
• settings.py: support newer versions of django-allauth
• squad/core/models.py: Change important metadata to support custom order
• squad/frontend/views.py,squad/core/models.py: move sorting of metadata
• squad/frontend/views.py: Add support for filtering project list by age

1.74

This 1.74 release patches a couple of pages improving overall performance.

It improves loading times of build tests page, test history and build comparison by tests.

The release also removes "Test failures" page, given that there's already and API endpoint for it and it is cumbersome to maintain an UI for it as well. Finaly, this release removes the transitions table from build comparison page, which allowed users to query changes by specific transitions. This is too expensive to compute in larger SQUAD instances.

Complete list of changes going in:

• api/rest.py:
  • fix failures with confidence pagination
  • re-add test id and test run on failures_with_confidence endpoint
  • support looking release builds only
• backend/tuxsuite.py:
  • avoid making extra requests when retrieving build_name
  • support tuxsuite sanity tests
• core/failures.py: use past N builds instead past N tests
• core/history.py: improve history performance
• frontend/comparison.py: refactor comparison to show off regressions and fixes only
• frontend/tests.py:
  • allow filtering tests by environment and suite
  • catch non-existant tests
  • reduce query size
• remove frontend/failures.py: there's an API endpoint for it

1.73

This release fixes a variety of bugs:

• flake8: fix misc new flake8 complaints
• frontend/templatetags: support newer versions of allauth package
• frontend/views.py: handle requests provinding invalid testrun id
• templates/notification/diff.txt.jinja2: fix typo when referencing environments from known issues

1.72.2

This 1.72.2 release does a few performance improvements in order to speed up fetching jobs, specially under heavy load.

1.72.1

This 1.72.1 release fix a change in Tuxsuite api.

1.72

This 1.72 release fixes a bug when fetching a Tuxsuite build related to a test. Also, it quickens fetching results from Tuxsuite by reusing HTTPs connections.

1.71.1

This 1.71.1 release fixes environment fetching in Tuxsuite backend when using callbacks.

1.71

This 1.71 release changes the way environment from callbacks are handled depending on the ci backend. The release also moves details on why builds are unfinished to the build page, due to that query be quite expensive.

1.70

This 1.70 release fixes the callback handler for receiving Tuxsuite results.

1.69.1

This 1.69.1 release fixes the previous one by adding wget to SQUAD's docker image.

1.69

This 1.69 release adds support to filtering projects by their latest modified date time.

1.68

This 1.68 release adds Google as one of the social account providers to log in into SQUAD alonside Github and Gitlab. Also thanks to Milosz the buttons for social logins will only be displayed if such providers are configured in the SQUAD instance.

The release also adds a new REST endpoint: statuses, which exposes TestRuns status directly. Hopefuly this will enable engineers to generate status reports on projects in an easier way.

1.67

This 1.67 release adds support for receiving callback events from Tuxsuite backends. This will allow build and test objects to be pushed directly to SQUAD which in turn will stop polling from Tuxsuite, saving unecessary requests. The release also fixes a bug when composing URLs used in github plugin.

1.66

This 1.66 release adds support for listening to LAVA websockets over ZMQ. The release also fixes infinite Tuxsuite polling when jobs run into infrastructure errors.

1.65

This 1.65 release adds support to cancelling tuxsuite jobs via SQUAD and also fix a bug when connecting to a RabbitMQ instance over amqps:// protocol.

1.64.1

This 1.64.1 release reverts django-prometheus as it shows a bug when acessing API and some other urls. The release also installs django-storages with dependecies, especially to work with GCP.

1.64

This 1.64 release updates django-storages to support new updates to Google's storage backend. The release also includes django-prometheus, that allows querying metrics from squad.

In the future, metrics can be custom made.

1.63

This 1.63 release adds an endpoint to builds view: compare. It allows one to compare builds against other builds in the same namespace or different namespaces (groups)

1.62

This 1.62 release adds an endpoint to testjobs view: resubmitted_jobs. Which lists all jobs that got resubmitted.

1.61

This 1.61 release changes the LAVA backend to start parsing feedback logs, as those sometimes contain important log information.

The release also adds group settings and uses that to determine if projects should be listed by latest update or by name.

Complete list of changes going in:

• ci: backend: lava:
  • also parse feedback as log
  • refactor too many if's
• core: models:
  • add settings to group models
  • fetch build metadata separated by testruns
• frontend: views
  • get number of projects from group settings
  • sort projects based on group settings

1.60

This 1.60 release speeds up queries that load the main page of squad and main page of a squad project. It also adds artificial boot tests to TuxSuite tests as long as adding a build_name metadata when fetching build results. The release also includes a command that allow adding build metadata retroactively to TuxSuite tests.

Complete list of changes going in:

• ci:
  • backend: tuxsuite: add build_name as build metadata
  • backend: tuxsuite: create a boot test for every TuxTest run
  • commands: add create_tuxsuite_boot_test command
  • commands: clean create-tuxsuite-boot-tests command
• core:
  • commands: fix command users crash with Django 2
  • models: add datetime to project
  • models: avoid having naive datetime format
• frontend: views: filter null suites in python
• frontend: views: speed up loading project page
• plugins: linux_log_parser: remove time before computing sha

1.59.3

This 1.59.3 release adds a couple of indexes to the TestJob model.

1.59.2

This 1.59.2 release generates build_name test metadata if there are not any. The release also installs the django-degub-toolbar by default and it can only be visible by superusers. It is very helpful to allow admins debug squad performance.

1.59.1

This 1.59.1 release fixes a bug when fetching metadata for test jobs in Tuxsuite backends.

1.59

This 1.59 release includes a few multiliner patterns for the linux log parser plugin. It also allows filtering badges by suite and environment. Finally, it also allow TuxSuite test results to capture the test's build metadata information.

Complete list of changes going in:

• ci: backend: tuxsuite: refactor fetch_test_results
• ci: backend: tuxsuite: support fetching build metadata
• frontend: badges: allow filtering badges by suite and environment
• frontend: badges: move badge code to badges.py
• plugins: linux_log_parser: add kernel-kasan multiline pattern match
• plugins: linux_log_parser: add kernel-kfence multiline pattern match
• plugins: linux_log_parser: check-kernel-exception: fix regex
• plugins: linux_log_parser: drop check-kernel-trace
• plugins: linux_log_parser: use one check-kernel-exception
• test: plugins: test_linux_log_parser: add a check-kernel-exception test

1.58.1

This 1.58.1 release fixes a bug in linux-log-parser when assigning logs and hides environment with no results in test history.

1.58

This 1.58 release changes the linux-log-parser plugin to append a shasum of a log instance in the name so that it is easier to compare log instances accross multiple builds.

Complete list of changes going in:

• plugins: linux_log_parser: compute contents to generate unique naming
• plugins: linux_log_parser: make 'except-trace' multi-line regex

1.57.2

This 1.57.2 release simply adds support for Google Cloud file storage background for django-storages, allowing SQUAD to store files in GCP.

1.57.1

This 1.57.1 release fixes two bugs:

• wrong project count in the home page
• proper split log in linux log parser plugin

1.57

This 1.57 release adds a few new changes with regards to api. Now job submissions with malformed definitions will be rejected. Also results submissions with bad datetime format will be rejected. Lastly, there's a new feature within the build page that when appending "/api" to its url, will redirect the request to the build api view.

Complete list of changes going in:

• api: add_test_run: signal invalid request on validation errors
• api: ci: reject job submission with malformed definition
• dev-docker: install pytest-django
• dev-docker: take a custom port number via $PORT
• frontend: build: add redirect URL to get API URL

1.56

This 1.56 release marks a very important change to SQUAD: it changes its license to GPLv3+.

The release also adds a new feature in builds allowing users to mark releases. This will be useful when comparing builds against releases, instead of comparing them against latest builds. Thanks Milosz!

Complete list of changes going in:

• Change license to GPLv3+
• api: add build filtering by is_release field
• core:
  • Add is_release and release_label to Build object
  • fix syntax issue
  • plugins: fix code style around yield
• frontend:
  • add UI for setting Build.is_release
  • fix reverse url for annotations UI
  • Add release indication in the build list
• Drop French translations
• Drop Norwegian translation

1.55

This 1.55 release fixes a bug when fetching tuxsuite tests when build had failed.

The release also contains a newer version os squad-plugins/tradefed, which fixes a bug parsing xml iteratively and parse ASSUMPTION_FAILURE tests as expected failure.

1.54.3

This 1.54.3 release improves performance of operations using TestComparison and MetricComparison with regressions and fixes only, by removing duplicated rows from the result query.

It also fixes the use case that retries fetching TuxSuite jobs.

1.54.2

This 1.54.2 release uses a refactored implementation of squad-linaro-plugins/tradefed, consuming much less memory when computing CTS/VTS results

1.54.1

This 1.54.1 release improves performance of fetch tasks by reducing the number of queries when computing tests stats.

The release also fixes a bug when fetching a job in TuxSuite that has unknown status.

1.54

This 1.54 release bring a handful of bugfixes and improvements:

• Bug fixes

  • handle LAVA HTTP/500 responses from the api
  • fix several bug in the metric page and improve overall performance
  • fix a race-condition bug when processing multiple result submissions

• New features

  • allow filtering builds by id and testjobs by backends

Complete list of changes going in:

• api: rest: add allow filtering testjobs by backend
• api: rest: allow filtering builds by id
• ci: lava: catch submission errors on 500 errors
• ci: tuxsuite: handle failed jobs
• core: BuildSummary: add uniqueness constraint
• core: queries: improve overall query performance
• core: queries: remove extra order_by
• frontend: chart.js: avoid drawing charts on empty environments
• frontend: queries: improve query performance
• frontend: templatetags: avoid having 'None' rendered
• frontend: views: avoid None in threshold metric data

1.53.2

This 1.53.2 release fixes a bug in the TuxSuite backend when fetching tests with failed builds. The release also fixes the number of tests used when calculating the confidence score for a given test.

1.53.1

This 1.53.1 release includes a missing "metadata" field in tests api REST endpoint.

1.53

This 1.53 release drops Django 2.2 support in SQUAD and add support to 3.2 and 4.0.

1.52

This 1.52 release includes a new feature in the linux-log-parser plugin that split the linux log in the boot part. The plugin now will generate tests in two suites "log-parser-boot" and "log-parser-test" which will represent the fault occurencies in both stages.

1.51

This 1.51 release introduces support for TuxSuite backends, allowing users to pull test and build results from tuxsuite.com.

It also adds a new API endpoint for querying failures with confidence

1.50

This 1.50 release improves performance of All metrics tab of the build page and adds pagination to All failures.

The release also adds a button on testjobs page allowing users to manually sending fetch requests to SQUAD.

1.49.1

This 1.49.1 release fixes the bug when loading failures with zero history.

1.49

This 1.49 release adds a new tab to the build page where one can see all the failures of a build along with a confidence score based on pre-defined per-project settings of threshold and number of builds in history.

1.48.2

This 1.48.2 release really fixes the bug when re-submitting jobs that weren't submitted in first place.

The release also improves testjobs page load times and mainly it improves load time of home page.

Complete list of changes going in:

• ci:
  • backend: lava undo resubmit on unsubmitted job
  • models: really re-submit unsubmitted jobs
• frontend:
  • ci: avoid re-checking if user can submit
  • ci: lazy-load testjob definition
  • ci: remove unecessary queries
  • ci: support changing number of jobs per page
  • templates: testjobs: avoid query for perent jobs
  • views: improve home page load time

1.48.1

This 1.48.1 release fixes 2 bugs in SQUAD. First happens when build metadata contains a list of integers and the second was a missing catch on exceptions when resubmitting jobs.

Complete list of changes going in:

• ci: models: handle resubmission exceptions
• core: templatetags: stringify any list

1.48

Happy 2022!

This 1.48 release adds a metrics page per build and also fixes a bug catching exceptions for LAVA backends using REST API instead of XMLRPC.

Complete list of changes going in:

• ci: Avoid redirection when cancelling or resubmitting LAVA jobs
• ci: add tests for 4xx LAVA responses
• ci: Fix LAVA backend in case or job resubmission
• all: add a page to view the metrics for a build

1.47

This 1.47 release adds support to build confidence configuration, allowing users to define configs to get test regressions with more confidence.

Complete list of changes going in:

• core: migrations: rename migration
• setup.cfg: ignore the .venv directory when running flake8
• all: add a project basic_settings api endpoint
• all: add build confidence project settings

1.46

This 1.46 release adds a new widget in the build page that allows users to follow up overall testjobs progress and accross environments.

The release also fixes a bug when metadata has list of lists.

• api: rest: add endpoint testjobs summary of a build
• core: templatetags: squad_notification: handle list of lists
• core: models: generate testjobs summary for builds
• frontend:
  • testjobs_progress: make green a little lighter
  • testjobs_progress: make proportional progress bars
  • build: allow seeing testjobs progress for each environment
  • ci: filter job_status by exact string
  • build: add testjob progress bar

1.45

This 1.45 release adds several features around testjobs. The first is the ability to remove resubmitted testjobs results via a project setting. Also, another setting has the capacity of telling SQUAD to reset all build events upon testjob resubmission and new job submission. This means that build callbacks, email notifications and patch notifications can be retriggered automatically.

Complete list of changes going in:

• api: ci: atempt to fetch job as they are watched
• ci, core: allow resetting build events
• ci: models: delete results from resubmitted jobs
• core: migrations: add MetricThreshold to default squad auth group
• requirements: pin importlib-metadata
• frontend: testjobs:
  • disable job resubmission if already resubmitted
  • hide cancel button if job is already fetched
  • refactor test job controls buttons
  • remove dead code

1.44

This 1.44 release adds a bit of adjustments to the metrics changes done in the previous release, like support for fetchin all build metrics via a specific endpoint.

Complete list of changes going in:

• api: rest:
  • add metrics endpoint to builds
  • add note on forcing comparing unfinished builds
  • filter metrics by build, environment, and metadata
  • prefetch metadata for metrics endpoint
• core: models: fix typo in comment
• frontend:
  • build: add link to view build as api endpoint
  • compare_builds: add link the same comparison view in api
  • metricThreshold.js: fix identation

1.43.1

This 1.43.1 release fixes a bug when trying to update TestJob definition via REST api.

Complete list of changes going in:

• api: Allow to update TestJob definition via API

1.43

This 1.43 release does a handful of this. It:

1. Completely removes the metric.name field in favor of suitemetadata.name, this saves up lots of space in DB
2. Adds project reference to metric threshold model, thus allowing thresholds for all environments in a project
3. Adds regressions and fixes to metric comparison class

Overall, it improves metrics handling a little bit in SQUAD.

Complete list of changes going in:

• api: rest:
  • properly use project in metric thresholds endpoint
  • support metric comparison between project builds
• core:
  • comparison: make lighter/faster MetricComparison
  • templates: notification: display metric name in exceeded thresholds
  • models:
    • add metric regressions and fixes to ProjectStatus
    • add project to MetricThreshold
    • improve function finding exceeded metrics thresholds
• frontend:
  • thresholds: allow metrics name patterns and select all environments
  • views: use metadata__name in metrics.name
• models: remove name column from Metric
• tests:
  • test_basics: fix missing test
  • test_project_status: add project when creating thresholds

1.42

This 1.42 release continues improvements on metrics pages and queries that make use of the new references to build and environment in the metric table.

Complete list of changes going in:

• api, core, frontend, test: use suitemetadata.name in favor of metric.name
• api, core, frontend: avoid testrun joins
• api: rest: remove testrun reference in project lookup for metric viewset
• api: rest: remove testrun reference in project lookup for test viewset
• core: history: avoid using testrun to fetch tests
• core: queries: avoid using testrun to fetch metric build/environment
• frontend: queries: fetch metrics faster
• test: fix flake8 complain
• test_pending_migrations: temporarily disable this test

1.41

This 1.41 release adds '/api/builds//cancel/' endpoint so that users can cancel all running test jobs of a build.

The release also implements the same denormalization pattern used in the test model last year. It's important that if you are running a older squad instance that after this release you run the following command:

./manage populate_metric_build_and_environment

This will ensure that all new metrics will have the correct data migrated.

Complete list of changes going in:

• core: metric: add Build and Environment reference to Metric
• api: rest: add cancel endpoint to builds

1.40

This 1.40 release updates squad-plugins so that the subtasks in the tradefed plugin won't clog up non-ci_fetch queues.

1.39.1

This 1.39.1 release fixes a bug that allowed unauthenticated users to see groups with none or private-only projects.

Complete list of changes going in:

• README: update copyright year and add test badge
• scripts: test-ci: don't crash if not able to submit to qa-reports
• frontend: group_home: raise 404 on private groups
• test: mock: use stdlib's mock on python > 3.3
• travis: move to github actions

1.39

This 1.39 release makes known issues test names be parsed as regular expressions so that users can specify known issues as "ltp-/flawed-testname", instead of specifying each as a separate known issue.

Complete list of changes going in:

• core: tasks: add support for patterns in known issue test_name

1.38

This 1.38 release fixes two major bugs in SQUAD when communicating with LAVA backends:

1. When a testjob fails to fetch, and LAVA lab is out, SQUAD should handle the outage an give up trying to fetch such jobs.
2. When LAVA jobs fail due to "metadata is too large", the results api won't return a valid metadata field, thus causing SQUAD to break on that too

Also this release includes a health-check endpoint that shows the availability of most of SQUAD's services.

Complete list of changes going in:

• Dockerfile: add suport to django-health-check
• Dockerfile: fix django-storage error on closing s3 file
• ci: backend: lava: handle null error_msg
• ci: backend: lava: raise TemporaryFetchIssue on fetch timeout
• frontend: build-nav: add test summary to build header
• frontend: project_settings: gather local options
• health_check: allow health-check endpoint to staff user only
• setup.cfg: ignore "C101 Coding magic comment not found" flake8 errors
• travis: disable testing on real LAVA

1.37.1

This 1.37.1 release is a bug fix release. It fixes a bug that shows the "Callbacks" tab in builds with no callbacks and also fixes a bug in the listener process that wasn't restarting dead processes.

Complete list of changes going in:

• frontend: build-nav: fix callbacks count check
• ci: listen: restart dead processes

1.37

This 1.37 release adds a couple of new features:

• an option to allow builds to finish on notification timeout
• allow disabling environments, by setting -1 to the "expected number of testruns"
• attempts to make notifications not timeout
• add 'important metadata keys'
• display build callbacks, if any

Complete list of changes going in:

• api: ci: disable and environment for receiving new submissions
• core:
  • models: add flag to allow forcing builds to finish
  • models: make callback response_content larger than 1024
  • notification: use fase TestComparison
• frontent:
  • build_callbacks: add callbacks to the Build view
  • group_settings: avoid timeout deleting groups
  • project_settings: add important-metadata-keys
  • project_settings: add option to force finishing builds
  • project_settings: add help text disabling environment
• doc: conf: update copyrights year
• test: core: test_tasks_notification: skip test for sqlite

1.36.1

This 1.36.1 release fixes a bug when api clients tried to save project_settings but got their data discarted by the rest framework.

Complete list of changes going in:

• api: rest: make project_settings write only

1.36

This 1.36 release allow running build comparison against unfinished builds

1.35

This 1.35 release fixes a small issue when viewing all test results in Build page

Complete list of changes going in:

• frontend: tests: improve performance loading all test results
• doc: document how callbacks work

1.34.1

This 1.34.1 release fixes Plugins notifications when the project has no recipients subscribed to it or when there's a race condition.

The release also fixes a scenario where a TestJob might get canceled before getting a job_id from the backend, therefore entering a limbo state where it can't be resubmitted.

Complete list of changes going in:

• core: tasks: notification: prevent duplicate patch_source notification
• ci: lava: fix resubmit on testjobs with empty job_id
• core: notification: mark as notified even if no recipients available

1.34

This 1.34 release adds several nice features:

1. Social login: now users will be able to login using their Github or Gitlab accounts
2. New notification strategy (ON_ERROR)
3. Adds implementation of test confidence score, when tests are run for the save build/suite/environment
4. Callbacks: for now only callbacks to finished builds are implemented extending it should be simple though

Among other minor bug fixes and performance improvements.

Complete list of changes going in:

• api:
  • add version endpoint
  • rest/views: handle callback duplicates
  • rest: create build callbacks via nested endpoint
  • rest: enhance builds nested endpoint in projects endpoint
  • rest: fix /api/projects//builds/
  • rest: hide project_settings
  • rest: use lighter version of TestComparison
  • views: create callback for build via createbuild
• ci: listen: increase backend check poll to 1 min
• core:
  • callback: accept default headers from project settings
  • migrations: add missing migration when adding new notification strategy
  • models: add Callback class
  • tasks: dispatch callback when build is finished
• dev-docker: add pytest dependency
• doc: api: document callback creation on createbuild api endpoint
• socialaccount: add Github and Gitlab social account login
• socialaccount: prevent Github/Gitlab login to pre-existing users
• test: add test to check for pending migrations
• test: fix pytest
• Dockerfile: use debian buster-backports as base image
• Handle multiple test results.
• Introduce new notification strategy ON_ERROR.

1.33

This 1.33 release tweaks TestComparison making it much faster when only regressions and fixes are needed. It brings these changes through a single database query, instead of loading all tests in memory.

The release also saves precious time when fetching lots of builds and tests from the API.

Last by not least, this release of SQUAD also comes with a new field to Build called patch_url which stores the originator url of that build.

Complete list of changes going in:

• api: rest
  • order tests by id instead of build_id
  • remove leftover print statement
  • squeeze in a few extra ms fetching builds
  • squeeze in a few extra ms fetching tests
• core:
  • comparison: fix regression detection
  • comparison: fix regression detection
  • comparison: use raw sql to get regressions and fixes
  • frontend: Display URL from patch source
  • models: use metadata for retrieving test full name
• docs: fix a typo in the api docs
• Dockerfile: freeze importlib-metadata version
• dev-docker: freeze importlib-metadata version
• test: core: avoid unnecessary project status update

1.32

This 1.32 release completely removes TestRun and Attachment file fields, leaving it to be saved in storages only.

The release also tweaks the script that fixes buggy squadplugin generated SuiteMetadata objects.

Complete list of changes going in

• core, commands: 4th attempt to make faster fix
• core: delete old storage fields for TestRun and Attachment

1.31

This 1.31 release adds a long-wanted feature in SQUAD which is the ability of fetching Build's tests without having to go through TestRun table. Some queries are going to be optimized and large installations will feel the difference almost right away.

This release also fills up all environment columns when checking a test's history.

Complete list of changes going in:

• api: rest: add tests endpoint to build
• api: rest: add build, environment and metadata filters
• ci: backend: lava: handle HTTP 408 as TemporarySubmissionIssue
• core, history: add None to all builds
• settings: increase max upload size to 10MB

1.30

This 1.30 release adds Build and Environment references to the Test model as it would make a lot of SQUAD queries run much faster and simpler, going around TestRuns. The latter is still very needed for storing test run files and metadata.

This release also enables selecting which fields from api endpoints to be serialized.

Complete list of changes going in:

• core: migrations: make transaction non-atomic
• core: test: add Build and Environment reference to Test
• api, rest: enable filtering specific fields

1.29

This 1.29 release stops logging backends faults as errors and log as warnings instead. The intention is to error-log only squad-related errors.

Complete list of changes going in:

• ci:
  • lava: clear TestJob.failure in backend implementation
  • tasks: submit: log message as warning instead of error

1.28.2

This is a hotfix when unauthenticated users try to access project home.

Complete list of changes going in:

• squad: frontend: check whether user is logged when displaying subscriptions

1.28.1

This is a quick release to add an improvement of the command that fixes squadplugins tests.

Complete list of changes going in:

• core: commands, rewrite command to fix tradefed

1.28

This 1.28 release starts using storage to provide TestRun and Attachment files, deprecating the use of the same fields in the DB. Future releases will completely remove such fields and will help control database growth on installations with lots of data.

The release also clears TestJob fetch failures after a successful fetch. It also fixes a bug in the bell icon in the project page that signals whether or not a user is subscribed to that project.

Complete list of changes going in:

• api:
  • rest: hide deprecated TestRun file fields
  • rest: make build, project and suitemetadata listings faster
• ci:
  • add started_at and ended_at fields to TestJob
  • models: clear TestJob.falure on successful
• core:
  • models: add save_files to TestRun
  • models: delete files as TestRun and Attachment are deleted
  • models: deprecate TestRun and Attachment storage database fields
• frontend: notification bug

1.27.1

This is a quick release to hide storage fields

Complete list of changes going in:

• api: rest: hide storage fields

1.27

This 1.27 release starts using external storage for test run files as a step prior to remove them from DB. Next releases will come accordingly.

The release also works around a bug with LAVA REST responses that don't always include the unit of a metric.

Lastly, this release adds a new model called PluginScratch, to be used by plugins whenever extra database storage is required. Plugins should clean up their data after work is finished.

Complete list of changes going in:

• ci: work around LAVA REST error
• commands: migrate_attachments: avoid OOM errors
• core:
  • add PluginScratch object
  • delay notification if there are PluginScratch-es
  • migrate_attachments: reduce number of threads
  • start using storage
• doc:
  • conf: turn off magic quotes
  • plugins: make gerrit configuration yaml code
  • fix curl calls in plugins page
• plugins: gerrit: use same regex for split and match checks

1.26

This 1.26 marks a big change in SQUAD: it completely removes the name from Test models. This field/column is the responsible for half the size of DB and it might become an issue in setups with hundreds of millions of tests.

This release also starts adapting SQUAD to use storage for TestRun files (tests, metrics and logs) and Attachment. The next release should start using these new fields and further releases will swap to use storage fields only, thus saving lots of space in DB.

The release also fixes a timeout when viewing a build page, and a timeout when acessing api for testrun/suite tests.

Lastly, this release makes Postgres an optional dependency for SQUAD, which now should be installed as pip install squad[postgres] if that RDBS is required, otherwise Sqlite will be used instead.

Complete list of changes going in:

• api: improve testrun/suite tests load times
• core:
  • add FileField to Attachment to store contents
  • add FileFields to store Testrun attachments
  • add mgmt command for moving attachments out of DB
  • allow Attachment.data to be null
  • commands: add script to clean tradefed bad entries
  • fix progress print in mgmt commands
  • migrations: fix storage migrations
  • models: increase size of password in PatchSource
  • models: remove name column from Test
• dockerfile: add django-storages and boto3
• dockerfile: downgrade boto3
• frontend, views: fix suite parsing in test details
• frontend: views: avoid loading attachment data
• settings: define default location for storage
• setup: make postgres optional
• test: core: test storage fields

1.25.2

This 1.25.2 release fixes two bugs: first treats lava results' metadata field as both string and yaml, the second bug hunt us down for a few months triggering gerrit test exceptions at random, but it's fixed now.

Complete list of changes going in:

• ci: backend: lava: Parse results always expects metadata as a dict.
• core: utils: improve cryptographic functions

1.25.1

This 1.25.1 release fixes a bug that caused broken links to show up in default notification templates.

Complete list of changes going in:

• core: templates: notification: Fix broken links

1.25

This 1.25 release adds a few major items:

• adds support of "unit" for metrics, but still preserves backwards compatibility
• api:
  • standardizes API to use self discoverable url instead of id for all endpoints
  • handles http errors as Json, instead of regular Django pages
• prepare squad to get test name column removed by making the field nullable and stop using it
• adds option to disable sending emails to admins in setups that use other types of notification, e.g. Sentry
• adds support for celery result backends, which allows celery to run group of tasks

Complete list of changes going in:

• api:
  • rest: sandardize url-id in rest api
  • http: handle 404 as json on api requests
• core:
  • models: add unit field to Metric model
  • models: add shortcut to get project settings
  • migrations: "rebased" migration to make test name nullable
• models: use SuiteMetadata.name in favor of Test.name
• plugins:
  • gerrit: add support to custom labels
  • gerrit: allow multiple labels review
• settings:
  • add celery result backend
  • add option to turn off admin error emails
  • fix SQUAD_SEND_ADMIN_ERROR_EMAIL flag values
• test: remove leftover print

1.24

This 1.24 release adds "tests" to suite endpoints, makes test job endpoint a bit faster to load and fix the recently added "Known Issues" project tab.

Complete list of changes going in:

• api: rest: defer definition from TestJob endpoint
• api: rest: add tests endpoint to suite view
• frontend: fix missing project nav in knownissues
• test: fix gerrit unit tests

1.23

This 1.23 release adds a few items to frontend: download attachments button right on build view, download metric charts and known issues on project view.

The release also changes task id for fetch tasks, this will help debugging fetch-related errors.

Complete list of changes going in:

• ci: tasks: define task_id for fetch tasks
• core:
  • frontend add group 'privileged' access level
  • make PatchSource.token nullable
• frontend:
  • Fix a typo on the delete project button
  • add known issues to project view
  • export metrics graphs as picture
  • rest: add dropdown to download attachments

1.22

This 1.22 release increase metric name field from 100 characters to 256, as it is for test name. The release also allows by default all users to make changes to projects, as long as they belong to the respective group.

Complete list of changes going in:

• core:
  • make metric name 256 characteres long instead of 100
  • add project perms to default squad group
  • migrations: remove print creating permissions

1.21

This 1.21 release changes the lava backend XML-RPC transport layer to use requests, also including a pre-defined timeout. The release adds Celery plugin for Sentry users.

Complete list of changes going in:

• ci: add tests for LAVA backend call timeouts
• ci: lava: change XML-RPC transport to use requests
• frontent: build: include test jobs with no status in Test jobs tab
• settings: add CeleryIntegration to sentry

1.20

This 1.20 release adds log entries when users change objects via the API. It also allows OPTIONS database arguments to be passed via environment variable.

Complete list of changes going in:

• Translated using Weblate (Portuguese)
• Added translation using Weblate (Portuguese)
• core: add tests for LogEntry when using API
• Allow equal sign in settings variable value.
• api: log user actions as LogEntry

1.19

This 1.19 release adds a filter to testjob view page that allows users to query target jobs instead of going page by page.

Complete list of changes going in:

• frontend: add filter to testjobs view
• settings: django-toolbar: use squad jquery
• test: test_listen: fix multiple calls with backends
• ci: backend: Use project settings in LAVA backend

1.18

This 1.18 release fixes tooltips for test jobs view, changes how groups are displayed in the home page and also prioritize project settings over backend settings when resubmitting test jobs.

Complete list of changes going in:

• ci: lava: ensure project settings take priority
• frontend: fix tooltips in testjobs page
• frontend: home: separate groups and user spaces

1.17

This 1.17 release adds a few changes to test results layout in build view. It collapses all results by default and display an overall summary of tests in the box title for suite and environment boxes.

This release also adds an extra button that allows users to select build comparison type (test or metrics) in build view.

Complete list of changes going in:

• api: rest: add filterset_class attribute to StatusViewSet
• core: commands: add fill_test_metadata command
• frontend:
  • add choice of comparison type
  • add logo do api page
  • fix test result url to point to history
  • test_results: add collapse/expand all option
  • test_results: add overall summary in suite/environment boxes
  • test_results: make suitebox the default layout
  • test_results: move toggle box to the left
• plugins: linux_log_parser: create metadata
• release-docker: tag release image name
• settings: init sentry plugin with squad release
• settings: really configure celery max retries when queue server is out of reach

1.16.2

This 1.16.2 release fixes a bug when filtering objects by project's full name.

Complete list of changes going in:

• api: rest: fix project filter
• Dockerfile: allow containers make ssh connections

1.16.1

This 1.16.1 release fixes a lava crash when trying to download big log files from a lava instance that times out. The release also improves load time in test history view.

Complete list of changes going in:

• ci: fix lava backend log download
• frontend: test_history: improve load time

1.16

This 1.16 release improves load time of compare tests across different projects, creates a default authentication group so that users have object-level permission and allow download of build attachments.

Complete list of changes going in:

• frontend:
  • add URL for downloading build attachments
  • add test history link in test list
  • allow serving files from database
  • compare: improve compare load times
  • fix attachment downloads
  • test the actual response contents of all download urls
• add migrations to create auth group and add users
• api: rest: add more status details
• attachment: add a sample unit test
• core: store Attachment's mime-type in the model
• pytest: only check coverage on ci

1.15.1

This 1.15.1 release improves load time of group, project and build page.

Complete list of changes going in:

• core: admin: fix timeout deleting objects in admin view
• frontend:
  • improve group page load times
  • improve load times for project and builds page
  • views: fix page view for unauthenticated users
  • views: improve build page load time

1.15

This 1.15 release adds pagination to list of test jobs of a build, along with a UI for navigating between previous and next builds.

The release also fixes a broken link to test history and other small bug fixes.

Complete list of changes going in:

• api: rest: make project//test_results faster
• ci: lava: update backend implementation to ensure proper URLs
• frontend:
  • add pagination to testjobs view
  • add prev & next in build page
  • fix URL reverse for test names with /
  • fix crash when paginator page is not found
  • fix filtering box in build view
  • restore legacy test history url + bugfix
• Translated using Weblate (Norwegian Bokmål)

1.14

This 1.14 release adds an API endpoint that allow comparison between builds from the same project. It also fixes a bug related to LAVA ci backends when retrieving listener url.

The release also improves the docker image and pushes it to https://hub.docker.com/repository/docker/squadproject/squad on every release.

Complete list of changes going in:

• api:
  • rest: endpoint to compare two builds
  • rest: fix environment filter in knownissue
• ci:
  • fix LAVA listener port retrieval
  • fix get_listener_url() in case of REST
• frontend: comparison: fix transitions
• misc:
  • Dockerfile: improve Dockerfile
  • release: release docker image along with pip release
  • remove CODEOWNERS file
  • requirements: fix dependencies for broken celery 4.4.4
  • settings: allow SMTP port customization
  • test-docker: remove extra testing under docker
  • travis: add verbosiness do test under docker

1.13

This 1.13 release marks 4 years of SQUAD project, yay! It also adds a logo for the project along with other small bug fixes and new features.

The LAVA backend is now compatible with LAVA RESTfull interface, also now we're running tests against a real version of LAVA running on a Docker container.

There was a small change in the workflow to check test details. The testrun page has been completely removed in favor of less clicking to get to test metadata and history.

The linux log parser plugin now captures a new class of bug called "invalid opcode", and it catches more of "BUG" bugs.

Complete list of changes going in:

• ci:
  • Enable REST API in LAVA backend
  • fix ProjectStatus processing in fetch()
  • improve TestJob.cancel()
  • test lava backend using real LAVA instance.
• core:
  • Implementation of ProjectStatus baseline
  • add ProjectStatus baseline field
  • add compute_project_statuses command
  • fix compute_build_summaries command
• frontend:
  • build: fix missing "failures only" filter
  • add test details and remove testrun page.
• plugins: linux_log_parser: improve BUG matches and add "invalid opcode"
• misc:
  • add logo to the README
  • add logo to the main template.
  • update the copyright years line to extend to 2020

1.12

This 1.12 release adds a bell icon to project UI allowing users to subscribe/unsubscribe from projects notifications, among other small fixes and additions.

Complete list of changes going in:

• api: add docstring to endpoints with additional methods
• api: rest: handle null test_name in project/test_results
• frontend: add subscribe feature to project listing
• frontend: allow to subscribe/unsubscribe from project view
• static: annotation: better handle error messages
• test: fix flake8 warning

1.11

This 1.11 release adds several new features. A new flag in Project/Backend settings allow processing valid results of LAVA jobs that had an Infrastructure error. In the test job page of a build, a user can now choose to cancel a job that is submitted but not yet fetched, also sending this cancel action to job backend.

Complete list of changes going in:

• api:
  • document field lookups
  • rest: add ID to all possible serializers and filters
  • rest: add resubmit and cancel methods to TestJob objects
• ci:
  • add support for cancelling CI jobs
  • lava: add flag allowing to accept results from failed jobs
  • models: handle race condition without wait
• doc:
  • api: add note about Squad-Client tool
  • api: add status to testrun endpoint and metrics endpoint
  • api: remove usergroups documentation
  • intro: add a note about xfail tests
  • intro: add note on regressions and fixes
• frontend:
  • add Cancel button to test job list
  • add link to full log from test list page
  • ci: reduce number of queries for testjobs view
• core: fix project counter display on index page

1.10.1

This is a bug fix release:

In case the job is still in the queue or is in progress, fetch() raises TemporaryFetchIssue from within block that catches FetchIssue. Since TemporaryFetchIssue derives from FetchIssue, the exception is immediately consumed and fetch_attempts counter is increased. This leads to maxing out fetch_counter for jobs that stay in the queue for a long time. This patch removes the exception and instead returns from the fetch() function without an error. This doesn't result in increasing fetch_attempt counter.

Complete list of changes going in:

• api: rest: add ID field to TestJob object
• ci: fix Backend.fetch() implementation
• travis: fix reuse docker lint
• Translated using Weblate (French)

1.10

This 1.10 release fixes a race condition bug that happens whenever two or more workers fetch a single TestJob, triggering a fetch issue. Also it adds suport to Sentry, a tool to manage log events.

The release also create a separate endpoint for Metrics objects.

Complete list of changes going in:

• api: rest: fix force-created reports
• ci: models: fix race condition for fetch
• core:
  • rest: add top-level metric endpoint
  • tasks: fix job_id as integer
  • tasks: notification: keep only one task for notification on timeout
  • tasks: remove try-catch block of notification task
• manage: exclude tests that break on sqlite
• settings: add support to Sentry

1.9.1

This is a quick release that fixes two bugs regarding the linux log parser plugin.

Changes:

• plugins: linux_log_parser: ignore empty logs
• core: history: check for empty suite metadata

1.9

This 1.9 release really fixes linux-log-parser plugin, adds badges for builds and fixes bugs discovered when using squad-client. Also we made "job_id" optional when submitting test results through the api.

Complete list of changes going in:

• core:
  • api: add status to testrun
  • data: handle null test result
  • model: MetricThreshold remove project
  • tasks: make "job_id" optional
• celery: avoid crash when no broker is configured
• doc: fix python example for submissions
• frontend: add badge for build
• plugins: linux_log_parser: run plugin for testruns
• settings: run tasks when there is no broker

1.8

This 1.8 release updated linux-log-parser plugin to search for kernel panics as a one line error. Also it now searches for "BUG" as well. It also migrate metrictreshold to use environments.

Complete list of changes going in:

• core: models: remove threshold contraint
• core: models: Change client code for MetricThreshold model and migrate old data
• core: notification: avoid sending emails when body >1MB
• plugins: linux_log_parser: make 'kernel-panic' one-line regex
• plugins: linux_log_parser: add BUG regex
• scripts/upload: remove build leftover files
• test: test_notification: remove unused attribute

1.7

This 1.7 release updated examples in the documentation, making them more secure by default. It fixes bugs when submitting test results.

Also, there are new additions to the UI: now test results in the build page are displaying failed ones by default. The user can toggle the visualization to the old one as wanted. A bug in the collapse/close button was fixed as well and by default, all suites/environment boxes are expanded on page load.

Complete list of changes going in:

• api: rest: show testrun in test
• doc: make auth-token examples more secure by default
• doc: intro: add example of submit test results with requests
• ci:
  • models: backend: handle duplicated testjob as new exception
  • models: refactor try-except block
  • tasks: clean test job failure message after successful submission
• core:
  • models: add environment to MetricThreshold
  • tasks: ensure job_id to be integer or string
  • models: finish builds status earlier
• frontend:
  • test_results: expand all groupings by default
  • build: test results: show failures only by default
  • templatetags: add helper function to update GET parameters
  • test_results: fix collapse/expand button
  • project_settings: add environments to project settings UI
  • templates: project_settings: fix basics page title
• requirements.txt: top off django version

1.6.1

This 1.6.1 release fixes a bug cause when SQUAD works with SQS FIFO queues. The bug prevented newer tasks from being delivered to workers until newer tasks were complete.

Complete list of changes going in:

• squad: celery: make tasks groups unique on SQS
• pytest.ini: include more tests that were being ignored
• pytest.ini: bump minimal code coverage
• core: tasks: fix bug on testrun status table where 'has_metrics' defaults to false for testruns that have metrics
• api: rest: enable displaying null for empty metrics and tests on testrun api view

1.6

This 1.6 release adds support to queue suffix names, which enables fixing a bug that happens if SQUAD was configured with AWS SQS and a lab entered in maintenance state.

It also adds the ability to switch test results layout when viewing a build home page.

Complete list of changes going in:

• ci: backend: lava: add exception when a lava backend is offline
• frontend:
  • build: add option to change test results layout
  • views: order environments columns by alphabetical order
• settings:
  • fix notification tasks routing
  • add support to suffix-named queues

1.5

This 1.5 release fixes a bug that made SQUAD submit a single TestJob multiple times. It also allows project admins to create copies of projects with the Save as option.

Complete list of changes going in:

• ci: tasks: avoid multiple submissions
• core: admin: enable save as option for projects
• frontend: project_settings: add advanced settings tab
• Updated translation:
  • Translated using Weblate (Norwegian Bokmål)

1.4

This 1.4 release fixes a bug when viweing all test results page and enables more filteting options for build and testrun api endpoints.

Complete list of changes going in:

• api:
  • rest: enable filtering testruns by 'completed'.
  • rest: enable created date filtering on for builds in api
• frontend:
  • tests: remove unecessary ordering
  • tests: reduce queries to list tests
  • tests: simplify count of pages
  • tests: remove duplicate queries to metadata
  • tests: fix bug when listing tests without metadata

1.3.1

This 1.3.1 release includes a minor bug in the api and support to work with AWS SQS:

• settings:
  • add support to custom polling interval
  • add support to prefix-named queues
  • turn on debug only when needed
• api: fix URL pattern for api/ paths
• http: authenticate users before checking permissions
• Add coverage testing with pytest

1.3

This 1.3 release fixes a 500 http error code when accessing linux-log-parser tests, also improving its log detection, including WARNINGS.

The release also fixes some minor issues related to docker setup, among other new features and fixes that you can see in the full log below:

• core:
  • test_history: handle tests with no metadata
  • plugins: linux_log_parser: improve kernel log parsing
• frontend: reduce query time fetching metric names
• misc:
  • debug: add django debug toolbar
  • doc: add firewall note when running on docker
  • Dockerfile: ignore version constraints from requirements.txt

1.2

This 1.2 release fixes a couple of performance issues when fetching testjobs from backends and when using the REST api, among other small fixes.

It stops ignoring duplicated tests for same environments and test suites when calculating build summary (e.g. number of passing and failing tests). Instead, use partial summaries already calculated for test runs.

We tweaked the backend code that fetches tests before calculating regressions and fixes. If a build had a significant high number of test runs it would make comparison much slower. So we avoid querying all test runs at once when running TestComparison.

There were changes in the backend code of the REST api that reduced the number of trips to db, making some endpoints load faster.

Complete changelog below:

• core:
  • comparison: remove the use of iterator over tests
  • comparison: filter tests by chunks of testruns
  • comparison: fetch only id from testruns
  • comparison: filter tests by testrun ids
  • comparison: prefetch known issues
  • comparison: lowered number of testruns chunk
  • tasks: ReceiveTestRunData: ignore tests and metrics with long names
  • models: remove duplicate call to build.finished
  • test_summary: simplify summary calculation
  • project: reduce amount of trips to database
  • environment: set default expected_test_runs to zero
  • build: make finished false when no jobs or testruns
  • migrations: add missing migration for Django upgrade
  • Group: sort aggregate query explicitly
  • plugins: ignore most parameters
• ci:
  • lava: handle unicode errors gracefully
  • lava: fetch jobs right away
  • listener: respect Backend listen_enabled
  • Backend: add listen_enabled attribute
• doc:
  • fix typo in .readthedocs.yml
  • add configuration for readthedocs build
• api:
  • disable post forms
  • rest: reduce amount of queries and speed up some queries
  • utils: remove duplicate DRF backend
  • rest: avoid queries containing all projects
  • rest: test: reduce number of queries in the database
  • rest: remove deprecation warnings against django-filters 2.x
• Added translations:
  • French
• misc:
  • worker: don't constrain concurrency by default
  • squad.urls: replace deprecated shortcut function
  • tests: remove unecessary usage of Django's TestCase class
  • core, ci: stop pytest from confusing our Test* classes with tests
  • test_test: avoid pytest confusing helper method with a test
  • pytest.ini: add pytest configuration

1.1

• ci/lava: replace concatenation with StringIO
• settings: split tasks to separate queues
• requirements.txt: fix minimal version for pyyaml
• squad.run.worker: listen on all configured queues by default
• doc: document how to manage different queues

1.0.3

• api: utils: add CursorPaginationWithPageSize
• Added translation using Weblate (French)
• ci/lava: adjust hangling of malformed logs yaml for newer PyYAML
• ci/lava: resubmit: exit early
• ci/lava: extract handling of failed submissions
• ci/lava: resubmit: handle errors on the LAVA side
• api: resubmit: handle submission errors gracefully
• ci: lava: speed up conversion of YAML of logs to pain text

1.0.2

This release fixes a small issue with the gerrit plugin that attempts to send notification with malformed patch_id

Complete changelog below:

• plugins:
  • plugins: gerrit: check patch_id before sending notification
• Updated transations:
  • French (updated)

1.0.1

• yaml_validator: drop usage of simple yaml.load
• api: ci: fix definition file encoding
• Updated translations:
  • Polish (completed)
  • French (added)

1.0

This 1.0 release marks the availability of a feature set that we envisioned back when squad was started. We still have a lot to improve, though, so we will continue to work on new features and improvements.

This release also brings compatibility with Django 2, which we now use by default. However, using with Django 1 is still supported. We recommend Python 3.6 or newer.

Since we are bumping the major version number, we are also making two backwards-incompatible changes that you need to be aware of:

• Test results from incomplete jobs are now completely ignored.
• The LAVA CI backend used to map the success of the "auto-login-action" from a lava job to a test called "boot". This is now ignored by default. If you rely on this, you can re-enable this behavior by setting CI_LAVA_HANDLE_BOOT in your project settings (only available in the Django admin interface for the moment). See the documentation for details.

Below, you will find a summary of the changes in this release.

• frontend:
  • frontend: templatetags: add str to global functions for templating
  • frontend: compare-project: refactor project comparison UI
  • frontend: compare-project: order projects alphanumerically
  • frontend: compare-project: compare different builds
  • frontend: filter comparison by transitions
  • frontend: fix compare projects submit
  • frontend: shrink transitions filter table
  • frontend: translation: translate django templates
  • frontend: test_history: fix broken javascript
• api:
  • api: rest: add ComplexFilterBackend to GroupViewSet
  • api: rest: give write only access to _password field
• ci:
  • ci: ignore all results from incomplete test jobs
  • ci: backend: lava: change option to handle lava boot results
• core:
  • core: Build.test_suites_by_environment: make ordering of test results consistent
  • core: admin: mark password field as not required
• misc
  • Add license information for consumption by reuse
  • Added reuse (SPDX compliance tool) to travis.
  • migrate to django2
• doc:
  • doc: ci: add CI_LAVA_HANDLE_BOOT to docs
• plugins:
  • plugins: gerrit: remove capture_output
  • plugins: gerrit: set code-review to -1 when tests fail
• Updated translations:
  • Portuguese (Brazil)
  • Polish
  • Norwegian Bokmål

0.68.3

• frontend: results_table: show "mean (stddev)" details only for metric comparison
• core: plugins: fix gerrit plugin

0.68.2

• ci: improve parsing of LAVA logs

0.68.1

• frontend: fix page title in project settings
• ci: catch YAML ScannerError in LAVA backend

0.68

• Translated using Weblate (Portuguese (Brazil))
• test/karma.conf.js: make chromium work on docker
• api: rest: fix rest-framework detail_route
• frontend
  • frontend: js: update lodash to 4.17.14
  • frontend: compare-tests: fix auto complete initialization
  • frontend: compare-tests: add auto-width to select2
  • frontend: css: fix word-wrap
• core:
  • core: add management sub-command to create/update auth tokens
  • core: api: support passing test log in the JSON file
  • core: plugins: fix builtin plugins path
  • core: plugins: add gerrit builtin plugin
• ci
  • ci: lava: fetch test logs if available
  • ci/backends/lava: modify unit tests to check logs retrieval
• docs: document notification plugins

0.67

• frontend:
  • frontend: combine compare menu
  • frontend: add compare build to build list
  • frontend: order projects alphanumerically
  • frontend: rename "Explore" menu to "Groups"
  • frontend: metrics: display range of values
  • frontend: metrics: fix Y axis configuration
  • frontend: add option to compare build and projects by metrics
  • frontend: bring compare menu to front
  • frontend: use gettext in login template
  • javascript: changed floatThread to floatThead
• ci:
  • ci: backend: lava: extract settings to separate method
  • ci: backend: lava: add option to ignore lava boot results
• doc:
  • doc: ci: add CI_LAVA_IGNORE_BOOT to docs
• core
  • core: queries: make data entries more readable
  • core: queries: expose measurement ranges
  • core: add MetricComparison class
• scripts/testdata: generate more interesting metrics
• i18n:
  • New translation: Spanish (Mexico)
  • Updated translation: Norwegian Bokmål
  • Updated translation: Polish
  • Updated translation: Portuguese (Brazil)

0.66

• frontend
  • frontend/templatetags: fix pagination get_page_url
  • frontend: fix floatThead
  • charts: always redraw dynamic metrics
• api:
  • api: allow Authorization: Token in resubmit calls
  • api: return proper value when resubmit is not successful
• core:
  • metrics: Add dynamic metric summary
• i18n
  • Added a partial Norwegian Bokmål translation
  • Updated Brazilian Portuguese translation
  • doc/translating.rst: add instructions to translate on weblate

0.65

• i18n: add Brazilian portuguese translation for SQUAD UI
• core
  • core: import_data: adjust dates on imported data
  • core: import_data: ignore test runs with no metadata
  • core: import_data: display some indication of progress
  • Add environment to MetricsSummary and TestSummary
  • Add BuildSummary class
• doc:
  • doc/api: fix HTTP method for resubmit endpoints
  • doc: add details about LAVA multinode jobs
• api:
  • api: fix authentication in resubmit API
  • api: fix tests for CI API
• ci:
  • ci: allow cloning LAVA results with measurements
  • ci: add support for LAVA multinode jobs
  • ci: make sure null backend is never used
• frontend
  • Add metrics summary to charts
  • Make default charts to be overall metrics summary per build

0.64.1

• i18n: ship compiled message catalogs

0.64

• frontend:
  • rewrite build settings with Django forms/views
  • Standardize "settings" tab to be similar to Group and Project settings tab name
  • extract "test results summary" into a shared template
  • mark strings for translation
  • Show "Projects" tab only if user had specific permission
  • compare_projects.jinja2: add pagination to test results
  • cache downloaded static assets
  • frontend/project_settingspy: add more attributes
  • squad/controllers/charts.js: display tooltip on line hover
  • frontend: allow empty searches in test comparison page
• i18n
  • Document translation process
  • scripts/update-translation-files: drop empty line at the end of .pot files
  • add Polish translation for SQUAD UI
• core: mark strings for translation
  • core/notification.py: add number of skipped tests to default email template subject
  • core/notification.py: include metrics in context of email notifications
• ci: testfetch: add option to fetch in the background
• api
  • api: add subscribe/unsubscribe endpoints to Project
  • api/rest: Add KnonwIssue filtering to Test object
  • doc: added description for subscribe/unsubscribe endpoints
• doc/index.rst: add missing dependency on Debain/Ubuntu
• fix yaml.load default Loader warning

0.63

• api:
  • Fix api/data call date arguments
  • avoid crash on delayed reports with empty error message
  • fix serialization of Project.enabled_plugins_list
• ci:
  • lava: compose boot test identifier from job_name, i.e. instead of just "boot", the boot tests results from lava will be named "boot-${device-type}"
• core:
  • add 'users' management command
  • group membership is now represented explicitly, and there are three access levels:
    • result submitters (can submit test results)
    • admins (can change anything in the project)
  • drop obsolete Token model
  • Add support for archiving projects (Archived projects are hidden by default from from the group page)
• docker: reduce image size
• frontend:
  • Add build settings tab
  • Add group and project self service interfaces. it is now possible for regular users to:
    • Create new groups (authenticated users only)
    • Create users namespaces (groups in the format "~${username}"), to host personal projects
    • On groups where one is an admin:
      • Edit group setttings
      • Delete the group
      • Create new projects
    • On projects where one is a admin:
      • Edit project settings
      • Delete the project
  • mark strings that compose the home page as translatable
• i18n: add initial infrastructure
• mail: add bulk mail headers to outgoing mail to avoid autoreplied

0.62.1

This release has no functional changes. It just fixes the artifacts published for the previous release.

0.62

• core:
  • models.EmailTemplate: add jinja2 syntax validation
  • TestComparison: avoid loading too many objects at once. This fixes a long-running issue with excess RAM usage on workers.
  • allow superuser access to all groups, as well as access to empty groups by group members.
  • Refactor project status rebuild command
• frontend:
  • add pagination to builds view
  • support groups and project with empty name
  • prevent displaying 'secrets' from LAVA job definition
  • make regressions and fixes popover stay on screen until explicitly closed, so the data in them can be copied for pasting elsewhere.
• docker
  • docker-compose.yaml: add initial version
• celery:
  • set maximum number of producer connection attempts
• api:
  • Add query result limit to api/data

0.61

• Add management command to update project statues from scratch.
• travis:
  • fix detection of Javascript test failures
  • fix capture of exit status
• Fix a few javascripting
• config.js: removed 'content-type' configuration
• Add import to appConfig for compare.js
• Fix broken charts tests
• Refactor ng apps
• squad/_threshold_table.jinja2: restrict admin controls
• squad/_threshold_table.jinja2: give more specific restriction
• Make all ajax requests contain CSRF header
• Refactor angular apps
• Initialize charts with default summary on all environments.
• Error output missing from failed test cases in tests view.
• api: add missing fields to ProjectStatusSerializer
• core/notification.py: turn off escaping for text emails
• docs: add step-by-step on how to set up SQUAD with LAVA
• Fix previous build ordering in project status test comparison.

0.60

• Make notification strategy a per-recipient choice.
• api:
  • fix URL generated to baseline in DelayedReport
  • fix report caching
  • add 'subject' to reports
• frontend: turn Thresholds metrics name into a select control.

0.59

• Add community connector files for Google Data Studio data source.
• doc: correct errata in curl example
• api:
  • restrict visibility of groups via the API
  • Add all test results filtering.
• ci:
  • ci/backend/lava.py: fallback project_settings

0.58 (0.57)

• api:
  • fix the /builds//report API

0.56

• api:
  • add schema for REST API clients.
  • make api/data returns all results if the metrics is not specified.
  • add endpoint for delayed reports, which are produced in the background
• ci
  • lava: add option to handle lava suite
  • ensure that CI test jobs are always explicitly linked to a target Build object.
• core:
  • Always create a ProjectStatus instance together with a Build one. This solves a long-standing issue where builds that did not receive any test results yet do not show up in the UI.
• core, frontend:
  • add support specifying metric thresholds.
  • add support for marking points as outliers.
  • squad.core.data: fix result checking
• frontend:
  • limit filtering on build page to suite names

0.55

• frontend:
  • fix handling of custom templates for 404 and 401 reponses
  • Merge angular apps on build page into one.
• core, frontend: implement data retention policy
• celery: log memory usage for tasks that use more than 1MB
• ci:
  • fix testjobs resubmit
• api:
  • gracefully handle incorrect project IDs in filters
  • fix test comparison results

0.54

• frontend:
  • Add Annotation line in graphs.
  • Add tooltips on chart sliders.
  • Add Unit tests for JS code.
• ci:
  • lava: Clean up is_pipeline checks.
• core:
  • add tracking to EmailTemplate changes

0.53.1

• frontend: Fix missing changes in Jinja templates

0.53

• frontend: migrate all templates to Jinja2
• core:
  • fix incorrect notification template names
  • comparison: compose results from a single database lookup

0.52.1

• Backport fixes from master branch:
  • frontend: fix pagination iterator variable
  • celery: really set celery to log with the same settings as the main app
  • celery: workaround missing attribute in billiard frame objects

0.52

• Add infrastructure for counting database queries
• squad.manage: check performance counts when running tests
• api:
  • add advanced filtering backend
  • add suitemetadata endpoint
  • add support for listing suite/test names in project
  • test.api.test_rest: add extra test data
• core: TestComparison: optimize database access
• frontend:
  • Add indicator when adding/updating tests.
  • fixes to compare.js and compare.html
  • fix test history table for Chrome
  • Fix test_run's job_id on build page
  • limit testjob/ urls to support only integers
  • replace comparetest combos with select2
  • Move chart.js bundle script from base template to metrics.
  • charts: Remove x-axis ticks in case of an empty result set.

0.51.2

• core: NotificationDelivery: allow new notifications on changes
• core: TestComparison: fix performance regression handling xfail

0.51.1

• scripts/release: don't distribute local_settings.py

The previous release erroneously included a local configuration file, and has been removed from PyPI. This release fixes that mistake, and supercedes the previous.

0.51

• core:
  • Make order of tests important in notifications
  • notifications: avoid duplicated "X FAILED TEST JOBS" notifications
  • queries: use build date for X axis
  • queries: also count xfail when calculating test pass %
  • queries: fix Test pass % in the presence of multiple test runs
  • TestComparison: record xfail -> pass transitions as fixes
• frontend:
  • build page: visually indicate that "more info" is available
  • improve presentation of known issues in the UI
  • display reason for build being unfinished
  • create separate view for full metadata
  • Make it possible to display the charts page in fullscreen
  • test history: add links to group and project
• api:
  • allow to filter ProjectStatus by last_updated field
  • add 'comparetest' to the api UI header
  • provide metrics data in CSV as well
  • Limit number of points in charts
  • fix pagination in TestRun detail routes

0.50.1

• frontend:
  • display "Not submitted and" "Not fetched" is list of test jobs
• core:
  • admin: List test counts for ProjectStatus
  • add 'xfail' to default test statuses
• ci:
  • lava: avoid extra request when fetching results

0.50

• api:
  • add regressions and fixes to ProjectStatus
  • add test for api/knownissues/ endpoint
  • allow for filtering with substrings
  • change pagination for some views
  • fix KnownIssuesViewSet filter fields
  • fix TestJobFilter to allow TestRun relation
  • speed up API UI for builds
• core:
  • add counter for tests with status xfail
  • cache Status.has_metrics
  • notification: avoid duplicate notifications
  • notification: ensure metadata is sorted
  • ProjectStatus: make test count fields default to 0
  • rename KnownIssue.environment to environments
  • tasks/RecordTestRunStatus: reduce code duplication
  • Test: record xfail when matching any active known issue
• doc: added docs on REST API
• frontend:
  • add indication of unfinished builds
  • allow substring searches in compare test view
  • allow users to subscribe/unsubscribe to email notifications in a project
  • build: improve column widths in test results table
  • build: make "details" URL parameter independent of selection order
  • build page: also expand details when clicking suite name
  • display known issues across the UI
  • download: handle packages without a top-level directory
  • fix 500 when accessing nonexisting build testjobs
  • fix links to test run details
  • fix test_run.html after changes to templatetags
  • present regressions and fixes in the build list
  • redesign build page for speed
  • test_run: remove <small> from UI
  • add tests to cover all basic URLs

0.49

• frontend:
  • add shortcut to latest finished build
  • add compare test page with dynamic content
• api:
  • allow for baseline selection with build//email API
  • add Suite endpoint
  • make API web frontend more responsive
  • add pagination to test_result route
  • add full_name to project
• ci:
  • admin: list testjob creation timestamp
  • make sure test job is marked fetched
• core:
  • Build: check expected test runs even with CI jobs

0.48

• frontend:
  • improve footer wording
  • Group testresults by suite and env in build page
• api:
  • add Test object and more filtering options
• core:
  • ProjectStatus: cache test run counts. This provides a large speedup to the project page.
• ci:
  • lava: fix case when LAVA fails to provide error_type

0.47

• core:
  • ProjectStatus: correctly handle 0 expected_test_runs
  • detect changes from 'fail' to 'pass'
• frontend:
  • add SVG badge as separate view
• api:
  • add endpoint for PatchSource object
  • make all 'id' fields read-only
  • expose 'finished' flag to Build
• ci:
  • lava: prevent password leaking in error messages
• scripts:
  • add squad-config script for managing external config

0.46.2

This release provides the proper artifacts for SQUAD 0.46

0.46.1

The release artifacts for this version are incorrect, and should not be used.

0.46

The release artifacts for this version are incorrect, and should not be used.

• api:
  • fix crash when accessing TestRun.Metrics
  • add endpoint for KnownIssue object
  • order build results by ascending instead of descending
• ci/Backend: allow disabling polls
• ci/admin: show poll_interval and max_fetch_attempts in Backend listing
• core:
  • add tests for KnownIssues
  • display known issues in email notifications
  • limit Project.enabled_plugins_list to applicable plugins
  • limit PatchSource.implementation to related plugins
  • Add KnownIssue model class
• frontend:
  • Improve TestRun and TestSuite pages
  • remove 'Build' and 'Test Run' from the page header
  • display when known issue is intermittent
  • display known issues in light orange
  • test history: display known issues
  • display Known issues in test results page
  • build page: sort test runs by suite slug
• plugins:
  • add Github build status notification plugin
  • add optional features option to plugin fields
  • add get_plugins_by_feature
  • split core plugin support from builtin plugins

0.45.1

• ci/admin: only link to test job with valid URL
• settings: fix periodic tasks schedule

0.45

• api:
  • add endpoint for creating builds
  • report issues with email templates without crashing
• ci/lava:
  • allow resubmitting LAVA Test failures
• core:
  • add base infrastructure for patch builds
  • add CreateBuild task
  • add tasks to notify patch builds
  • change Project.enabled_plugins_list to PluginListField
• plugins:
  • add API for patch source notifications
  • add PluginListField and PluginField
• frontend:
  • improve the readabiliy of the headers
  • switch tabs to pills so they are easier to locate visually
  • handle missing suite names in test history page
  • link to test run from build page (insted of to details of each suite)

0.44

• api:
  • disable HTML controls for filtering
  • only expose Build.metadata on specialized endpoint
  • testjobs: prefetch backend objects
• core:
  • prevent fetching large text fields from TestRun by default
  • TestHistory: allow pinning the top build
  • TestHistory: sort environments by slug
• frontend: test history: add permalink with pinned top build

0.43

• Drop Django 1.10 support
• core:
  • add pagination support to TestHistory
• api:
  • minor fixes to make API more uniform
  • omit Build.finished
  • prefetch test runs when handling builds
• frontend:
  • paginate test history page
  • get user avatars from gravatar.com
  • add TestJob count numbers to build view
• ci:
  • admin: display TestJob submission date
• squad.run:
  • display unicorn options
  • add --fast option for fast startup

0.42

• core:
  • Mark optional fields optional
  • fetch project and group for Test
  • add DB indices for identifier-like fields
  • comparison: avoid extra, slow database query

0.41

• api:
  • allow write-only access to backend tokens
  • add 'email' method to the Build object
  • added tests for build/email REST api
  • add Group and UserGroup objects to REST api
  • add tests for Group REST API
  • allow changing slug in UserGroups
  • add 'id' and 'metadata' fields to Build object
  • add all Project fields to REST API
  • allow filtering on most of the Project fields
  • add search and sorting features
• ci:
  • add reference to resubmitted TestJob
  • make parent_job read-only in admin
  • lava: allow supressing resubmit emails with backend settings
• core: add Group.description
• frontend:
  • display list of groups in home page
  • add link to TestJob's parent
  • display model.name instead of model.slug
• doc:
  • install.rst: document installation of RabbitMQ
  • restructure docs and include ci setup
• scripts/git-build: allow building package without having runtime dependencies installed

0.40

• ci:
  • move backend settings to database
• ci/lava:
  • fix resubmit() function
  • properly handle invalid SSH handshake
• core/notification:
  • drop test history info from default templates (eliminates a performance bottleneck with builds that have a large number of failed tests)
  • skip creating HTML version of the email if not required
• plugins:
  • add testjob postprocessing hook

0.39.3

• celery: correctly load configuration from Django settings

0.39.2

• settings: take Celery broker URL via environment

0.39.1

• fix crash in admin by removing debug print

0.39

• api: add REST API for email templates
• ci/lava:
  • don't crash if there is no metadata
  • update listener to match new LAVA state machine

0.38

• core, api: migrate to Django REST Framework tokens
  • The old squad-specific Token model has been migrated to Django REST Framework tokens. The actual data for the old tokens is still there, but it's not used for anything anymore. It will be automatically removed in the next release.
• core:
  • add support for test case variants
• frontend:
  • return 404 on non-existing data
  • add initial user settings UI
  • add API token settings page
  • improve display of descriptions in project list
• api
  • Add CORS support via django-cors-headers
  • fix TestSerializer
  • make Project.slug readonly
• ci/lava:
  • add more strings to automatic resubmit list
  • parse LAVA log using incremental parser
  • add unit test for log parsing

0.37

• admin: allow manually triggering post-processing of test run data
• api: add filter_fields to BuildViewSet
• api: add ID field to objects returned by REST API
• api: Add ProjectStatus to REST API
• ci: fetch test result data in chunks in LAVA backend
• ci/lava: restore downloading logs
• frontend: Add pagination to test and metric listings
• frontend: fix environment label in tests history table
• frontend: improvements to the resubmit UI
• frontend: paginate "all test results" page
• scripts: add script to migrate testruns between projects
• Store and display metadata about environments, suites, tests, and metrics

0.36

• frontend:
  • retitle test results page to "All test results"
  • hide non-failing test results by default
  • improve formatting of "test results" tables
  • link test results to test history in "all test results" page
• ci/lava: don't crash when lava listener provides no status

0.35

Upgrade notes: this version drops support for starting the celery-related daemons (worker and scheduler) using the "./manage.py | squad-admin" command line interface. To start those daemons, you should now use the standard celery command line interface, i.e.

• celery -A squad worker for the worker, and
• celery -A squad beat for the scheduler.

Changes:

• api:
  • Added a REST API for accessing most of the data in SQUAD. This API is only adequate for read-only access for now.
  • The API is self-describing and features a API browser when accessed with a web browser. This API browser is linked from the navigation bar at the top.
• frontend:
  • make login link redirect to original page
• settings:
  • respect proxy headers when generating absolute URLs
• upgrade to celery v4
  • Drop support for SQL-backed periodic task scheduling
  • requirements.txt: drop restriction for using celery v3

0.34.1

• core/notification: don't spam admins

0.34

• ci:
  • add created, submitted and fetched dates to TestJob
  • fill in submission and fetch dates
  • admin: avoid loading all Build and TestRun objects
• core/notification:
  • fix tests for notification_timeout
  • core/notification: notify only once on timeout
• frontend:
  • display testjob.failure if available

0.33

• squad.run: exec() into an actual gunicorn process
• ci/admin: make Job ID a link to the backend
• ci/lava/listener: log only messages related to test jobs of interest
• ci:
  • save TestJob.last_fetch_attempt before fetching
  • delay updating project status until after TestJob is saved
• core
  • tasks: make database transaction explicit
  • make updating project status optional
  • fix failed testjob notification templates

0.32.3

• Revert "squad.run: exec an actual gunicorn process"

0.32.2

• ci: fix off-by-one error

0.32.1

• squad.run: exec an actual gunicorn process
• ci: handle maximum fetch attempts in works as well

0.32

• core: fix query for "test pass %"
• ci: limit fetch attempts with temporary issues
• ci/lava:
  • Fix exception handling for failed log fetching
  • disable log fetching for the moment

0.31

• core.admin: list and fiter by ProjectStatus.finished
• ci/lava:
  • speed up parsing of structured logs and test results from YAML
  • fix parsing of test suite names

IMPORTANT: starting from this version, the LAVA backend for CI jobs requires that PyYAML has been compiled with support for libyaml. So if you are upgrading from a previous version and are using the LAVA integration, make sure that is the case.

• python3 -c 'import yaml; print(yaml.__with_libyaml__)' must print True
• if not, make sure you have the development files for libyaml installed (e.g. libyaml-dev) before (re)installing PyYAML.
  • To reinstall PyYAML: pip install --upgrade --force-reinstall --no-cache-dir PyYAML

0.30.1

• ci: Reimplement poll as a series of fetch operations
• core.queries: optimize query for "tests pass %" metric
• frontend: add links to test history

0.30

• ci:
  • formally associate TestJobs with their target build
  • lava: remove per-job failure notifications
• core/Build: use pending CI jobs in the definition of finished
• core/notification:
  • add support for delayed notifications
• core/notification:
  • drop retry logic from notification task
  • extract a reusable base HTML template
  • force sending notifications after a timeout
  • improve design of moderation warning in HTML
  • notify admins of failed test jobs
• frontend:
  • add filtering to build page
  • add floating table headers
  • list failures on top, and allow filtering in Test results page
  • prioritize test suites with failures in build page

0.29.1

• frontend: return 404 for unexisting build on test run page
• core:
  • allow empty list of enabled plugins
  • notifications: add missing important metadata dict

0.29

• api: set 'submitted=True' on TestJobs created with 'watchjob' API
• ci:
  • add more details to failed test job notifications
  • lava: delay email notification to allow for storing the object
  • lava: update TestJob name and status
  • update failed testjob subject
• core:
  • notification: include only important metadata in emails
  • postprocess test runs, using plugins
  • Project: add field to store list of enabled plugins
• frontend
  • hide group slug when in the group page
  • Fix loading metrics chart configuration from URL
• plugins:
  • add the beginnings of a plugin system
  • add basic documentation for both using and writing plugins
  • add a linux_log_parser plugin as an example. It still needs a few improvements before it can start to be used seriously.

0.28

• core:
  • modify test_suites_by_environment to provide count of pass, fail, and skip tests
• README.rst: fix copyright notice to mention AGPL
• frontend:
  • optimize build listings
  • return 404 on non-existing Build, TestRun, and Attachment
  • re-add missing red background for failed tests in test results tables
• doc: move documentation to sphinx

0.27

• core:
  • display metadata in a grid in HTML notifications emails
  • handle list as metadata keys in emails
  • Test: add log field
• frontend:
  • add line break between metadata list values
  • highlight rows under the mouse on project and build listings, and in the list of test suites in the build page
  • remove "ed" suffix from test results
  • align width of top navigation bar with content width
  • turn entire suite rows into links
  • improve HTML markup
  • redesign the TestRun page
    • failures are listed at the top, with their corresponding log snippet if available
      • note however that assigning log snippets to test results is not implemented yet; will probably be available on the next update.
    • skipped and passed tests are hidden by default, but can be displayed with a click

0.26

• Dockerfile: run out of the box
• api: create Build object when creating TestJob
• core, ci: drop usage of VersionField
• core:
  • don't overwrite ProjectStatus with earlier data
  • fix test for not sending duplicated notifications
  • remove ProjectStatus creation/update from transaction
  • make it possible to specify important metadata
  • make Build metadata the union of test runs metadata
• ci: make TestJob.build the same type as Build.version
• frontend:
  • add missing "incomplete" word in builds table
  • add titles for project internal pages
  • present test jobs in build page
  • convert builds table into a grid
  • redesign the build page
  • update Font Awesome hash
  • use a grid for metadata everywhere
  • display only important metadata for build

0.25

• Change license to the Affero GPL, v3 or later
• MANIFEST.in: remove redundant lines
• Normalize email addresses
• README
  • README.rst: remove mention of Debian packages for assets
  • README.rst: update list of dependencies on Debian
• ci: lava: add 'auto-login-action' to automatically resubmitted patterns
• core
  • core/Build: sort test suites in test_suites_by_environment
  • core/notification: Do not send dup notifications
  • core: added project description
• frontend
  • frontend: added support for logging in on small screens
  • frontend: change license mentioned in the header
  • frontend: display skip percentage and tooltips in test bars
  • frontend: download static assets from their original locations
  • frontend: hide project list header on small screens
  • frontend: hide zeros in build listing
  • frontend: improve UI consistency
  • frontend: only replace download.status if needed
  • frontend: use better colors for pass/fail
• gen-test-data: do everything that is needed under the hood
• git-build: fix clean of old builds
• scripts
  • scripts/git-build: build Python packages from the git repository
  • scripts/release: exclude download assets from the tar vs git check
  • scripts/travis: abandon git-based cache of static assets
• setup.py: correctly exclude code from test/ from being installed
• submit-test-data: also generate skips

0.24

• core
  • provide test suites executed by environment
• README updates

0.23

• core/notification:
  • add support for having a custom subject as part of an email notification template.

0.22

• ci
  • handle fetching failures with less noise, and in a way that is independent of the test job backend. This reverts the LAVA-specific handling added in 0.21.
• ci/lava
  • add support for using boot information from LAVA as an articial boot test and as a boot time metric.

0.21

• frontend:
  • Add missing red bar in group main page for test failures
• core:
  • add support for per-project custom email templates
  • comparison: use environment name is available
• Add script to run a development environment on docker
• ci/lava
  • log and notify by email any errors when fetching test jobs

0.20.3

• core:
  • add management command to force sending an email report.
    • This can be used for example to help local testing
• ci/lava:
  • filter events down do the ones we can (and want to) handle
• frontend:
  • fix crash when viewing projects with no data

0.20.2

• frontend:
  • fix javascript error

0.20.1

• core:
  • fix update of ProjectStatus objects

0.20

• core:
  • admin:
    • move "re-send notification" action to ProjectStatus
    • expose Build data
    • sort ProjectStatus by build date
  • Test results:
    • use just "skip" instead of "skip/unknown"
  • ProjectStatus: determine previous (baseline for comparison in notification) dinamically, by getting the previous build that has complete data.
  • Project: avoid duplicated projects in listing
  • notification: list explicitly number of skipped tests
• frontend: improve wording on project home page
• ci/listen: spawn listener processes without fork()

0.19

• core:
  • notifications:
    • retry if ProjectStatus id does not exist (yet). Handles race condition when worker process tries to send a notification before the corresponding data has been commited to the database by the process requesting the notification.
  • Build data:
    • don't count tests that have been retried twice. e.g. if a test job is resubmitted, the test results produced will override any corresponding test results from previous test jobs.
• frontend:
  • optimize database queries used to compose build page. Data tested shows a reduction of ~95% in the response time.
  • avoid producing exceptions when users try to access an unexisting group (not just returns an 404 error quietly).
  • show all builds in the project front page (i.e. don't omit the last build, that already has details displayed, from the full list of builds).
  • hide resubmit button from unprivileged users (who should't be allowed to resubmit in the first place).
• ci/lava:
  • automatically resubmit jobs that failed due to infrastructure problems that we already know about.

0.18.1

• core/admin:
  • display "moderate notifications" in project listing
  • filter ProjectStatus by project
  • add several filters for the project listing
• settings: set SERVER_EMAIL

0.18

• ci:
  • mark proper TestRun status on awkward LAVA failure
• frontend:
  • display squad version in the base template
  • several improvements to the UI to make browsing data more effective
• core:
  • notitifications are now sent immeditately after there is enough data for each build, instead of on pre-scheduled times.
  • notifications can now be moderated by admins before being sent out to users.

0.17

• core:
  • update "last updated" data every time new results arrive for a given build
  • notification: clearly identify tests that never passed as such
• ci:
  • lava: report incomplete TestRun when TestJob is canceled
• frontend:
  • fix group page to use correct status data (pass/fail counts, metric summary)

0.15

• core:
  • Test names are now ordered alphabetically by default
  • Site home page and project home page were fixed to display the correct build status information (tests pass % and metric summary)
  • notification: avoid spurious empty lines in plain text notification
  • admin: allow filling in slug when creating Environment
  • notification: group columns by environment in changes table
  • notification: send a single email
  • record project status at submission time instead of only when processing notifications
  • notification: add a per-project flag to control whethet to send a text/html alternative representation together with plain text content
• ci:
  • add job_url to TestRun metadata if present
• ci/lava
  • filter LAVA logs to include only the serial console output
• infrastructure
  • settings: enable exception notifications by email
• frontend:
  • fix resubmit JS code
  • serve TestRun logs directly (i.e. allow viewing them in browser instead of forcing a download)