Does anyone else have a problem where everytime you need to commit using the TeamCity VS plugin, you have to re-enter the TeamCity server address and credentials?
So should anyone stumble across this again - simple answer is to upgrade to the latest version! Worked for us.
Related
I am currently on SonarQube Community Edition and I am trying to Integrate SonarQube with BitBucket. I have created an OAuth Consumer in my BitBucket Account and when I try to add it in SonarQube's BitBucket Cloud I am getting an error which is not properly complete I Guess (Unknown url : /api/alm_settings/create_bitbu... )
I don't know what I am doing wrong or if SonarQube Community Edition doesn't allow me to integrate BitBucket ALM. I am attaching a screenshot of the same
Cheers,
As it turns out, I have solved this issue and am posting the solution for whoever needs it.
It just so happens that this was an issue with the version of SonarQube I had. I updated SonarQube to the latest version(v9.6.1) and that resolved my issue.
Cheers,
The requirements on the following page state that you need to install Visual Studio with Xamarin on your local TFS server to setup Xamarin CI builds:
https://developer.xamarin.com/guides/cross-platform/ci/intro_to_ci/
topography of the CI
This is a real pain. We have lots of developers that rely on our local TFS server, most of whom don't do any Xamarin development. As such, any changes are heavily scrutinized. This often leads to us not installing the latest VS/Xamarin releases, as it's considered too risky for this vital bit of infrastructure.
We could have a Windows build machine with VS and Xamarin installed, that is connected to a Mac build machine. We'd be free to update the Windows and Mac build machines regularly, without the fear of compromising the TFS server. Is this possible? If not, why not?
Thanks in advance.
That diagram can't be right. There is no reason why you'd need VS or Xamarin installed on your TFS app tier.
I think it's showing a simplified configuration where the Windows build agent is installed alongside the app tier. That is a supported setup but is never, ever recommended by anyone, for exactly the reasons why you don't want to do it.
The diagram is simplified. You don't need to install anything on your TFS server. What you do instead is to install a Build Agent on a separate machine or virtual machine.
The installation details for the TFS 2017 / VSTS build agent v2 can be found in the official visual studio documentation.
The procedure is similar for both TFS and VSTS, where you generate an access token in TFS/VSTS, then simply enter the url for the TFS/VSTS instance when running the build agent install script, along with the access token.
There are build agents for Windows, Linux and macOS, so it is up to you how you configure how iOS builds are made.
is it possible to make the TFVC Plugin of SonarQube work with VSTS?
If I want to use the Plugin to connect with the TFVC of our VSTS-Account I get a not authorized exception. I'm pretty sure that the credentials are correct. Or Are there any special rights which are needed for that?
19:54:37.632 ERROR - Unable to TFS annotate the project which raised the following authentication exception: TF30063: You are not authorized to access xxx.visualstudio.com\DefaultCollection.
the configuration seems all correct, because the plugin works with a TFS2015-Server without any issues.
I'm Testing the plugin localy with the sonar Scanner V1.1.
SonarQube Version 5.2, TFVC Plugin Version 2.1
Thank you for your help!
Apparently this scenario is not supported yet. I ran into the same problem and I found the following issue on the backlog of the SonarQube team:
With the current TFVC Annotate plugin code author information is not seen for VSO hosted builds, this MMF is to enable the same.
You can find this information on: https://jira.sonarsource.com/browse/MMF-85
So until they fixed it I fear you'll need to disable this plugin...
I have a long-standing Azure project that I built in VS2012 against the Azure SDK 2.4, and am attempting to migrate it to VS2015 and Azure 2.7. I am able to build the project and run it locally, but when I attempt to deploy it fails with the following error:
Access to the path 'C:[user folder]\AppData\Local\Temp[random chars]\roles[solution]\base\x86\msshrtmi.dll' is denied
When I attempt to view that containing folder it doesn't exist... perhaps it is removed after the publish failure? I've found the msshrtmi.dll within the solution folders, and have tried changing the platform targeting that has been claimed to help other msshrtmi.dll issues, but most of those seem to be fails at build time not publish time.
I've re-built a new Azure solution and imported my web role project and get the same result. I've never had to delve deep in to the VS configuration/build/deploy world before and am hoping someone can help point me in the right direction.
Thanks in advance for your help!
I had the same exception. My resolution was a workaround given to me by the Microsoft Azure Tools team - package or publish on a 64-bit machine. My VM was 32-bit. As soon as I packaged on the 64-bit machine, this error went away and I could publish once again.
The same team members said this issue will be fixed in the Azure 2.7.1 release around the end of August.
I'm trying to set up continuous integration at my current place of work. It's not something I've done before so I'm fairly certain that there will be a few steps I've not done or things I'm un-aware of.
I installed TeamCity Professional 7.1.3 on a build server (Windows Server 2008 R2). I've created a simple .NET application that has no database connections and only three NUnit tests. This app uses .NET framework 4.
I set up a build step using NUnit and received a number of errors but I've now resolved them, basically by installing the .NET framework on the build server.
I'm now adding an extra step using Visual Studio but TeamCity now displays the warning 'No enabled compatible agents for this build configuration'.
This question looks similar to mine:
What do I need to install a Visual Studio 2010 (sln)-compatible Build Agent in TeamCity? and it helped me solve the problems I had with NUnit but not for this current problem.
Is there something I've missed during my set-up? If I'm building and running tests with NUnit do I need to bother with this second step?
You installed the full framework, correct -- not just the client pieces? Here's a TeamCity forum post on how to resolve the Unmet requirements:DotNetFramework4.0_x86 exists compatibility error when you've previously installed the framework.