Skip to content

Commit c79ddda

Browse files
updating the release process (#1067)
1 parent ab3efa3 commit c79ddda

File tree

3 files changed

+18
-3
lines changed

3 files changed

+18
-3
lines changed

.gitignore

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,4 @@ release.properties
2727
**/*$py.class
2828
**/*.pyc
2929
**/.DS_Store
30-
system-test/domains
30+
**/.hugo_build.lock

documentation/2.0/content/developer/ReleaseProcess.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This document describes the process that should be followed to create a WebLogic
1111
- A local installation of WebLogic Server 12.2.1.x must be available.
1212
- The person running the release process must have admin privileges on the [WebLogic Deploy Tooling GitHub repo](https://github.com/oracle/weblogic-deploy-tooling) because the release process pushes to the master branch directly.
1313
- The person running the release process needs to create a GitHub Personal Access Token for the repository with (at least) the `repo:status`, `repo_deployment`, `public_repo`, and `security_events` privileges.
14-
- The person running the release needs a server added to their Maven `settings.xml` file, where the GitHub Personal Access Token is stored, as shown below. Note that this token can either be stored in plain text or encrypted using [Maven password encryption](https://maven.apache.org/guides/mini/guide-encryption.html).
14+
- The person running the release process needs a server added to their Maven `settings.xml` file, where the GitHub Personal Access Token is stored, as shown below. Note that this token can either be stored in plain text or encrypted using [Maven password encryption](https://maven.apache.org/guides/mini/guide-encryption.html).
1515

1616
```xml
1717
<servers>
@@ -22,6 +22,21 @@ This document describes the process that should be followed to create a WebLogic
2222
</servers>
2323
```
2424

25+
- If the machine from which the release process is being run requires a proxy server to access the Internet, the person running the release process needs an active proxy configured in their Maven `settings.xml` file.
26+
27+
```xml
28+
<proxies>
29+
<proxy>
30+
<active>true</active>
31+
<id>my-proxy</id>
32+
<protocol>http</protocol>
33+
<host>proxy server DNS name</host>
34+
<port>proxy server port</port>
35+
<nonProxyHosts>list of DNS names/patterns separated by |</nonProxyHosts>
36+
</proxy>
37+
</proxies>
38+
```
39+
2540
### Software release process
2641
The best practice is to write the release notes that will be published to GitHub prior to starting the steps below.
2742

github-release.xml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@
4040
<plugin>
4141
<groupId>io.rhpatrick.mojo</groupId>
4242
<artifactId>github-maven-plugin</artifactId>
43-
<version>0.6</version>
43+
<version>0.7</version>
4444
</plugin>
4545
</plugins>
4646
</pluginManagement>

0 commit comments

Comments
 (0)