The basic concept of CI is that you have a system that builds the code and runs automated tests everytime someone makes a commit to the version control system. These tests would include unit and functional tests, or even behavior driven tests. The benefit is that you know – immediately – when someone has broken … Read more
End of the story: After fiddling with the permissions of the integration account, DCOM, service activation, etc. without any luck, I finally simply disabled ICE validation in the continuous integration build, while still keeping it in the local build. To disable ICE validation you can set SuppressValidation to true in the .wixproj file: <PropertyGroup> <SuppressValidation>true</SuppressValidation> … Read more
What worked for me was changing single quotes to escaped double quotes So from: “lint”: “eslint ‘**/*.{ts,tsx}'” To: “lint”: “eslint \”**/*.{ts,tsx}\”” The reason is because it depends on the console you are using – possibly the operation system (that’s why it can work for you while it’s not working for others and via versa) Source: … Read more
BUILD_NUMBER is the current build number. You can use it in the command you execute for the job, or just use it in the script your job executes. See the Jenkins documentation for the full list of available environment variables. The list is also available from within your Jenkins instance at http://hostname/jenkins/env-vars.html.
it is a good solution for build system, my suggestion: Your current jenkins works as master CI (probably started by user jenkins) Create another user in same machine or another machine to work as jenkins slave mode jenkins slave can be invoked from jenkins master, and it can use different user like vagrant who had … Read more
When you talk about scaling CI you’re really talking about scaling the use of your CI server to handle all your feature branches along with your mainline. Initially this looks like a good approach as the developers in a branch get all the advantages of the automated testing that the CI jobs include. However, you … Read more
Yes, it’s possible: Several agents can be installed on a single machine. They function as separate agents and TeamCity works with them as different agents, not utilizing the fact that they share the same machine. After installing one agent you can install additional one, providing the following conditions are met: the agents are installed in … Read more
You can use Parameterized Trigger Plugin which will let you pass parameters from one task to another. You need also add this parameter you passed from upstream in downstream.
Team City is by far and away the best CI server out there. Its killer feature for me is the tight integration with IDEs (IntelliJ, Eclipse and VisualStudio). It can show you, for example, when a file you’re editing in the IDE becomes out of date, who changed it and what they changed. You can … Read more
You can change default time limit in two ways job.<id>.timeout-minutes sets a timeout for a whole job job.<id>.steps.timeout-minutes sets a timeout for a single step Your scenario: my-job: runs-on: ubuntu-latest timeout-minutes: 30