Menu
The Azure management interface is abhorrently slow to load up the web jobs list, and the new portal just times out and fails 95% of the time.
We have a lot of WebApps (often deployed per region) in Azure running web jobs. It's extremely cumbersome and slow to have to go through the UI to do all this.
I know that the Kudu API offers start/stop mechanisms for web jobs and you can just drop a file called 'disable.job' in the job folder to stop it, but these all require going through the extremely annoyingly slow UI to download publish credentials ($username, password).
Is there a PowerShell cmdlet I've somehow missed or a public script out there to help do this? Ideally I just want to supply my Azure credentials or import the certificates.
(Honestly, it's rather surprising that Microsoft's key cloud/DevOps product would be almost entirely UI-dependent, and on an extremely slow/useless UI at that.)
353
If you set the web app that hosts your job to run continuously, run on a schedule, or use event-driven triggers, enable the Always on setting on your web app's Azure Configuration page. The Always on setting helps to make sure that these kinds of WebJobs run reliably.
Incorrect: WebJobs can be triggered by both queue messages and blobs. B. Incorrect: WebJobs can be created as standalone executables or scripts.
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.
It's hard to find, but here's a link to the documentation for Start and Stop:
Start: Documentation
Example: Start-AzureWebsiteJob -Name MyWebsite -JobName MyWebJob -JobType Continuous
Stop: Documentation
Example: Stop-AzureWebsiteJob -Name MyWebsite -JobName MyWebJob
78
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
