During the execution of tests within the pipeline, the following error occurs:
The problem appeared after I launched a local server with port 9999 in order to build an allure report. The server was later stopped, but the problem persisted. How to fix the error?
Related
Running bash script in Azure pipeline. I am trying to rerun the npm publish step x-times if there is any network error is detected.
Is there any way to detect a network error specifically and rerun the whole task again?
I've found this document (https://learn.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-195-update#automatic-retries-for-a-task) but I believe this reruns the process regardless of the error type.
I pulled the latest docker image for sonarqube and the image runs fine. The sonarqube server is listening at localhost:9000. When I run the dotnet sonarscanner begin to analyze asp.net Core 3.1 project, after some time, I get timeout error. Below is the log from the command
Using the .NET Core version of the Scanner for MSBuild
Pre-processing started.
Preparing working directories...
18:47:29.653 Updating build integration targets...
18:49:09.803 Failed to request and parse 'http://localhost:9000/api/server/version': The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
18:49:09.811 The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
18:49:09.814 Pre-processing failed. Exit code: 1
The API request works fine through Postman. What could cause the failure?
After I try to change port 9000 to 8000 and retry and it worked!
ports:
- "8000:9000"
iam running my karate code from Jenkins. where ia, getting below error.
ERROR com.intuit.karate - evaluation of 'karate-config.js' failed: javascript function call failed: ReferenceError: "karate" is not defined .
karate config file keeps on running.
iam using mvn test command to run the job.. even I have tried in Jenkins machine and mvn command works. only in through Jenkins iam getting issue.
Try to upgrade java version in Jenkins server.
I'm currently using Docker for Windows with Bamboo. I'm running into the problem, that when a Docker task fails, the error log only shows that exact message, that the task failed. But it doesn't show the error message from within Docker, like compilation errors, access denied or out of memory. Is there any way to get to these error messages?
You can setup a task in the "Final tasks" area of your job. This job will execute regardless of whether the tasks in the job failed or not.
Depending on how you are running Docker in Bamboo you can make this a Docker task or a script task and use the Docker logs command to output the logs from the container. This should tell you why the container failed to run (e.g., build, run-time error, initialization failure).
Docker Logs CLI
Using teamcity 5.1 (build 13360)
Usually everything works as expected
Occasionally it gets into a state where the server runs a build and it thinks the agent is running it, but the agent doesn't actually run the build
I see no sign of the build being run by the agent in its logs
So the build just runs forever on the server
I have restarted agents and the server
So it appears it recovers after a few hours
I just left a build running and it completed after a while
Don't know if restarting server / agents helped or not