# Running multiple versions on the same machine?

**URL:** https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260
**Category:** SCM-Manager (General)
**Created:** [October 12, 2021, 1:57pm UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260 "2021-10-12T13:57:01Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![pcc2](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pcc2](https://community.cloudogu.com/u/pcc2)
#### Post date: [October 12, 2021, 1:57pm UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/1 "2021-10-12T13:57:01Z")

</div>

Currently running version 1.55

Wanting to upgrade to the latest version 2.24

The migration tool I assume won’t touch a 1.55 version, so is therefore possible to install 2.24 on the same machine but different port, and gradually move our repos over manually? Don’t want to shutdown the old version until the new version is up and running OK.

---

<div class="post-metadata">

### Author: ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)
#### Post date: [October 12, 2021, 2:48pm UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/2 "2021-10-12T14:48:33Z")

</div>

The upgrade **will** change the scm-home directory that you specify. So **do not** run it unless you have a good backup or you are running it on a test environment. You cannot start a 1.60 after the scm-home folder has been migrated to 2.x.

To run the upgrade, you will have to update to version 1.60 first, so all old data is updated to this release. After this, you can start with 2.24.0. On the first start with the home of 1.60, you will get a page with a migration assistant. Here you can select, where the repositories shall be stored.

Nonetheless, running two instances in parallel should be possible, but not with the same scm-home directory. If you just want to try a SCM-Manager 2 instance without the old data, you can set another scm-home folder and another port. How you can do this depends on your installation. It would be easy and with low risk to do it with docker, for instance.

Hope this helps.

---

<div class="post-metadata">

### Author: ![pcc2](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pcc2](https://community.cloudogu.com/u/pcc2)
#### Post date: [October 13, 2021, 8:15am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/3 "2021-10-13T08:15:21Z")

</div>

Many thanks for your helpful reply, we will try to upgrade to 1.6 today after doing a full backup, then proceed to 2.24.

---

<div class="post-metadata">

### Author: ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)
#### Post date: [October 13, 2021, 8:59am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/4 "2021-10-13T08:59:30Z")

</div>

We’d love to hear back from you 🙂

---

<div class="post-metadata">

### Author: ![pcc2](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pcc2](https://community.cloudogu.com/u/pcc2)
#### Post date: [October 13, 2021, 10:03am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/5 "2021-10-13T10:03:39Z")

</div>

We are now at 1.6, a missing repo caused 1.6 to fail to load, but after manually removing the repo from the xml file, it now seems to work.

Now for 2.24 🙂

---

<div class="post-metadata">

### Author: ![pcc2](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pcc2](https://community.cloudogu.com/u/pcc2)
#### Post date: [October 13, 2021, 10:35am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/6 "2021-10-13T10:35:13Z")

</div>

yum/dnf only want to install V2.12.

Trying to install 2.24 specifically states:  
Error: nothing provides java-11-openjdk-headless needed by scm-server-2.24.0-.noarch

Does 2.24 require updated Java ?

---

<div class="post-metadata">

### Author: ![sebastian.sdorra](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/sebastian.sdorra/32/7_2.png) [@sebastian.sdorra](https://community.cloudogu.com/u/sebastian.sdorra)
#### Post date: [October 13, 2021, 11:35am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/7 "2021-10-13T11:35:47Z")

</div>

Which os do you use?

SCM-Manager itself runs fine on Java 8 or newer versions, but the rpm has a hard dependency to Java 11.

---

<div class="post-metadata">

### Author: ![sebastian.sdorra](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/sebastian.sdorra/32/7_2.png) [@sebastian.sdorra](https://community.cloudogu.com/u/sebastian.sdorra)
#### Post date: [October 13, 2021, 11:41am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/8 "2021-10-13T11:41:49Z")

</div>

That yum offers only v2.12 is interesting, we have done the migration from maven to gradle in version v2.13.

Could you explain how you configured yum for the scm-manager repository?

---

<div class="post-metadata">

### Author: ![pcc2](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pcc2](https://community.cloudogu.com/u/pcc2)
#### Post date: [October 13, 2021, 11:50am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/9 "2021-10-13T11:50:54Z")

</div>

We use Linux 4.11.12-100.fc24.x86\_64

Created SCM-Manager.repo in /etc/yum.repos.d

[scm-manager]  
name=SCM-Manager Repository  
baseurl=https://packages.scm-manager.org/repository/yum-v2-releases/  
enabled=1  
gpgcheck=1  
priority=1  
gpgkey=file:///etc/pki/rpm-gpg/SCM-Manager

dnf list | grep scm-server  
scm-server.noarch 2.12.0-1 @scm-manager  
scm-server.noarch 2.24.0- scm-manager

dnf update scm-server  
Last metadata expiration check: 1:17:00 ago on Wed Oct 13 11:32:41 2021.  
Dependencies resolved.  
Nothing to do.  
Complete!

dnf install scm-server  
Last metadata expiration check: 1:17:17 ago on Wed Oct 13 11:32:41 2021.  
Package scm-server-2.12.0-1.noarch is already installed, skipping.  
Dependencies resolved.  
Nothing to do.  
Complete!

---

<div class="post-metadata">

### Author: ![sebastian.sdorra](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/sebastian.sdorra/32/7_2.png) [@sebastian.sdorra](https://community.cloudogu.com/u/sebastian.sdorra)
#### Post date: [October 13, 2021, 12:59pm UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/10 "2021-10-13T12:59:22Z")

</div>

Ok, it looks like you are seeing only version 2.12.0, because it is the last version which does not require java-11 it only “recommends” the usage of java 11. It looks like Fedora 24 does not ship Java 11, so dnf shows you the last installable version for you machine.

---

<div class="post-metadata">

### Author: ![pcc2](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pcc2](https://community.cloudogu.com/u/pcc2)
#### Post date: [October 13, 2021, 1:13pm UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/11 "2021-10-13T13:13:35Z")

</div>

So I could theoretically ignore that dependency for now and try and install Java 11 at a later date?

---

<div class="post-metadata">

### Author: ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)
#### Post date: [October 13, 2021, 3:11pm UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/12 "2021-10-13T15:11:05Z")

</div>

Hi, we’ve tried, but we cannot create an RPM that can be installed in Fedora 24 without breaking new installations. There are some other options, though:

1. Of cause we recommend to update to a current version of Fedora.
2. If this is no option for you, you can still use the [unix package](https://www.scm-manager.org/download/2.24.0/#unix), or
3. run SCM-Manager with [docker](https://www.scm-manager.org/docs/2.24.x/en/installation/docker/).

Both ways you have the downside, that you will not get automatic updates, but to get an impression of SCM-Manager 2 and test the migration, this should serve you well and both ways aren’t complicated. Maybe you can upgrate Fedora, when you’ve decided to migrate to SCM-Manager 2.

I’m afrait that’s all we can offer.

---

<div class="post-metadata">

### Author: ![pcc2](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pcc2](https://community.cloudogu.com/u/pcc2)
#### Post date: [October 14, 2021, 10:27am UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/13 "2021-10-14T10:27:35Z")

</div>

Hi,

I did a file comparison between 2.12 and 2.24 Unix installations and the only file that appeared to change was the .war file, so I stopped the service, copied the 2.24 war file over and restarted the service. Now it works as a proper service (thanks to the RPM of 2.12) but is at 2.24.

We have no problem doing a manually upgrade as and when needed.

Many thanks for your help!

---

<div class="post-metadata">

### Author: ![christoph.loose](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/christoph.loose/32/1400_2.png) [@christoph.loose](https://community.cloudogu.com/u/christoph.loose)
#### Post date: [July 5, 2022, 2:59pm UTC](https://community.cloudogu.com/t/running-multiple-versions-on-the-same-machine/260/14 "2022-07-05T14:59:03Z")

</div>


