I've asked this question on Gitter, but answer directed me to the documentation I followed.
I'm administrator of TeamCity 2017.2.2 with agents running on Windows 10 (except one on 7). I installed allure-teamcity plugin version 2.6 and added allure tools in version 2.6 as described in the documentation.
The problem is the tool is propagated to the agent on upgrade, but not the plugin itself. Main server shows me the runner I can use as a build step, but once configured none of agents accept this configuration. I've checked agent directory and logs - the plugin is not there and logs doesn't indicate that there was even attempt to pull.
As a holder of commercial license I asked JetBrains technical support, but they told me I need to ask Allure authors. GitHub sends people to Gitter and here, hence the question after unlucky attempt on Gitter.
What do I need to do to get the plugin correctly pulled and working on agents?
Is allure plugin even compatible with TeamCity 2017.2.2?
The problem is that Allure TeamCity plugin looks for a tool called allure-commandline. So you need to make sure that allure-commandline.zip is present in your <TeamCity Data Directory>/plugins/.tools directory.
Related
I want to setup continua ci with octo deploy. In the past I was able to do it. but now with newer version of octodeploy it seems difficult
First continua didn't find a matching agent because the Octo.Default.Path wasn't resolved. I found out that it searches an octo.exe
but in the current octodeploy there is none
So I changed it to point to the octo.server.exe
Now the build starts but it gets a "ressource not found" response.
So i'm not sure i
The only documentation I can find is from 2014
Does somebody know if my change in the path is correct or even better if there is a more current documentation?
The Octo.Default property collector in Continua CI is looking for the Octopus CLI executable. This needs to be installed on the agent, and added to the PATH of the Continua CI Agent service user, for the property collector to pick up the executable. The Octo.Default property collector is used for the Octo Pack and Octo Push actions. These actions are not required if using the MSBuild actions and Octopus Deploy build event handler as described in the blog you linked to. See also my reply to your forum post.
We are using scripted build in our VSO environment and integrate with SonarQube, using the SonarQubePreBuild and SonarQubePostTest tasks.
Especially since SonarQube version 5.2 we experience that builds are always succeeding as long as SonarQube succeeds in generating the report.
For VSO Git pre-commit policies we have configured pull requests to start a build including SonarQube analysis.
However the configured Quality Profile is not met for the project, the build seems to succeed since SonarQube was able to do the actual analysis.
...But we want the build to fail....since quality conditions are not met.
We could add an additional custom (powershell) task to retrieve the results from the SonarQube instance, but what if we are running in preview mode and reports are not stored in the SonarQube database?
Before 5.2 you could use the Build Breaker Plugin to have the build fail in VSO. But the Plugin is no longer compatible with 5.2 and is planned to be included in Sonar Core in 5.4.
See this question for details.
I am using TeamCity 8.1.3 and have one task in the build queue and compatible enabled agent.
In "Build Queue" teamcity says that task "Can run on" - "2 agents"
Both agents are idle.
I tried to reinstall teamcity, reinstall buildAgent and install agent on another machine.
Tried to run agent as root. I read all agent logs and didn't find any errors; only warnings for not installed VCS tools (i need only git and its installed - no warning for it).
Why wont the agent run my task?
If the VCS tools aren't installed then TeamCity can't pull down your code and run the agent.
From the TeamCity documentation http://confluence.jetbrains.com/display/TCD8/Git+(JetBrains):
Git support in TeamCity is implemented as a plugin. Git needs to be installed on the server machine and, if the agent-side checkout is used, on the agents.
and
[Build configuration] will run only on the agents where git was detected or specified in the agent properties.
So you need install git.
This page covers installation instructions for Windows, Linux and Mac: http://git-scm.com/book/en/Getting-Started-Installing-Git. This SO post discusses installation as well: Git for beginners: The definitive practical guide
I can see two possible reasons
One of the implicit requirements not fulfilled. You need to check the enqueued build info for this, it tells why exactly the build is in the queue with compatible agents but not running. Examples can be: limitation on simultaneous builds in build or template configuration, shared resources unavailable etc. This would be listed in the little popup next to the enqueued build label
I've seen this happening when a requirement wasnt fulfilled initially (I had build configuration limited to 1 build at a time) when the build was enqueued, then it was corrected but the queue cached this requirement. Re-enqueuing the build sorted that.
Hover by mouse cursor to your VCS engine (e.g. git) and maybe you'll see there this message:
Changes have not been collected yet
In that case check performance of your TC and vcs server. (this I just guess from the message)
We are trying to install a CI Platform with (Jenkins,sonar,eclipse ...).
So that every developer can make analysis on his code before commit, I'm wondering between two alternatives :
running local analysis with the sonar plugin.
install the different plugins that sonar use (findbug,pmd,checkstyle ...) and configure them to meet the sonar configuration.
I'm not sure which alternative to use? I used to work with findbugs,pmd, checkstyle in eclipse and they look great.
Can you tell me which is the best alternative?
Thanks in advance.
Regards.
With Sonar plugin you can manage the violations like:
Create a review
Mark a violations as false positive or fixed
View the hot classes and hot violations
View yours reviews
If you use separate plugins you have to go sonar web to do that.
The great advance of sonar is the reviews.
Other question is how many projects you have and will have. I currently work with more than 70 projects and many profiles. Is more simple to me run analysis with one plugin, because I need just add the server and find the project. With other plugin you need add the link for each project in each plugin configuration.
Why not install the Sonar Eclipse plugin?
This was designed to solve the following problems:
Sonar does not support parallel analysis of the same project. This issue rules out the option of each developer running Sonar locally. (See SONAR-2761, SONAR-3306)
You don't really want developers uploading metrics and source code into the Sonar database. They could be working on an uncommitted workspace and would therefore cause both inaccuracies and confusion if Sonar is being used for code review.
Sonar is really designed to be run from a continuous integration server (like Jenkins), building code that has been submitted onto a shared codestream (or branch)
The big advantages of using the Eclipse plugin are:
True local analysis, no updates of the Sonar database
Configuration of the other tools is retrieved from the Sonar server and jars automatically downloaded.
Centralized management of Sonar quality profiles
I would like to integrate Jenkins with Redmine. If some build breaks, Jenkins would open an issue in Redmine to notify it with the console output.
How can I do it? Are there any plugins? Are there any implementation guides? I couldn't find a solution yet.
There are two ways to achieve this
install hudson plugin inside redmine, see http://www.redmine.org/plugins/t-ando_redmine_hudson , it will let you know the build inside redmine. (**2014.5.7 [Updated] change to redmine plugin list **)
install redmine plugin inside jenkins (hudson), unfortunately the plugin is not maintained any more, https://wiki.jenkins-ci.org/display/JENKINS/Redmine+Plugin . And JIRA jenkins plugin is a way how redmine plugin should be supported.
([Updated] the plugin is back since 2013)
[updated] I tried to add this functions for solution 2 in 2011.2, see my blog: http://larrycaiyu.com/blog/2011/02/24/associate-ci-build-information-in-redmine-issue-by-using-redmine-rest-api/, but I stopped after that, because
In the community, it seems solution 1 is preferred.
lots of functions are already inside JIRA, it is better to persuade them to make it as a common issue plugin inside jenkins.
You can try the e-mail-to-issue option in Redmine.
Configure Jenkins to send an e-mail to Redmine with detailed report.
Configure Redmine to accept the e-mail and transfer it to the issue.
You can configure whatever template you wish so the reports will be user-friendly. Further more Redmine has a simple incoming mail parser so that you can omit info you don't need.
No plugins needed, only settings in both tools.