-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathconfig.xml
More file actions
186 lines (186 loc) · 9.07 KB
/
Copy pathconfig.xml
File metadata and controls
186 lines (186 loc) · 9.07 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
<?xml version="1.0"?>
<?xml-stylesheet type='text/xsl' href='style.xsl'?>
<config>
<!-- The location that files should be downloaded to -->
<downloadlocation>C:\temp\</downloadlocation>
<product name="core">
<bamboo>
<projectkey>CO</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>True</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\CO-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName>core</databaseName>
<databaseBackup>C:\temp\test-machine-spike\CI_Core.BAK</databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency></dependency>
</dependencies>
</product>
<product name="psi">
<bamboo>
<projectkey>PSI</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>True</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\PSI-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName>psi</databaseName>
<databaseBackup>C:\temp\test-machine-spike\CI_Psi.BAK</databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency>core</dependency>
<dependency>fileactive</dependency>
</dependencies>
</product>
<product name="austraclear">
<bamboo>
<projectkey>AOU</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>True</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\AOU-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName>austraclear</databaseName>
<databaseBackup>C:\temp\test-machine-spike\CI_Austraclear.BAK</databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency>core</dependency>
<dependency>fileactive</dependency>
</dependencies>
</product>
<product name="gcs">
<bamboo>
<projectkey>CSII</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>True</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\CSII-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName>CourierService</databaseName>
<databaseBackup>C:\temp\test-machine-spike\CI_CourierService.BAK</databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency>core</dependency>
<dependency>fileactive</dependency>
</dependencies>
</product>
<product name="transactive-Bcp">
<bamboo>
<projectkey>TBCP</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>False</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\TBCP-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName>TransactiveBcp</databaseName>
<databaseBackup>C:\temp\test-machine-spike\CI_Tbcp.BAK</databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency>core</dependency>
<dependency>fileactive</dependency>
</dependencies>
</product>
<product name="fileactive">
<bamboo>
<projectkey>MFT</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>True</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\MFT-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName>Fileactive</databaseName>
<databaseBackup>C:\temp\test-machine-spike\CI_Fileactive.BAK</databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency>core</dependency>
</dependencies>
</product>
<product name="fileactive_workflow">
<bamboo>
<projectkey>FAW</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>True</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\FAW-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName></databaseName>
<databaseBackup></databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency>core</dependency>
</dependencies>
</product>
<product name="lvss">
<bamboo>
<projectkey>LVSS</projectkey>
<plankey>CI</plankey>
<buildnumber>latest</buildnumber>
</bamboo>
<files>
<!-- File locations can be passed as HTML links, GIT Links or Windows locations -->
<!-- You can set uselocalartifacts to true to override pulling artifacts down from bamboo -->
<uselocalartifacts>True</uselocalartifacts>
<!-- artifacts is the location of the artifacts directory containing core-database, web-service etc. -->
<artifacts>C:\temp\LVSS-CI-latest</artifacts>
<!-- databaseBackup is the location of the BAK file export -->
<databaseName>lvss</databaseName>
<databaseBackup>C:\temp\test-machine-spike\CI_lvss.BAK</databaseBackup>
<!-- moddedBuildTools allows us to pass a diffetect build-tools directory than the one that is pulled down with artifacts. This as because some of the deployment scripts need to modified to allow for local deployment. -->
<moddedBuildTools>C:\temp\test-machine-spike\build-tools</moddedBuildTools>
</files>
<dependencies>
<dependency>core</dependency>
</dependencies>
</product>
</config>