I'm trying to build a Bot for MS Teams using TeamsFX extension for Visual Studio. I've started from the demo and so far (not without excruciating pain) managed to get my functionality implemented.
Now I want to deploy my Bot to AWS (not Azure) so I want to build the Bot Package with its manifest but when I choose "Build Teams Package" I get the following error:
[2021-08-18T17:59:50.918Z] [Info] - [core] start task:executeUserTask, inputs:{"projectPath":"/Users/teamsapp","platform":"vsc","vscodeEnv":"local","function-dotnet-checker-enabled":{}}
[2021-08-18T17:59:50.920Z] [Debug] - [core] success to aquire lock on: /Users/teamsapp/.fx
[2021-08-18T17:59:50.986Z] [Debug] - [core] success to get questions for executeUserTask
[2021-08-18T17:59:50.987Z] [Error] - [Teams Toolkit] Teams Package build failed!
[2021-08-18T17:59:51.043Z] [Debug] - [core] persist project setting file: /Users/teamsapp/.fx/settings.json
[2021-08-18T17:59:51.044Z] [Debug] - [core] lock released on /Users/teamsapp/.fx
[2021-08-18T17:59:51.044Z] [Info] - [core] finish task:executeUserTask
[2021-08-18T17:59:51.044Z] [Error] - code:AppStudioPlugin.TeamsPackageBuildError, message: Teams package build failed. You must run 'Provision in the Cloud' first to fill out certain fields in manifest.
How can I build the teams app package?
We tried it using TeamsFX and it worked fine for us. Could you please check if all the fields in manifest are Updated? I hope you are following all the required points as mentioned in Create a Microsoft Teams app package.
Related
I’m trying to integrate SonarQube with Azure Devops. I have done the configuration in the SonarQube administrator ( Administration > Configuration > General Settings > ALM Integrations , select the Azure DevOps tab, and click the Create configuration button) and setup the service connection in Azure Devops. Also configured the SonarScanner properties file.
sonar.projectkey= Project
sonar.projectName= Project name is given
sonar.login = token from SonarQube
Verified the Sonar-scanner using cmd command “sonar-scanner -h”. The sonar-scanner.bat file also has successfully executed.
In Azure devops Build pipeline, have configured the branch - Prepare Analysis Configuration, Run Code Analysis and Publish Quality Gate Result. When we run the pipe it fails with the below error.
ERROR: Not authorized. Please check the properties sonar.login and sonar.password.
ERROR: Error during SonarScanner execution
ERROR: Not authorized. Please check the properties sonar.login and sonar.password.
INFO: ------------------------------------------------------------------------
##[error]ERROR:
ERROR: Re-run SonarScanner using the -X switch to enable full debug logging.
ERROR:
Below are the last lines of the log
“GET /batch/file?name=sonar-scanner-engine-shaded-9.0.1.46107-all.jar HTTP/1.1” 200 - “-” “ScannerCLI/4.6.1.2450” “AXtcvnCkoRmL3dzQAADB”
“GET /api/settings/values.protobuf HTTP/1.1” 401 - “-” “ScannerCLI/4.6.1.2450” “AXtcvnCkoRmL3dzQAADC”
Kindly help me with the above error. Thanks in Advance.
Finally, I made it working.
It turned out that you don't need to put the sonar.login = token into the sonar-project.properties.
What you need to do is:
to generate the token on the Sonar side;
place it to the service connection properties on Azure DevOps: in your Azure DevOps project, go to Settings > Service Connections and pick the service connection you use to connect to Sonar (if you don't have any, probably you should create one. It should be of type SonarQube). So in the properties of a service onnection of this type, there is a placeholder for a token, you won't miss it.
finally, if your service connection is named, say, SonarConnection, and you Sonar project key is My-Project, then your Azure pipeline will be looking like:
trigger:
- master
- staging
- dev
pool:
vmImage: ubuntu-latest
steps:
- task: SonarQubePrepare#5
inputs:
SonarQube: 'SonarConnection'
scannerMode: 'CLI'
configMode: 'file'
projectName: 'My Project'
projectKey: 'My-Project'
- task: SonarQubeAnalyze#5
- task: SonarQubePublish#5
inputs:
pollingTimeoutSec: '300'
(I also use TLS connection to my SonarQube server with Let'sEncrypt certificates.)
I am getting the following error on mvn azure-webapp:deploy
[ERROR] Failed to execute goal com.microsoft.azure:azure-webapp-maven-plugin:1.9.1:deploy (default-cli) on project mprsreporting: Status code 403 -> [Help 1]
I am following the instructions here...
This was an issue with multiple subscriptions and the maven plug in attempting to deploy on a wrong subscription. Fixed it by changing the default subscription
Below is Azure error log from the Azure release pipeline.
2020-07-24T05:17:13.7712974Z ##[section]Starting: Deploy Azure App Service
2020-07-24T05:17:14.0464143Z ==============================================================================
2020-07-24T05:17:14.0465719Z Task : Azure App Service deploy
2020-07-24T05:17:14.0469391Z Description : Deploy to Azure App Service a web, mobile, or API app using Docker, Java, .NET, .NET Core, Node.js, PHP, Python, or Ruby
2020-07-24T05:17:14.0469849Z Version : 3.163.5
2020-07-24T05:17:14.0470410Z Author : Microsoft Corporation
2020-07-24T05:17:14.0470921Z Help : https://aka.ms/azureappservicetroubleshooting
2020-07-24T05:17:14.0471274Z =============================================================================
2020-07-24T05:17:16.0650643Z Got connection details for Azure App Service:'XXXXX'
2020-07-24T05:17:17.6576087Z (node:764) Warning: Use Cipheriv for counter mode of aes-256-ctr
**2020-07-24T05:17:17.6627737Z ##[error]Error: No package found with specified pattern: D:\a\r1\a\Drop<br/>Check if the package mentioned in the task is published as an artifact in the build or a previous stage and downloaded in the current job.**
2020-07-24T05:17:22.9168975Z Successfully added release annotation to the Application Insight : XXXXX
2020-07-24T05:17:24.8686063Z Successfully updated deployment History at https://XXXXX.scm.azurewebsites.net/api/deployments/231595567842919
2020-07-24T05:17:24.8933576Z ##[section]Finishing: Deploy Azure App Service
P.S. I have checked build pipeline, I can download build Artificats, but it displays below warning.
[warning]Directory 'D:\a\1\a' is empty. Nothing will be added to build artifact 'drop'.
Assuming you meant you have solved the build artifact empty issue, but the release pipeline still had issue in Azure App Service deploy task.
As the error mentioned, there is "No package found with specified pattern: D:\a\r1\a\Drop", you need to check how you define the package, try format $(System.DefaultWorkingDirectory)/**/*.zip instead of $(System.DefaultWorkingDirectory)\Drop.
As task "Publish Build Artifact" publish artifact from $(build.artifactstagingdirectory), so we need add a task "Copy files" to copy your files ** from $(system.defaultworkingdirectory) to $(build.artifactstagingdirectory) **. which copied my build to stagingdirectory.
I want to generate microservices application with only Back-end code.
I found solution in this.
And I used jhipster --skip-client but It's still have some Font-end files like node-modules,packege.json...
After that, I found another solution instead of jhipster --skip-client . I use jhipster:server and it works . I didn't have any Font-End file,but I could run by use mvnw . This is my error
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.184 s
[INFO] Finished at: 2019-05-08T16:20:28+07:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:properties-maven-plugin:1.0.0:read-project-properties (default) on project test-mic: Properties could not be loaded from File: C:\Users\DatNT80\Desktop\TestMic\sonar-project.properties -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
How can I resolve my problem
jhipster --skip-client is the correct way to generate a server only application. By invoking jhipster server, you are using an internal "jhipster sub-generator" which will likely result in an incomplete or even non working application.
The package.json and node_modules are not frontend files. They are required to locally install jhipster as a JavaScript dependency of your project (jhipster is coded in JS). This way when invoking jhipster in your app directory, it is garanteed to use the same jhipster version as the one your app was generated with.
I followed this excellent tutorial on Getting Started with Node.js but get the following error when running the last command gcloud preview app deploy .:
/Users/me/Google Drive/appengine-nodejs-quickstart> gcloud preview app deploy .
Updating module [default] from file [/Users/me/Google Drive/appengine-nodejs-quickstart/app.yaml]
08:51 PM Host: appengine.google.com
Error 400: --- begin server output ---
Failed Project Preparation (app_id='s~foo-bar-123'). Failed to enable APIs.
--- end server output ---
ERROR: (gcloud.preview.app.deploy) Command failed with error code [1]
I was able to run the app locally just fine using gcloud preview app run .. I checked and I do have Billing enabled for the project and some default APIs are enabled. Here's the results from docker version if it helps:
Client version: 1.3.2
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): 39fa2fa
OS/Arch (client): darwin/amd64
Any ideas what could be the issue?
I'm an engineer on the managed vms team and have looked into the issue. I believe the problem is we have changed our terms of service and you need to accept the before you can continue to use the product. Obviously, our messaging in this case is bad and needs to be fixed.
For now you need to go to cloud.google.com/console, select your project, and accept the new terms of service.