We have an Azure Website setup with a "staging" deployment slot, and we use a continuous Azure WebJob to process long-running background jobs. It appears that when you publish to the Website (and include the WebJob binaries), that the WebJob will restart itself if it was previously stopped.
Our current deployment process looks like the following:
Is there a trick (say a flag file or something) to tell a WebJob NOT to start up after publishing?
There is however an easier way to do this via Application Settings inside the Configuration section of our App Service where the WebJobs are located. WEBJOBS_STOPPED – setting this to 1 will disable all jobs, and will also stop any jobs that are currently running.
Summary. Azure Functions offers more developer productivity than Azure App Service WebJobs does. It also offers more options for programming languages, development environments, Azure service integration, and pricing. For most scenarios, it's the best choice.
To deploy a continuous WebJob in a stopped state simply add a file called disable.job
at the root of your WebJob (binaries), this will tell the framework that the WebJob is currently stopped.
To view this behavior you can simply stop a continuous WebJob and see that this file is generated and placed at the WebJob's directory.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With