jambas on Tue, 24 May 2016 04:28:45
What is the recommended way to use a Batch Apps with CI/CD? There don't seem to be any automated facilities for uploading application packages, and when I try to upload my new packaged app as a zip file over my version 1 of the app, and my nodes download it on reboot/reimage, they don't seem to actually overwrite the old stuff with it. It's like the app is cached somewhere that I don't have access to, that isn't the blob storage record of it in my storage account.
I've gotten the hashes of the files on my Octopus server, Blob storage where it uploads it to, and from the TVM itself after a re-image, and I see the following:
Octopus - 63C358EF1FE7B70B7A7DE9FA70657E0963BC0D1E0D679990F2651459B73A877C
BlobStorage - 63C358EF1FE7B70B7A7DE9FA70657E0963BC0D1E0D679990F2651459B73A877C
TVM - 56A357E029D3EBDEE01CC1E771B9DF74ED42DA1A1036D29631E8E296460E6B8C
The file last modified dates are also as I would expect if the new files are not overwriting the old ones.
Dave Fellows on Tue, 24 May 2016 19:37:41
New/updated Application Package files needs to be "activated" through the Management API (at which point a snapshot of the blob is made). So, you can copy the updated package to storage, but you would need to call the ActivateApplicationPackage[Async] Management API operation. This could be done with the Batch Management Library or soon, the PowerShell commandlets (Application Package support is coming *very* soon).
Hope that answers your question.
jambas on Tue, 24 May 2016 21:15:21
Thanks for the information Dave! will have to give this a shot this week/weekend. Can you guys update the documentation? I feel like I scoured it a good bit but didn't find anything :/
Dave Fellows on Tue, 24 May 2016 21:59:27
Yes, absolutely. We will review the documentation and modify to make this more explicit. Thank you for the feedback.
Principal Group Software Engineering Manager Azure Big Compute