...
| Div |
|---|
|
On this page| Table of Contents |
|---|
| maxLevel | 2 |
|---|
| exclude | On this page |
|---|
| type | flat |
|---|
| separator | pipe |
|---|
|
|
Summary
The addTask action can be used to add arbitrary tasks to a job. However, you must know the parameter fields that each task uses and needs. Normally, the task provider doesn't document this. However, they can be discovered. We have documented some examples already - see Examples for AddTask action. If the task you want is not already documented, then you need to discover the fields needed. There are 2 ways to discover these fields.
...
| Table plus |
|---|
|
| Step | Discussion |
|---|
| In Chrome, to to View → Developer → Developer Tools → Network tab | Or similar tool that captures interactions between your browser and the server. | | Go to the UI to add a task manually |
| | Either add or update a task that you want to automate |
| | Save the task | Try to fill in or select most fields you are interested in so they will show up as being set. | | Look for a POST and a line under that contains fields and values looking like your task input | Look for field names that match fields on the screen. There are lots of other fields that should be ignored. Example: selectedRepository_0=defaultRepository&cleanCheckout=true | | Add the fields to the addTask action using the various field parameters | Example: --field "myfield=myvalue" or similarly with field1, value1, etc ... |
|
...