Question 104810 in Azure Question posted in
The official documentation to get you started can be found here.

Added a new VSTS extension to marketplace, Able to install that extension but not showing in azure pipeline task

Added a new VSTS extension to vsts marketplace https://marketplace.visualstudio.com/items?itemName=ManishSingh.soapuiazure&ssr=false#overview

I am able to install this extension on organization but not able to see this in task list to add in pipeline.

Got some way to fixed this on internet like uninstall and reinstall – Didn’t worked
Disabled and enable – didn’t worked.

Tags:

2

Answers


  1. 0

    Test to install the same extension and it will show the task: Soap UI on Azure in the task list.

    For example:

    enter image description here

    You can add the task to Agent Job or Deployment Job.

    On the other hand, if you are not able to find the task after installing it, you can try to open a Browser InPrivate Window and use the same steps to search the task in Azure Pipeline.

    Login or Signup to reply.
  2. 0

    The extension uses the deprecated PowerShell v1 execution handler for Azure Pipelines and needs to be upgraded to the Powershell3 execution handler. The v1 handler is from the era of the v1 agent that shipped in 2015 and was replaced by a complete rewrite in the summer of 2016.

    ##[warning]Task ‘SoapUI on Azure’ (2.0.6) is using deprecated task execution handler. The task should use the supported task-lib: https://aka.ms/tasklib

    For me the task fails to show up in the YAML task helper, but it does show up in the classic UI based pipelines and releases.

    You may be able to just make it work when using the Get YAML helper in the classic UI:

    steps:
- task: ManishSingh.soapuiazure.5ad1e1bc-7ee6-49c8-b12f-7b7606c5b0e4.SoapUI on Azure@2
  displayName: 'SoapUI project.xml'

    Then simplify that to:

    steps:
- task: SoapUI on Azure@2
  displayName: 'SoapUI project.xml'

    ^^^^
    Tested this and it works.

    But it looks like this extension could use some love. I already see a few things wrong with it:

    • Using deprecated task handler
    • always downloads SOAPUI from blob storage (useful for Hosted agents, but not for persistent agents)
    • Manifest issues
      • space in Task Name (task.json)
      • guid in Task ID (in vss-extension.json)

    Some of these are likely unfixable, cause the marketplace makes it very hard to change identifiers once the task is published publicly.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search