WebJob cannot be added from portal if deployment form source control is configured

We solved it by not disconnecting a pipeline.

We solved it by implementing a seperate WebJob Build/Release Pipeline.

Here are the steps that worked for us:

In Azure Portal

• Create a virtual application in your app service

In DevOps

• In your build pipeline Important Notice: add the following Argument: --output $(build.artifactstagingdirectory) to the build step.

• In your release pipeline

This deploys the WebJob to the correct directory. In our case: $(System.DefaultWorkingDirectory)/_ms-reporting-webjob-dev-CI/drop

Having a look at the Kudo Console in our App Service the file location for our WebJob is:

Kudu Console

The workaround that worked for me was uploading the webjob directly via the Kudu Console.

Open the Kudu Console by selecting "Advanced Tool" --> "Go" in Your App Service on the Azure Portal.

Once on the Kudu portal open a "Debug Console" --> "CMD"

Go to the directory for your webjobs: "d:\home\site\wwwroot\app_data\jobs\continuous\{job name}" (https://github.com/projectkudu/kudu/wiki/WebJobs)

Then drag and drop the .zip file you prepared to upload your webjob (https://github.com/projectkudu/kudu/wiki/Kudu-console)

The job will now be listed on the Azure Portal and be started.

I used the following physical path in the Virtual Application and it solved it for us

site\wwwroot\App_Data\jobs\triggered\jobname