Build strategy issue

Using Jenkins
1

Jenkins setup:

Hello, we have an existing Jenkins server running with version 2.303 and we planned to upgrade the Jenkins to latest version 2.462.2

We are not doing inplace upgrade, we have setup new Jenkins server with the latest version and installed all required plug-ins here and migrated the data from old server to new one.

The problem is with the plug-in Pipeline:Multibranch build strategy extension. Many jobs in the old Jenkins have the field “build included regions strategy” - trigger build for included regions with some condition.

After the data migration to new Jenkins, that particular field “ trigger builds for included regions” is not added. Except this all the data and all the jobs are migrated fine,

We have more than 300 pipelines where we need to add this field manually.

Old Jenkins - Multibranch build strategy extension : 1.0.10
New Jenkins - Multibranch build strategy extension : 55.v71b

These are versions installed in both the servers.

How can I get that particular filed for all the jobs after the data migration.

Thanks
Rizwan

2

Hi @MarkEWaite

Can you suggest the version for the plug-in Pipeline:Multibranch build strategy extension which supports Jenkins-2.303 and jenkins-2.462.2.

In our Jenkins 2.303 the version is 1.0.10 and Jenkins-2.462.2 it’s 55.v71b and we are facing issue with build strategies field.

So looking for one common version which is supported by both versions of Jenkins.

Thanks

3

Sorry, but I’m not willing to do the research to find the version of that plugin that supports Jenkins 2.303. The Jenkins update center provides plugin compatibility information for Jenkins versions for approximately the preceding year. Jenkins 2.303 was released 3 years ago. The update center no longer provides compatibility information for that release.

I think it would be much better for you and for others in the Jenkins community if you submit a bug report to that plugin with all the details recommended in “How to report an issue”. You can check the existing issues to see if one of them matches the problem that you are seeing.