task-lib | A Task implementation for JavaScript | Runtime Evironment library

is there a way to debug an azure devops task extension?

Yes, According to the Step 1 in the article "Add a custom pipelines task extension", after installing all the required libraries and dependencies and adding all the required task implementation files, you can compile and run the task with PowerShell or other shells. By default, the task is run with debugging mode. See the example I share below.

is it possible to pass parameter and load them via tl.getInput?

Sure, you can pass the value of tl.getInput as an parameter. See the example I share below.

is there a state of the art or a complete guideline how to develop azure devops task extension?

Currently, the Microsoft Docs about DevOps extensions is the best guide for us to develop DevOps extensions.

Follow your case, I also test on my side, below are the main source code I use:

• task.json

The problem was, that I build not whole dependencies.

The key to the problem, I think it should be a path configuration problem, unable to access your webjob application.

So I suggest you create a virtual application in portal.

For more details, you can refer to this blog. If you need further help, please let me know.

How to publish webjob from azure devops to azure app service using Azure app service deploy task

You can set environmental variables in azure pipeline by defining it in the Variables section. You can add below to your yaml pipeline.

It worked after change in local.properties file from:

I could not get the actual gradle process to create the reports so I found a work around

• Set the gradle task to "build jacocoRootReport"
• Use the "Publish Code Coverage Results" task (set up to use Jacoco)

I got the solution we need to remove the webdeploy 4.0 and downgrade to webdeploy 3.6 and then its working well.

Is this even possible with custom tasks, at this point? If so, what are some options that I can look into?

I am afraid this is impossible to create a custom task to dynamically populate a pickList input without service endpoint.

As we know, service endpoint provides the URL, authentication info to make the calls. Without that, we could not get the HTTP Get call. That the key point of this issue.

Besides, Azure devops currently don't support data source bindings to associate to task input to query a public URL. MS will consider adding this support going forward.

You could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps:

Hope this helps.

The .apply() method on any function gives you two features:

1. It lets you set the this value when the function is called.
2. It lets you pass an arbitrary array of arguments that will be unpacked into actual arguments (not in an array) when the function is called.

In this case, it is likely feature #2 that it is being used for here because path.resolve() accepts an arbitrary number of arguments. If you're not using the latest versions of node.js or coding to a lower level of Javascript support and thus don't have the spread operator, then .apply() would be the natural way to pass an arbitrary number of arguments to a function when the arguments were passed to you in an array.

If you look at the source for the path module and find the code for the resolve() function, you will find that it does not use a this value at all so the path object is used ONLY as a namespace object. Thus, you can send any value of this you want into the resolve function and it will make no difference.

So, probably, the code is using .apply() not so that it can set the value of this, but so that it can pass an arbitrary array of arguments to the function.

But I'm at a loss as to what is the effect of calling via apply rather than just calling path.resolve() directly. Can anyone explain?

If you showed us more of the surrounding code, we could answer with more certainty, but it seems likely that the pathSegments variable is already an array of path values that this code wants to pass to path.resolve(). If that's an arbitrary array, then the two simplest ways to pass that array as separate arguments to path.resolve() are: