Azure WebJob deployed from Bitbucket is set up as continuous instead of scheduled

Question

When deploying a webjob from Bitbucket (using continuous deployment), the process seems to ignore any settings created for the job, like schedule and name.

The webjob resides in its own solution, without any site.

Is it possible to somehow add a hook or change some variable in the deployment process to deploy the job as scheduled instead of continuous?

Answer 1

It's not so much about Bitbucket, but more generally about git based deployment. Things are not as smooth as they could be, but can be made to work. One way is:

• Create a dummy Web App in VS. It can empty.
• Add your console app to the same solution, and Add it as a WebJob to the WebApp (details here).
• For the scheduling, you may want to look at this post.