From 60c620bd81f1f1db36eeabf54827e2e7650a47af Mon Sep 17 00:00:00 2001 From: James Taylor Date: Wed, 18 Sep 2024 10:24:22 +0100 Subject: [PATCH 1/6] Fix broken link Signed-off-by: James Taylor --- src/markdown-pages/docs/manage-ecosystem/runs-prepare.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md b/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md index 02e63459..2cf7a4ed 100644 --- a/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md +++ b/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md @@ -3,7 +3,7 @@ path: "/docs/manage-ecosystem/ecosystem-cli-runs-prepare" title: "Selecting tests to run in an Ecosystem" --- -If you have a group of tests that you want to run in batch, the simplest way to do this is by defining these tests inside a portfolio. You can create a portfolio of tests by using the `runs prepare` command. You can build the portfolio from single or multiple [test streams](https://galasa.dev/docs/writing-own-tests/test-streams). +If you have a group of tests that you want to run in batch, the simplest way to do this is by defining these tests inside a portfolio. You can create a portfolio of tests by using the `runs prepare` command. You can build the portfolio from single or multiple [test streams](/docs/manage-ecosystem/test-streams). This portfolio of tests can then be run by using the [runs submit command](/docs/manage-ecosystem/ecosystem-cli-runs-submit). When you submit the tests to run, you need specify only the portfolio name on the command, rather than listing all of the classes. From 04a14adf9cba90127c6404341b0191adff541992 Mon Sep 17 00:00:00 2001 From: James Taylor Date: Tue, 17 Sep 2024 14:19:21 +0100 Subject: [PATCH 2/6] Update supported Java versions to include Java 17 See galasa-dev/projectmanagement#1823 Signed-off-by: James Taylor --- src/markdown-pages/docs/cli-command-reference/cli-prereqs.md | 2 +- .../docs/cli-command-reference/runs-submit-local.md | 2 +- .../docs/cli-command-reference/zipped-prerequisites.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md b/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md index 6572788f..6abaaf39 100644 --- a/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md +++ b/src/markdown-pages/docs/cli-command-reference/cli-prereqs.md @@ -9,7 +9,7 @@ The following section explains more about the software prerequisites that you ne ### Java JDK -Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 17 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation. +Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 21 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation. ### Maven diff --git a/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md b/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md index 3cdda364..cb4b53d6 100644 --- a/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md +++ b/src/markdown-pages/docs/cli-command-reference/runs-submit-local.md @@ -16,7 +16,7 @@ Local runs do not benefit from the features that are provided when running tests To use the `galasactl runs submit local` command, the `JAVA_HOME` environment variable must be set to reference the JVM in which you want the test to run, as described in the [CLI prerequisites online](/docs/cli-command-reference/cli-prereqs) and [CLI prerequisites offline](/docs/cli-command-reference/zipped-prerequisites) documentation. This is because the local java run-time environment is used to launch the test locally. To check that `JAVA_HOME` is set correctly, the tool checks that `$JAVA_HOME/bin/java` exists in Unix or Mac, and `%JAVA_HOME%\bin\java.exe` exists on Windows. -The level of Java must match the supported level of the Galasa version that is being launched. Use the `galasactl --version` command to find the galasactl tool version. We currently support Java version 11 to version 16 JDK. _Note:_ We do not currently support Java 17 or later. +The level of Java must match the supported level of the Galasa version that is being launched. Use the `galasactl --version` command to find the galasactl tool version. We currently support Java version 11 to version 17 JDK. _Note:_ We do not currently support Java 21 or later. You can view the full list of options that are available with the `galasactl runs submit local` command in the Galasa cli repository. diff --git a/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md b/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md index dcba9058..5e05e20b 100644 --- a/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md +++ b/src/markdown-pages/docs/cli-command-reference/zipped-prerequisites.md @@ -9,7 +9,7 @@ The following section explains more about the software prerequisites that you ne ### Java JDK -Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 17 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation. +Required. Galasa tests and Managers are written in Java - you need to install a Java version 11 JDK or later to use it. _Note:_ We do not currently support Java 21 or later. After installing, you must set the `JAVA_HOME` environment variable to your Java JDK installation path and check it set successfully by running the command `echo $JAVA_HOME` on Mac or Unix, or `echo %JAVA_HOME%` on Windows (PowerShell). The returned result shows the path to your JDK installation. ### Gradle From e8bba9ba34ce6e04796b210c34eec572d4f6e304 Mon Sep 17 00:00:00 2001 From: James Taylor Date: Tue, 17 Sep 2024 20:48:56 +0100 Subject: [PATCH 3/6] Document the new galasactl runs delete command See galasa-dev/projectmanagement#1210 Signed-off-by: James Taylor --- src/data/nav.yaml | 2 ++ .../docs/manage-ecosystem/runs-delete.md | 28 +++++++++++++++++++ 2 files changed, 30 insertions(+) create mode 100644 src/markdown-pages/docs/manage-ecosystem/runs-delete.md diff --git a/src/data/nav.yaml b/src/data/nav.yaml index 204bbd4c..1a68300c 100644 --- a/src/data/nav.yaml +++ b/src/data/nav.yaml @@ -117,6 +117,8 @@ path: /docs/manage-ecosystem/cli-runs-get - title: Downloading test artifacts path: /docs/manage-ecosystem/ecosystem-cli-runs-download + - title: Deleting test run results + path: /docs/manage-ecosystem/cli-runs-delete - title: Upgrading path: /docs/upgrading - title: Managers diff --git a/src/markdown-pages/docs/manage-ecosystem/runs-delete.md b/src/markdown-pages/docs/manage-ecosystem/runs-delete.md new file mode 100644 index 00000000..284987e7 --- /dev/null +++ b/src/markdown-pages/docs/manage-ecosystem/runs-delete.md @@ -0,0 +1,28 @@ +--- +path: "/docs/manage-ecosystem/cli-runs-delete" +title: "Deleting test run results" +--- + +Over time, test run results build up and take up space in the Galasa Ecosystem. You can delete test runs which have completed in the past by using the `galasactl runs delete` command. + +You can view the full command syntax in the Galasa cli repository. + +## Working with the `galasactl runs delete` command + +The following example deletes a test run called _C1234_: + +``` +galasactl runs delete --name C1234 --bootstrap http://example.com:30960/bootstrap +``` + +## Identifying test runs to delete + +Use the `galasactl runs get` command to find the names of the test runs to delete. For example, use the `--age` option to specify a time period in which the tests ran. + +``` +galasactl runs get --age 6w:1w --bootstrap http://example.com:30960/bootstrap +``` + +The `--format raw` option is useful if you are writing a script to delete multiple test runs. + +You can view the full command syntax for `galasactl runs get` in the Galasa cli repository. From 8ed628cbde850f771cabbf0c64ab411f69c5a3db Mon Sep 17 00:00:00 2001 From: James Taylor Date: Tue, 17 Sep 2024 12:05:32 +0100 Subject: [PATCH 4/6] Update docs for 0.37.0 release See galasa-dev/projectmanagement#1991 Signed-off-by: James Taylor --- .../docs/ecosystem/ecosystem-installing-k8s.md | 10 +++++----- .../docs/managers/galasa-ecosystem-manager.md | 2 +- .../running-simbank-tests-cli.md | 2 +- src/markdown-pages/docs/upgrading.md | 10 +++++----- src/markdown-pages/highlights.md | 11 ++++++++++- src/pages/index.js | 2 +- 6 files changed, 23 insertions(+), 14 deletions(-) diff --git a/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md b/src/markdown-pages/docs/ecosystem/ecosystem-installing-k8s.md index 1967f7e9..8b728c79 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.36.0 - 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.37.0 - by running the following command: On Mac or Unix: ```console helm repo update \ helm upgrade galasa/ecosystem --reuse-values \ ---set galasaVersion=0.36.0 --wait +--set galasaVersion=0.37.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.36.0 --wait +--set galasaVersion=0.37.0 --wait ``` where:
diff --git a/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md b/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md index 8b110a7e..4c7c9611 100644 --- a/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md +++ b/src/markdown-pages/docs/managers/galasa-ecosystem-manager.md @@ -154,7 +154,7 @@ The following are properties used to configure the Galasa Ecosystem Manager. | Required: | No | | Default value: | None | | Valid values: | Valid URL | -| Examples: | galasaecosystem.isolated.mvp.zip=https://github.com/galasa-dev/isolated/releases/download/v0.36.0/galasa-isolated-mvp-0.36.0.zip | +| Examples: | galasaecosystem.isolated.mvp.zip=https://github.com/galasa-dev/isolated/releases/download/v0.37.0/galasa-isolated-mvp-0.37.0.zip | diff --git a/src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli.md b/src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli.md index e750fe6c..28699b86 100644 --- a/src/markdown-pages/docs/running-simbank-tests/running-simbank-tests-cli.md +++ b/src/markdown-pages/docs/running-simbank-tests/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 [Running Galasa SimBank online](../running-simbank-tests/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.36.0`. +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.37.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/upgrading.md b/src/markdown-pages/docs/upgrading.md index 925e9605..78de496d 100644 --- a/src/markdown-pages/docs/upgrading.md +++ b/src/markdown-pages/docs/upgrading.md @@ -34,12 +34,12 @@ Galasa releases 0.35.0 and earlier support the use of Gradle versions 6.8.x, 6.9 To use Gradle version 8.0 or later to create Galasa projects and build and compile Galasa test code, complete the following steps: -1. Edit the `build.gradle` file in the OBR directory of your parent project, setting the plug-in values at the top of the file to version `0.36.0`, as shown in the following example: +1. Edit the `build.gradle` file in the OBR directory of your parent project, setting the plug-in values at the top of the file to version `0.37.0`, as shown in the following example: ``` plugins { ... -id 'dev.galasa.obr' version '0.36.0' -id 'dev.galasa.testcatalog' version '0.36.0' +id 'dev.galasa.obr' version '0.37.0' +id 'dev.galasa.testcatalog' version '0.37.0' ... } ``` @@ -51,11 +51,11 @@ tasks.withType(PublishToMavenLocal) { task -> task.dependsOn mergetestcat } ``` -3. In each test project `build.gradle` file, set the `dev.galasa.tests` plug-in to version `0.36.0` to ensure that the build uses the correct plug-in. +3. In each test project `build.gradle` file, set the `dev.galasa.tests` plug-in to version `0.37.0` to ensure that the build uses the correct plug-in. ``` plugins { ... -id 'dev.galasa.tests' version '0.36.0' +id 'dev.galasa.tests' version '0.37.0' ... } ``` diff --git a/src/markdown-pages/highlights.md b/src/markdown-pages/highlights.md index 8f451442..24cd9395 100644 --- a/src/markdown-pages/highlights.md +++ b/src/markdown-pages/highlights.md @@ -18,7 +18,15 @@ 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.36.0 - Release Highlights +## 0.37.0 - Release Highlights + +- Galasa now supports Java 17. + +- You can delete a test run by using the `galasactl runs delete` command. Deleting a test run removes all information about the test run along with any associated artifacts from an ecosystem's RAS. + + +
+0.36.0 - Release Highlights - You can now create Galasa projects and build and compile Galasa test code using Gradle version 8. For more information, see the `Upgrading tests to compile using Gradle version 8` section in the [Upgrading](docs/upgrading) documentation to understand the changes you need to make. @@ -31,6 +39,7 @@ Access the Galasa source code in [GitHub](https://github.com/galasa-dev) and ope - Various defect fixes - Various documentation updates +
diff --git a/src/pages/index.js b/src/pages/index.js index 928902db..9986ea41 100644 --- a/src/pages/index.js +++ b/src/pages/index.js @@ -126,7 +126,7 @@ const IndexPage = () => ( Learn more From 214fad4a740194b8424cfab61538112694b2caa3 Mon Sep 17 00:00:00 2001 From: James Taylor Date: Wed, 18 Sep 2024 11:40:08 +0100 Subject: [PATCH 5/6] Fix bootstrap typo Signed-off-by: James Taylor --- .../docs/manage-ecosystem/runs-get.md | 22 ++++++++--------- .../docs/manage-ecosystem/runs-prepare.md | 24 +++++++++---------- .../docs/manage-ecosystem/runs-submit.md | 8 +++---- 3 files changed, 27 insertions(+), 27 deletions(-) diff --git a/src/markdown-pages/docs/manage-ecosystem/runs-get.md b/src/markdown-pages/docs/manage-ecosystem/runs-get.md index 53ca149e..35aa127e 100644 --- a/src/markdown-pages/docs/manage-ecosystem/runs-get.md +++ b/src/markdown-pages/docs/manage-ecosystem/runs-get.md @@ -59,14 +59,14 @@ The following example command returns test status in a summary format for tests On Mac or Unix: ``` - galasactl runs get --bootstrap http://example.com:30960/boostrap \ + galasactl runs get --bootstrap http://example.com:30960/bootstrap \ --requestor bobsmith --age 2w:1w ``` On Windows (Powershell): ``` - galasactl runs get --bootstrap http://example.com:30960/boostrap ` + galasactl runs get --bootstrap http://example.com:30960/bootstrap ` --requestor bobsmith --age 2w:1w ``` @@ -80,7 +80,7 @@ On Windows (Powershell): Results are returned on the terminal in the following example format: ``` -$galasactl runs get --bootstrap http://example.com:30960/boostrap \ +$galasactl runs get --bootstrap http://example.com:30960/bootstrap \ --requestor bobsmith --age 2w:1w --format summary submitted-time(UTC) name status result test-name @@ -103,13 +103,13 @@ The following example command returns test status in a details format: On Mac or Unix: ``` -$galasactl runs get --name U456 --bootstrap http://example.com:30960/boostrap \ +$galasactl runs get --name U456 --bootstrap http://example.com:30960/bootstrap \ --format details ``` On Windows (Powershell): ``` -galasactl runs get --name U456 --bootstrap http://example.com:30960/boostrap ` +galasactl runs get --name U456 --bootstrap http://example.com:30960/bootstrap ` --format details ``` @@ -122,7 +122,7 @@ where: Results are returned on the terminal in the following example format: ``` -$galasactl runs get --name U456 --format details --bootstrap http://example.com:30960/boostrap +$galasactl runs get --name U456 --format details --bootstrap http://example.com:30960/bootstrap name : U456 status : finished result : Passed @@ -150,13 +150,13 @@ The following example command returns test status in a raw format: On Mac or Unix: ``` -galasactl runs get --name U456 --bootstrap http://example.com:30960/boostrap \ +galasactl runs get --name U456 --bootstrap http://example.com:30960/bootstrap \ --format raw ``` On Windows (Powershell): ``` -galasactl runs get --name U456 --bootstrap http://example.com:30960/boostrap ` +galasactl runs get --name U456 --bootstrap http://example.com:30960/bootstrap ` --format raw ``` @@ -181,19 +181,19 @@ On Mac or Unix: ``` galasactl runs get --age 1d --result failed,envfail \ ---bootstrap http://example.com:30960/boostrap +--bootstrap http://example.com:30960/bootstrap ``` On Windows (Powershell): ``` galasactl runs get --age 1d --result failed,envfail ` ---bootstrap http://example.com:30960/boostrap +--bootstrap http://example.com:30960/bootstrap ``` Results are returned on the terminal in the following example format: ``` -galasactl runs get --age 1d --result failed,envfail --bootstrap http://example.com:30960/boostrap +galasactl runs get --age 1d --result failed,envfail --bootstrap http://example.com:30960/bootstrap submitted-time(UTC) name status result test-name 2023-05-05 10:55:29 U456 ending Failed MyTestName1 diff --git a/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md b/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md index 2cf7a4ed..ce999ea5 100644 --- a/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md +++ b/src/markdown-pages/docs/manage-ecosystem/runs-prepare.md @@ -20,7 +20,7 @@ On Mac or Unix: ``` galasactl runs prepare \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --portfolio my_portfolio.yaml \ --stream BestSoFar \ --package dev.galasa.simbank.tests @@ -30,7 +30,7 @@ On Windows (Powershell): ``` galasactl runs prepare ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --portfolio my_portfolio.yaml ` --stream BestSoFar ` --package dev.galasa.simbank.tests @@ -46,7 +46,7 @@ On Mac or Unix: ``` galasactl runs prepare \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --portfolio my_portfolio.yaml \ --stream BestSoFar \ --package dev.galasa.simbank.tests,dev.galasa.example.banking @@ -56,7 +56,7 @@ On Windows (Powershell): ``` galasactl runs prepare ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --portfolio my_portfolio.yaml ` --stream BestSoFar ` --package dev.galasa.simbank.tests,dev.galasa.example.banking @@ -72,7 +72,7 @@ On Mac or Unix: ``` galasactl runs prepare \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --portfolio my_portfolio.yaml \ --class dev.galasa.simbank.tests/SimBankIVT \ --class dev.galasa.simbank.tests/BasicAccountCreditTest @@ -82,7 +82,7 @@ On Windows (Powershell): ``` galasactl runs prepare ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --portfolio my_portfolio.yaml ` --class dev.galasa.simbank.tests/SimBankIVT ` --class dev.galasa.simbank.tests/BasicAccountCreditTest @@ -101,7 +101,7 @@ On Mac or Unix: ``` galasactl runs prepare \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --portfolio my_portfolio.yaml \ --stream BestSoFar \ --package dev.galasa.simbank.tests \ @@ -113,7 +113,7 @@ On Windows (Powershell): ``` galasactl runs prepare ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --portfolio my_portfolio.yaml ` --stream BestSoFar ` --package dev.galasa.simbank.tests ` @@ -134,14 +134,14 @@ On Mac or Unix: ``` galasactl runs prepare \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --portfolio my_portfolio.yaml \ --stream BestSoFar \ --package dev.galasa.simbank.tests \ --override zos.default.lpar=MYLPAR \ --override zos.default.cluster=MYPLEX \ galasactl runs prepare \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --portfolio my_portfolio.yaml \ --append \ --stream BestSoFar \ @@ -154,14 +154,14 @@ On Windows (Powershell): ``` galasactl runs prepare ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --portfolio my_portfolio.yaml ` --stream BestSoFar ` --package dev.galasa.simbank.tests ` --override zos.default.lpar=MYLPAR ` --override zos.default.cluster=MYPLEX ` galasactl runs prepare ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --portfolio my_portfolio.yaml ` --append ` --stream BestSoFar ` diff --git a/src/markdown-pages/docs/manage-ecosystem/runs-submit.md b/src/markdown-pages/docs/manage-ecosystem/runs-submit.md index c5f89c73..6c1fb177 100644 --- a/src/markdown-pages/docs/manage-ecosystem/runs-submit.md +++ b/src/markdown-pages/docs/manage-ecosystem/runs-submit.md @@ -19,7 +19,7 @@ On Mac or Unix: ``` galasactl runs submit \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --portfolio my_portfolio.yaml \ --poll 5 \ --progress 1 \ @@ -31,7 +31,7 @@ On Windows (Powershell): ``` galasactl runs submit ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --portfolio my_portfolio.yaml ` --poll 5 ` --progress 1 ` @@ -58,7 +58,7 @@ On Mac or Unix: ``` galasactl runs submit \ - --bootstrap http://example.com:30960/boostrap \ + --bootstrap http://example.com:30960/bootstrap \ --class dev.galasa.simbank.tests/SimBankIVT \ --class dev.galasa.simbank.tests/BasicAccountCreditTest \ --stream BestSoFar \ @@ -69,7 +69,7 @@ On Windows (Powershell): ``` galasactl runs submit ` - --bootstrap http://example.com:30960/boostrap ` + --bootstrap http://example.com:30960/bootstrap ` --class dev.galasa.simbank.tests/SimBankIVT ` --class dev.galasa.simbank.tests/BasicAccountCreditTest ` --stream BestSoFar ` From 0060a8268fd25015a0929d20bed33b02e3b197c6 Mon Sep 17 00:00:00 2001 From: James Taylor Date: Thu, 19 Sep 2024 15:51:44 +0100 Subject: [PATCH 6/6] Revert Gradle plugin versions to 0.36.0 The Gradle plugin does not always get released with a new Galasa version so there is no 0.37.0 version See: - galasa-dev/projectmanagement#1991 - galasa-dev/projectmanagement#1999 Signed-off-by: James Taylor --- src/markdown-pages/docs/upgrading.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/markdown-pages/docs/upgrading.md b/src/markdown-pages/docs/upgrading.md index 78de496d..925e9605 100644 --- a/src/markdown-pages/docs/upgrading.md +++ b/src/markdown-pages/docs/upgrading.md @@ -34,12 +34,12 @@ Galasa releases 0.35.0 and earlier support the use of Gradle versions 6.8.x, 6.9 To use Gradle version 8.0 or later to create Galasa projects and build and compile Galasa test code, complete the following steps: -1. Edit the `build.gradle` file in the OBR directory of your parent project, setting the plug-in values at the top of the file to version `0.37.0`, as shown in the following example: +1. Edit the `build.gradle` file in the OBR directory of your parent project, setting the plug-in values at the top of the file to version `0.36.0`, as shown in the following example: ``` plugins { ... -id 'dev.galasa.obr' version '0.37.0' -id 'dev.galasa.testcatalog' version '0.37.0' +id 'dev.galasa.obr' version '0.36.0' +id 'dev.galasa.testcatalog' version '0.36.0' ... } ``` @@ -51,11 +51,11 @@ tasks.withType(PublishToMavenLocal) { task -> task.dependsOn mergetestcat } ``` -3. In each test project `build.gradle` file, set the `dev.galasa.tests` plug-in to version `0.37.0` to ensure that the build uses the correct plug-in. +3. In each test project `build.gradle` file, set the `dev.galasa.tests` plug-in to version `0.36.0` to ensure that the build uses the correct plug-in. ``` plugins { ... -id 'dev.galasa.tests' version '0.37.0' +id 'dev.galasa.tests' version '0.36.0' ... } ```