build-agent

Jenkins Windows slave: Authentication failed if running as service

由 二次信任 提交于 2019-12-22 10:16:05
问题 I have a Jenkins slave running on Windows 10 (1607). If I run the slave direct as JNLP this slave can clone from the git repository (authentification with username and password). If I start the same slave as a service, git clone fails with Authentication failed for ... . The service is created over the "File" menu of the slave and is running as "Local System Account". What's going wrong? Here is the output from Jenins: 00:00:00.003 Started by user <commit-user> 00:00:00.005 ln -s builds

TFS 2010 API: Queue builds synchronously and get the state of each queued build: “Run On Agent (waiting for build agent)”

由 本秂侑毒 提交于 2019-12-22 06:59:47
问题 Is it possible to queue builds synchronously? I tried something like this: CodeActivity: [BuildActivity(HostEnvironmentOption.Agent)] public sealed class QueueNewBuild : CodeActivity<BuildResult> { // The Team Project that the build definition belongs to. [RequiredArgument] public InArgument<IBuildDetail> BuildDetail { get; set; } // The build definition to queue [RequiredArgument] public InArgument<String> BuildDefinition { get; set; } protected override BuildResult Execute

Azure hosted agents - Visual Studio 2017

由 為{幸葍}努か 提交于 2019-12-21 04:34:19
问题 I set up a hosted agent in Azure to do a CI build but I'm getting the following warning during the Visual Studio build step before the build fails: "Visual Studio version '15.0' not found. Looking for the latest version." Looking at the documentation for hosted agents it looks like they're not deployed with Visual Studio 2017: https://www.visualstudio.com/en-gb/docs/build/concepts/agents/hosted Does anyone know when the hosted agents will be deployed with Visual Studio 2017 or when this will

Visual Studio Team Services: Agents Configuration for different environments in release definition

由 烈酒焚心 提交于 2019-12-14 03:24:46
问题 I am using Visual Studio Team Services, Release management and Continuous integration on the cloud. My release definition contains two environments: Dev and PRO. I want to know what the possible configuration if i don't want to buy a license. we need to associate each of the environments with specific agent. I guess they are called private agents. So are the agents installed on those release environments (which are on local domain) private agents? if yes, can i configure those 2 environments

Where is $(System.DefaultWorkingDirectory) set for builds in TFS2015?

由 ╄→尐↘猪︶ㄣ 提交于 2019-12-12 13:08:15
问题 I'm trying to modify the value of this variable as it currently points to the source folder of whatever build gets run on the agent instead of the root of the build. Does anyone know where I can modify this variable? I've looked at the agent's configuration .json file but didn't find anything relevant. 回答1: You can define $(System.DefaultWorkingDirectory) in Variables tab in Build Definition. I just had a quick test, if I define a new value to $(System.DefaultWorkingDirectory) , the output in

What is the purpose of Binaries\_PublishedWebsites directory under TFS build

由 生来就可爱ヽ(ⅴ＜●) 提交于 2019-12-10 15:04:18
问题 TFS generates a publish directory under the build agent working directory: Z:\TFSBuilds\1\box\CT\Binaries\\_PublishedWebsites I am supposing that this is where TFS is automatically publishing the site. How can I use it for auto publishing of sites... as Should we refer our IIS website to this directory. What is the purpose of it? 回答1: Firstly, the working directory is as the name says, a "working" directory. That is where the build agent downloads the source, perform compiles etc. It also

Azure SDK not available on Hosted VS2017 VSTS Build Agent?

由 妖精的绣舞 提交于 2019-12-07 15:11:34
问题 Our .Net projects are using VS 2017, and requires Azure Storage Emulator in Azure SDK to run unit tests. Our CI/CD is running in VSTS. We want to use some hosted build agent in VSTS agent pools. There are two issues we encountered. Firstly, according to official document, Hosted VS2017 seems don't have Azure SDK installed. Secondly, when running command C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe start , it failed with Error: Unable to start the

Azure SDK not available on Hosted VS2017 VSTS Build Agent?

由 ≯℡__Kan透↙ 提交于 2019-12-06 01:52:05
Our .Net projects are using VS 2017, and requires Azure Storage Emulator in Azure SDK to run unit tests. Our CI/CD is running in VSTS. We want to use some hosted build agent in VSTS agent pools. There are two issues we encountered. Firstly, according to official document, Hosted VS2017 seems don't have Azure SDK installed . Secondly, when running command C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe start , it failed with Error: Unable to start the storage emulator . The VSTS Hosted agent is running as service that you can’t start storage emulator (init

TeamCity build agent becomes disconnected after adding self-signed https certificate to teamcity

由 我的梦境 提交于 2019-12-03 05:09:15
问题 I added a self-signed certificate to my Teamcity BuildServer to introduce https support so that it can now be accessed at https://ServerUrl:8443 (More details about how here ) The result was that I was able access the server via https, but my build agent was now disconnected. How to fix this? 回答1: The build agent works as a client to the build server and communicates with it using http/https, and it turns out that when you add a self-signed certificate the build agent does not accept it. I

TeamCity build agent becomes disconnected after adding self-signed https certificate to teamcity

由 五迷三道 提交于 2019-12-02 18:18:58
I added a self-signed certificate to my Teamcity BuildServer to introduce https support so that it can now be accessed at https://ServerUrl:8443 (More details about how here ) The result was that I was able access the server via https, but my build agent was now disconnected. How to fix this? The build agent works as a client to the build server and communicates with it using http/https, and it turns out that when you add a self-signed certificate the build agent does not accept it. I needed to Let the build agent know the new path for communicating with the server Let the build agent know
订阅 build-agent