Build and deploy Azure web jobs

[TWith2Sugars]

Deploying webjobs via msdeploy is awkward for my self so I built this bit of code to build a zip of the files in the release folder and and push it via the rest api that Azure Websites have.

This makes use of the zip controller.

It works but is a bit rough in some places, for example it dependent on "/bin/release" for the location of the dlls to zip up.

This is an example of how you'd call it:

// Define webjobs/website
let webJobs = [{Name = "webjob1"; JobType= WebJobType.Continuous; Project ="WebJobProject1"}
                       {Name = "webjob2"; JobType= WebJobType.Triggered; Project ="WebJobProject2"}]
let webSite = {WebSite.Url = Uri("https://yoursite.scm.azurewebsites.net")
                      UserName = "$yoursite"
                      Password = "somepassword"
                      WebJobs = webJobs }

// Targets to build/deploy

Target "PackageWebJobs" (fun _ ->
    PackageWebJobs(fun p -> {p with OutputPath = "bin"}) [webSite]
)
Target "DeployWebJobs" (fun _ ->
    DeployWebJobs(fun p -> {p with OutputPath = "bin"}) [webSite]
)

[TWith2Sugars]

Should call this package rather than build?

[TWith2Sugars]

Other problems could be in the package section it doesn't package folders :\

[TWith2Sugars]

Should I take in a list of web sites or just one and let the users handle multiple? All this would mean is less code as deployWebJobsToWebSite would be the deploy method.

[raymens]

I'd really like it to be able to deploy from any location, as my binaries are not in the bin/release folder (currently).

[TWith2Sugars]

So an option in the params to specify the zip/dll location would be better? Perhaps default it to bin/release?

[raymens]

Yes, the source aswell as the target location of the zipping process. I wouldn't mind any defaults, as long as it's not that hard to change the defaults.

[TWith2Sugars]

Right, made the change to specify the directory to zip.

Doesn't feel right being part of the params type ,might be better with the webjob type so that each job could potentially have a different directory location to zip.

[TWith2Sugars]

Could make each WebJob type specify the directory to zip and the location of the zip file. This would give us the most flexible solution I think.

[TWith2Sugars]

I've made a change so that each webjob is responsible for it's own dll location/package location. This means there is a bit more emphasis on the end user to specify locations but this does give more flexibility.

This is what the code would look like to call it now:

// a function to crete webjobs based on my projects structure
let private createWebJob site name jobType project = 
    let path = jobTypePath jobType
    { Name = name
      JobType = jobType
      Project = project
      DirectoryToPackage = sprintf "src/%s/bin/Release" project
      PackageLocation = sprintf "bin/%s/webjobs/%s/%s.zip" site path project }

let webJobs site = [createWebJob site "webjob1" WebJobType.Continuous "WebJob1"
                    createWebJob site "webjob2" WebJobType.Triggered "WebJob2"]

let site = Uri("https://yoursite.scm.azurewebsites.net")
let webSite = {WebSite.Url = site
               UserName = "$yoursite"
               Password = "password"
               WebJobs = webJobs site.SubDomain }

Target "PackageWebJobs" (fun _ ->
    PackageWebJobs [webSite]
)
Target "DeployWebJobs" (fun _ ->
    DeployWebJobs [webSite]
)

[raymens]

That would make it usable for my (and others) usecase(s), I like it.

[forki]

Is it ready to merge?

[TWith2Sugars]

If every one is happy then yeah

[forki]

cool thanks!

[dsyme]

Could you add documentation for this as well, and submit a link to https://github.com/fsharp/fsfoundation/edit/gh-pages/guides/cloud/index.md?

[TWith2Sugars]

Something along the lines of: http://fsharp.github.io/FAKE/typescript.html ?

[forki]

Yes that would be great