WebJobs have stopped being built and included in deployment

We have been successfully using Kudu to build and deploy our site for quite some time. We’re using a custom deploy script, which is based on the one generated by Kudu. The only modifications to the script were additions to package up some stuff with gulp.

Today, I needed to reconfigure GitHub-based deployment because our repository was renamed. In both slots (production and CI), the build succeeded with the same source, but the continuous WebJobs — there are six — are not being included in the build or deployed bits. It has been a couple months since a build was triggered. Because I had to reconfigure our deployment, I lost deployment history and can’t roll back.

I checked the Microsoft.Web.WebJobs.Publish to see if there had been any updates and found none.

This is a .NET 4.6 Web API application. We are using webjobs-list.json in the Properties directory of the source to include our jobs. I’ve been using Visual Studio 2015 to develop locally.

Please let me know what other information would be helpful.

Thanks!

[davidsidlinger]

My guess is that the change to packages.config got committed without the update of the .csproj making it in. I do think that future versions of the package should cause a MSBuild failure if the expected import is missing. I know that many other packages do this.

[davidsidlinger]

@vijayrkn You solved it. The .csproj didn’t get updated when we upgraded packages. This was fine until I reconfigured deployment in the App Service, which blew away the repository on the instance and removed the “dead” reference to 1.0.12.

<Import Project="..\packages\Microsoft.Web.WebJobs.Publish.1.0.12\tools\webjobs.targets" Condition="Exists('..\packages\Microsoft.Web.WebJobs.Publish.1.0.12\tools\webjobs.targets')" />

My everlasting gratitude.