continuous-integration

问题 I am trying to find a tool that can solve the following problem: Our entire test suite takes hours to runs which often makes it difficult or at least very time consuming to find out which commit broke a specific test since there may be 50 to 200 commits in between test runs. At any given time there are only very few broken tests, so rerunning only the broken tests is very fast compared to running the entire test suite. Is there a tool, e.g. a continuous integration server, that can rerun

问题 I am trying to find a tool that can solve the following problem: Our entire test suite takes hours to runs which often makes it difficult or at least very time consuming to find out which commit broke a specific test since there may be 50 to 200 commits in between test runs. At any given time there are only very few broken tests, so rerunning only the broken tests is very fast compared to running the entire test suite. Is there a tool, e.g. a continuous integration server, that can rerun

问题 I am setting up Continuous Integration and Continuous Delivery infrastructure, My solution contains web projects, dlls, and a Console Application. My issue is that all of my projects get included in the build artifact except the console application This is the default MSBuild arguments i use /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactstagingdirectory)\WebApp.zip" /p

问题 I am setting up Continuous Integration and Continuous Delivery infrastructure, My solution contains web projects, dlls, and a Console Application. My issue is that all of my projects get included in the build artifact except the console application This is the default MSBuild arguments i use /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactstagingdirectory)\WebApp.zip" /p

问题 I am setting up Continuous Integration and Continuous Delivery infrastructure, My solution contains web projects, dlls, and a Console Application. My issue is that all of my projects get included in the build artifact except the console application This is the default MSBuild arguments i use /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:DesktopBuildPackageLocation="$(build.artifactstagingdirectory)\WebApp.zip" /p

问题 We recently moved from SVN to git. We work with a main "release" branch (master), and feature branches for every feature a dev is working on. In TeamCity we have a project for every feature branch, and of course a project for the master. When we worked with SVN, whenever someone merged from master to his feature branch or vice-versa, the merge was treated by TeamCity as one commit. Now, with git, every merge causes TeamCity to show all of the commits that came with this merge. This causes

问题 We recently moved from SVN to git. We work with a main "release" branch (master), and feature branches for every feature a dev is working on. In TeamCity we have a project for every feature branch, and of course a project for the master. When we worked with SVN, whenever someone merged from master to his feature branch or vice-versa, the merge was treated by TeamCity as one commit. Now, with git, every merge causes TeamCity to show all of the commits that came with this merge. This causes

问题 Our continuous delivery set-up, until recently, was delivering Service Fabric packages using the following command: msbuild SFApp.sfproj /t:Package This was necessary because the target Package is unavailable at the solution level. I.e. The command msbuild SFSolution.sln /t:Package Fails, as the target does not exist. As our dependency mesh grows, it gets to a point in which most interfaces projects will not build without a solution file (to work around the "OutputPath does not exist" red

问题 I'm new to Docker and was reading up on Docker. It's a great way to test systems in a self contained and reproducible standardized configuration (when done correctly). However, in all the things I've read, there doesn't seem to be too much emphasis on how the testing should occur with docker containers. The docker is used to "contain" the infrastructure and application (code) for easy testing (as well as deployment). But sometimes test codebases are be large and not so simple too. And one can

问题 I'm new to Docker and was reading up on Docker. It's a great way to test systems in a self contained and reproducible standardized configuration (when done correctly). However, in all the things I've read, there doesn't seem to be too much emphasis on how the testing should occur with docker containers. The docker is used to "contain" the infrastructure and application (code) for easy testing (as well as deployment). But sometimes test codebases are be large and not so simple too. And one can