Geek asks and answers

Make Jenkins to create multiple configurations with variable svn urls

I want to automate the build processes.

We have 30+ configurations, each of which has a different SVN branch. Ideally, I would like to avoid creating 30 separate Jenkins missions due to maintenance efforts and the risk of human error.

This is what the “multi-configuration project” was designed for in Jenkins, but unfortunately Jenkins does not support the use of the axis of the configuration matrix in the SVN URL.

I also cannot build using a parameterized assembly, because Jenkins will not allow the use of variables in local control paths (the variables in the URLs work fine, but they always end up in a directory with a name ${BRANCH}(literal).

At the end of the day I would like to check https://domain.ext/something/${BRANCH}/and keep it in /some/path/${BRANCH}. Even better if it is done in such a way that I can take advantage of Jenkin SCM's built-in features (e.g. polling).

How can I make Jenkins understand what I'm trying to achieve?

+3
source share
3 answers

- , , . ( " " ), "", ( ). , , .

, (, SVN) . , , .

+1

, SVN , . , 'svn update' .

0

: , SVN-.

$SVN_BRANCH URL- . , ( ). , , , - .

Now I have finished using the Jobcopy Builder plugin: I deactivated my initial task and used it as a template. In the copy job, I have a “copy” build step that copies the deactivated job, replaces $ SVN_BRANCH with the actual branch name (trunk or branch / some_branch) and activates these two jobs. Since I also checked the overwrite option, all job configurations are updated after running the “copy job” and the build history is saved.

0
source

More articles:


All Articles