I’m following the Microsoft official tutorial in order to configure BizTalk 2020 with DevOps, and the release pipeline is deploying the MSI “properly” but at the end I’m getting the error message:
“No mapping was made between account names and security identifiers.”
Any suggestions?
this a biztalk related conf issue. look at this thread :
https://social.msdn.microsoft.com/Forums/en-US/6f2fae62-0f68-4ba9-ba6a-be9e973e4cfc/biztalk-server-2010-no-mapping-between-account-names-and-security-ids-was-done?forum=biztalkgeneral
Related
The Team Foundation Server plugin is not available in Jenkins. The Jenkins official page shows the message:
Distribution of this plugin has been suspended due to unresolved security vulnerabilities
Is there any alternative to this plugin using which I can integrate Team Foundation Server with Jenkins?
MS have effectively abandoned support for TFVC and for the plugin.
You can still grab the plugin from the GitHub TFS plugin releases page and upload manually. ({JENKINS_URL}/pluginManager/advanced ). You may have to reconcile any dependencies manually.
MS recommended alternative is the tf command line from a shell step (brutal), which they also silently abandoned support for TFS SDK/CLI.
ps: aside from the vulnerability ( SECURITY-1506 / CVE-2020-2249 ), it does not meet the OSI open source license requirements - INFRA-2751 to be made available via the plugins site.
2021-03-30: It appears the OSI licensing issue has been resolved. This Jenkins Community post suggests a fix to SECURITY-1506 / CVE-2020-2249 is available in a fork but additional security issues ( SECURITY-2283 / CVE-2021-21636, CVE-2021-21637 (permission check), CVE-2021-21638 (CSRF) ) are outstanding, need to be resolved and released, or someone steps up to adopt the plugin.
pss: M$ also announced (23 February, 2021) retirement for Azure plugins for Jenkins, effective February 29, 2024.
I want to migrate form TFS 2010 to Azure DevOps online and was following Azure DevOps Migration Guide.pdf and running into issues when trying to validate my project collection.
On the other hand I had to see other MSFT documentation and it tells a different path:
Where as Azure DevOps Migration Guide says:
What is the best way to migrate from TFS 2010 to Azure DevOps online ?
Look closely. One document is more recent than the other. The first screenshot shows Azure DevOps Server 2020 as the end point. The other shows TFS 2018.
You need to upgrade to the most recent version of Azure DevOps Server in order to migrate to Azure DevOps cloud. The "best way" is always to follow the most recent official documentation.
If you're looking for help with performing the migration, you need to ask a new question that asks a specific question about the issue you're encountering.
We recommend that you use data migration tool to migrate data from Azure DevOps Server to Azure DevOps Services.
The data migration tool for Azure DevOps supports the two latest releases of Azure DevOps Server at a given time. Releases include updates and major releases. Currently the following versions of Azure DevOps Server are supported for import:
Azure DevOps Server 2019.1.1
Azure DevOps Server 2019 Update 1
Please update your TFS version and then Migrate your server to Azure DevOps
We are using InstallShield 2013 Limited Edition with TFS 2013 Build Server.
Occasionally our tfs XAML builds failed with error:
C:\Program Files (x86)\MSBuild\InstallShield\2013Limited\InstallShield.targets (108): Exception Caught
License of InstallShield 2013 Limited Edition is successfully activated on Build Server Machine(WIN 7 machine).
Due to this error, complete build failed. To fix this, we need to restart tfs build server machine.
Please suggestion some permanent fix for this issue. Let me know if need any additional information.
If you get error saying InstallShield.Tasks.dll was not found or could not be loaded like screenshot below:
Solution:
Set the MSBuild Platform on your Build Definition to “X86” as shown
below:
If you get error saying InstallShield Licence has expired like screenshot below:
Solution:
Set your Build Service to run with a domain account instead of
“NT_AUTHORITY\Network Service”.
My system is an on-premises setup for TFS 2015 and I am trying to get Release Management working with my Jenkins continuous integration system. I have recently added the ""Visual Studio Team Services Continuous Deployment" plugin to Jenkins. After finding out that I need to have Basic Authentication enabled on my TFS server to avoid a 401 - Unauthorized: Access is denied due to invalid credentials. error I am getting to the next error: NullPointerException.
I have looked through the code for the vsts-cd-plugin to see that there is an explicit reference to this API call that I don't believe is in TFS 2015 Update 3...
"/_apis/release/releases?api-version=3.0-preview.2"
Has anyone been successful in using the vsts-cd-plugin with Jenkins and an on-premises TFS 2015 setup? Does anyone have a suggestion on how I can fix this problem to create a TFS Release from Jenkins?
The API version 3.0-preview.2 is for Visual Studio Team Services, it is not included in On-premise TFS. In On-premise TFS, you need to use 2.2-preview.1.
api-version = 3.0-preview.1
Using on-premises: An earlier, and slightly different, version of this
Release Management API is available in Team Foundation Server 2015
Update 2. To use, you must specify an API version of 2.2-preview.1.
New release references a release definition to deploy an application
comprising of one/
You can try to download the source code of the plugin and update the API version and then build it on your local machine and install it in Jenkins.
Im trying to set up deployment on my Team Foundation Server 2015.
I set it up to deploy to a Azure website.
But when i check in code and it tries to build i get the following error "No agent could be found with the following capabilities: msbuild, visualstudio, azureps"
I did set up a agent pool and its online.
Hope someone can help
You need to install visual studio and azure powershell on your build server.