Skip to content

Updating readme with code generation instructions#4079

Merged
hovsepm merged 8 commits intoAzure:masterfrom
vivek-microsoft:master
Oct 10, 2018
Merged

Updating readme with code generation instructions#4079
hovsepm merged 8 commits intoAzure:masterfrom
vivek-microsoft:master

Conversation

@vivek-microsoft
Copy link
Copy Markdown
Contributor

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Oct 5, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Oct 5, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Oct 5, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Oct 5, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#3534

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Oct 5, 2018

Automation for azure-sdk-for-go

Encountered a Subprocess error: (azure-sdk-for-go)

Command: ['/usr/local/bin/autorest', '/tmp/tmpjodwdr0s/rest/specification/workloadmonitor/resource-manager/readme.md', '--go', '--go-sdk-folder=/tmp/tmpjodwdr0s/src/github.com/Azure/azure-sdk-for-go', '--multiapi', '--use=@microsoft.azure/autorest.go@~2.1.114', '--use-onever', '--verbose']
Finished with return code 1
and output:

AutoRest code generation utility [version: 2.0.4283; node: v8.11.4]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
   Loading AutoRest core      '/root/.autorest/@microsoft.azure_autorest-core@2.0.4283/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4283)
   Loading AutoRest extension '@microsoft.azure/autorest.go' (~2.1.114->2.1.114)
   Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
Processing batch task - {"tag":"package-2018-08-31-preview"} .
Failure during batch task - {"tag":"package-2018-08-31-preview"} -- Error: [Exception] No input files provided.

Use --help to get help information..
[Exception] No input files provided.

Use --help to get help information.

@AutorestCI
Copy link
Copy Markdown

AutorestCI commented Oct 5, 2018

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2500

@azuresdkci
Copy link
Copy Markdown
Contributor

Can one of the admins verify this patch?

@hovsepm
Copy link
Copy Markdown
Contributor

hovsepm commented Oct 5, 2018

@vivek-microsoft please resolve merge conflicts.

@hovsepm
Copy link
Copy Markdown
Contributor

hovsepm commented Oct 9, 2018

@vivek-microsoft I think the error is the name of the swagger for Go and Java package-2018-08-31-preview where your readme contains default tag for only tag: package-2018-08-preview. try to remove date 31 from Java and Go swagger reference.

@hovsepm hovsepm merged commit 714d35e into Azure:master Oct 10, 2018
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.

5 participants