This may be a very simple fix but I can't seem to find how to set the time zone after a solid amount of googling. This is what we get in email letting us know if the build failed or was successful:
Date of build:
2011-05-24T00:59:44
Time to build:
17 minutes 26 seconds
Last changed:
2011-05-24T00:55:47
This build actually occurred at 6:20 pm. Any tips, help, or advice is greatly appreciated!
are you using .net cruisecontrol or the java version? We are using the java version and we also had the same problem.
Are you using the exec plugin to execute your builds? If yes then this is the problem. I wrote a specific plugin for our build environment and the time bug was gone. Now time is accurately displayed.
Related
I am new to TeamCity. I am facing this issue. I have several tests running as part of a system test. Some of the tests after completing the run, shows result of an earlier day. Please see the image in the link below:
As you can see, it shows it was ran 3 days ago with a build number 164. But if I go to the log of that test, I can see the correct info
If I run the same test again, it shows the build is outdated
But even after completing this run, it shows the same result as in the first image.
Can someone please let me know what I have to do to fix this?
Maybe you are generating history builds, you can check this article in the official Team City documentation.
History builds
Might be a very basic question, but I can't seem to find any straightforward documentation on how to do it.
I have a very basic UI test that runs every couple hours, and every once in a blue moon the build is unstable because the test fails for one reason or another(finicky selenium stale elements, other anomalies). I would like it so that that the job retries the build again if it is unstable, and if it is still unstable after the second try, then send out the alert (currently using Slack notifications in the post build actions section).
Is there a way to do this? Thanks in advance!
The naginator jenkins plugin allows you to rerun a build for unstable builds as well as failures. You will have to install the plugin in jenkins.
https://wiki.jenkins.io/display/JENKINS/Naginator+Plugin
We have a project using TeamCity which Triggers a build when changes are detected to the VCS with a 60 seconds quiet period.
I want to configure this trigger in such a way that the VCS trigger will not build if the last successful build was within 1 hours time. However, if there is no build detected in the past 1 hour and a change is detected in the VCS then the build should trigger instantly.
Is there a way I can achieve this task in TeamCity?
Thanks,
Vishal
As far as I understand you want to trigger not more than one build per hour. Currently it is not possible to configure in TeamCity. Here is the related request: https://youtrack.jetbrains.com/issue/TW-26302. Please vote for it.
We are using TeamCity 6.0.2 and have a build configuration that runs SoapUI tests. The tests themselves run in approx. 45 seconds when running in command line.
To see the results of the test, we use Ant JUNit report watcher with this Report paths value:
TestSoapUI\SoapUI-testresults\TEST-*.xml
And then the tests are taking up to 15 minutes, with a CPU at 100%.
What can we do to reduce this time? Other report path? Separate the test step from the report step?
(We also filed an issue to JetBrains, if you're interested:
http://youtrack.jetbrains.net/issue/TW-16404)
The issue was solved by the JetBrains team:
http://youtrack.jetbrains.net/issue/TW-16404
Upgrade to TeamCity 6.0.3 if you have the same problem.
We configured TeamCity to do nightly builds based on a time trigger at 8pm on a standalone VCS root.
The root is configured to pull the tip. It is also set to do a clean checkout every time.
Has anyone else encountered an issue where not all modified files up to the point in time that the configuration is triggered on will be included. So for example we had a nightly build at 8pm on 8/13/2009, a checkin at 5pm, one at 6pm, but when the build triggered at 8pm on 8/14/2009 some of the changes are included and some are not.
I might be missing something really obvious here, but the result is a "successful" build that does not include all the changes!
Any help greatly appreciated.
I'd recommend you to submit an issue at the bug tracker. Enable debug logging and attach the VCS logs for the problematic checkout to the submitted issue. Refer to the Reporting Issues document for the details.
Otherwise, it's hard to say anything without the version information and the logs. Such issues can be solved much faster via JetBrains tracker/support than here.