Hi,
This 0.7 release adds a method in the project model to fetch its
environments among other minor bug fixes.
The release also changes the home of squad-client docker image to
squadproject/squad-client.
Complete list of changes below:
* add methods to fetch environments from a project
* change the attribute from complete to finished
* core: models: add nested endpoints to models
* examples: fix URL in build_report
* fix the example for filtering on finished builds
* manage: avoid configuring api when running tests
* release: change docker repo to squadproject
Ch{eers,arles}
This 1.15 release adds pagination to the 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/<id>/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)
Ch{eers,arles}
Hi,
I was recently asked to prepare a docker compose that includes both
LAVA and SQUAD. This was fairly easy (a few hurdles with LAVA master,
but nothing serious). Currently I have a setup that has SQUAD parts in
separate containers, and LAVA master in separate. SQUAD connects to
LAVA using docker network. This unfortunately causes incorrect URLs
produced nu LAVA backend in LAVA are incorrect. They point to internal
docker addresses and are not accessible from outside. To give the
proper example:
- LAVA master runs in a container named lava-master. It listens on
ports 8000 (http) and 5555 (zmq)
- SQUAD has backend configures with LAVA url as http://lava-master:8000/RPC2
The result is that metadata in SQUAD builds show job URLs as
http://lava-master:8000/scheduler/job/<job id>. Obviously this URL
isn't available from the host network. If I configure backend to use
host's network URL it won't be able to connect. At least I don't know
how to make this happen. Does anyone have any idea how to fix it? Is
there a way for docker encapsulated apps to communicate using host's
network? Here is a link to my docker-compose:
https://github.com/mwasilew/lite-lava-docker-compose/blob/lite/docker-compo…
milosz
Hi
This 0.6 release adds basic caching for fetching data. It also adds
support for fetching metrics and a shortcut for comparing two builds
from the same project.
Complete list of changes below:
* core:
* api: ignore netrc auth
* models: add metrics
* models: add suite do project model
* models: fix metrics and testrun status endpoints
* shortcuts: add shortcut to compare builds
* manage: add basic caching
* shortcuts: return exit code of submit operation
* tests: add test for submit_results return value
Ch{eers,arles}
Hi
This 1.14 release adds an API endpoint that allows 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
Ch{eers,arles}
Hi,
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 "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
Ch{eers,arles}
