Skip to content

Update Batch cmdlets to use general availability API #663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jul 31, 2015
Merged

Update Batch cmdlets to use general availability API #663

merged 5 commits into from
Jul 31, 2015

Conversation

jasper-schneider
Copy link
Contributor

The Batch service went GA with an updated REST API that involved some reorganization and renaming of service entities.
The Batch cmdlets have been updated to reflect these changes. The tests have been rerecorded, the help xml has been updated, and the changelog has also been updated.
Because of the API changes, I unfortunately had to touch just about every Batch cmdlet and its associated tests, but most of the changes are just renames (Name -> Id, workitem -> job schedule, vm -> compute node).

jasper-schneider added 4 commits July 28, 2015 13:46
Update NuGet package reference
Update generated models
Updated wrapper for PagedEnumerable
Update to handle BatchClient changes
Update Utils
Rename directories and client files
Update cmdlets
@azurecla
Copy link

Hi @jasper-schneider, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!


It looks like you're working at Microsoft (jaschnei). If you're full-time, we DON'T require a contribution license agreement.



If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@stankovski
Copy link
Member

Running post-checkin tests since PR is too large to review: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-on-demand/29/

@stankovski
Copy link
Member

Running MSI build since PR is too large to review: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-msi/351/

@stankovski
Copy link
Member

Test http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-on-demand/29/ failed:

 CSC : error CS1577: Assembly generation failed -- Referenced assembly 'Microsoft.Azure.Batch' does not have a strong name [D:\workspace\powershell-on-demand\src\ResourceManager\Batch\Commands.Batch\Commands.Batch.csproj]

@jasper-schneider
Copy link
Contributor Author

Yup, we had a problem in our signing process for one of our NuGet dependencies, in the process of resolving.

@jasper-schneider
Copy link
Contributor Author

Submitted a fix, I hit restart on the Jenkins build: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-msi/376/

@jasper-schneider
Copy link
Contributor Author

The Jenkins build has passed.

@jasper-schneider
Copy link
Contributor Author

Ah, didn't see that there were 2 Jenkins builds. Restarting the "on demand" build here: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-on-demand/41/

yugangw-msft added a commit that referenced this pull request Jul 31, 2015
Update Batch cmdlets to use general availability API
@yugangw-msft yugangw-msft merged commit 01b2fcb into Azure:dev Jul 31, 2015
@jasper-schneider jasper-schneider deleted the clientV2 branch July 31, 2015 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants