You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/howto-update-for-was-fixpack.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Please follow sections below in order to update the solution for next tWAS fixpa
5
5
## Updating the image
6
6
7
7
1. Which file to update for WAS version?
8
-
* For `twas-nd` image, update the following properties in file [`virtualimage.properties`](https://github.com/WASdev/azure.websphere-traditional.image/blob/master/twas-nd/src/main/scripts/virtualimage.properties#L14-L15), e.g.:
8
+
* For `twas-nd` image, update the following properties in file [`virtualimage.properties`](https://github.com/WASdev/azure.websphere-traditional.image/blob/main/twas-nd/src/main/scripts/virtualimage.properties#L14-L15), e.g.:
9
9
10
10
```bash
11
11
WAS_ND_TRADITIONAL=com.ibm.websphere.ND.v90
@@ -14,7 +14,7 @@ Please follow sections below in order to update the solution for next tWAS fixpa
14
14
15
15
Note: only the major version should be specified, the minor version should not be hard-coded as the Installation Manager will intelligently install the latest available minor version.
16
16
17
-
* For `ihs` image, update the following properties in file [`virtualimage.properties`](https://github.com/WASdev/azure.websphere-traditional.image/blob/master/ihs/src/main/scripts/virtualimage.properties#L22-L25), e.g.:
17
+
* For `ihs` image, update the following properties in file [`virtualimage.properties`](https://github.com/WASdev/azure.websphere-traditional.image/blob/main/ihs/src/main/scripts/virtualimage.properties#L22-L25), e.g.:
18
18
19
19
```bash
20
20
IBM_HTTP_SERVER=com.ibm.websphere.IHS.v90
@@ -63,14 +63,14 @@ Please follow sections below in order to update the solution for next tWAS fixpa
63
63
Note: Currently Graham Charters has privilege to update the image in marketplace, contact him for more information.
64
64
65
65
1. Do we need to update the solution every time we do the image update?
66
-
* Yes. That's because image versions of [`twas-nd`](https://github.com/WASdev/azure.websphere-traditional.cluster/blob/master/pom.xml#L51) and [`ihs`](https://github.com/WASdev/azure.websphere-traditional.cluster/blob/master/pom.xml#L57) are explicitely referenced in the tWAS solutoin. Make sure correct image versions are specified in the `pom.xml` of the solution code.
66
+
* Yes. That's because image versions of [`twas-nd`](https://github.com/WASdev/azure.websphere-traditional.cluster/blob/main/pom.xml#L51) and [`ihs`](https://github.com/WASdev/azure.websphere-traditional.cluster/blob/main/pom.xml#L57) are explicitely referenced in the tWAS solution. Make sure correct image versions are specified in the `pom.xml` of the solution code.
67
67
68
68
## Updating and publishing the solution code
69
69
70
70
Note: The steps included in this section are also applied to release new features / bug fixes which have no changes to the images.
71
71
72
72
1. How to update the version of the solution?
73
-
* Increase the [version number](https://github.com/WASdev/azure.websphere-traditional.cluster/blob/master/pom.xml#L23) which is specified in the `pom.xml`
73
+
* Increase the [version number](https://github.com/WASdev/azure.websphere-traditional.cluster/blob/main/pom.xml#L23) which is specified in the `pom.xml`
74
74
* Also update the `twasnd.image.version` and `ihs.image.version` (obtained from publish step)
75
75
76
76
1. How to run CI/CD?
@@ -96,7 +96,7 @@ Note: The steps included in this section are also applied to release new feature
96
96
1. Create a [release](https://github.com/WASdev/azure.websphere-traditional.cluster/releases) for this GA code and tag with the pom.xml version number.
97
97
98
98
1. How to test the solution, what testcases to run?
99
-
1. Wait until the soluton offer is in`Publisher signoff` (aka "preview") stage;
99
+
1. Wait until the solution offer is in`Publisher signoff` (aka "preview") stage;
100
100
1. Run test cases defined in [twas-solution-test-cases.pdf](twas-solution-test-cases.pdf). Note: use "preview link"for each test case.
101
101
102
102
## What needs to be cleaned up from test env and how to clean them up?
Copy file name to clipboardExpand all lines: src/main/resources/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
- Content that required to create an Azure applicatoin offer from [Commerical Marketplace Overview](https://partner.microsoft.com/en-us/dashboard/commercial-marketplace/overview) -> New Offer > Azure Application
4
4
- See [Azure applicatoin offer](https://docs.microsoft.com/en-us/azure/marketplace/cloud-partner-portal/azure-applications/cpp-azure-app-offer) for details
5
-
- When submitting the offer, use content from [this directory](https://github.com/WASdev/azure.websphere-traditional.cluster/tree/master/src/main/resources) (To-Be-Changed), but apply the changes in this file on top
5
+
- When submitting the offer, use content from [this directory](https://github.com/WASdev/azure.websphere-traditional.cluster/tree/main/src/main/resources) (To-Be-Changed), but apply the changes in this file on top
0 commit comments