I'm trying to set up TeamCity (latest version -- 6.0.3) to play nicely with a ClearCase view.
I've found several resources online, some on this site, but mostly outdated.
I am not sure whether configuring TeamCity with ClearCase is possible.
Few questions i have:
Should I be using a Dynamic View or Snapshot view?
Any special configurations needed to be done?
Is there any tutorial on how to set this up?
All my efforts so far have not succeeded, receiving all sorts of errors...
Please help me in setting this up.
BTW: if there is another FREE alternative for TeamCity that will integrate well with ClearCase, it is also a valid option.
The only setup I saw working with ClearCase and TeamCity is by using the TCC (TeamCity ClearCase plugin) developed by my colleague Gilles Philippart:
TCC GitHub repo: as illustrated by this recent commit, it is based on a snapshot view.
I don't have many details on the setup, but it works well with a TeamCity6.x.
Related
I see a big difference in the look & feel between the online dashboard (https://sonarqube.com/projects or https://sonarqube.com/governance?id=MASTER_PROJECT) and the one that we see by default on our local installation of sonar (v5.6.3).
I'm wondering about whether the online look & feel can in someway be easily applied to a local installation. It's just a matter of css/js or behind we have also a completely different HTML structure?
Any information about this will be much appreciated.
I think I've found the answer to my question. The nice-looking online demo is based on an Enterprise Grade deployment of sonar with the governance plugin.
https://www.sonarsource.com/why-us/products/plugins/governance.html
https://www.sonarsource.com/solutions/deployments/enterprise-grade/
Can't you update your install to the latest version? There have been UI changes in both version 6.0 and 6.1
http://www.sonarqube.org/sonarqube-6-0-in-screenshots/
http://www.sonarqube.org/sonarqube-6-1-in-screenshots/
I've just installed the latest SonarQube 5.0.1 locally to try it out. The project I'm working with at the moment is hosted in Bazaar (bzr) source control. I looked at the SonarQube list of SCM plugins here:
http://docs.sonarqube.org/display/SONAR/Plugin+Library
Bazaar is not listed. Are there any workarounds or independent projects that I could use to get the scm history information from Bazaar into SonarQube? At this point I am just trying to get a sense of the value of the information to our project, rather than worry about a scalable production-ready solution.
There is currently (2015-04-09) no SCM plugin for Bazaar. If you wish to contribute one, feel free to take inspiration from e.g the SonarQube SCM integration plugin for Git.
TeamCity appears to store the definitions for builds, projects, templates etc as XML internally.
This is exposed in the "Administration > Audit" view where you can see diffs that people made to individual configurations, at URLs like http://teamcityserver/admin/settingsDiffView.html?id=project:project10&versionBefore=8&versionAfter=9&actionId=3151
I'd like to manage a TeamCity setup partially from outside the web interface - e.g. for example keep the build definitions in version control and perhaps programmatically generate them.
Is there any way I can directly upload definitions in this format (or any similar alternative)? I'm aware that there are various APIs and extension points to TeamCity but haven't managed to find any that gives direct access to anything like this.
I can live with the format changing with TeamCity versions if necessary - it would be a reasonable price to pay for the other benefits.
For TeamCity 9.x and newer
As reported by Ganesh in the comments to this answer, an option was added in 9.x that supports changes and versioning through Source Code Management (SCM) tools. Please see his answer for 9.x and beyond.
For TeamCity 8.x and older
It might not be the "approved" way, but you can edit the project files on disk, and those changes will appear in your build configs. I have successfully edited them outside of the Web UI after they were created.
So, you could probably open that folder up as a restricted network share or set up ssh.
You'll find it at $TeamCityData/config/projects/ and then they are stored in subfolders such as $projectName/buildTypes/$buildFile.xml
An example is:
E:\TeamCityData\config\projects\CSandbox\buildTypes\CSandbox_Project1TrunkBuildUnitTest.xml
TeamCity 9 adds a new "Versioned Settings" feature which keeps these XML files under version control and allows changes to be made via the VCS.
In TeamCity 9.0 this can be git or mercurial, and the upcoming TeamCity 9.1 will add support for Perforce and Subversion.
I've been using it with git for a few months and it works quite nicely in practice.
I sometimes have trouble persuading TeamCity to notice changes coming in from the VCS - particularly when deleting projects - but otherwise it's been really useful for standardising configuration and spinning up new job chains quickly.
Another slight annoyance is that you can't configure the location within the repository that the settings come from - it's always .teamcity in the root - so I've had to use multiple branches or repositories to manage multiple TeamCity servers.
We're currently using CruiseControl.NET as a continuous integration server for a number of ASP.NET web projects, but we're also evaluating TeamCity.
This is working great for our build server.
What we'd like to setup is a customer facing test server. I'm thinking that when we are happy for our latest development version to be released to the client for test, we could label it in SVN.
I'd then like a second build server to build this version ready for the client to see.
The question is this - is there any way to get either CruiseControl.NET or TeamCity to build only the latest labelled version of the code in a repository?
If anyone has any alternative suggestions, that'd also be greatly appreciated!
You could have a designated location or branch in your subversion repository e.g. \release then point the second TeamCity build server at that.
When your are happy with trunk then overwrite the existing location. The second build server will pick this up, build it, and even deploy it to a test server.
I don't think there's a way to do this directly in TeamCity. You can however configure your build trigger to filter on files and/or users. So, if you touch a given file to indicate release status in addition to or rather than labelling, you can use that.
The trigger filter could be, for example (untested):
+:/ReleaseVersion.cs
Is it possible for TeamCity to integrate to JIRA like how Bamboo integrates to JIRA? I couldnt find any documentation on JetBrains website that talks about issue-tracker integration.
FYI: I heard that TeamCity is coming out with their own tracker called Charisma. Is that true?
TeamCity 5 EAP has support for showing issues from Jira on the tabs of your build.
EAP Release Notes
you still don't have the integration in Jira itself which I would prefer
There is this plugin
https://marketplace.atlassian.com/plugins/com.stiltsoft.jira.teamcity
TeamCity does not have extensive integration with JIRA as Bamboo does, and I am not aware of a plugin that provides it. TeamCity does however, offer a generic integration option to external sites which can be used for basic JIRA integration.
From their documentation:
TeamCity allows to map patterns in VCS change comments to arbitrary HTML pieces using regular expression search and replace patterns. One of the most common usages is to map an issue ID mentioning into a hyperlink to the issue page in the issue tracking system.
Read more here: Mapping External Links in Comments
I haven't set this up yet on our local TeamCity, so I can't testify as to how well it works.
Yes, they are comming out with their own issue tracker.
Read more in this blogpost:
first eap for jetbrains issue tracker Charisma
you can try it here Charisma
and here you can see video for some of the features
you can download the EAP version from here
Charisma EAP download
TeamCity does have a free plugin for Atlassian Confluence. Its provides a nice way to show your build status on your wiki.
You can find it in the Atlassian marketplace:
https://marketplace.atlassian.com/plugins/com.stiltsoft.confluence.extra.confluence-teamcity-plugin
TeamCity has 3 build in Issue Tracking Systems:
1.BugZilla
2.JIRA
3.YouTrack
And there's a way to install the custom plugin for other ITS.
I did an integration with FogBugz issue tracking system with TeamCity 9.x.
https://github.com/jozefizso/teamcity-fogbugz