-
Notifications
You must be signed in to change notification settings - Fork 936
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
Who owns the NPM package azure-streamanalytics-cicd? #122
Comments
Hi @oising , sorry about this. Our team is investigating and will fix it soon. A member of the team will respond to this thread once it is fixed. |
So is this the right repo for bugs about the tool? You could probably add this to the docs on npm and nuget ;) |
I think @oising meant version 2.2.6, the latest release. |
Oops, yes. |
Hi @oising, thanks for helping us improve the cicd tool! Would you mind move this bug to that repo? we could discuss further there. |
And BTW, could you share with me a sample ASA job you're using, so I could try to repro this issue on my side? |
@pengyuli-ms Sorry, we won't be able to share our job since it relies on data that is private. But it seems that the issue is more fundamental than data. The tool has a runtime error with some kind of assembly reference being missing (Microsoft.Build.dll) |
@oising Sure, and I noticed you're running the CICD command using a VS project, in the same directory of the And actually the ASA VS extension is out of date,You could use ASA VSCode extension to create project in the future, it supports more features. (you could reference this issue discussion: microsoft/vscode-asa#65 (comment) for more detailed information.) |
Same issue here. I see no issue has been created @ https://github.com/microsoft/vscode-asa/issues ? |
Yep @kipusoep, could you help create one in that repo with your issue? |
aka https://www.npmjs.com/package/azure-streamanalytics-cicd
We have an issue where the latest release 2.2.1 has broken our pipeline. Before I fill this out with details, can you direct me to the correct repo if this is not it. If it is the correct one, then reply back and I will continue here.
The text was updated successfully, but these errors were encountered: