Posted on 2020-10-09 by SCM-Team
Hello SCM-Manager community,
time flies and three months have passed already since we released the community edition of SCM-Manager 2. Thenceforth we give our very best to bring you new features and new plugins regularly and make the SCM-Manager your favorite repository management tool. We hope you will like the changes and enhancements we made.
We added the concept of API keys to SCM-Manager. Each user may generate API keys based on his own permissions.
An API key will be stored encrypted in the SCM-Manager and works like a password. It can be used for REST API calls and even for the SCM-Protocols like git.
If you don't want that the API key have all your permissions you may limit them by selecting a permission role like
OWNER on creation.
We migrated the SCM-Archive-Plugin which already exists for SCM-Manager 1. You may download your sources from a repository as a zip file. Just select your directory and click on the archive button.
Please mind that due to a little bug you should update to version 2.6.2 of SCM-Manager beforehand.
And we also created an entirely new plugin for you which may not amuse your developers.
Custom RegEx Validator from the Commit-Message-Checker-Plugin will protect your selected branches and ensure all commits pushed to the SCM-Manager fulfill your requirements.
If you are using the Redmine or the Jira plugin for SCM-Manager, you don't even have to think of a regex but simply select our prebuilt validations.
Example: Every commit pushed to your main branch has to contain an issue id from your project management system.
In SCM-Manager 1 we already supported submodules for Git, Mercurial and Subversion. Unfortunately on our big rebuild for SCM-Manager 2 this feature got disabled. We enabled submodules again and now your nested repositories are linked in the source view of the parent repository.
As always stay excited for the next big features which we are currently working on.