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
* Feature: Added failOnExist parameter for allocateDS, deleteDataset and deleteDatasetsByMask declarative/Freestyle UI methods (checks the presence/absence of a dataset on the system) ([db232f49](https://github.com/zowe/zowe-zdevops-jenkins-plugin/commit/db232f49))
Copy file name to clipboardExpand all lines: README.md
+44-19Lines changed: 44 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Thank you for considering IBA Group for your mainframe needs.
27
27
28
28
## Before use - Plugin configuration
29
29
After successfully installing the plugin, you need to configure it for further work - this will require a minimum of actions.
30
-
1. Move to “Manage Jenkins” -> “Configure System / System” -> scroll to the very bottom of the list of installed plugins and find the panel with the name - <b>“z/OS Connection List”</b>
30
+
1. Move to 'Manage Jenkins' -> 'Configure System / System' -> scroll to the very bottom of the list of installed plugins and find the panel with the name - <b>'z/OS Connection List'</b>
31
31
2. This setting allows you to add all necessary z/OS systems and configure access to them.
32
32
It is necessary to set the connection name (it is also the ID for declarative methods in the code). For the example: ```z/os-connection-name```
33
33
3. The URL address and port of the required mainframe to connect via z/OSMF. Example: ```https://<ip-addres>:<port number>```
*```dsn:"EXAMPLE.DATASET"``` - The name of the dataset to be allocated
77
100
*```dsOrg:"PS"``` - The dataset organization (could be only PO, POE, PS, VS)
78
101
*```primary:"1"``` - The primary allocation size in cylinders or tracks
79
102
*```secondary:"1"``` - The secondary allocation size in cylinders or tracks
80
103
*```recFm:"FB"``` - The record format (could be only F, FB, V, VB, U, VSAM, VA)
104
+
*```failOnExist:"False"``` - If the dataset already exists and the option is enabled, execution will halt. (Boolean parameter, is set to 'False' by default)
81
105
82
106
**Optional parms:**
83
107
*```volser:"YOURVOL"``` - Volume serial number where the dataset will be allocated.
* You cannot delete a VSAM dataset this way. Otherwise, you will get output similar to:
@@ -178,7 +203,7 @@ Pipeline can be used either directly inside the ```Pipeline``` code block in the
178
203
This pipeline example uses all currently available methods and functionality of the Zowe zDevOps plugin.
179
204
180
205
**Steps to Execute the Pipeline:**
181
-
1. Add a zosmf connection in settings (<b>“Manage Jenkins” -> “Configure System / System” -> z/OS Connection List</b>). Enter a connection name, zosmf url, username and password.
206
+
1. Add a zosmf connection in settings (<b>'Manage Jenkins' -> 'Configure System / System' -> z/OS Connection List</b>). Enter a connection name, zosmf url, username and password.
182
207
2. Create a new Jenkins item -> ```Pipeline``` and open its configuration.
183
208
3. In the ```Pipeline``` section, paste the code from the example below and replace all the necessary variables with your data
184
209
4. Done, enjoy the minimal ready-made pipeline template!
Assuming a <b>.hpi</b> file has been downloaded, a logged-in Jenkins administrator may upload the file from within the web UI:
326
-
1. Navigate to the <b>Manage Jenkins > Manage Plugins</b> page in the web UI.
351
+
1. Navigate to the <b>Manage Jenkins > Plugins</b> page in the web UI.
327
352
2. Click on the <b>Advanced</b> tab.
328
353
3. Choose the <b>.hpi</b> file from your system or enter a URL to the archive file under the <b>Deploy Plugin</b> section.
329
354
4. <b>Deploy</b> the plugin file.
@@ -334,8 +359,8 @@ Assuming a <b>.hpi</b> file has been downloaded, a logged-in Jenkins administrat
334
359
3. To generate the ```target``` dir with generated-sources - you have to run the Maven command: ```mvn localizer:generate```
335
360
4. Next, you need to generate an installation file: .hpi or .jpi file (both are installation files for the Jenkins plugin). This can be done by executing Maven command ```mvn install``` or by ```mvn hpi:hpi```.
336
361
5. After building the .hpi/.jpi file, it should appear in a <b><Plugin-project-name>/build/libs/<hpi_file_name>.hpi</b> directory
337
-
6. Next you need to login into the Jenkins, move to the <b>“Manage Jenkins” -> “Manage Plugins” -> “Advanced (tab)” -> “Deploy Plugin”</b> (You can select a plugin file from your local system or provide a URL to install a plugin from outside the central plugin repository) <b>-> Specify the path to the generated .hpi/.jpi file</b> (or by dragging the file from Intellij IDEA project to the file upload field in the Jenkins).
338
-
7. Click <b>“Deploy”</b>, reboot Jenkins after installation. The Plugin is ready to go!
362
+
6. Next you need to login into the Jenkins, move to the <b>'Manage Jenkins' -> 'Plugins' -> 'Advanced settings (tab)' -> 'Deploy Plugin'</b> (You can select a plugin file from your local system or provide a URL to install a plugin from outside the central plugin repository) <b>-> Specify the path to the generated .hpi/.jpi file</b> (or by dragging the file from Intellij IDEA project to the file upload field in the Jenkins).
363
+
7. Click <b>'Deploy'</b>, reboot Jenkins after installation. The Plugin is ready to go!
339
364
340
365
## How to run Jenkins plugin in Debug mode in a local Jenkins sandbox
0 commit comments