zeaslity/ProjectOctopus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[ Agent ] [ CMII ] - 完成工具类的代码

Browse Source
This commit is contained in:
zeaslity
2024-01-09 16:42:27 +08:00
parent 36b8e36392
commit 22faf15665
18 changed files with 1307 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
setting-aliyun.xml
View File

@@ -193,7 +193,7 @@ under the License.
| or the command line, profiles have to have an ID that is unique.
|
| An encouraged best practice for profile identification is to use a consistent naming convention
| for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
| for profiles, such as 'env-devFilght', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
| This will make it more intuitive to understand what the set of introduced profiles is attempting
| to accomplish, particularly when you only have a list of profile id's for debug.
|
@@ -218,7 +218,7 @@ under the License.
-->
<!--
| Here is another profile, activated by the system property 'target-env' with a value of 'dev',
| Here is another profile, activated by the system property 'target-env' with a value of 'devFilght',
| which provides a specific path to the Tomcat instance. To use this, your plugin configuration
| might hypothetically look like:
|
@@ -237,12 +237,12 @@ under the License.
| anything, you could just leave off the <value/> inside the activation-property.
|
<profile>
<id>env-dev</id>
<id>env-devFilght</id>
<activation>
<property>
<name>target-env</name>
<value>dev</value>
<value>devFilght</value>
</property>
</activation>