multi-configuration

Jenkins slaves workspaces

由 ◇◆丶佛笑我妖孽 提交于 2021-02-10 23:41:36
问题 I have a Jenkins multi-configuration project that I want to build on two slaves (Slave-1 and Slave-2) which are located on two different VM's. I am having a problem with how Jenkins attempts to create different workspaces for each slave. I want to use the same workspace path on each VM. I am getting my project files from Perforce and want to put them in the directory c:\workspace on both VM's. However when I run a build, I look on the VM that has Slave-1 and it stores the project files under:

Access file parameter in jenkins

由 自闭症网瘾萝莉.ら 提交于 2020-01-03 03:32:08
问题 I'm working on a multiconfiguration job( Regression_L1 ) in Jenkins whose task is to run 2 kinds of tests( test1 and test2 ). In the multiconfiguration job, it triggers an executor job( Regression_executor ) to run script for the selected test. The Regression_L1 job is restricted to run in matrix_service_jobs node, while the matrix jobs are to run in the slave node custom_matrix_service_jobs node. The Regression_executor job is restricted to run in remote machines with a specific label(RL1

Make Jenkins build multiple configurations with variable SVN URLs

由 爱⌒轻易说出口 提交于 2019-12-12 14:06:08
问题 I want to automate our build processes. We have 30+ configurations, each with a different SVN branch. Ideally, I would want to avoid having to create 30 separate Jenkins jobs, due to maintenance effort and risk of human error. This is what "multi-configuration project" in Jenkins was designed for, but unfortunately Jenkins doesn't support using the configuration matrix axis in the SVN URL. I also cannot build using parameterized build, because Jenkins will not allow the variables to be used

Is it possible to convert a Jenkins free-style job to a multi-configuration job?

由 只谈情不闲聊 提交于 2019-12-03 14:51:07
问题 I have quite a few free-style jobs in Jenkins that I would like to convert to multi-configuration jobs so I can build across multiple platforms under one job. These jobs specify quite a few build parameters and I would like to not have to set them up manually again by creating new multi-configuration jobs. Each job is currently limiting their builds to the platform we've been building on and the only other option I see is to clone the existing job and change the restriction to the new

How to configure jenkins multi-configuration build and test

由 自古美人都是妖i 提交于 2019-12-01 16:43:11
I need to build and test on multiple configurations: linux, osx and solaris. I have slave nodes labeled "linux", "osx" and "solaris". On each configuration, I want to (a) build (b) run smoke tests (c) if smoke tests pass, then run full tests, and perhaps more. I thought that multi-configuration jobs might be the answer, so I setup a multi-configuration build job and it starts concurrent builds on each OS. The build job will trigger a downstream smoke-test build, which, in turn, triggers the full-test job. I've run into the following issues If one of the configurations fails, the job as a whole

How to configure jenkins multi-configuration build and test

由 被刻印的时光 ゝ 提交于 2019-12-01 15:45:36
问题 I need to build and test on multiple configurations: linux, osx and solaris. I have slave nodes labeled "linux", "osx" and "solaris". On each configuration, I want to (a) build (b) run smoke tests (c) if smoke tests pass, then run full tests, and perhaps more. I thought that multi-configuration jobs might be the answer, so I setup a multi-configuration build job and it starts concurrent builds on each OS. The build job will trigger a downstream smoke-test build, which, in turn, triggers the

Jenkins and multi-configuration (matrix) jobs

由 夙愿已清 提交于 2019-11-27 18:08:12
Why are there two kinds of jobs for Jenkins, both the multi-configuration project and the free-style project project? I read somewhere that once you choose one of them, you can't convert to the other (easily). Why wouldn't I always pick the multi-configuration project in order to be safe for future changes? I would like to setup a build for a project building both on Windows and Unix (and other platforms as well). I found this question ), which asks the same thing, but I don't really get the answer. Why would I need three matrix projects (and not three free-style projects), one for each

Jenkins and multi-configuration (matrix) jobs

由 左心房为你撑大大i 提交于 2019-11-26 22:38:28
问题 Why are there two kinds of jobs for Jenkins, both the multi-configuration project and the free-style project project? I read somewhere that once you choose one of them, you can't convert to the other (easily). Why wouldn't I always pick the multi-configuration project in order to be safe for future changes? I would like to setup a build for a project building both on Windows and Unix (and other platforms as well). I found this question), which asks the same thing, but I don't really get the
订阅 multi-configuration