Reputation: 10236
I'll add a task for tokenization (https://github.com/openalm/Extension-UtilitiesPack) to my build definition and the build definition will execute and do everything exactly as expected. However, if I were to reopen the build-definition, the new task will be missing (even though it's actively being used in builds).
If I were to add a task of a different type it will show up as expected on future visits. I've not used this VSIX/task very much, but I've used (read: added-executed-viewed) with this task at least once in the recent past and this did not happen. So, this doesn't necessarily happen every time. It looks like the same general issue affects more than one task installed from this same VSIX. Any suggestions and where to go from here for testing/debugging this?
Upvotes: 1
Views: 311
Reputation: 30488
I encountered this when the extension itself was coded to be visible only to 'Release'.
You can see this in the task.json under the 'visibility' key:
{
"id": "3311DF41-0CBE-467C-A1EB-6007DFACDCEC",
"name": "MyExt",
"friendlyName": "My Extension",
"description": "This is my extension",
"helpMarkDown": "[Link]",
"category": "Utility",
"visibility": [
"Build",
],
....
TFS will allow these to be added in, and in some instances will display them. A bit of a bug there methinks.
Fortunately, I had control of the task JSON, so created a new version with the following:
....
"visibility": [
"Build",
"Release"
],
....
Upvotes: 0
Reputation: 13
I am having the same problem with the On Premises Tasks (https://marketplace.visualstudio.com/items?itemName=technossusllc.on-premises-build-tasks), such as the Database Deployment task.
I can add the task (it shows up), it will perform, but about 75% of the time, when I edit my build definition, the Undo button lights up immediately (before I do anything), and I can see that my task (Database deploy) was removed. If I hit Undo, it comes back. What process is removing tasks?
Upvotes: 0
Reputation: 51073
Please take a look about custom task with below info:
Currently only ‘Agent Pool Administrators’ are able to add/update or remove tasks.
Tasks are server-wide, this means that you will upload to the server, not to a specific collection or project.
According to your description, first thing that pops to mind is that the task category is incorrect (non-existing or invisible). Visibility tells you what kind of task it is, possible values are: Build, Release and Preview. Currently only Build-type tasks are shown.
More detail info about custom build task, please refer this link: vsts-tasks
Upvotes: 1