When Teamcity makes successful build, it outputs green "Success" label (or "Tests passed...").
Can I customize this label, for example, output environment variable there?
You can customise the build status message shown for completed builds using the TeamCity service messages. The TeamCity documentation describes in good detail the format for these messages, which just need to be outputted to stdout. Following is an example of the build status message:
##teamcity[buildStatus status='SUCCESS' text='{build.status.text} and some aftertext']
Build Script Interaction with TeamCity documentation
Related
I have a background workflow that ends with a Stop step. This step has an optional Status Message attribute that I populate with some details I need to be logged.
After the workflow has run I can find the workflow Status Reason (="Succeeded") and other details in the corresponding System Job record. I would also expect to find the stored info in the Message field, but it's not there. I've tried static and dynamic Status Messages, but no success with neither.
Does anybody know where that message is stored?
Basically the Message in Details section of System Job is a placeholder for some useful error message/logging tracker to log with the help of ITracingService.Trace by developer or by platform when something breaks/exception captured.
The status reason is not the good place for logging success scenario message, rather for canceled scenario to pop custom message to user & rolling back the transaction.
Not sure why you want to store there, but better use a custom field or even a note (annotation) can help you in better way. Avoid storing successful workflow execution logs anyway.
Check in system jobs:
Also, uncheck this value:
Then, you could try running the workflow sync. I prefer this than waiting for the async service.
I am trying to send a slack failure notification if the Jenkins build is a failure.
However, whenever the notification comes in slack, it is not a clickable URL. It comes as http://${MASTER_NODE}:1234/job/abc/2/
I am not able to make the master node of Jenkins dynamic, as a result, it just prints as MASTER_NODE and not converting to a clickable URL.
Any possible solution for this?
Instead of using this http://${MASTER_NODE}:1234/job/abc/2/,
$BUILD_URL in custom message
click here to see image
The only information I can show in my github repo is the build status
Is there a possible way to show additional information, like test coverage, skipped tests ... ?
Not at the moment. You can add the suggestion here
I have configured my sonar project view to receive a sonar PDF report however i am still not getting the same on email. Below are the steps I performed:
I have created a view where I have included my 6 projects. I gave
execute permission on view not on individual project.
I have set Executive Report option to come daily and provided email
id's to receive the pdf
I have set the Subscribe button which says "You are receiving PDF
reports by email every day."
Please suggest what is missing. Also the report doesn't include much details about the sonar code analysis. Is it possible to include below parameters:
Test Coverage
Unresolved Issues
I am not getting much help from Vendor on same.
I have setup TeamCity with JMeter plugin. Under Build Configuration -> Build Features, I selected 'Performance metrics calculation'. I can see the build log is cumulative with previous execution results. However, when checking for failure conditions in the build log for 404 or 500 status code, it always fails if at least one previous instance has these response codes. Without this, the build always says Pass even if there are couple of requests that fail with error codes.
Under 'Check reference values', is it possible to set reference values to check the metrics against responsecode for errors? The only available options are 'Average', '90% line' and 'Max'. Any insight into how I can add options to select and search for error response codes?
Screenshots attached for reference
Thank you.
TeamCity JMeter Performance Metrics Collection
The plugin is open source so theoretically you should be able to add required metric to check.
As a workaround I can suggest using Response Assertion to check response codes. If you need to test only "200" status code - it will be the matter of only one assertion (same level as HTTP Request samplers).
See How to Use JMeter Assertions in Three Easy Steps article for more details on conditionally failing JMeter requests