Skip to content

Latest commit

 

History

History
176 lines (146 loc) · 10.4 KB

CHANGELOG.md

File metadata and controls

176 lines (146 loc) · 10.4 KB

Not released yet

Nothing new here

1.2.0

  • KARAF_SECRETS_ON_STARTUP env triggers Karaf secrets scanning on startup
  • Images support for linux/arm64 architecture. For Karaf image, please use 1.2.0-arm64 tag when running on Mac Apple Silicon processors.

1.1.0

This release fixes security issue, upgrading Browsermob and Karaf dependencies to log4j 2.17.1 fixing CVE-2021-44832 and other Log4jShell vulnerabilies. If you migrate from version older than 1.0.0, please remember to execute all steps in upgrade notes for all the version between this and your current version.

  • PR-33 - Update BrowserMob Proxy image to the version without log4jshell vulnerability.
  • PR-34 - build custom version of Apache Karaf 4.2.0 with updated pax.logging dependencies.

1.0.0

Images moved to my new Docker Hub space: https://hub.docker.com/u/malaskowski

This means you need to update both image name and tag in you AET instance cluster to be able to fetch the latest version of AET Docker images (rename skejven/aet_XXX:0.14.0 to malaskowski/aet_XXX:1.0.0).

  • PR-28 - Before the start of a Karaf service, Docker secrets are exported to environment variables.
  • Base images updates:
    • aet_client image base updated to alpine:3.14
    • aet_report image base updated to httpd:2.4.48-alpine

0.14.0

  • PR-27 - Karaf provisioned with all dependencies - offline mode provisioning support.
  • PR-26 - AET Docker client for running AET suites with no dependencies but Docker
  • PR-22 - changed no of Selenium Grid Nodes replicas in order to improve tests results stability.
  • PR-23 - updated mongodb image version to 3.6. Important: if you are upgrading AET from the version that used mongo 3.2, please read carefully upgrade notes before migrating. Updated docker swarm schema to 3.7.

Upgrade notes

  1. Backup your data!

  2. Upgrade to mongo image 3.4 first (set image: mongo:3.4 in aet-swarm.yml and deploy - docker stack deploy -c aet-swarm.yml aet). Wait until AET stack will be up.

  3. Assuming you have open port 27017 for mongo run:

    docker exec -it `docker ps --filter expose=27017/tcp -q` bash -c 'mongo --eval "db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )"'

    This should say { "featureCompatibilityVersion" : "3.2", "ok" : 1 }.

  4. Set setFeatureCompatibilityVersion flag to 3.4 (read more in MongoDB upgrade notes), run:

    docker exec -it `docker ps --filter expose=27017/tcp -q` bash -c 'mongo --eval "db.adminCommand( { setFeatureCompatibilityVersion: \"3.4\" } )"'

    You should see: { "ok" : 1 }

  5. Upgrade to mongo image 3.6 (set image: mongo:3.6 in aet-swarm.yml and deploy - docker stack deploy -c aet-swarm.yml aet). Wait until AET stack will be up.

  6. Set setFeatureCompatibilityVersion flag to 3.6 (read more in MongoDB upgrade notes), run:

    docker exec -it `docker ps --filter expose=27017/tcp -q` bash -c 'mongo --eval "db.adminCommand( { setFeatureCompatibilityVersion: \"3.6\" } )"'

    You should see: { "ok" : 1 }

  7. You are good to go :).

0.13.1

  • PR-21 Proxy all API endpoints via report app: /api, /suite, /xunit Upgrade notes:

Upgrade notes

If you were using AET_WEB_API env for the aet-report service, please note, that it now points to the Karaf instance, not directly to the /api endpoint. Simply remove /api from AET_WEB_API env property value.

0.13.0

0.12.2

  • PR-19 - Enable exposing AET WebAPI via Report server

0.12.1

  • PR-17 Update maven repositories to use https over http. Fixes '501-https-required' error while downloading karaf dependecies. More info about the issue here.

0.12.0

  • PR-11 Report docker image base changed from Ubuntu to httpd Alpine (386 MB to 150 MB)
  • Removed suite generator from the report image (it lacks Open Source license)
  • PR-12 introduces AET Lighthouse Extension to the aet example swarm stack
  • AET Version upgraded to 3.3.0 release

0.11.0

  • AET Version upgraded to 3.2.2 release

0.10.0

Upgrade notes

All Karaf AET artifacts (bundles, features and configs) are now stored in the Karaf Container in the /aet location:

├── aet
│   ├── bundles
│   ├── configs
│   └── features

The main change concerns configs which were previously stored directly under root /configs inside the Karaf container. Remember to adjust your instance deployment config to that change.

0.9.0

  • Fixed ActiveMQ not working jmx interface
  • AET Version upgraded to 3.2.1 release
  • AET artifacts are no longer stored in the repo but downloaded
  • Important change: since AET-463 there are one less bundles. That caused:
    • aet_karaf provision healthcheck looks for 187 instead of 188 bundles active
    • healthcheck for the karaf container looks for 203 active bundles instead of 204

0.8.0

  • AET Version upgraded to 3.2.0 release
  • AET OSGi configs managed by mounted config volume in the stack file
  • example-aet-swarm module with example cluster setup and configs

how to migrate to 0.8.0 from 0.7.1

Because of PR-6 now OSGI configs are mounted as separate volume for Karaf image. If you upgrade your AET instance from the previous version please do following steps:

  1. As usual, update images version in your aet-swarm.yml file (to 0.8.0).
  2. Add volumes section to the karaf service with following volume definition:
    volumes:
      - ./configs:/configsp
  1. Download example-aet-swarm.zip from the release and unzip it. Copy configs folder to the same place, where you placed aet-swarm.yml.
  2. Remove environment section from the karaf service. You may now configure REPORT_DOMAIN and REPORT_DOMAIN OSGi configs in the configs directory.
  3. As usual run docker stack deploy -c aet-swarm.yml aet to update your AET stack.

0.7.1

  • PR-4 - fixed incorrect format of ChromeWebDriverFactory config

0.7.0

  • AET Version upgraded to 3.1.0 release

0.6.1

  • Fixed problem with Karaf configuration files permission denied

0.6.0

# 0.5.0 - please don't use this version - AET Version upgraded to 3.0.1

0.4.1

  • Fixed maintainer label
  • More generic build and release scripts (with version arg)
  • Fixed Runner OSGi config
  • Beta version of AET suite generator

0.4.0

  • Swarm file removed from the repository, it will be available only in the release artifact
  • full AET log now is available with docker service logs aet_karaf -f (from Karaf internal, runner, worker and cleaner)
  • AET version upgraded to 3.0.0-rc01

0.3.0

  • latest AET from master (with Chrome support, new OSGi configurations, suite history support and advanced screenshot comparison)
  • Karaf base image with resolved bundles from features file
  • Karaf container HEALTHCHECK (in swarm config)
    • Original HEALTHCHECK from the Karaf's Dockerfile was moved to swarm config because of some odd behaviour (container never was healthy when multi-stage build was applied)
    ARG HEALTHCHECK_PHRASE="204 bundles in total - all 204 bundles active"
HEALTHCHECK --interval=1m --timeout=10s --start-period=120s \
   CMD curl -v --silent http://karaf:karaf@localhost:8181/system/console/bundles 2>&1 | grep -Fq ${HEALTHCHECK_PHRASE} || exit 1
  • version of compose-file upgraded from 3 to 3.6 (for the healthcheck start_period option), notice it requires Docker Engine 18.02.0+
  • upgraded way of downloading Apache Karaf distribution

0.2.0

  • latest AET from master (with Chrome support and new OSGi configurations)
  • added Karaf image ENV variable MONGODB_URI that enables to set mongoURI at the cluster manager level (e.g. to external MongoDB instance)
  • optionally running Karaf in Debug mode

0.1.0

  • expose port range in BrowserMob container
  • updated AET app (from the latest milestone/chrome-support)
  • selenium grid updated to 3.14.0-arsenic
  • added Karaf image ENV variable REPORT_DOMAIN that enables to set ReportConfigurationManager.reportDomain at the cluster manager level