I'm trying to trigger the build for each pull request and in that build i want to access the pull teamcity.pullRequest.number
teamcity.pullRequest.number parameter is not identified in Teamcity even after adding the pull request build feature.
I'm using the TeamCity Enterprise 2019.1.3 (build 66439).
Please suggest how to access these teamcity parameters.
Thanks in advance.
After googling I came to know that the parameter teamcity.pullRequest.number is available in 2019.2 and above versions.
As I'm using the lower version I'm unable to access it.
for more info click here
Related
I'm running TeamCity Enterprise 2019.2.4 (build 72059).
Is there an easy API call to get the username of a person who disabled a build step?
If that is not possible, as I suspect, what's the API endpoint to get a list of all modifications for a build configuration, and then the endpoint to get the contents of that modification?
Mind you, this is not about VCS changes. I know how to get those.
I enabled versioned settings for that project, so I just check the git history for the file that represents the build configuration and parse the commits for the one that disabled the build step.
Is there any way I can get any sonarqube api which can provide the build number of bamboo or any bamboo api which can give sonarqube info.This would really help.
I have so far tried both side but i am surprised both the system are quite clueless about each other. Why it is not possible that a build which ran sonarqube as as one of it's job doesn't have any information about that. Also neither in sonar it tell which build has actually triggered that sonar execution
(Not sure I understand what exactly you are looking for, perhaps this ...? )
I don't believe you can relate a specific Activity (SonarQube analysis) to a specific build (Bamboo), just project to job.
You must have SonarQube Server configured in Bamboo
When executing your job, you can add these sonar.links optional parameters to the analysis step:
sonar.links.homepage Project home page.
sonar.links.ci Continuous integration.
and
sonar.links.scm Project source repository.
sonar.links.issue Issue tracker.
Maybe also specify sonar.host.url=$SONAR_HOST_URL (where SONAR_HOST_URL is the global setting in Bamboo) in the analysis step parameters.
Those populate the Project Overview page sidebar:
That should provide the links from SonarQube back to the other systems of interest.
If you have properly configured Bamboo, you should see a link in Bamboo to the SonarQube project, post execution.
I am very new to udeploy and looking for a feature to pull latest version of artifacts from one of our build tool using simple http download from a given url.
I can see that "Source Configuration Type" has many option available like filesystem, teamcity, git repo etc, but no option is available for a simple url download.
I am actually using teamcity build and teamcity provides GET API to download artifacts, I understand that uDeoploy is also using this teamcity feature but the url it is constructing is not correct and throwing 401 exception (unauthorized) when not auth information is not provided, it should be using teamcity guest access to download the artifacts.
Please Note: when login information is provided it is working fine
any thoughts.
You can adjust the guest account privileges inside the Administration Panel, then inside the Users management, there is a link to setuo the guest account privileges.
We've got our source code up in BitBucket cloud and we're using TeamCity, with the "Commit Status Publisher" plugin. I was using our repository url (for example https://bitbucket.org/test/test.git) as the "Stash base url", which worked for a while, but then I started getting a 404 just recently. I tried using BitBuckets new build status api (https://confluence.atlassian.com/bitbucket/buildstatus-resource-779295267.html?_ga=1.155356926.432767113.1452136822), but I get a 405 error. Does anyone know which url I should be using and how to configure this in TeamCity? Is there a better plugin I could be using?
Thank you in advance,
Andrew
Bitbucket Cloud (bitbucket.org) and Bitbucket Server (formely known as Stash) use different API. Please install the latest version of the Commit Status Publisher plugin, it provides a dedicated support for Bitbucket Cloud.
Does anyone know how to setup TeamCity so that it would create a new JIRA issue for each build breakage/failure?
We are trying to categorize/track/get-stats on our build breakages and need some kind of db. JIRA would most likely do the job.
If you can configure TeamCity to emit an email on failure, you can add issues in Jira via email.