diff --git a/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md b/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md index 3432e790..609e1fd3 100644 --- a/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md +++ b/src/markdown-pages/docs/cli-command-reference/running-simbank-tests-cli.md @@ -50,7 +50,7 @@ In order to run the Galasa SimBanks tests you need to add some configuration inf The SimBank tests are held in the Galasa simplatform repository in GitHub. To start running the tests you need to clone the repository, if you have not already done so. To find out how to clone the cli repository, follow the instruction in the `Launching SimBank` section in the [Exploring Galasa SimBank online](simbank-cli) documentation. -After cloning the repository, complete the following steps to run the SimBankIVT test that is provided with Galasa. The following example uses SimBank OBR version `0.25.0` and Galasa uber OBR version `0.34.1`. +After cloning the repository, complete the following steps to run the SimBankIVT test that is provided with Galasa. The following example uses SimBank OBR version `0.25.0` and Galasa uber OBR version `0.35.0`. You can find the version of the `dev.galasa.simbank.obr` that you are using by looking in the `pom.xml` file in the `dev.galasa.simbank.obr` folder. The `dev.galasa.uber.obr` is the OBR that contains all the bundles that are needed for Galasa to work including Managers, any required dependencies, the framework, etc. The version of the `dev.galasa.uber.obr` depends on which version of Galasa you have installed. diff --git a/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md b/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md index f6d4a0cb..5dddab24 100644 --- a/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md +++ b/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md @@ -53,8 +53,8 @@ Complete the following steps to install a Galasa Ecosystem by using Helm: helm repo add galasa https://galasa-dev.github.io/helm ``` - If the repository exists, run the ```helm repo update``` command to get the latest versions of the packages and then run ```helm search repo galasa``` to see the available charts.
- _Note:_ The Galasa Ecosystem Helm chart deploys three persistent volumes (PVs). If you need to provide a Kubernetes storage class for these PVs, download the values.yaml file and update the `storageClass` value in the file with the name of a valid storage class on your cluster. If you are deploying to minikube, you can optionally use the standard storage class that is created for you by minikube, but this is not required. -1. Download the values.yaml file if you have not done so already, and edit the values of the following properties: + _Note:_ The Galasa Ecosystem Helm chart deploys three persistent volumes (PVs). If you need to provide a Kubernetes storage class for these PVs, download the values.yaml file and update the `storageClass` value in the file with the name of a valid storage class on your cluster. If you are deploying to minikube, you can optionally use the standard storage class that is created for you by minikube, but this is not required. +1. Download the values.yaml file if you have not done so already, and edit the values of the following properties: - Set `galasaVersion` to the version of Galasa that you want to run. (See the [Releases](/releases) documentation for released versions). To ensure that each pod in the Ecosystem is running at the same level, do not use `latest` as the Galasa version. - Set `externalHostname` to the DNS hostname or IP address of the Kubernetes node that is used to access the Galasa Ecosystem services. If you are deploying to minikube, the cluster's IP address can be retrieved by running `minikube ip`. @@ -225,14 +225,14 @@ You can then deploy your Galasa tests to a Maven repository and set up a test st ## Upgrading the Galasa Ecosystem -Get the latest version of the Ecosystem chart and upgrade the Galasa Ecosystem to use the newer version of Galasa - for example version 0.34.1 - by running the following command: +Get the latest version of the Ecosystem chart and upgrade the Galasa Ecosystem to use the newer version of Galasa - for example version 0.35.0 - by running the following command: On Mac or Unix: ```console helm repo update \ helm upgrade galasa/ecosystem --reuse-values \ ---set galasaVersion=0.34.1 --wait +--set galasaVersion=0.35.0 --wait ``` On Windows (Powershell): @@ -240,7 +240,7 @@ On Windows (Powershell): ```console helm repo update ` helm upgrade galasa/ecosystem --reuse-values ` ---set galasaVersion=0.34.1 --wait +--set galasaVersion=0.35.0 --wait ``` where:
diff --git a/src/markdown-pages/highlights.md b/src/markdown-pages/highlights.md index cc64b6b5..27d4882c 100644 --- a/src/markdown-pages/highlights.md +++ b/src/markdown-pages/highlights.md @@ -17,8 +17,13 @@ We have the following available Slack channels: Access the Galasa source code in [GitHub](https://github.com/galasa-dev) and open issues in the [project management repository](https://github.com/galasa-dev/projectmanagement). +## 0.35.0 - Release Highlights -## 0.34.1 - Release Highlights +- A fix to the database connector of the DB2 Manager + + +
+0.34.1 - Release Highlights - Retrieve a list of all active personal access tokens in the Ecosystem by using the `galasactl auth tokens get` command. Use the information to revoke or delete an access token. @@ -29,6 +34,7 @@ Access the Galasa source code in [GitHub](https://github.com/galasa-dev) and ope - Various bug fixes - Various documentation updates +
diff --git a/src/pages/index.js b/src/pages/index.js index 1c08e90b..51fa499b 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -126,7 +126,7 @@ const IndexPage = () => ( Learn more