continuous-integration

问题 During my build process, I am trying to create 2 artifacts. One artifact for pipeline-related scripts and code, and another for the Release product. I am trying to set this up in a way that the pipeline-related scripts and code are centrally managed in a separate repository and then imported into each production build pipeline upon execution. I have been able to import the code from External Git, but then I hit a snag... The trouble that I'm running into is that when I am creating the Build

问题 I'm using Jenkins since a little moment now, but I wanted to do something and I can't find how to do it... In deed, I want to trigger my projects with two differents way: every 4 hours and for every commit. But for each case, I don't want that all my Jenkinsfile is executed, only some specific stages. Is it possible to do that with Declarative Pipelines ? Thanks in advance 回答1: Unfortunately this is not available out of the box yet. Cloudbees has a proprietary plugin called "checkpoints"

问题 I'm using Jenkins since a little moment now, but I wanted to do something and I can't find how to do it... In deed, I want to trigger my projects with two differents way: every 4 hours and for every commit. But for each case, I don't want that all my Jenkinsfile is executed, only some specific stages. Is it possible to do that with Declarative Pipelines ? Thanks in advance 回答1: Unfortunately this is not available out of the box yet. Cloudbees has a proprietary plugin called "checkpoints"

问题 I want to know how we can specify the pool of users who will receive the mail if the build fails. For example :- If there are 10 users who are part of the changes in a particular build, but I want to send e-mails only to those whom I have specified and configured to receive mails. Rest will not receive the mails Suppose I want to send mails only to A, B, C. Even if build fails because of User D, I don't want to send mail to D. Basically, I am asking if there is a way we can constrain the list

问题 I am trying to configure CruiseControl .net to build our repository code periodically and run the tests included in the solution. I have configured the retrieving code from the svn server and building part. But I am unable to run tests on it. MSBuild keeps on complaining that. error MSB4057: The target "Test" does not exist in the project. I also tried running the tests through command line to see if that works with the same error. I used: MSBuild.exe TestProject.csproj /t:Test My

问题 Currently I have my git set up for AngularJS Projects. I do testing locally and if the tests pass I commit the code to Git repo. What I want to do is set up the UI project with CI and CD such that even after testing locally when I commit the code to Git repo it should trigger tests and then build (for Angular2 or minify for example for AngularJS) the project ready to be used. If the tests fail it should reject the push/changes. It should then push the passed code to the appropriate deployment

问题 I have a solution with reference to Telerik assemblies. The referenced version has been installed on the build server. The issue is that the continuous integration build always succeeded until I upgraded the Telerik assemblies in the solution and on my build server. The build now fails giving the classical: Could not resolve this reference. I checked my solution and everything is set to reference the specific version. The most suprising is that if I open the solution locally on the build

问题 I have a solution with reference to Telerik assemblies. The referenced version has been installed on the build server. The issue is that the continuous integration build always succeeded until I upgraded the Telerik assemblies in the solution and on my build server. The build now fails giving the classical: Could not resolve this reference. I checked my solution and everything is set to reference the specific version. The most suprising is that if I open the solution locally on the build

问题 I have a solution with reference to Telerik assemblies. The referenced version has been installed on the build server. The issue is that the continuous integration build always succeeded until I upgraded the Telerik assemblies in the solution and on my build server. The build now fails giving the classical: Could not resolve this reference. I checked my solution and everything is set to reference the specific version. The most suprising is that if I open the solution locally on the build

问题 We have a hudson setup with just one executor. we want to get to a point where we can have at least 2 executors. The problem that is stopping us from doing this is a job which cannot be run in parallel. Explanation: we have many svn branches configured on hudson. The flow for a particular branch will look like A->B->C In this flow, B writes and deletes data from oracle. we are good, if there is only one branch set up on hudson. But, we have many svn branches on Hudson. So there could be a