Hi, I’m using SCM Manager 2.37.0 and I’m trying to upgrade it. The instructions only talk about install.
I’ve tried extracting the new version and overwriting the files, and editing the scm-server.xml, and the service fails to start.
If I delete all the files and then extract the new SCM version, edit the scm-server.xml and start the server, then the server starts OK, but I’m left with a preconfigured server (I get the config page), without all the users I’ve defined before.
I’m not warried about security issues since the server is not accessible from outside of our network. The only reason I’m trying to update is because I think I stepped into a bug.
I get a Smudge error followed by Object ‘cdaf4b19b2f69901ad45c45dce565c826a785732ac39567f5176663414a3a20c’ not found
If I take the file that it fails to fetch from the lfs repository, and put it under repositories\repo_name\store\blob\git-lfs\
with the name of cdaf4b19b2f69901ad45c45dce565c826a785732ac39567f5176663414a3a20c.blob then when I try git lfs pull, I get:
expected OID cdaf4b19b2f69901ad45c45dce565c826a785732ac39567f5176663414a3a20c, got e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 after 0 bytes written
And the file I pasted in the git-lft directory is deleted.
I downloaded a tool from github that calculates the SHA256 hash of files, and the correct hash for my file is indeed cdaf4b19b2f69901ad45c45dce565c826a785732ac39567f5176663414a3a20c (and certainly not e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855)
Are you aware of such bug?
If so, and the bug was already fixed, then how should I upgrade SCM Manager without loosing my configuration and users?
Thanks
Well, after pulling my hair, I accidentally found out that windows things is it a harmful file, but not my windows, but the windows machine hosting the lfs storage on azure.
It recently installed or updated Azure Arc, and the hash e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 is the one of a 0 bytes file (because the access to the file was blocked).
So I’m left with 1 question: How to update / upgrade my version to the latest?
I edited the scm-server.xml and also the new config yaml file to match the used port.
In the scm-server.xml I have configured the SCM_HOME, and I assumed that it will work and keep the users and repositories.
However, maybe it doesn’t work because the server is hosted on one machine, while the storage and configuration on another one (This used to work with version 2.37.0).
I have:
Where there is a folder called SCM-Repo on C: root.
And the SCM sub folder is actually a shortcut to a network path (in the form of \server\Folder\Subfolder ), and it used to work… Maybe it doesn’t work in the new version.
Is there a better way to map the SCM_HOME to a network drive?
Am I missing something in the upgrade process?
10x
Hey @saragani do you want to migrate on 3.3.0?
If so you have to follow the instructions on this site: https://scm-manager.org/blog/posts/2024-01-16-scm-manager-3-0-0/
With 3.x there is no longer a scm-server.xml needed.
Hi,
actually scm-server.xml is still relevant (you pack it in your zip and in the installation instructions you talk about it). What’s not needed is the server-config.xml which was replaced by a config.yaml file
I have problems migrating and still keeping my repositories and users settings. This might have to do with the fact that they are stored in a network drive. I need to investigate it