SCM-Manager now on GitHub

Migration in progress

As previously announced, all SCM-Manager repositories are being migrated to GitHub, because Bitbucket has announced the ending support for Mercurial.

Soon, all repositories will be available under the SCM-Manager organization on GitHub. It is our goal to have all repositories migrated within the next two weeks.

Once all the repositories are on GitHub, we will get onto migrating the issues and the wiki.

SCM-Manager 2.0.0-rc2

About six weeks ago we presented you the first release candidate of SCM-Manager 2. Now we finished the RC-2. Here are our favorite new features:

Unification of source and commits become “code”

We got feedback that the navigation points “Commits” and “Sources” on the right side led to confusion, because the branch context was lost on navigating between those two. Therefore we joined them into the new “Code” view. Here you can switch between sources and commits without loosing the branch context.

Code highlighting in diffs

As now we support syntax highlighting in diff views including pull requests. Below you can see screenshots from RC-1 (left) without syntax highlighting and from RC-2 (right) with syntax highlighting.

Initialize Repositories

On repository creation you can now initialize your repository with an initial commit, which contains a readme with title and description of the repository.



Markdown Preview

In the source view markdown files will be rendered by default. You can switch to source view with a toggle in the right upper corner.



Changelog

Added

  • Set individual page title
  • Copy on write
  • A new repository can be initialized with a branch (for git and mercurial) and custom files (README.md on default)
  • Plugins are validated directly after download
  • Code highlighting in diffs
  • Switch between rendered version and source view for Markdown files

Changed

  • Stop fetching commits when it takes too long
  • Unification of source and commits become “code”

Fixed

  • Classloader leak which caused problems when restarting
  • Failing git push does not lead to an GitAPIException
  • Subversion revision 0 leads to error
  • Create mock subject to satisfy legman
  • Multiple versions of hibernate-validator caused problems when starting from plugins
  • Page title is now set correctly
  • Restart after migration

How to get RC-2

Currently there are two ways to run SCM-Manager 2:

Docker

To start SCM-Manager with a persistent volume on port 8080 run the following command:

docker run -p 8080:8080 -v scm-home:/var/lib/scm --name scm scmmanager/scm-manager:2.0.0-rc2

Standalone Server

The standalone server requires an installed jre version 8. You can download the binaries here:

  • .tar.gz (sha1: eb5eccefcd34bea1bc7c054a9ba32a6ce664f278)
  • .zip (sha1: 00dacaee4ecd817238c45f2e9e271bcc933cc056)

Extract the downloaded archive and start scm-server/bin/scm-server or scm-server\bin\scm-server.bat. Your scm-manager should now be running on port 8080.

Give feedback

If you run into problems or you want to give us feedback for the new version, feel free to contact us using the mailing list (scmmanager@googlegroups.com).

SCM-Manager 2 – First release candidate

We are more than happy to announce that the first release candidate of SCM-Manager 2 is ready!

Since the last news about SCM-Manager 2 we have worked on the missing key features like the plugin center or anonymous access to repositories. Now it is done and we are offering you the chance to try RC-1 yourself.

How to get RC-1

Currently there are two ways to run SCM-Manager 2:

Docker

To start SCM-Manager with a persistent volume on port 8080 run the following command:

docker run -p 8080:8080 -v scm-home:/var/lib/scm --name scm scmmanager/scm-manager:2.0.0-rc1

Standalone Server

The standalone server requires an installed jre version 8. You can download the binaries here:

  • .tar.gz (sha1: 954e3f5c7a5e743d3db530f9865fece1660c9680)
  • .zip (sha1: f72f473032e6043d767a89ebc621c222f36dfa9e)

Extract the downloaded archive and start scm-server/bin/scm-server or scm-server\bin\scm-server.bat. Your scm-manager should now be running on port 8080.

Migration from SCM-Manager 1

First of all: Before you try migrating to SCM-Manager 2 we advice you to backup all your repositories!

If you already want to migrate from SCM-Manager 1 to the new version, you can do that pretty easily. All you have to do is to upgrade your SCM-Manager to at least version 1.60. Once you have done that, you have to start SCM-Manager 2 with the same home folder. When you access SCM-Manager 2, there will be a wizard that will help you to migrate your repositories to the new structure of SCM-Manager. After that, it will perform the migration fully automatically.

For more information about the migration have a look here.

Why you should get it

Even though SCM-Manager 1 already was pretty good, we are convinced that SCM-Manager 2 is way better! Now that all key features are implemented it is worth looking into the new version. If you want to fresh up your mind about the changes and new features, you can look here:

Give feedback

If you run into problems or you want to give us feedback for the new version, feel free to contact us using the mailing list (scmmanager@googlegroups.com).

 

Migration to GitHub

Because of the soon ending support for Mercurial repositories on Bitbucket (link) we decided to move all SCM-Manager repositories to GitHub.

Since there won’t be a major repository hosting platform left that supports Mercurial, it was inevitable for us to migrate the SCM-Manager repository from Mercurial to Git. Of course, we could have stayed on Bitbucket with git repositories, but some GitHub features like vulnerability scanning made it easy for us to move away from Bitbucket.

We have already started to migrate the repositories for plugins and the SCM-Manager repository will follow soon. On GitHub you can find all repositories here: https://github.com/scm-manager.

 

Cloudogu support team

Some time ago a vigorous involvement with SCM-Manager was announced in the Cloudogu blog. In the first step, Cloudogu joined the development of SCM-Manager 2. Now, as the second step, Cloudogu assigned a team to actively help with the support for SCM-Manager. The team will do what a support team does: answer your questions, evaluate and fix reported bugs and feature requests.

Because we don’t want to oversee your questions and reports, we decided to centralize the support channels. These are the channels that we will be watching from now on:

If you try to get in touch with the support team using another way, we might not reply. To prevent these situations, we will disable other options for example by deactivating the comment function here on the website.

We are looking forward to hearing from you.

SCM-Manager 2 development

Over the last couple of years it became clear that SCM-Manager 1 does not have the capabilities to fulfill the requirements of a modern SourceCodeManagement Tool. Great feature requests had to be rejected, because they simply could not be implemented with SCM-Manager 1. That is why the development of SCM-Manager 2 started. Now, thanks to the tremendous effort of Cloudogu, it is almost done and ready to use. This is what it looks like.

SCM-Manager 2 screenshot

Major changes at a glance

The big differences between SCM-Manager 1 and 2 are the technologies: the frontend of SCM-Manager 2 is based on React and Redux. The backend uses HATEOAS to provide a level 3 REST API.

Based on the new architecture and on acquired experiences from SCM-Manager 1, the new version will have numerous new features and some changes that make SCM-Manager 2 more convenient and secure. The changes and new features will be introduced in additional posts here. So stay tuned!

Missing features

Even though the development of SCM-Manager 2 is almost complete, there are still some features missing. That is for example the plugin center and a migration path from SCM-Manager 1 to 2.

If you can’t wait for the official release, you can get the latest build of SCM-Manager 2 here or the latest Docker image here.

From now on, we will share details about the new features of SCM-Manager 2 here.

SCM-Manager 2 gets a boost by Cloudogu GmbH

In 2010 I started the development of SCM-Manager.  Since 2013 I have a strong partner: Cloudogu GmbH. In the past they contributed to the project by helping with support cases and the development of several plug-ins like Groupmanager, CAS, scm-htpasswd and Checkstyle.

Because of many feature requests that cannot be realized with SCM-Manager 1, I decided to start the ambitious “SCM-Manager 2” project. Unfortunately, over time I realized that it is too much work to provide support for SCM-Manager 1 and to develop SCM-Manager 2 at the same time. Now, after four years of collaboration, Cloudogu and I decided that it was time to concentrate more power on the development of SCM-Manager 2, because we want it to play an important role in Cloudogu EcoSystem.

Thanks to this collaboration, the development of SCM-Manager 2 will speed up. Moreover we will be able to ensure a permanent development of SCM-Manager and the community support as you know it.

I would also like to thank you, the community, because SCM-Manager would not be the same without you. Thanks to all your feature requests, bug reports and enhancements helped me to improve it.  So be asured, SCM-Manager is and will always be Open Source.

So stay tuned! There are a lot of interesting things going on!

SCM-Manager 1.60 with support for Java 9 and 10

Version 1.60 of SCM-Manager is now available for download. Version 1.60 is the first version with support for Java 9 and 10.

Downloadhttp://www.scm-manager.org/download/
Release noteshttps://bitbucket.org/sdorra/scm-manager/wiki/release-notes
Getting startedhttps://bitbucket.org/sdorra/scm-manager/wiki/getting-started

Posted in release, scm-manager | Comments Off on SCM-Manager 1.60 with support for Java 9 and 10