SCM-Manager Blog Feed

New Plugins

Wed, 21 Jan 2026 10:00:00 GMT

Dear SCM-Manager Community,

It's been a while since you heard from us, but we haven't been idle. While a lot of our capacity is currently going into migrating our frontend from React 17 to React 19, we still managed to develop some nice features we would like to introduce to you.

Custom Properties Plugin

You can now install the Custom Properties Plugin.

In the simplest case, you can use it to manage your repositories by applying custom properties as tags. However, you can also use them to configure your Jenkins builds.

If you are using build libraries, you can now influence them using custom properties that are read by build pipelines as environment variables. For example, you could disable specific build stages based on a boolean property, or run different commands depending on whether a project uses Jest or Vitest.

MCP Server

In the last post, we mentioned the new MCP Plugin.

We have now brought it from a proof of concept to a fully useful tool. It can also be extended by other plugins, such as the Review Plugin, which adds functionality to search for pull requests and comments, or to create new pull requests.

Want to let an AI handle repetitive tasks, like updating licenses in a repository? Just tell it to create a new branch, execute the changes, and create a pull request when it's finished. All you have to do at the end is review the result.

Here are some screenshots of a litte experiment:

Closing Words

We would appreciate feedback on both features. Do not hesitate to report any issues you encounter or share your thoughts on the changes.

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our community platform.

SCM-Manager 3.11.0

Mon, 29 Sep 2025 10:00:00 GMT

Dear SCM-Manager Community,

At the end of last week, we released SCM-Manager version 3.11.0. This release wasn't actually planned yet; however, we recently made a mistake that we have corrected with this release.

Unfortunately, we accidentally published a release of our development version, where we are working on a big frontend library update (the adaptations for React 19). We sincerely apologize to everyone who experienced problems as a result. This should not have happened. Luckily, this release only contained changes to the user interface, so there is no risk of data loss.

Nevertheless, we have two interesting new features to announce with this release, too.

MCP Server

For all those who like to experiment with AI, we can recommend taking a look at our new MCP Plugin. This implements an MCP server with initial tools for the SCM-Manager (listing repositories, creating repositories, creating or changing files in a repository, as well as a global search). After installing the plugin, the server is available under the URL path /scm/api/mcp. A normal API token is required for login (use a header named Authorization with the value Bearer ey... (your API key preceded with Bearer). In our initial tests, the AI handled these functions well.

Marking Reviewed Files

In the review plugin, it has long been possible to mark files in the diff of a pull request as "reviewed". This marking is now also reflected in the file tree, so that with larger changes, there is a better overview of what has not yet been reviewed.

Closing Words

We would appreciate feedback on both features. Do not hesitate to report any issues you encounter or share your thoughts on the changes.

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our community platform.

SCM-Manager 3.10.0

Wed, 20 Aug 2025 10:00:00 GMT

Dear SCM-Manager Community,

yesterday we released version 3.10.0 of the SCM-Manager.

This release does not introduce major new features or visible changes. Instead, it contains important adjustments that prepare the software for upcoming compatibility improvements with external systems using go-git.

These other changes might be of interest to you:

If you are using Prometheus or other monitoring tools, you can now use them to monitor the performance of the storage layer. This might be of interest if you are experiencing performance issues.
When you are using the review plugin, the committer of merges or squash commits is now set to the user who performed the merge or squash. This ensures that the commit history reflects the actual originator of the changes.
For the review plugin, you will see that there is a new merge strategy available: fast-forward-only. This strategy allows you to enforce that merges are only performed if the branch can be fast-forwarded, meaning that there are no new commits on the target branch other than the ones being merged. If this is not possible, the merge will be rejected. This can help to keep the commit history clean and linear.

Closing Words

Especially with the migration of the plugins to the new persistence layer, we have made significant progress. On the other hand, these have been big changes. So we are looking forward to your feedback on this release. Do not hesitate to report any issues you encounter or share your thoughts on the changes.

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our community platform.

SCM-Manager 3.9.0

Tue, 05 Aug 2025 17:00:00 GMT

Dear SCM-Manager Community,

a few days ago we released version 3.9.0 of the SCM-Manager. This release is a continuation of our efforts to improve the performance using SQLite. While migrating some more plugins to the new persistence layer, we noticed that we needed some more features. But you will also find some other minor changes in this release that address some of the community's issue reports.

Changes in the core

When the development of SCM-Manager started many years ago, the word 'changeset' was being used a lot more often than it is today. Now, the term 'commit' is omnipresent in the world of version control systems. We have therefore decided to rename the term 'changeset' to 'commit' in SCM-Manager.

We often receive feedback that the deletion of a repository is too easy. In the administration view of a repository, deletion is only one click away. To address this, we have added a confirmation dialog where the name of the repository has to be typed in once more when deleting a repository. This should help prevent accidental deletions of repositories.

Another little change affects the commit details view. We realized that we were inconsistent regarding the timestamps of the different 'events' of a commit. In Git, a commit can have an 'author' referring to the person who wrote the code, while the term 'committer' refers to the person who actually created the commit. This can be different people and it can happen at different times, for example when a commit is rebased or cherry-picked. We have therefore clarified this by displaying the times alongside the author and the committer.

Further plugins using the new persistence layer

As mentioned above, we have migrated some more plugins to the new persistence layer. This time, the following plugins have been migrated:

Review Plugin
Landingpage Plugin
Trace Monitor Plugin

This should result in a better performance when using these plugins and increased stability of the SCM-Manager.

Closing Words

Especially with the migration of the plugins to the new persistence layer, we have made significant progress. On the other hand, these had been big changes. So we are looking forward to your feedback on this release. Do not hesitate to report any issues you encounter or share your thoughts on the changes.

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our community platform.

LDAP plugin account hijacking vulnerability

Thu, 22 May 2025 12:00:00 GMT

Hello SCM-Manager Community,

In our previous post, we addressed a vulnerability in the CAS plugin. During our follow-up review, we discovered the same issue in the LDAP plugin.

We’ve released an update that not only patches this vulnerability but also enhances overall access security.

Please update immediately to the latest scm-ldap-plugin version 3.1.1!

If you don’t use the LDAP plugin, you’re not affected and no action is needed.

Security is our top priority, and we’re continuously working to keep our platform as safe as possible. Thank you for your trust and ongoing support!

CAS plugin account hijacking vulnerability

Wed, 21 May 2025 12:00:00 GMT

Hey SCM-Manager Community,

we have discovered a vulnerability in the CAS plugin that could potentially lead to unauthorized access to user accounts. Under certain conditions, it would have been possible to perform actions on behalf of other users. We immediately reworked the plugin and released an update that fixes this vulnerability and improves access security.

We strongly recommend that all users update to the latest version of the scm-cas-plugin. Please update your plugin version! If you are currently using a 2.x version, please upgrade to 2.5.1. If you are currently using a 3.x version, please upgrade to 3.3.2.

If you don't use the CAS plugin, you are not affected by this issue. We take security seriously and are always working to keep our platform safe. Thank you for your trust and continued support.

SCM-Manager 3.8.0

Thu, 17 Apr 2025 17:00:00 GMT

Dear SCM-Manager Community,

today we released version 3.8.0 of the SCM-Manager. In this release cycle, we focused on finishing the implementation for the SQLite support mentioned in our previous blog post here. We also reimplemented parts of the Pushlog Plugin, so it now uses SQLite for persisting its data. Besides those big changes, we also added new features and improved upon existing ones.

Pushlog Plugin with SQLite Support

In the past, we have experienced performance problems regarding the Pushlog plugin with repositories that have a high number of commits. We were able to trace these performance problems back to our XML-based persistence layer in the SCM-Manager. To get these problems under control, we switched the persistence layer of the Pushlog plugin to our SQLite API. This means that loading Pushlog entries should no longer lead to slow loading times, even with larger repositories.

To benefit from this update, simply upgrade the SCM-Manager to version 3.8.0 and install the latest version of the Pushlog plugin. Previous Pushlog entries do not have to be migrated manually, this happens automatically when the SCM-Manager is started. When importing and exporting repositories, these Pushlog entries are also retained and are automatically migrated to SQLite.

Export of Pushlog Entries

In addition to the performance improvements, we have also implemented a new feature for the Pushlog plugin. With the latest version of the Pushlog plugin it is now also possible to download all Pushlog entries of a repository as a CSV file. The download link for this CSV file can be found on the information page of each repository. This CSV contains for each commit of the repository the time when this commit was pushed and by which user.

Commit Reverts

In everyday developer life, it occasionally happens that commits are created and pushed, that you want to revert again at a later point in time. The version control system Git supports this with the following command git revert <commit>. To better support this process, we now also offer the option of reverting a specific commit in the UI of the SCM Manager. For this purpose, a button has been introduced in the details view of a commit which, when clicked, reverts the respective commit and then redirects the user to the new commit with the removed changes.

Configuration of JWT Lifetimes

JWTs are used in the SCM-Manager to authenticate users. These usually have a limited lifetime. In the case of the SCM-Manager, this was previously limited to one hour. This meant that users were forced to log in again after a certain period of inactivity. Several feature requests from the community have made us aware that there is a need to make the lifetime of a JWT configurable and thus reduce the frequency with which users have to log in again. We have responded to those requests from the community and have now made it possible to specify a lifetime for JWTs in hours in the general settings of the SCM-Manager. We ask you to use this feature with caution, as a longer JWT lifetime also represents a security risk.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our community platform.

JWT Configuration and SQLite Support

Tue, 11 Mar 2025 17:00:00 GMT

With the next minor release, we are introducing some exciting changes, particularly regarding JWT (JSON Web Token) configuration and Javadoc. We would also like to give you an outlook on what lies ahead regarding SQLite.

JWT – Flexible Lifetime Configuration

You will be able to set the JWT lifetime on an hourly basis in the global configuration. This gives you more control over token validity and allows you to adjust security settings to match your requirements.

If you reduce the token lifetime in the configuration, all previously issued tokens will immediately become invalid. This ensures a consistent security strategy and prevents older tokens from staying active longer than necessary.

We are also introducing a new option for infinite JWTs in the configuration file (config.yml), but we strongly advise against using it. Keeping tokens valid indefinitely poses a significant security risk. If you choose this option, ensure you have alternative protection measures in place to prevent unauthorized access.

This feature will be available with the next release.

Javadoc

From now on, we will publish the Javadoc for the latest SCM Manager core version on our website with every release. In Java, Javadoc comments are used as a standardized method to document code. This is a first step and will be updated and expanded to improve clarity and help developers better understand the core API.

The entry point for this will also be available via the development section in the documentation.

SQLite Support – A Work in Progress

SCM-Manager currently works with XML files to save settings and status, which can sometimes become hard to handle in larger instances or over time. In these cases, we sometimes encounter performance problems when reading and writing. Especially aggregations over different data sets are cumbersome and often slow. We introduced a lot of caching mechanisms, but we think, we've met a dead end here. The advantages, on the other hand, are simple migrations of data or manual changes on the basis of XML files and simple expandability by plugin developers.

So after weighing pros and cons for a while, we identified SQLite as a possible alternative, tested it positively and are happy to confirm that it's in development! We created an API, that on the one hand extends the existing store API so that migration is simple, but on the other hand allows somewhat complex queries, that are still type-safe. This could be done without moving away from the simple entity based approach with XML annotations. Instead of XML files, entities will be stored as JSON blobs in the database. These JSON blobs can be handles extremely fast and effective by SQLite.

However, we don't want to make any premature promises. There is no fixed timeline for when SQLite will be fully integrated. As a user, you should not notice any changes at all (despite some performance improvements, if we're lucky). The only downside will be, that data for plugins using this new store will no longer be stored exclusively in the directory of the repository. Exports and imports will work the same way as before, nonetheless.

Also, we will not migrate everything into the new database. Only those use cases where we've experienced performance issues or data inconsistencies will be migrated. So this only effects a tiny number of plugins. Things like configurations will probably never be moved away from XML files. It is way too convenient to be able to modify them manually when something does not work as expected (like an authorization plugin that blocks any access).

Since development is still in progress, now is the perfect time to share your thoughts. What do you need from SQLite support? Are there specific use cases we should consider? Community feedback is crucial to shaping our roadmap, so let's discuss! We encourage you to join the conversation in our community forums or through other channels.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our community platform.

SCM-Manager 3.7.0

Fri, 24 Jan 2025 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 3.7.0. In this release cycle, we focused on improving the handling of git repositories by optimizing the performance of git modifications via UI and enabling the usage of partial clones and fetches. We also improved the user experience of creating pull requests. This release also includes other new features and bugfixes for the core and the following plugins:

Review Plugin
Repository Avatar Plugin
Landing Page Plugin
Jira Plugin
Webhook Plugin
Repository Size Plugin
Repository Mirror Plugin

Performance Improvements for Git Modifications

With the previous implementation of commits via UI, it was required for the SCM-Manager to locally clone a repository within the working directory to apply the changes of a commit. The commit was then created after applying those changes and pushed to the actual repository. The biggest bottleneck of this approach was the cloning of the repository, because it heavily depended on the size of the repository. At first, we tried to improve this issue by caching a cloned repository. But this only helped marginally, because it required the repository to already be cached, and it did not help at all when merging pull requests.

This release contains a new approach. Instead of relying on a cloned repository, for the creation of the commits for us, we started to create the commits ourselves with the help of the JGit library. Because of this approach we achieved a drastic improvement in terms of speed. Now the creation of a commit via UI does not depend on the size of the affected repository.

If you still notice poor performance regarding commits, please contact us via GitHub or our community platform.

Partial clones and fetches for Git Repositories

Git supports partial clones or fetching of a remote repository. However, it requires the repository to configure the property uploadpack.allowFilter with true. We have now enabled this property for all git repositories so that clients may use this feature. It does not matter if the repository is newly created after the update or already existed before the update.

We added suggestions to create pull requests for a recently pushed source branch, to further improve the user workflow when working with pull requests. These suggestions are shown in banners rendered below the title of a repository view. Each banner contains the information which branch was recently pushed by the current user, a button to quickly navigate to the create pull request view with the respective branch preselected as the source branch and a button to delete the suggestion itself. Please take a look at the review plugin documentation for further information.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our community platform.

Potential leak of password details in trace log

Fri, 17 Jan 2025 17:00:00 GMT

We found a potential risk that could reveal details about user passwords in the trace log. Passwords or parts of them have never been logged in plain text, though.

To fix this issue, we released new versions of SCM-Manager:

2.46.5 (a fix for a slightly older version)
2.48.4 (for those who do not want to update to 3.x yet)
3.6.1 (the fix for the latest version)

We highly recommend to update to one of these versions.

SCM-Manager 3.6.0

Fri, 06 Dec 2024 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 3.6.0. In this release cycle, we focused on improving upon already implemented features. For example, we worked on the layout of the changeset and diff view, the editing experience of markdown documentation, and the general accessibility of our webapp. This release also includes other new features and bugfixes for the core and the following plugins:

Documentation Viewer Plugin
Review Plugin
Tag Protection Plugin
Readme Plugin
Support Plugin
Repository Size Plugin
Pushlog Plugin
Editor Plugin
Gotenberg Plugin
Trace Monitor Plugin

New Layouts in the Changeset and Diff Views

The previous release added a file tree containing every file changed by a commit or a pull request. Based on the feedback we received from users, we added the ability to change the layout of the file tree and the diffs. It is now possible to switch between three layout modes using a radio group at the top.

The first mode hides the file tree and only shows the file diffs. This improves the handling of diffs containing long lines of code.

The second mode shows the file tree and the file diffs. Allowing quick navigation between file diffs while reviewing them.

The third mode hides the file diffs and only shows the file tree. This improves the handling of files with a long path and filename. The navigation to a specific file also works in this mode. After jumping to a file, the layout mode changes to show both file tree and file diffs.

New Markdown Editor

In the previous blog post we already announced a rich text editor for editing markdown files. With this release the new editor is now officially published. It is available through the newest version 1.1.0 of the "Documentation Viewer Plugin".

This editor provides a rendered view of the current markdown document and a toolbar to format selected text. Besides tables, it supports the complete basic markdown syntax. To get an overview over all available features, you should take a look at the plugin documentation.

For future releases we are planning to add syntax highlighting for code blocks, support of tables and an additional source view.

Accessibility Improvements

Accessibility is an important and serious topic for the developer team. Therefore, we wanted to highlight some of the work we put in to improve it. We started by optimising the handling of our webapp by assistive technologies like a screen reader. To achieve this we started changing our HTML structure slightly to better utilize the semantics of HTML elements and also added some aria attributes to certain elements.

The high contrast mode also got some redesigns to better adhere to accessibility design guidelines. For example links are now underlined and therefore easier to distinguish from basic text.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 3.5.0

Thu, 10 Oct 2024 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 3.5.0. In this release cycle, we continued on improving the user experience of working with pull requests and changesets. Furthermore, this release also provides new features and bugfixes in the core, "Review Plugin" and the newly released "Documentation Viewer Plugin".

New File Tree in the Changeset and Diff Views

To improve the handling of changesets and pull requests with a huge amount of file changes, we added a file tree to support users navigating through the changeset and diff view.

This file tree allows users to have a better overview of all the files, that are changed by changeset or a pull request. Each file can also be used as an anchor, to jump to the diff of the corresponding file. It also forces the loading of that diff, if it has not been loaded yet. Future releases will polish the file tree further, by adding features to accommodate the different workflows of different users. User feedback for this feature is highly appreciated.

Documentation Viewer Plugin

It is pretty common that the documentation of a repository is contained within the repository itself. To improve the handling of those documentation files, we started to develop the "Documentation Viewer Plugin". The goal of this plugin is to make the user experience of viewing and editing the documentation as easy as possible. The first release offers a quick access link at the repository sidebar navigation to the documentation itself.

For further information on how to use this plugin, take a look at the plugin documentation page. In the next release cycle, we will focus on improving the editing experience by implementing a rich markdown editor.

Conflicting Files in the Pull Request Diff View

If a pull request contains conflicting changes, a user would need to navigate to the "Conflict" tab to see which files are affected by a conflict. This might require a user to jump back and forth between the "Diff" and "Conflict" tab to conduct his review. We solved this issue, by also indicating with a warning icon which files contain a conflict within the "Diff" tab.

Improved Performance for Pull Request Overview

The SCM-Manager team is currently also focusing on improving the performance of the SCM-Manager. In the course of pursuing this goal, we started by optimizing the response time of the pull request overview page. We noticed a huge hit to the response time, if users tried to load all pull requests of a repository (tested with over 300 pull requests). The pagination did not curtail the response time. This issue occurred due to a lackluster implementation of the corresponding endpoint. We fixed the implementation issues and reduced the response time by a significant amount.

If you find any performance related issues, please notify us either on GitHub or our community platform.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 3.4.0

Thu, 22 Aug 2024 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 3.4.0. In this release cycle we put a huge emphasis on improving the user experience of working with pull requests and changesets. Additionally this release contains multiple new features and various bugfixes in three plugins and one newly released plugin, the BlueSpice plugin.

BlueSpice Plugin

BlueSpice is a free and open source tool for creating your own wiki and knowledge base. BlueSpice is frequently used in combination with the SCM-Manager within the Cloudogu Ecosystem, for documentation purposes. The aim of this plugin is to bring the documentation from a BlueSpice instance closer to the associated repositories, by providing a direct link from the repository sidebar to the corresponding documentation page, made available by a BlueSpice instance. For further information on how to use this plugin, take a look at the plugin documentation page.

Modified Files Overview in Changeset and Diff Views

To improve the user experience, working with changesets and diffs, we added an overview of the amount of files that are added, modified and deleted by a pull request / changeset. This overview can be seen at the top of the diff / changeset view. We added this feature based on the feedback of current users. With this feature, it should be easier to estimate the actual size and complexity of a pull request / changeset.

To reduce the confusion created by ambiguous or confusing icon buttons, we have replaced the buttons at the top of the diff view with a drop-down menu, indicated by a cogwheel icon.

External Merge Tools

With git and a .gitattributes file it is possible, to define an external merge tool for certain files. In earlier versions the SCM-Manager the review plugin did not consider these merge tools and tried to merge the files on his own. If you now try to merge two branches that cannot be merged with a fast forward and at least one of the modified files requires an external merge tool, a conflict appears in the pull request view with the message that the pull request contains files which can only be merged by an external merge tool.

Repository Mirror Plugin

In previous versions of the repository mirror plugin, there was a problem that mirrors were updated even though this mirror had already been deleted. This resulted in the server log being flooded with exceptions at regular intervals. Until now, only a restart of the SCM-Manager could solve this problem for a deleted mirror. The latest version of this plugin fixes this error entirely, by cancelling the update schedule upon mirror deletion.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 3.3.0 and an important vulnerability bugfix

Mon, 08 Jul 2024 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 3.3.0. This release focuses primarily on an important vulnerability bugfix, that prevents users from escalating their privileges in a namespace of repositories. Additionally, some new features and minor bugfixes were also added to this release.

Namespace privilege escalation

With version 3.0.4 a new feature was released for namespace privilege settings. This feature could be abused to escalate the privileges of a user within a namespace. Every version between 3.0.4 and 3.2.2 is exploitable with this vulnerability. Therefore, we would strongly advise to update your SCM-Manager to version 3.3.0 as soon as possible, if you are running one of the affected versions.

Merge Tool Detection

In git it is possible to configure that certain files can only be merged by external merge tools, instead of using the git internal merge tool. This configuration can be provided inside a repository with a .gitattributes file. The backend merge api of the SCM-Manager can provide feedback if two branches can be merged, by checking for merge conflicts. With version 3.3.0 the SCM-Manager can also check, whether two branches can be merged, by evaluating the .gitattributes file and check if a file needs to be merged by an external merge tool first.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 3.2.0

Thu, 23 May 2024 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 3.2.0. This release is focused on some new features and various bugfixes in 3 plugins.

Whitespace changes

There is now an option to hide whitespace changes. This should make it easier to focus on the actual changes and reduce noise. The buttons are located in the changeset view as well as in your pull requests.

Furthermore, it is possible to show and hide your whitespaces and tabs in your file.

Review Plugin

It is now possible to add images to your comments by copy and pasting them into the textarea. Currently, we support images with the file format JPG, PNG or GIF. The maximum size of an image is currently limited to 8MB. This is an early implementation, and we are planning to improve it. For example by adding the drag and drop support of images.

In your pull request, the target branch can only be changed when no other pull requests with the same branch exist and the new pull requests has differences. Moreover, the pull request UI got upgraded with a sticky header that lets you see the important information, even while scrolling down.

Additionally, there were also several small improvements and bugfixes. Please make sure to update your plugins, too!

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 3.1.0

Wed, 10 Apr 2024 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 3.1.0. This release focused on performance, various bug fixes and new features in over 8 plugins

Performance improvements

We improved the speed of repository imports and mirrors by optimizing the scan of commits in each branch and tag. Additionally, the user can ignore the import of LFS files to enhance the performance. Previously the import of a large repository like the linux kernel could have taken days, but after the optimization it only takes several minutes.

In some cases we encountered the issue that events of the same type blocked the event bus, for example indexing new repositories. Because one specific event handler could only be executed once at the same time and therefore blocking the execution threads for other event handlers. As an event handler is submitted for execution, we now check if the event handler is already being executed by a different event. If that is the case, we postpone the execution of the new event without blocking the execution threads with waiting event handlers.

Mail Plugin

The SCM-Manager supports email notifications for various events. In the past this could lead to the users inbox getting flooded with many notifications in a short period of time. To prevent this issue, we implemented a feature to summarize multiple emails into one. The summarization behaviour can be configured by the user in multiple ways. The documentation of the configuration can be found under the Mail Plugin.

Readme Plugin

In the past the readme of a repository was shown on its own page within the repository. Now the readme was moved to the code section of the repository and is rendered below the file tree. The readme page used to only show the content of a readme file from the root path of the default branch. With this update the readme section is displaying the content of a readme file from the currently selected branch and path. If the current path and branch do not contain a readme file, then nothing gets shown.

Upload of directories

In the current editor plugin it is possible to upload files. In the upload dialog it is now possible, to also upload empty directories. If you upload an empty folder we will generate a .scmkeep file to prevent the directory from being ignored by the version control system. Sadly this feature is only usable in chromium based browsers. This feature is somewhat unstable, but we want you to try this out and leave some feedback.

Other changes

If you have an open pull request, it is possible to change the target branch
It is possible to reopen a rejected pull request
The decision to delete the source branch after the merge can be made while creating the pull request
You can leave the editor with the keyboard now

... and a lot of other small improvements and bugfixes. Please make sure to update your plugins, too!

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 3.0.0

Tue, 30 Jan 2024 17:00:00 GMT

Dear SCM-Manager Community,

recently we announced that SCM-Manager 3.0.0 is nearly finished. Yesterday we finally released the new version and are proud that SCM-Manager, which was created in 2011 by Sebastian Sdorra, reached another milestone.

What does this mean for you and your SCM-Manager?

The most important point is, that your daily work with SCM-Manager will not change. The user interface, workflows and CLI remain the same.
All your plugins remain fully compatible.
If your scm-server uses the default configuration the migration to 3.0 will be fully automatic.
If you use custom scm-server configurations, you will have to migrate them. Learn more about migration in the migration guide.

If you want to dive deeper into the reasons for the new major release, please refer to our previous blog post.

Documentation

We already gave you a sneak peek for the new server configuration. The whole configuration can be done inside the config.yml. Also, all configuration options can be set via environment variables, which can be really helpful for Docker and Helm deployments.

Read the docs.

Disclaimer

We tested the major changes thoroughly and did our best to ensure maximum compatibility. It is still recommended that you back up your server before upgrading. If possible also consider to try this new deployment on your staging environment before upgrading production systems.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 3.0.0

Tue, 16 Jan 2024 17:00:00 GMT

Dear SCM-Manager Community,

We are finally confident to announce SCM-Manager 3.0.0 which will be released soon. But before you get too excited or even panic, we would like to clarify what actually changed and how you can make the upgrade as effortless as possible.

Why the new major version?

SCM-Manager follows semantic versioning. This simply means that the new version represents the nature of the changes included. Version 3.0.0 contains breaking changes that the administrators and/or developers must be aware of and take actions. We tried to keep the breaking changes as minimal as possible, but we also wanted to take the opportunity to make some changes that we have been planning for a long time. The chances are that you will not notice the major version at all. At least users should not notice any changes.

But let's take a look at what actually will be changed and why.

What will change?

Unavoidable breaking changes

Because the old version of Jetty (the underlying webserver) ran out of maintenance, we finally had to upgrade Jetty to the newer version. By doing so, we ran into breaking changes regarding the server configuration. This regards custom settings like a different context path or SSL configuration that has been taken place in the server-config.xml.

The second bigger obstacle we stumbled upon is that many newer Java libraries are already (only) available for jakarta instead of javax. This means that we had to upgrade many other libraries to newer versions.

New config format

We took the opportunity for breaking changes and finally simplified our server configuration. The new configuration will fully be explained in the docs and can be done via a single config.yml or environment variables (this should simplify the configuration for instances running with docker). It combines and simplifies the server configuration, the logging configuration and a lot of other sometimes hidden webapp configurations in a single file.

To give you a sneak peek of how the new config.yml could look like:

# base server config
##  Address to listen 0.0.0.0 means on every interface
addressBinding: 0.0.0.0
port: 8080
contextPath: /scm

## Evaluates headers set by a reverse proxy like X-Forwarded-For, X-Forwarded-Proto and X-Forwarded-Host
forwardHeadersEnabled: true

## increase http header size for mercurial
httpHeaderSize: 16384

# ssl config - ssl is only evaluated if key store path is set
https:
  ## path to your cert file
  keyStorePath: ""
  keyStorePassword: secret
  keyStoreType: PKCS12
  sslPort: 8443
  redirectHttpToHttps: false

# Temp directory used for jetty webserver. The temporary directory for internal operations can be configured as "workDir" in webapp.
tempDir: ./work

# logging
log:
  ## Destination of logging files
  logDir: ./logs
  rootLevel: WARN
  enableFileAppender: true
  enableConsoleAppender: true
  logger:
    sonia.scm: INFO
    com.cloudogu.scm: INFO

webapp:
  ## Sets explicit working directory for internal processes, empty means default java temp dir
  workDir:
  ## Home directory "scm-home" which is also set for classpath
  homeDir:
  cache:
    dataFile:
      enabled: true
    store:
      enabled: true
  ## Warning: Enabling this option can lead to security issue.
  endlessJwt: false
  ## Number of async threads
  asyncThreads: 4
  ## Max seconds to abort async execution
  maxAsyncAbortSeconds: 60
  ## Amount of central work queue workers
  centralWorkQueue:
    workers: 4
  ## Strategy for the working copy pool implementation [sonia.scm.repository.work.NoneCachingWorkingCopyPool, sonia.scm.repository.work.SimpleCachingWorkingCopyPool]
  workingCopyPoolStrategy: sonia.scm.repository.work.SimpleCachingWorkingCopyPool
  ## Amount of "cached" working copies
  workingCopyPoolSize: 5

Plugin Compatibility

We ensured that all SCM-Manager 2.x plugins are fully compatible and will run with SCM-Manager 3.x. The automatic migration on your first start with version 3.x could take some minutes depending on the number of installed plugins, because they have to be converted once with the built-in plugin adapter. This means you cannot downgrade afterwards. We want to mention that neither your repositories nor any data files will be processed and will not be modified.

New java version

Java 11 is outdated, as the end of life was reached in September 2023. SCM-Manager 3.x requires Java 17, which in the best case should simply be beneficial for the performance.

tl;dr

The new major version is mainly a technical upgrade. It's configuration has been simplified a lot and is now done via a single config.yml or environment variables. This is the only incompatibility which must be adjusted by an administrator.

Aside from that, the new version is fully compatible with the old one. All plugins will work as before. Also, the UI, REST API, CLI and Core APIs will not change. Most users will not notice the major version.

Support for older SCM-Manager versions

Beginning with the official release of SCM-Manager 3.0.0 we will end the support for SCM-Manager 2.x. Critical security issues will potentially be fixed, but we strongly suggest to upgrade your SCM-Manager asap. If your upgrade is blocked by the changed configuration format, and you need more options for the Jetty configuration, we will do our best to help you asap.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.48.0

Wed, 22 Nov 2023 12:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 2.48.0 (to be honest, it's 2.48.1 due to a small bug in the ui). For some of you, the most important new feature comes with an new plugin: The Custom Storage Plugin.

Custom Storage Plugin

With version 2.x of SCM-Manager we changed the way, how repositories are stored. Instead of using the repository type and name for the directory structure, we now use the id of the repository. This makes it easier to handle renames of repositories and to handle special characters in the name. But it also makes it harder to handle repositories outside SCM-Manager, like backup or using other mounted directories.

The new Custom Storage Plugin allows you to configure the directory structure of your repositories. You can use the repository type, name, id or any combination of these to configure the directory structure. You can even use a custom template to configure the directory structure for new repositories.

Signature Check Plugin

The Signature Check Plugin allows you to check the signature of commits. This is useful, if you want to make sure, that commits are signed by a trusted person.

Other changes

It is now possible to rebuild the search index and invalidate all caches in SCM-Manager. This might be useful, if you experience inconsistent data in SCM-Manager. You can find this feature in the global settings.
The Repository Size Plugin will now load the sizes of the repositories one by one. This should provide a better user experience, if you have a lot of repositories or very big ones.
You, the community, found a bug regarding the branch protection in the review plugin. This is fixed now.
If you are using the SSH Plugin, you can now set your preferred protocol for the information page.

... and a lot of other small improvements and bugfixes. Please make sure to update your plugins, too!

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.47.0

Thu, 12 Oct 2023 12:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 2.47.0. Alongside this core release we have released over 10 plugin upgrades improving accessibility and fixing various bugs.

Repository List Overhaul

We are continuously evaluating the accessibility and usability of our user interface to provide the best possible experience for all kinds of users. In this iteration, we have refactored the repository list on the landing page to meet modern accessibility standards and be more clear in its communication. Additionally, users can now collapse individual namespaces which is persisted while browsing the application.

We have also improved our checkboxes, the chip input, all our new card layouts, the global search bar and several plugins with similar goals in mind. Check out the Review Plugin for example.

What's next

This will be the last planned feature release before we are bringing out a new major version of the SCM-Manager. In this release, we are tackling an important upgrade of our core dependencies to future-prove the system. Most if not all plugins should work out of the box but the core might need some manual adaptions if you are using custom jetty configurations. We are going to release more information in the accompanying blog post once it's ready.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.46.0

Fri, 25 Aug 2023 17:00:00 GMT

Dear SCM-Manager Community,

today we released the new version of the SCM-Manager 2.46.0. This release focused on fixing bugs issued from the community, reworking ui components and releasing two new plugins.

UI Rework

We have finally finished the rework of the branches, tags and pull requests views. They are now using the new card based layout, which is heavily focused on better UX and accessibility. As always we are depending on your feedback, so that we can be sure, that we are moving to the right direction.

Mustache Template Plugin

For a long time SCM-Manager has supported Mustache as a template engine. But most users had the issue not knowing how to actually use the feature. Therefore we developed a plugin to document the models available in the Mustache templates.

Repository Size Plugin

One important information that was missing in the SCM-Manager, is the actual size of each repository. SCM-Manager repositories not only consist of the repository data but also include metadata, LFS files and some internal temp files for operating the repository. You can now see the actual sizes on the repository information page

Administrators can get an insight of every repository size on one consolidated list.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.45.0

Tue, 18 Jul 2023 17:00:00 GMT

Dear SCM-Manager Community,

apart from some new features and bugfixes, we focused on the UI performance of SCM-Manager in the last weeks and we would love to get feedback for this. So keep on reading and check out, whether you can improve your experience.

Performance

To be honest, the increased number of plugins slowed down SCM-Manager a bit when there are many repositories to handle. Especially the landing page could take a while to load. So we figured out that it is time to take a look at the overall performance. We identified three major fields, where we could do something:

Stores: One benefit of SCM-Manager from our point of view is, that it is independent of any database engine. You do not need to set up a Postgres or a MySQL database alongside SCM-Manager and there is no need for additional back-ups besides the scm-home directory. A downside on this is, that handling lots of XML files (which are used by SCM-Manager to keep its data) takes its time.

To increase performance on this, we added caches for all XML based stores in SCM-Manager. To use this caching, you have to enable this explicitly by setting the property scm.cache.dataFileCache.enabled to true for data caching and scm.storeCache.enabled, to enable caches for configurations.
Authorization: While processing a request, SCM-Manager checks permissions quite often. We detected a bit of overhead here, because internal models were copied internally without explicit need. We cleaned this up and on the way clean up logging a bit.
Waterfall-style requests: When the landing page is installed, its features like favorite repositories, tasks, and other items were triggered only after the actual repositories have been loaded. There is no reason for this, so now all parts of the landing page will start loading at once and the full page should be present faster.

Java 17

In addition to the performance improvements, we updated our docker images and the rpm and deb packages to use Java 17 by default. If you run into any issues with this, please feel free to contact us! We hope, that using Java 17 might lead to additional performance improvements, too.

Default Merge Message

If you use the review plugin to improve your development process, you might find it useful to use custom commit messages for merge pull requests. Now, you can configure custom templates for this. For these templates, we use the well established Mustache template engine.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.44.0

Fri, 09 Jun 2023 17:00:00 GMT

Dear SCM-Manager Community,

the new version comes with some improvements. This includes the tag overview, the review plugin and the webhooks.

Tag Overview

The tag overview of your repository comes with a slightly new look. Functions, such as deleting a tag, are now hidden behind a three-point menu. This is a change that will be implemented in the future on other views, such as the branch and pull request overviews. Especially there it should provide a better overview.

Review plugin

The new version of the review plugin introduces some new features. It is now possible to provide pull requests with labels, such as 'feature' or 'bug', and default tasks, such as 'Update documentation' or 'Update changelog'. Furthermore it is possible to configure a default merge strategy. In addition, configurations can now be made at the namespace level.

Webhooks

The webhook configuration shines in a new design, which should significantly increase the clarity when creating or editing a webhook.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.43.0

Wed, 12 Apr 2023 17:00:00 GMT

Dear SCM-Manager Community,

the new version fixes several bugs reported by you. We want to especially mention that we fixed the frontend bug with SVN externals which was accidentally broken some releases ago. Also, we improved the permission handling for Mercurial so that most extensions which were unsupported should work now with SCM-Manager. Thanks again to Matt Harbison for the suggestions on how to optimize the extension support.

Audit Log

A new feature we added is the Audit Log for SCM-Manager. You can activate it by downloading the new plugin. It keeps track of all changes which create, modify or delete data in SCM-Manager. Repository configurations are also tracked but repository internal changes are explicitly ignored since they already version themselves.

Images in diffs

Another new feature that was missing for quite a long time are images for diffs. You will now see your rendered image files for single changesets, using the compare view and also for pull requests diffs. We are already planning to add more view modes for these images like "dynamic slider".

Accessibility: New UI libraries

SCM-Manager is free to use and available for many platforms. But we also want it to be accessible to use for most users which is certainly not an easy task to do. Some first steps were to create multiple themes and improve keyboard navigation. Right now we are creating new UI libraries for SCM-Manager development. We hope it will not only improve the UI/UX but also boost our development speed and maybe even motivate new plugin developers to write own extensions.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.42.x

Fri, 17 Feb 2023 17:00:00 GMT

Dear SCM-Manager Community,

after almost a month, we have a new version for you. You might notice that there is already a bugfix version 2.42.1. The reason for that was a conflict between the updated svn library and our ssh plugin. We fixed this immediately and thus released version 2.42.1.

Apart from that we want to inform you about two new features: a new permission overview, new possibilities for webhooks and the selection of PR default reviewers.

Overview for Permissions

As there are many permissions to manage within the SCM-Manager, it can get quite cluttered and confusing which permissions are set for different users and groups. Additionally, users can be sorted into groups via external systems such as LDAP or CAS. Until now, admins could not access an overview over such external groups.

To tackle those two problems, the new version comes with an integrated permission overview. The overview can be accessed via the information page for each user. Within this overview you can see all groups that a user got assigned to at their last login. Underneath you will find a table with information on all namespaces and repositories which have permissions directly set for the user and their groups.

Headers for Webhooks

A frequently asked for feature were headers for webhooks, which we now implemented in the Webhook Plugin. Assigned passwords can be concealed, so they will neither be stored as clear text nor shown on the user interface.

PR Default Reviewer

With the release, you now have the option to save default reviewers for pull request. Default reviewers can be selected in the section Pull Requests under the Pull Request Configuration. Please note that this is a repository specific configuration. For each pull request the default reviewer is pre-selected, but can also be de-selected if needed. This feature is located in the Review Plugin.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.41.0

Mon, 23 Jan 2023 17:00:00 GMT

Dear SCM-Manager Community,

you haven't heard of us for two months now, but we haven't been idle all the time. Last week, we released version 2.41.0 of SCM-Manager with two features requested by you, our community.

Configurable repository list

Some of you want to change the amount of repositories on the startup page or hide archived repositories. You can do this now with the Landingpage Plugin. If you have not taken a look at it before, now it is the time to do so. Besides the ability to change the page size or to hide archived repositories, it can also show the latest activities, information about pull requests and you can mark repositories as favorites so that they are always at the top of the first page.

You can find the new configuration options by pressing the small settings icon next to the header "mySCM" on the top of the repository page. There, you can also deactivate features you do not want to use.

Image resolution in Markdown

Maybe you are as great a fan of Markdown as we are. Then you will most probably be glad to hear about our latest fix: Relative image paths in markdown documents will now be displayed correctly in the previews. This also holds true for the Review Plugin.

Small fixes

You may notice other smaller fixes, for example sticky file headers in diff views or that the namespace is preselected whenever you create a new repository after you selected a namespace.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.40.0

Tue, 22 Nov 2022 17:00:00 GMT

Dear SCM-Manager Community,

in the following few paragraphs we have summarized some of the changes and features available in the new release. We have also fixed a series of complicated bugs and are actively preparing to make new integrations with third-party systems easier in the future.

Keyboard Shortcuts

Over the last month we have worked tirelessly on the previously announced keyboard shortcut system. We hope these will allow users to move around quicker and speed up their workflows, saving time in the process.

You can open the context-sensitive list of shortcuts available to the active user on the current page by pressing ?.

Otherwise, you can always look things up in the documentation.

Enhances LFS Support

For some time now, SCM-Manager supports LFS for git. With this release, LFS files will also be handled correctly in the repository import. So if you want to move your repository with LFS files from another repository manager to SCM-Manager, this now is easier than ever. Just click "Add Repository", select "Import Repository", enter the URL of your old repository and some credentials (if necessary) and you are on your way.

Good News for Plugin Developers

We love to support our community in the implementation of new ideas. Below, we listed some new public APIs released alongside 2.40.0 you might find interesting. Please open a question in our forum whenever you need a kick-start for your new plugin or if any of the new features are unclear.

Shortcuts API

The Shortcuts API is simple to use and open for plugin developers. For further information on how to use it in your plugin, please refer to the documentation available in @scm-manager/ui-components.

Extensible Webhooks

We released an update to our Webhook Plugin that allows developers to create integrations tailored to their needs.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.39.0

Thu, 15 Sep 2022 14:00:00 GMT

Hello SCM-Manager Community,

over a month has passed since our last feature release during which we have taken the time to round up some significant additions to our global search. Two brand-new plugins are ready for you in addition to several quality of life improvements and bugfixes.

Global Search

We focused again on the global search for SCM-Manager. This time we created two new plugins for you. With the Commit Search Plugin all your repository commit messages will be added to the search index. On the other hand the Binary Search Plugin is very useful if you work with the common office document formats like Excel, Word, PowerPoint and many more. Using Apache Tika the textual content of these files is parsed and also added to your search index. But keep in mind that depending on the size of your repositories these two plugins could impact your instance's performance.

Besides that we added some additional convenience features like more detailed documentation and the new Reindex button to refresh your repository index manually.

What's coming next ?

We are currently working hard on integrating keyboard shortcuts to first the search and then to other parts of the application. As with any newly trodden terrain, we want to move carefully and ensure proper function and quality before making it available in our next minor release.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.38.0

Mon, 08 Aug 2022 14:00:00 GMT

Hello SCM-Manager Community,

we continuously put in the effort to improve the SCM-Manager. This iteration focused on extensions to the CLI, contextual search and additional information for the pull request overview.

Due to complex changes to our underlying frontend build infrastructure, we experienced unexpected problems with local plugin builds after the release. We have implemented a solution and released it under 2.38.1, but none of this negatively impacts production instances.

CLI Extensions

It is now possible to manage plugins and permissions to the same extend to which it is possible through the web interface.

Contextual Search

We made our global search context-sensitive, which allows you to search in a specific namespace or a specific repository directly.

Enhanced Pull Request Overview

Improvements were made to both the Review- and the CI-Plugin that add additional columns to the Pull Request table. They provide information on the status of the workflow engine as well as the current CI-status.

SSH Plugin

We bumped the version of the underlying library sshd from 2.5.1 to 2.9.0. This was required because Ubuntu 22.04 could not handle the SSH keys with the "outdated" RSA algorithm. This update caused a breaking change we were not aware of. The default host key algorithm was changed from RSA to EC automatically and the host keys were regenerated. This caused a lot of trouble because all systems had to accept the changed host keys.

To prevent this issue for everyone else, we added a config field which keeps the previous host key algorithm. If you want to upgrade your algorithm, you need to manually change your host key algorithm in the SSH config via the UI.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.37.0

Wed, 29 Jun 2022 14:00:00 GMT

Hello SCM-Manager Community,

with every fresh release come new, exciting features that we do not want to keep from you. Beside the usual bugfixes, we want to highlight three additions/changes this time.

Git-LFS Support when Mirroring Repositories

A quite subtle, but much requested feature that we had to exclude in the initial implementation of the repository mirroring feature due to complexity. It caused our team many headaches, but ultimately we tamed the beast. Now, you can reap the benefits by mirroring from sources that include git-lfs files. Yes, that includes SCM-Manager 1.x instances!

Try it right now!

New Plugin: External File Links

The latest addition to our plugin roster is useful especially for integrations with external file storage systems, where you do not want to duplicate data but would still like to include a quick reference in your source code or documentation.

It adds a button to the source action bar where you can simply enter the external file's url and a file name for your link and voilà, you just created a new external file link.

Of course, editing links is also possible and works quite similar to editing any other file through the Editor Plugin.

To visit one of those links, open the file and click the button that is boldly presented to you.

We made it work this way to keep the plugin compatible with other functionality in the SCM-Manager, as a file link internally is just an ordinary file with a specific format.

Check it out!

Updated Email Templates

Last but not least, we have performed a long-overdue tidy-up of the email templates in our Mail Plugin.

Just to give one example, expect the pull request related emails sent by your Review Plugin to look that much neater!

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.35.0

Thu, 02 Jun 2022 14:00:00 GMT

Hi SCM-Manager Community,

with the new release of SCM-Manager we made some significant changes we have to tell you about. Most importantly, if you still use Java 8, now is the time to update your system.

Java 11

From version 2.35.0 on, SCM-Manager has to be run at least with Java 11. If you still use Java 8, this is the time to update, not only due to SCM-Manager, but also because Java 8 is out of maintenance. We have eagerly anticipated this for a long time, because now we can use some nice new features of the more recent Java releases.

Plugin Wizard

For those of you that are about to set up a new server, you will notice an additional initialization page: a plugin wizard. We have thought about different use-cases of the SCM-Manager from personal usage up to large development teams. We've done this, so that you can get the best experience possible from your SCM-Manager.

Command Message Check

For some time now, we have the Commit Message Checker. With this, you can make sure that your commit messages comply with pre-defined rules. Though this is useful, it still may be tedious, when you have created a bunch of commits locally before pushing them and are just then being reminded of the rules. With our new CLI client it is now possible to create a pre-commit hook that will check you commit message against the SCM-Manager server and doing so will ensure, that your commit will not be rejected afterwards.

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.34.0

Fri, 13 May 2022 14:00:00 GMT

Hi SCM-Manager Community,

we have done some serious spring cleaning in the last couple of weeks which included many improvements in the areas of accessibility and user experience as well as a large number of bugfixes.

There is too much to cover it all but a small selection of tweaks and new features are showcased in this blog post. For the full list, please head over to our changelog.

New Docker multi-arch builds

Did you know that you can also use the SCM-Manager with Docker ? Our official images are available on Dockerhub and from this version forward, we are releasing additional linux builds for arm64 and arm/v7 architectures. It future-proves our build-pipeline for broader application possibilities and if you ever wanted to run your SCM-Manager in a Docker container on a Raspberry Pi, this is also for you!

Ignoring changeset CI status in Pull Request workflow rules

Overall our workflow engine for pull requests is performing as intended, but there was an edge case where a build-breaker carried over when branching which resulted in the pull request having failed workflow rules based on CI status, even if the target branch did not contain it anymore. The rule simply checked both the changeset and the pull request and if any of them were unsuccessful, it failed. To fix this, we added a new checkbox to all workflow rules regarding CI status' that allows you to disable changeset checks and only verify the PR status for a particular rule.

The action bar in the source view has been struggling with an ever-increasing number of buttons due to new features added from plugins over the last couple of months. It is not tragic yet, but could soon pose a problem and is already borderline unsightly on small and medium screens. We therefore implemented a new overflow menu that hides secondary actions and frees space in the action bar while still giving plugin developers full control where to place their actions. All Editor Plugin actions are now displayed in this menu, but the File Lock Plugin for example still displays the lock state outside the menu as a primary action.

Visibility of selected lines in source view

Since we recently first introduced the High Contrast and then shortly after the Dark themes for the SCM-Manager, some pages needed additional attention. When creating permalinks for a line of code in the source view for example, the code line is highlighted with a different background color. This worked well in Light Mode but the default values were not optimal for either High Contrast Mode or Dark Mode. The challenge we faced was keeping both the contrast between page background and highlighted line as well as the contrast between highlighting color and the actual text at a readable level. This proved close to impossible which lead to a compromise: the selected line now has an additional bar on the left side which provides visually impaired users a clear indicator that stands in stark contrast to the page background while the background color of the highlighted line is tuned to ensure optimal readability.

High Contrast Mode

Dark Mode

Light Mode

Closing words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.33.0

Fri, 29 Apr 2022 14:00:00 GMT

Hey SCM-Manager Community,

today we can proudly present the first version of the SCM-Manager CLI client. We also fixed lots of small and some bigger bugs which were reported by you.

CLI

We and some community members have been wishing for a dedicated CLI for SCM-Manager for several years, and we finally got the opportunity to build a first version of it. The CLI client is available for many package managers and as a direct download on our website. We even support FreeBSD to support our power user Will Senn. The client is mostly self-explanatory, there is nevertheless a documentation for the setup and the general concepts behind it.

In the first version we focused on administrators and allow to manage repositories, users and groups. The CLI client already supports templating for many commands and provides translations for English and German.

To give you an idea of how the CLI could be used:

We already have more ideas to add for the CLI like plugin management, permission management or repository clone. If you miss anything for your workflows or scripts don't hesitate to give us feedback.

Syntax Highlighting

Syntax Highlighting is a very big topic for SCM-Manager since we have different components which rely on this like Diff, Global Search, Blame View or File View. One bigger issue we had on this was that the browser happened to freeze with some huge files.

We managed to fix this issue by disabling the syntax highlighting dynamically if some certain threshold was exceeded. Therefore it may occur that some of your files will no longer be highlighted properly. Before your browser would simply crash, so this should be the better solution.

We actually have an idea to enable syntax highlighting on any file size but this is very complex, and we will deal with it in the future.

Final words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.32.0

Thu, 10 Mar 2022 14:00:00 GMT

Hey SCM-Manager Community,

for the last month we focused on theming as we introduced the new dark mode. Besides, we worked on giving you the opportunity to provide feedback directly from SCM-Manager.

Dark mode

As high contrast mode targeted accessibility we also were in need for a more relaxed dark theme. The new official dark mode has more relaxed colors which might help if you have to code late at night.

Feedback

We would like to get more feedback from you, and therefore we tried to make it more simple to provide us feedback directly. You can use the button in the lower right corner to display a form and easily submit your thoughts, suggestions and compliments.

Disclaimer: The data you provide will only be used by the SCM-Manager development team and will not be shared with third parties. For further information check out our Privacy Policy.

Final words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.31.0

Fri, 18 Feb 2022 14:00:00 GMT

Hey SCM-Manager Community,

for the last month we worked on our backends and improved some stuff you hopefully should not notice. Therefore, this new release contains mostly smaller improvements and bugfixes.

Collapsing empty directories

One new feature we've added is collapsing empty directories in the repository source view. You can still access these collapsed directories via the breadcrumb navigation.

We have been working on the big topic of "accessibility" for quite some time. Many of the requirements such as screen reader support or better keyboard support were more complicated than we expected. Although we will never stop working on accessibility, we should be done with the initial rebuild and can focus more on new features again. If you are depending on it, we are grateful for any kind of feedback.

Final words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

XML-Parser Expat (CVE-2022-23852)

Wed, 02 Feb 2022 12:00:00 GMT

Hey SCM-Manager Community,

Maybe you have heard about a new vulnerability regarding Expat which is likely as dangerous as Log4Shell.

The SCM-Manager is only affected if you have the PlantUML-Plugin installed. We highly recommend uninstalling this plugin until we can provide a fixed version. If your SCM-Manager is running inside the Cloudogu Ecosystem you also need to take down the PlantUML Dogu.

Also find the related forum post here.

SCM-Manager 2.30.0

Mon, 24 Jan 2022 17:00:00 GMT

Hey SCM-Manager Community,

you may have read our last blog post warning you about a Path Traversal vulnerability in SCM-Manager. If you haven't already, please update your instance to the latest SCM-Manager version as soon as possible to fix this issue.

Alerting

We have already been working on an alert system that will warn you directly in your instance when a vulnerability is found that affects your installed SCM-Manager core and plugin versions. To make sure you don't miss any important patches, each user is notified of existing security vulnerabilities. These alerts in the header will only appear if there are known vulnerabilities that affect your installed versions.

Compare

Another code related feature we have added is 'Compare'. You can now create diffs and list changesets between two branches, tags or revisions. This function can be found on the branch/tag detail page and at the top of the source viewer.

Note: For revisions you can use the shortened version, but it must be a unique identifier. Example: use 0b4c742 instead of 0b4c7429265cee9277766ddbbb2ad9a87f058d42.

Autocomplete

SCM-Manager uses the autocomplete component in several forms. We have taken into account the feedback we have received about this component over the past few months and have revised it. The biggest change for you should be that we now use autocomplete for repository namespaces in the creation form.

Final words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

Path Traversal Vulnerability

Mon, 17 Jan 2022 17:00:00 GMT

Hey SCM-Manager Community,

thanks to an attentive user, we got notice of a path traversal vulnerability in SCM-Manager. Affected are all versions from 2.0.0 up to 2.29.0.

We released a hotfix 2.29.1.

Update now!

Your SCM-Manager Team

SCM-Manager - Recap 2021

Mon, 03 Jan 2022 10:00:00 GMT

Hey SCM-Manager Community,

It's the first Monday of the new year, and we just started working on the next major features to improve your SCM-Manager experience. But before going forward we wanted to do a little recap and share our SCM-Manager highlights of 2021.

Recap

We had 16 feature releases in the last year including these big changes:

Repository Import and Export for Git, HG and Subversion
Frontend refactored to utilize react-query which dramatically improved performance
Metrics for SCM-Manager which can be collected with the related plugins as JSON or OpenMetrics
Global Notification System
Repository Mirroring with the Repository Mirror Plugin
Global search for most entities in SCM-Manager
Complete overhaul of the repository overview
Added High Contrast Mode and improved accessibility in general
Introduction of the Cloudogu Plugin Center (with more features to come)

Besides the core changes, we also created some useful plugins which can lift your SCM-Manager workflows up to a new level. We cannot go into the details of all the new plugins here, but we strongly recommend having a look at the following:

Gotenberg Plugin - Renders office files like Word or Excel inside your SCM-Manager file view
Landingpage Plugin - Adds additional relevant information to each user's repository overview page
Content Search - Enables search for content inside files of your repositories

Blog Post Series

The SCM-Manager is getting bigger and more complex with every release. We are aware of this and work on making plugin development easier and more accessible for everyone. If you are interested in developing your own SCM-Manager plugins we would love to share our knowledge with you and support your plugin.

Some months ago we released a guide on how to create your first SCM-Manager plugin. You can read this three part series on the Cloudogu Blog. It is based on the development of the Custom Links Plugin.

Final words

Even with the world going crazy it seems the last year was not that bad for SCM-Manager. We still have many cards up our sleeves to deliver many exciting features. If you would like to share this journey with us, feel free to join our community and provide your input.

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.28.0

Thu, 23 Dec 2021 10:00:00 GMT

Hey SCM-Manager Community,

some time has passed since 2.27.0, and the hassle around log4shell brought us some bugfix releases (because we use logback and not log4j, we had some less severe issues in SCM-Manager). But now it is time for a new feature release 2.28.0.

Branch Details

If you take a look at the branches for a repository, you will find small graphs to tell you, how many commits a branch is ahead and/or behind in regard to the default branch. And if you use the review plugin or the ci plugin, you will also find information about pull requests and the current build status of the branch.

Move/Rename

Don't want to clone a repository just to rename a file or directory? Now you can do this with the editor plugin. We hope you will find this useful.

Fixes

The high contrast mode had some issues like unreadable colors in the user/group select component for example. We fixed the flaws in the core (and we promise to fix the remaining bugs in some plugins soon).

And the next time you use the search functionality, you may notice some changes too, like code syntax highlighting if you have installed the content search plugin.

Final words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

Log4Shell

Mon, 13 Dec 2021 09:00:00 GMT

Hey SCM-Manager Community,

We're sure you've heard about the vulnerability in log4j called Log4Shell. As far as we can say, SCM-Manager is not affected by this, because log4j is not used in SCM-Manager (for logging, we use Logback).

However, if you have installed plugins from external sources, you can check whether log4j is used somewhere by running this little script using the script plugin:

println org.apache.logging.log4j.core.lookup.JndiLookup.class.protectionDomain.codeSource

If you get the following error, everything should be fine:

javax.script.ScriptException: javax.script.ScriptException: groovy.lang.MissingPropertyException: No such property: org for class: Script0

If log4j is available, you will get the name of the library.

Feel free to contact us if you have further questions. You can contact the DEV team directly on GitHub and make sure to check out our new community platform.

Update (2021-12-15)

On December, 14th the Logback team released a patch that removed a potential vulnerability. This can be exploited, if the attacker has write access to the logback configuration file. Although this should not be possible with SCM-Manager out of the box, we still recommend to upgrade to version 2.27.3 of SCM-Manager, where we have updated this dependency.

SCM-Manager 2.27.0

Wed, 17 Nov 2021 15:00:00 GMT

Hey SCM-Manager Community,

once again we improved the accessibility by cleaning up our html structure and improve the screen reader support. Besides, we also created two new plugins which may be useful for your workflows with SCM-Manager.

Gotenberg Plugin

Some weeks ago we learned about Gotenberg as an easy-setup, powerful server to convert office binary files like docx, xlsx and pptx to pdf. We created the Gotenberg Plugin to integrate this mechanism into SCM-Manager. Now all binary files which can be processed by Gotenberg are directly show as pdf inside your SCM-Manager.

Word Document

Excel Sheet

PowerPoint Presentation

Configuration

For this to work you have to start a Gotenberg server and configure it in SCM-Manager. Example docker-compose.

If your SCM-Manager is running inside the Cloudogu Ecosystem, you can install the Gotenberg Dogu for free and restart SCM-Manager. The plugin will be automatically installed and configured for you.

File Lock Plugin

The second new plugin we want to introduce is the File Lock Plugin. This plugin enables frontend support for the file locks we introduced in version 2.26.0. It can be helpful to lock files, especially binary files, if you are editing them. This way other users will know the file is currently locked by you and can not be edited without unlocking it before.

If someone tries to overwrite your locked file by uploading a newer version, a warning will appear. Locked files can be unlocked by every user with write permission to the repository to prevent locking files longer than needed.

Other changes

Upgrades to Webpack 5 and Node 16
Improved screen reader support
Show repository contact in the overview
Fix minor ui glitches after introducing the high contrast mode

Version 2.27.1?

Right after we released version 2.27.0, an SCM-Manager community member reported to us that the frontend bundles are broken. This is a nasty error between Webpack 5 and the plugins we use. It is really hard to reproduce, but we think that we have fixed it. If you also got errors on the SCM-Manager frontend, please let us know.

Final words

Are you still missing an important feature? How can SCM-Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM-Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

Java 11

Thu, 11 Nov 2021 11:11:00 GMT

Hey SCM-Manager Community,

Java 8 has been around for quite a long time now and it has served SCM-Manager quite well. But everything has come to an end.

So today we are here to tell you, that we will quit support for Java 8 in March 2022. We chose this date, because according to Oracle the support for Java 8 will end then, too. So, if you still run SCM-Manager on Java 8, you should start your transition to Java 11, which will be our next target platform.

If you already run on Java 11 (or above), or use Docker, there is nothing you have to do. If you use our Debian or RPM packages, these would force you to install Java 11, if you still run on Java 8. For those using the unix or windows packages, please make sure that you have installed Java 11.

We do not expect any issues. Nonetheless, if you run into some, feel free to contact us on our community platform.

SCM-Manager 2.26.0

Fri, 05 Nov 2021 15:00:00 GMT

Hey SCM-Manager Community,

we would like SCM-Manager to be accessible for as many users as possible. We aren't there, yet, but we have taken some major steps. Maybe the most obvious one: You can change your theme.

Accessibility

As well as it might seem so, our first goal was not to create a dark mode, but a theme with high contrast. You can change your preferences on your profile page. Turning colors inside out is no easy task (aside from the technical requirements). But you have to start somewhere, so we present this new design knowing, that we still have some flaws like the header in the source view. We will tackle these in the next releases, so please stay patient.

The high contrast mode now looks something like this:

And for those who depend on screen readers, we have some advancements, too: We have added lots of alt tags and made errors accessible.

We would love to get feedback from you!

PDF Preview

From this release on, we will show PDF files in the file view, just like images.

LFS Lock Protocol

For fans of Git LFS, we have implemented the file lock protocol. Mind that you will not see those locks in the frontend, but we are working on this right now.

Final words

Are you still missing an important feature? How can SCM Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager v1 Plugin Center

Wed, 27 Oct 2021 09:42:42 GMT

Hello SCM-Manager Community,

On June 04, 2020 we released SCM Manager v2 in the first stable version. That was 510 days ago. Today we decided to shutdown the PluginCenter for version 1 on April 30, 2022, and we also disabled access via http today.

What does this mean for running 1.x instances?

Running instances will continue to run without interruption. Installing and updating plugins will only be possible via https until the April 30, 2022. From May 01, 2022 on, it will no longer be possible to install or update plugins for v1 at all, but running instances will of course continue to run.

How can I make sure that my v1 instance uses https?

To make sure that your instance uses https to access the PluginCenter, the URL under Config -> General -> Plugin repository must start with https and not http. Normally the URL should look like this:

https://plugins.scm-manager.org/scm-plugin-backend/api/{version}/plugins?os={os}&arch={arch}&snapshot=false

If the URL uses http, SCM-Manager will only show the installed plugins on the plugins tab and not the ones from the plugin center.

It's time to upgrade!

If you still have running 1.x instances, now is the right time to upgrade to v2. Take a look at our migration guide. If you still have questions, we are happy to answer those in our forum.

SCM-Manager 2.25.0

Fri, 22 Oct 2021 15:00:00 GMT

Hey SCM-Manager Community,

With the new version 2.25.0 we have completely redesigned the landing page. We also fixed some minor bugs and added some minor features to various plugins. Our next big topic will be accessibility aka a11y. Here we will improve keyboard navigation and screen reader support, and we have already started to create our new theme High Contrast Mode which is actually dark but not the Dark Mode.

But let's talk about what the current version includes.

Landing Page Plugin

SCM-Manager already provided a Landing Page Plugin which adds a new start page before the repository overview. This page showed all user related information like favorite repositories, open tasks and recent events in SCM-Manager. We improved this landing page by merging the widgets like the favorite repositories into the repository overview. Also, we added a configuration to let you choose which widgets should be shown on your personal repository overview.

NEW LANDINGPAGE

Tell us how you feel about these changes and what else we could do to improve your efficiency working with SCM-Manager.

Custom Links Plugin

We created a new plugin which allows you to add custom links to your SCM-Manager footer. You can add your imprint, legal pages or some instance related links, so every user can reach them.

Initially, the Custom Links Plugin could only be installed manually via the Community Forum. It can now be found on its plugin page along with its installation instructions.

Minor changes / bug fixes

We added a conflict check for the Editor Plugin to prevent overwriting files if someone else has already changed them.
We added another specific permission with write access for the SSL Context Plugin.
The footer is now also displayed on the login page.
The Repository Template Plugin can now automatically mark repositories as templates by using the corresponding action in the repository settings.
It is no longer possible to delete the default branch of a repository as this may cause several problems in SCM-Manager.

Final words

Are you still missing an important feature? How can SCM Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager 2.24.0

Thu, 07 Oct 2021 15:00:00 GMT

Hello SCM-Manager Community,

Since SCM-Manager is mainly concerned with repository management, our target audience is mostly from the IT field. However, during the development of SCM-Manager we found that other fields like engineers, craftsmen, scientists and office workers also want to use this tool for their purposes and workflows. SCM-Manager is a repository-focused tool, and we have no plans to change that. Nonetheless, since it is already possible to write plugins for almost anything without bloating the core of SCM-Manager, we would like to support other users besides developers and administrators. That's why we developed two new plugins that will make it easier for non-IT people to work with the SCM-Manager.

History Download Plugin

The History Download Plugin is more like a shortcut for a feature which was already technically possible. On the sources view you can see the files inside a repository. Click on the new icon to expand history view with all versions of this file and the direct download links. You see the 10 latest changes but can fetch more results as you click on the bar below.

This feature was requested by SCM-Manager users who wanted to access their binary files directly from the sources view.

Manage Folder Plugin

The Manage Folder Plugin is perfect for people who are used to working with directories. By default, Git and Mercurial don't know directories at all, only files and paths. We wanted to make creating new directories and deleting entire directories more intuitive for office workers (similar to the Windows Explorer). To realize this feature with the different clients Git, HG and SVN, we introduced an .scmkeep file that holds your directory structures.

By clicking on the create button a folder creation modal shows up. You can create sub-directories on one or more nested levels. Since these are repositories, each change has to be a commit/changeset. If you delete directories, all included files and sub-directories also get deleted.

Recommendation: This plugin is a great addition if you already work with the Editor Plugin.

Minor changes

We fixed some minor bugs in the global search.
We cleaned up our own frontend code and prepared for upcoming accessibility improvements.
We fixed a bug regarding incorrect encoding for SVN directories with whitespaces.

Final words

Are you still missing an important feature? How can SCM Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

SCM-Manager Public Showcases

Wed, 29 Sep 2021 15:00:00 GMT

Hello SCM-Manager Community,

Today we would like to present you our new content that we have created in the last weeks. By now there are already over 40 plugins for SCM-Manager 2 in the official Plugin Center. We have noticed that most users don't even know what is already possible with SCM-Manager. That's why we worked with our partner Windcloud to build a public SCM-Manager instance that anyone can access without credentials. Our first showcases with the Jenkins integration, the Redmine integration, the Pull Request flow and the Script Plugin may help you find better workflows with SCM-Manager. This is just the beginning as we will be adding more and more content requested by the community.

In addition, we have added some of our own production repositories to be further developed on this public instance. We hope this provides some insight into our own work with SCM-Manager.

Find our showcases in the Cloudogu Community.

SCM-Manager Team - Ask me anything

Fri, 17 Sep 2021 15:00:00 GMT

Hello Community,

Join us in our upcoming Ask-Me-Anything-Session! Get the chance to get to know our team and ask them all your burning questions about SCM-Manager. Give us feedback on our latest releases, tell us your wishes around new features and let us know, how the SCM-Manager is a help for your projects.

Find the forum post here!

SCM-Manager 2.23.0

Wed, 08 Sep 2021 15:00:00 GMT

Hello Community,

today we released SCM Manager 2.23.0 which brings global search to a whole new level.

Search

Search was introduced with the quick repository search bar in version 2.21.0. Version 2.22.0 comes with a details page and allows searching by users and groups. Since version 2.21.0, we have learned a lot. We've learned what we want to search for and how we want to search. These learnings have led to a complete redesign of the search API and index.

Prior to version 2.23.0, all searchable items were included in the same index and separated by a type field. However, this caused problems during analysis, especially for fields that have the same name but are of different types and should be analyzed differently. With version 2.23.0, we create a separate index for each type. We have developed an API that makes it easier to handle multiple indexes.

The new version prepares the search and its APIs for new types of plugins:

Pull Requests (Review Plugin)
Comments (Review Plugin)
File Contents (Content Search Plugin)

File content search will get its own blog post soon.

Since the first version of the search it was possible to search in simple or expert mode.

Simple mode

Simple mode is the default setting and means that you enter the word you are searching for and that's it. The search looks for the entered value in a set of standard fields for each searchable type, e.g: Simple search looks in the namespace, name and description fields for the repository type.

If you want to make your search more specific, you should take a look at the expert mode.

Expert mode

Expert mode is automatically used when you enter a : in your query, since the : is the separator between the field and the value. With the expert mode it is possible to search explicitly in certain fields, for example:

type:git

returns any repository of type git.

It is also possible to use operators to create more complex queries, such as:

type:svn AND creationDate:[1577833200000 TO 1609369200000]

The above query will return all svn repositories created in 2020.

You may wonder how to remember the syntax and how to know these fields. For this reason we have created a special syntax help page.

Syntax page

The syntax page explains how to use the SCM Manager expert search. It lists operators, modifiers, wildcards, groupings, etc. It also shows the types that are searchable in your SCM Manager instance (types depend on permissions and installed plugins). Each type is listed with its fields, descriptions and some examples.

Central work queue

During the development of the Content search plugin, we encountered several problems with the old indexing API. The main problems were too much memory consumption and the order of indexing tasks. This problem has led to another new API, the central work queue. This new API should handle most asynchronous, long-running tasks in the future. In the first version, it is only responsible for the various indexing tasks.

What else?

There were a lot of minor user interface changes around quick search and detailed search. We have also improved how things are indexed, for example before 2.23.0 it was not possible to search for values with a hyphen.

Besides the search

There were a few bugs you reported that we were able to fix with this version, e.g:

The request method was lost on the Force Base Url Redirect
The login page was broken when the login info response could not be parsed.

Final words

Are you still missing an important feature? How can SCM Manager help you improve your work processes? We would love to hear from you about what you need most!

Do you have any questions or suggestions about the SCM Manager? Contact the DEV team directly on GitHub and make sure to check out our new community platform.

New SCM-Manager Community Platform

Sat, 04 Sep 2021 15:00:00 GMT

Hello SCM-Manager Community,

we are happy to finally announce our new SCM-Manager Community Forum. This platform connects SCM-Manager users and SCM-Manager developers, as this is where you can ask your questions, discuss ideas for new features with us, or create content to share with the community.

It's still a little early, but we plan to fill the platform with life in the coming weeks and months. The success of SCM-Manager is measured by the satisfaction of the users and the easy, smooth operation and management of this tool. That's why we continue to count on your valuable feedback and have created this new platform for you and for us.

We have had several opportunities to have a direct exchange with some of you recently. From this we have taken new ideas and especially improvement requests for the usability of the SCM-Manager. You may have already seen a small part of it, e.g. the repository overview. We would like to thank all supporters once again and invite all other SCM-Manager users to connect directly with the SCM-Manager development team.

What are you waiting for? Check out the new platform!

Survey - New Mercurial features

Wed, 01 Sep 2021 15:00:00 GMT

Hey SCM-Manager community,

as we progress with the SCM-Manager development we have figured out that we should integrate some more features for Mercurial to keep up with our Git development. But since we don't want to bloat SCM-Manager with unused gimmicks, we are not sure which features are actually desired by the users.

We created a short survey were you can tell us exactly which features you want for the next SCM-Manager releases. We will try our best to deliver your most voted features asap.

Take the survey here

SCM-Manager 2.22.0

Fri, 30 Jul 2021 15:00:00 GMT

Hey SCM-Manager community,

today we present you the next iteration of the new omni search and also the new design of the repository overview. We also added powerful caching for internal working copies and fixed some bugs you reported.

Omni Search - Details Page

With the last release, we added the search for repositories using the omni search in the header. Now, with the new release, we've added a button to show More Results additionally to the repositories shown as quick results. This leads to the new search details page which shows all search results categorized by the result type. If you search for repository descriptions, we also added highlighting inside the matching text fragments.

Tell us what you think about the new features and also stay excited since we've just started to implement the code search, so you can search inside your repository files, soon.

UI Redesign - Repository Overview

After the header, we have now redesigned the repository overview. We hope it is now clearer and easier to use. We really need your opinion on this, so please give us feedback on how you like our changes.

Caching for Working Directories

This feature is still experimental and a little hidden. Now you can activate caching for the internal working copies. This is especially helpful if you work a lot with the editor plugin or the review plugin, since it boosts the performance dramatically.

Try it out following our documentation.

Other changes

We fixed the file detection for hg repositories if directory and files were named the same
We decreased the log level of DefaultAdministrationContext from info to debug
We designed a new logo for the small header
We removed the repository short links on the overview since they were not used at all.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.21.0

Wed, 21 Jul 2021 15:00:00 GMT

Hey SCM-Manager community,

we took another big steps in the SCM-Manager development. We are really excited to tell you about the newest changes.

Omni search

One huge feature that we missed so far in SCM-Manager is the omni search. As the first implementation we added a quick search to the header which you can use to search for your repositories. We are already working on the advanced searches, so you will be able to also search for users, groups, inside your code, ...

Hint: We implemented the search with Lucene, so can already use the default lucene search syntax on your advanced queries.

We started to redesign the SCM-Manager UI. This time we changed the header which is now smaller and way more responsive than before.

Initial admin user

For security reasons we no longer provide the default admin user for your SCM-Manager instance. Now you have to create your admin on your first access to SCM-Manager via the UI. To create the administrator you need an initialization token which you can find inside your server log.

Hint: For automatic deployments you can create the administrator user automatically by setting the username and password with system properties. Check out the initialization documentation.

Other changes

The date on the repository overview is now the last modified date of the repository.
With the newest version of the editor plugin you can create files in empty repositories.
Improved cache invalidation when creating/deleting gpg keys.
Cloudogu plugins are now included in the SCM-Manager plugin center.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

Secure Code Warrior Plugin

Tue, 15 Jun 2021 15:00:00 GMT

Hey SCM-Manager community,

We are proud to inform you about our newest (and first) official partnership with Secure Code Warrior. As part of our cooperation, we created the SCM-SCW-Plugin which integrates the Secure Code Warrior learning material into SCM-Manager. Besides GitHub, SCM-Manager is the second exclusive integration with Secure Code Warrior support.

Who is Secure Code Warrior?

Secure Code Warrior offers a platform that provides developers, as well as others that are interested in security, with knowledge about security vulnerabilities. We think that their approach of using gamification and micro-learning works very well, because it sensitizes developers to the major topic of software security in the long term.

What is the SCM-SCW-Plugin?

The SCM-SCW-Plugin brings parts of the Secure Code Warrior knowledge into your SCM-Manager. We focused mainly on two scenarios for the first implementation, both of which depend on pull requests you may know from the SCM-Review-Plugin.

Scenario 1: Pull Request Description

A developer from our team has found a critical SQLI (SQL Injection) security bug in our code. He fixes the vulnerability on a new bugfix branch and creates a pull request in our SCM-Manager.

Issue: Unfortunately, no other developer has knowledge about SQLI and therefore cannot verify his changes.

Solution: As soon as the title or description of the pull request contains keywords related to the security-related fix, such as SQLI, Secure Code Warrior learning content will be shown directly on the pull request. Now the reviewers can learn about SQL injection before reviewing the changes.

Scenario 2: Pull Request Comments

A developer from our team creates a new feature regarding sql statements. He also pushes his feature on a new feature branch and creates a pull request in SCM-Manager.

Afterwards a reviewer checks the new features and finds some issues in the code. There is an attack vector which can be exploited with SQL injection using user-controlled inputs. The reviewer creates comments describing his findings in the pull request.

Issue: Now the developer needs to understand how this vulnerability works and how to fix it.

Solution: As soon as the reviewer posts comments which contain special keywords like sqli or SQL injection in the pull request, the Secure-Code-Warrior-Plugin adds matching content from Secure Code Warrior in an additional comment.

Where can I download this plugin?

This plugin is completely free and doesn't need an account for Secure Code Warrior. But since it is not available in the official SCM-Manager plugin center, it has be downloaded and installed manually.

Find out more about the plugin and how to install it in the official documentation. Register and download the SCM-SCW-Plugin from the cloudogu platform.

SCM-Manager 2.19.0

Tue, 08 Jun 2021 15:00:00 GMT

Hey SCM-Manager community,

with release 2.19.0 we have prepared SCM-Manager for two new plugins we hope you will find useful: The SSL context plugin and the repository mirror plugin.

SSL Context Plugin

For a long time SCM-Manager offers lots of plugins providing connections to other services such as Jenkins, Jira, Mail, and so on. Of course these connections should be secure, hence use TLS encrypted connections. In some environments, it still can be a challenge to create or get valid certificates accepted by a default Java installation.

With the new SSL contex plugin you can now inspect and (if they look legit to you) approve certificates that have been rejected by SCM-Manager.

Mirror Repositories

Some releases ago we introduced the import of repositories. Now we've taken the next step: You can now create so-called mirror repositories with the SCM repository mirror plugin (for Git and SVN). Such a mirror cannot be modified. Instead, it will create a clone of another repository and fetch changes in configurable intervals. In contrast to for example git clone --mirror, you can specify which branches and tags to mirror and set other preconditions.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.18.0

Thu, 06 May 2021 15:00:00 GMT

Hey SCM-Manager community,

in the newest release we mostly fixed bugs and improved our own development cycles. Nonetheless, we have two new features we wanted to point out to you.

Global Notifications

When developing features in the past, we have come across the need for a global notification system. This can be especially useful when a user triggers an asynchronous, time-consuming process and navigates to another page, such as repository export. In short, we added a global notification system consisting of toast messages and a notification feed.

PATCH endpoints

SCM Manager 2 can be controlled to a large extent via the REST API. A gap in our REST API were PATCH endpoints, which allow to update data partially. This is especially useful for configurations when only a few fields need to be changed. We addressed this issue and created a PATCH endpoint for the global SCM Manager configuration as a first step.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.17.0

Thu, 22 Apr 2021 15:00:00 GMT

Hey SCM-Manager community,

A new release is ready, bringing avatars for repositories, health checks, and some more fixes, especially in plugins.

Repository Avatars

Ever got lost in an SCM-Manager with lots of repositories? Then it's time to allow your imagination run free: With the new avatar plugin you can set avatars for each repository. Either use the default avatar build from the first letters of the namespace and name, choose from a collection of different icons, or import your own image (jpeg, png, gif or svg, even animated).

Health Checks

No matter how hard you try, your infrastructure may break in one place or another. From version 1.x you may remember the health checks. Those are back now. At startup, SCM-Manager checks some basic stuff like the existence of directories, so that you will get quick feedback for example when your mounted drive is missing. These checks can be triggered from the settings dialog whenever you have a the feeling something may be wrong. These manual checks may also run some more in-depth checks, depending on the type of the repository.

Fixes

Since the introduction of react-query in release 2.15.0, some plugins had the issue of involuntary reloads on focus changes. These should be fixed, now (for example for the OpenAPI plugin or the script plugin).

Another more tempting change regarding markdown views leeds to better and more secure sanitization of markdown content by including rehype.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.16.0

Fri, 26 Mar 2021 15:00:00 GMT

Hey SCM-Manager community,

We have made some radical changes in the last releases, and sometimes this breaks things. So we have not come around of fixing some more or less minor bugs the last weeks. But of course we also have new nice features for you: To reveal internals, we have added lots of metrics for you to explore, and for all users with non-ascii languages and all friends of emoticons we have relaxed the rules for namespaces, groups and usernames: You can now use nearly all Characters coming to your mind.

Checkout the newest release to find about everything that changed.

More Metrics

To make it short: You can now get metrics for

http requests,
authentication,
executor service,
caches,
work directories, and
events (there are lots of them)

Feel free to tell us, if you miss something.

UTF-8

It all began with a request, whether it would be possible to use Cyrillic letters for group names. What we ended up with is the support of UTF-8 in groups, usernames and namespaces. No idea how to call your namespaces? Now you can do this (but use it with care):

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.15.0

Fri, 12 Mar 2021 15:00:00 GMT

Hey SCM-Manager community,

with the new release it is now possible to search for filenames inside your SCM-Manager repositories, and with metrics you can gain insights into your SCM-Manager server. Checkout the newest release to find about everything that changed.

Search for files inside repositories

Finally, it is possible to search for files and directories within repositories. To search for a file, you can click the search icon next to the file path in the source view of the repository. On the file search page, you can enter parts of the name or the directory you are looking for. The search is based on the file path only and hits in the file name are ranked higher than hits in the path.

Tell us how you feel about the search function!

Partial diff

Another issue that noticeably affected performance was loading changesets with a lot of added/changed/deleted files.

We solved this matter by loading the changes in chunks. You will see 25 changed files directly and can load more by clicking on the button at the bottom.

Metrics

This new feature set should be especially interesting for administrators running SCM-Manager. We created a generic API which collects and provides metrics. The first set of metrics contains jvm metrics like memory, threads and garbage collection.

You can get the metrics as JSON or for Prometheus using the related plugin.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.14.0

Mon, 01 Mar 2021 15:00:00 GMT

Dear SCM-Manager community,

A month has passed, and we have been very busy implementing new features for you. We have focused on two larger areas during this time period to get the biggest improvements for everyone using the SCM-Manager on a daily basis.

Wrapping up Export & Import

We first started the import topic mid December and with this release finished the whole thing. It has been an enormous amount of work for a rich feature-set. We are proud of the results and would love you to give it a try.

Frontend Performance

We have had a lot of feedback both internally and from the community about the user interface feeling sluggish. We listened carefully and used the opportunity to remove tremendous amounts of bad legacy code while rewriting other parts to be more readable. The biggest benefit to the users, of course is the introduction of the stale-while-revalidate pattern to our whole frontend application. While not always being literally faster, the perceived performance, and the performance when switching back-and-forth between pages has improved drastically. We now display cached data for every screen and re-fetch up-to-date data in the background. Users will not notice this but instead the whole interface will feel quicker and more responsive.

For further information please have a look at the official react-query documentation.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.13.0

Fri, 29 Jan 2021 15:00:00 GMT

Dear SCM-Manager community,

it has been some time since we have released the last version of the SCM-Manager at the end of last year. This was over four weeks ago. Rest assured we were not in hibernation but used the time to tackle some larger features which we now proudly present to you.

Extended Export & Import

We built upon the rudimentary export functionality we implemented for subversion in the last release. Now it is possible to export repositories of any type, subversion, git and mercurial. Optionally you can export the repository compressed and/or with additional metadata. Please be aware that the export with metadata is still experimental and should not yet be used for backups.

An exported repository archive contains additional repository-specific data. Through the metadata-import this data can be imported.

PlantUML Plugin

We created a new plugin which extends our markdown renderer by allowing you to write PlantUML codeblocks that will be automatically rendered in the markdown view.

This is very useful for visual documentation of processes and interactions.

Permalinks

It is now possible to create a permalink to the active path in the source code view, may it be file or directory, by clicking the button on the left-hand side of the breadcrumbs navigation. The created link will be automatically copied to your clipboard. For all your sharing needs!

Gradle

The transition to Gradle as our primary internal build tool has taken quite some time. It is a major improvement but there is still some way to go. Some of the benefits include much better performance of our build pipeline and increased usability for our development team. Any plugins which are still written for Maven can be migrated towards Gradle with our dedicated tool.

Closing Words

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.12.0

Thu, 17 Dec 2020 15:00:00 GMT

Dear SCM-Manager community,

two weeks have passed, and again we have another SCM-Manager release: 2.12.0. We have four gifts for you, and one for us: Those of you using Mercurial can expect a much more simple setup, SVN users can now import SVN dumps, and all of you together can use a feature known from 1.x again: the archived repository. Last but not least you now can create links for specific code lines in the source view. And of course we fixed some bugs, for example an error when you wanted to take a look at files with non-ascii characters in their names.

Mercurial

Again and again people seeked help for not working Mercurial setups: Sometimes a path was wrong, sometimes the configured python version mismatched the one used by Mercurial, and so on. This should belong to the past now. We managed to simplify the somewhat complicated setup used to start Mercurial processes. You no longer need to specify a python binary, because the communication layer between the SCM-Manager and the Mercurial process is now implemented as an extension. We would love to get feedback for this one.

Import of SVN dumps

With the last release we introduced the import of git and Mercurial repositories from other servers. Now we added the possibility to import SVN dumps.

Repository Archival

You may have known this feature from version 1.x, now it's available in 2.x again: You can mark repositories as "archived". Such repositories cannot be modified any longer.

Permanent Links for Lines

Sometimes you want to point to a concrete line number in a source file, for example to send it to a colleague in a chat. Now you can simply create a URL for a line. Simply click on the link icon that you will see when you hoover over a line number. The generated URL will contain the line number and the current revision, so that the link will still work after the source has been changed.

Gradle

The gift we made for ourselfs is this: We start migrating our builds from Maven to Gradle. With the increasing code size of SCM-Manager our builds took more and more time, slowing down our development speed. In a first step we created the Gradle SMP Plugin to build our plugins with. We will now collect practical experience with this, but the first look is promising.

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.11.0

Fri, 04 Dec 2020 15:00:00 GMT

Dear SCM-Manager community,

today we released version 2.11.0 of SCM-Manager. Two big features are the import of git and mercurial repositories from URLs and the creation and deletion of tags after our changes to the branch views in the last release. Talking of branches: These are now separated into "active" and "stale" branches.

Import Repositories

When you create new repositories you can now choose to import other repositories (for now git and mercurial). To do so, click "Add Repository" and then select "Import repository" on the top right of the page. Here you can select the type (for now git or mercurial) and then you can enter a repository URL (for example from GitHub). If this repository is not public, you can enter username and password, too. Finally you just have to name the repository. If you installed the landingpage plugin you will see the result in the "Latest activities", with the mail plugin you will get a mail.

Create and Delete Tags

Like for branches, you now can create and delete tags in SCM-Manager. To delete a tag, you can press the bin icon in the overview or press "Delete tag" in the detail page for a tag. To create a new tag, you can use the little "Create Tag" button on the top right of a changeset detail view.

Active and Stale Branches

When you open the branches overview, you will notice that there are two tables: First there are the "Active Branches" below you will find "Stale Branches". We deem branches as "stale", when the latest commit of this branch is 30 days behind the latest commit of the default branch.

Hook Simplification

Last but not least we changed the way mercurial hooks are processed in SCM-Manager. The new communication is way more simple and we removed a theoratical vulnerability on the way.

Jenkins Plugin

Though this is no direct part of SCM-Manager, we want to point to our Jenkins Plugin. Using this you can create pipelines for single repositories and complete namespaces in Jenkins, trigger builds for branches, tags and pull requests automatically and more.

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.10.0

Fri, 20 Nov 2020 15:00:00 GMT

Dear SCM-Manager community,

our latest minor release is out now. Recently we released some new useful plugins for you which can improve your SCM-Manager experience. However we are also working on the SCM-Manager and adding more and more missing features.

Delete Branches

You can finally delete your branches via the UI. Keep in mind that deleted branches cannot be restored from the SCM-Manager.

Pull Request Validation

Using the SCM-Review-Plugin the SCM-Manager supports working with pull requests. We improved the validation and performance for the creation of new pull requests. Now you will be immediately informed if your selected branches for your new pull request are invalid.

REST API Documentation

With the SCM-OpenAPI-Plugin the SCM-Manager provides an easy-to-use REST API documentation integrated with Swagger. Unfortunately this automatic generated documentation wasn't as understandable as we expected. So we improved the endpoint descriptions and added some examples for the usage of our core API.

Improved Error Messages

Working with SCM-Manager you can limit access to repositories and enforce workflows using various plugins. If you do so, it is likely you may encounter some errors, for example when your commits were rejected because they do not fulfill the requirements which were defined using the SCM-Commit-Message-Checker-Plugin. In these cases we want to show you the exact reason why a error occured.

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.9.0

Fri, 06 Nov 2020 16:00:00 GMT

Dear SCM-Manager community,

in today's release we extend debugging capabilities, improve integration with external authentication systems and make a step towards a more inclusive and neutral codebase by giving you the option to name your default branch for git. We set the default to main (previously master). We hope this encourages our users to also evaluate their own codebases.

Trace API

Debugging is an important task and a good debugging system helps users and developers to pinpoint potential issues quicker and save time in the process. Because of that, we introduced a new tracing api that captures internal and external requests and gives you a neat visual representation of what is happening on the server.

The table can be sorted and filtered and details for dedicated requests can be retrieved for further inspection.

We currently implemented the core api and base functionality, but plan to extend this to include more detail and further catogries by integrating it into our plugin ecosystem.

User Converter

We introduced a new system in this release which allows you to enable a user converter that, as the name suggests, automatically converts users that have been created through the SCM-Manager UI (internal) to external users when they login through a third-party authentication system such as LDAP or CAS.

You can also convert users manually back and forth.

The current state is displayed on the user.

External users do not have a password and can therefore not log in through SCM-Manager directly.

When a user is converted to an internal user, you have to provide a password, so the user can log in again.

Default Branch Setting

It is now possible to define the default branch for all new repositories in the administration settings. This does not affect already existing branches, but should give you flexibility when migrating away from the obsolete master default. Please note that this only works, when you initialize your new repository.

General improvements and fixes

We have also fixed a series of nasty bugs that some of you might have experienced:

Cloning mercurial repositories with api keys does no longer lead to an unauthorized error even if permissions are set correctly
The option for cloning repositories via ssh for anonymous users is no longer visible in the ui as it is not possible anyways
You can now download public files through the rest api as an anonymous user with additional clients such as curl or postman

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.8.0

Tue, 27 Oct 2020 16:00:00 GMT

Hello SCM-Manager community,

in the recent releases we provided some comprehensive features to improve your experience using SCM-Manager. This time we took a step back and worked on our general code base.

Syntax Highlighting

SCM-Manager provides several code editors and code viewers which already support syntax highlighting. We managed to unify the syntax highlighter formatting. The color changes are particularly noticeable. Working on this we also reduced the size of the frontend bundles which will improve your overall frontend performance.

Fullscreen Mode

One new feature is the fullscreen mode. This should be pretty self-explanatory. See your file content or diff in fullscreen mode.

General improvements and fixes

As mentioned, a lot of our focus went on general improvements and bugfixes. Some of them are:

The email address is no longer required for user (frontend validation changed).
We fixed the syntax highlighting for the programming language go.
SCM-Manager plugins can now expose ui components to be shared with other plugins.

Are you still missing an important feature? How can SCM-Manager help you to improve your work processes? We would love to hear you most needed features!

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.7.0

Fri, 09 Oct 2020 16:00:00 GMT

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.

Personal API Keys

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 READ, WRITE or OWNER on creation.

SCM-Archive-Plugin

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.

SCM-Commit-Message-Checker-Plugin

And we also created an entirely new plugin for you which may not amuse your developers. The 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.

Submodules

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.

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.6.0

Fri, 25 Sep 2020 16:00:00 GMT

Hello SCM-Manager community,

some time has passed and we created some new features.

Namespace Permissions

Recently we added the possibility to filter your namespaces. Now we went one step further: you can manage your repository permissions on namespace-level. Just click on the blue gear icon and find the namespace permission settings.

Tags overview

If you missed it already it is finally here. The list of tags is now shown on your repository.

Latest release information

To keep your SCM-Manager up-to-date you will be informed about the latest release on the admin information page.

Merge with Rebase

The Review-Plugin already could merge your pull requests with different strategies like merge commit, fast-forward if possible and squash. Now we added the merge with rebase to keep your history nice and clean.

SSH Access Token Command

Also we added a new command in the SSH-Plugin which returns a valid access token with user permissions when called. This access token can be used for rest api calls.

Have some questions or suggestions for SCM-Manager? Connect directly to the DEV-Team on GitHub or our Support channels.

SCM-Manager 2.5.0

Fri, 11 Sep 2020 16:00:00 GMT

Hey,

we improved the general usability and workflow by adding some new features which you may checkout with this release.

You can now filter your repositories by namespace.

Also we created a new plugin which can improve your workflow by creating template repositories. A template repository is defined by adding a template definition file. Right after you may use your template to initialize new repositories.

Feel free to check out the new features and leave us a comment.

SCM-Manager 2.4.0

Fri, 14 Aug 2020 09:42:00 GMT

Today we are releasing the next minor version of the SCM-Manager with a number of exciting new features that we want to share in this blog post with you.

Full anonymous access

It is now possible to allow unauthenticated users to access parts of the SCM-Manager web interface (it was previously already possible for the api). The anonymous mode can be activated globally, either for ui and/or api. A new _anonymous user can then be granted permissions on a global or repository level, just like any other user.

Jumping to source code from diff

New button links to the source code are now available in the diff view of all commits, merges and pull request. This eases the review process by reducing the number of clicks a reviewer has to make to get to the file before and after a proposed change.

Full support for gpg signatures

Whenever a commit is made through the web interface of SCM-Manager for the first time, a new gpg key-pair is generated for the active users which is automatically used to sign any subsequent changes. Custom public keys can also be managed through a new administration page. Commit signatures and their status are displayed as a key icon directly next to the change.

Closing words

For the full changelog please visit the download page.

Server maintenance

Mon, 03 Aug 2020 12:10:42 GMT

On Thursday 06-08-2020 at 07:00 GMT+2 we will update the following parts of our infrastructure:

oss.cloudogu.com
packages.scm-manager.org

This can cause interruptions when downloading SCM-Manager and installing or updating plugins. The maintenance work should not take longer than a few hours.

SCM-Manager 2.3.0

Thu, 23 Jul 2020 16:00:00 GMT

With this new release we improved the general stability of SCM-Manager as we fixed some minor bugs. Also the documentation was updated on several topics like the SSL configuration or the Reverse proxy configuration.

It may seem obvious but we decided to show line numbers on most code viewers/editors. Feel free to leave us some thoughts about the changes or drop us a hint what you would love to see next.

We are already working on some new major features. Stay excited for the next versions.

SCM-Manager 2.2.0

Fri, 03 Jul 2020 11:09:42 GMT

Since SCM-Manager 1 it has been the most wanted feature, and now finally you can change the namespace and the name of your repositories. Just take a look at the new "Danger Zone" in the repository settings.

Another little feature is the capability to link to commits/changesets in other repositories in your commit messages and markdown documents like READMEs. Just use the format namespace/name@revision, eg. cloudogu/scm-manager@1234567.

Thanks to you, we were able to find and fix some bugs regarding the installation on various operating systems as well as the migration process. Keep this going.

SCM-Manager 2.1.0

Thu, 18 Jun 2020 15:21:49 GMT

With the release of 2.0.0 we did not stop. We just took a deep breath and continued doing what we love most. So here it is, version 2.1.0 of SCM-Manager, bringing to you some really nice new features.

New Features

Expandable Diff

It is now possible to expand the gaps between the so-called “hunks” in file diffs. So whenever you wondered where this closing bracket came from or how a chapter ends, you now don’t have to navigate to the original file.

Annotate / Blame

With the new annotate feature you now can see for each line of a file, who changed the line and when it was changed the last time. If you move over the annotation you can get even more information, including a link to the changeset.

Contributors

We improved the changeset details view. As you can see in the screenshot, all contributors of the changeset are shown grouped by their role. By now the contributors are getting detected from git trailers, git committer and may be expanded by plugins, e.g. Pushlog Plugin.

End User Documentation

As a start we managed to create a bunch of user oriented documentation for the core of SCM-Manager (e.g. for administration) as well as for many plugins (e.g. for the review plugin).

Lots of fixes

All of our work would be meaningless without users, and that is without you. We are grateful about the amount of feedback we receive. An important part of the feedback are error reports. In this release we were able to fix most of your reported issues. You are a great community. Please keep up with this.

Some of the fixes include an updated mercurial library to support newer versions of hg, a fix in the migration process when you used custom repository locations for your SCM-Manager v1, some UI fixes, and more. Have a look at the changelog for more information.

SCM-Manager 2.0.0

Fri, 05 Jun 2020 14:42:49 GMT

Good news, we made it. Before running out of numbers for our release candidates, we finally released version 2.0.0 of SCM-Manager.

It took us nearly 10 years, over 10,000 commits and 8 release candidates.

What’s new?

To be honest, more than we can explain in a single post, but we will try! In the next chapters we will give you an overview of the most important changes. More detailed blog posts and documents will follow.

Things that did not change are the reliable foundations, the easy installation process, the minimal maintenance, and the extensibility to match your specific needs.

But now, allow us to proudly present to you, what we at Cloudogu build for you over the couple last years.

Frontend

The most obvious change is the new user interface. We recreated the whole UI from scratch. The 1.x UI was based on ExtJS, which worked great, but by now its look is somewhat outdated. The good thing about ExtJS was, that it is possible to override any UI element from a plugin, which is great in terms of extensibility, but not really maintainable if you want to evolve the core. The new frontend stack is entirely based on React and Bulma and it has well-defined extension points, which make the whole site easier to maintain.

But enough about the technical background, here are some screenshots of the new UI:

Plugins

We created a whole new package format for the plugins, which should fix all the problems with v1 plugin installations. With the new format, only a single file has to be fetched, and the server can restart on its own.

We migrated 25 well-known plugins that were available for v1 (like jenkins, redmine, jira, ldap, cas, branch-wp, and so on). Additionally we also created a few great new plugins for you that were not possible with v1.:

Review Plugin

With the review plugin you can implement a branch based peer review process: Develop new features on a branch, create a pull request where you describe your changes, and let a peer developer inspect these changes. You can write comments for the whole pull request, for single files and even for changed lines. Finally, you can merge the branches inside of SCM-Manager. With the help of the CI plugin you can enforce complex workflows, for example to ensure, that Jenkins builds have been run successfully and only working code will be incorporated.

Editor Plugin

Have you ever wanted to make a small change in a repository? Like updating a README (which by the way can be displayed by the readme plugin) or uploading a new file? Now you can use the editor plugin to do so.

SSH Plugin

You are done with constantly entering your username and password? No problem, use the ssh plugin with an ssh key.

Landingpage Plugin (MySCM)

Sometimes it gets hard to keep track of important things. This is, where our new landingpage plugin comes into play: On a single page you can see your tasks, the latest events and relevant data like your favorite repositories.

OpenAPI Plugin

We are proud of the new level 3 REST API, and we would like to enable you to use it. Instead of writing a big documentation we give you an open API plugin to explore all the possibilities interactively.

Permissions

The permission model of SCM-Manager v1 was limited to the distinction between admins and users and it only used roles you could assign for single repositories. With version 2 you can now assign finly grained permissions, both globally and repository specific. The details about this are definitely a topic for another document.

Repository URLs

One of the most annoying things in v1 was the fact, that the URLs for the repository ui and the one for the checkout/clone are different. With SCM-Manager 2 we wanted to change this. In order to fix this problem, we had to introduce a limitation for the repository names. In v1 it was possible to create repositories with any depth (a/b/c). This makes it really hard to add an ui to the same path, because it is nearly impossible to differentiate between the name of the repository and technical routes. So we decided to introduce namespaces. In SCM-Manager 2, a repository identifier consists of two parts: the namespace and the name of the repository. The namespace can be auto generated with a strategy (e.g. current username, year, repository type) or can be chosen freely.

This change fixes the routing problem and removes the technical ids from the urls (which were nearly omnipresent in v1). For your convenience, we tried to create redirects from the old urls to the new ones if you migrate from v1 to v2.

Versioning

You may have noticed a little detail in our new version number: We moved from 1.60 to 2.0.0, that is, from now on we use semantic versioning.

Getting started

Want to get it right now? Head over to our new download page. You have the choice:

Docker
Kubernetes
Debian/Ubuntu
Red Hat/CentOS/Fedora
Generic Linux
Windows
Mac OS X

There is no excuse to not getting started today.

If you want to migrate from v1, please have a look at the migration instructions.

New website

Tue, 02 Jun 2020 15:23:49 GMT

Today we reached another great goal on our road to the 2.0.0 release.

We released our new website 🎉🥳

Our old website was a somewhat outdated wordpress blog. The blog was fine, but it does no longer match our needs. In the development process of SCM-Manager we use pull requests a lot, so we want to use that workflow for our website, too.

At that point it was clear that we need a completely new website which matches our needs. So we decided not only to create a new home for the blog and the marketing stuff, we decided to create a central place for nearly all SCM-Manager related information:

So we created a new pretty and blazing fast website. The new site is based on GatsbyJS, a static website generator which matches all our needs.

With the new website we decided also to remove the comment support from the site as announced at the Cloudogu support team post.

Documentation

The documentation is fetched from the docs folder of the SCM-Manger repository, and the docs for the plugins are fetched from the individual plugin repo. We know the documentation is far from complete, but we will work hard to fix that.

Contribution

If you find any issue in the website or in the docs please open an issue in the corresponding repository. If you are able to fix this issue by yourself, we are more than happy to accept a pull request.

New home for scm-manager packages

Mon, 18 May 2020 14:47:49 GMT

Before launching our 2.0.0 release we decided to optimize and modernize our infrastructure. One of the first notable changes is the new packages.scm-manager.org Nexus 3 instance replacing our old Nexus 2 instance on maven.scm-manager.org. With this migration most paths have been changed. But fortunately we were able to create redirects for most cases. Only users of the debian package will get errors because a redirect was not possible.

Our recommendation for all users is to update all configurations the new repositories.

Maven:

<repositories>

  <repository>
    <id>packages.scm-manager.org</id>
    <name>scm-manager public repository</name>
    <url>https://packages.scm-manager.org/repository/public/</url>
  </repository>

</repositories>

Yum/RPM (for SCM-Manager v1 only):

[scm-releases]
name=SCM-Manager Releases
baseurl=https://packages.scm-manager.org/repository/yum-v1-releases/
enabled=1
gpgcheck=0

For more detailed instructions have a look at the SCM-Manager documentation.

Apt/DEB (for SCM-Manager v1 only):

deb https://packages.scm-manager.org/repository/apt-v1-releases/ stable main

For more detailed instructions have a look at the SCM-Manager documentation.

Further Questions

If you have any questions or issues with the new repositories feel free to ask us on the mailing list.

SCM-Manager 2.0.0-rc8

Fri, 08 May 2020 18:23:51 GMT

Hey folks,

It’s been a month since our last release and today you get our newest version with some new features. Unfortunately, it is another release candidate, but we are optimistic that our final 2.0.0 release will be out soon.

The biggest change of this release candidate is the new workflow engine, which allows you to set validation rules for pull requests with the SCM-Review-Plugin. This way, you can enforce a certain workflow for merging a pull request.

The following rules can be configured with the workflow engine:

All reviewers have approved
At least x reviewers have approved
All CI status’ have to be successful (Example: All Jenkins builds have to be green)
There has to be at least x successful CI status’
All CI status’ of one type have to be successful
All tasks existing for this pull request are done

The status of the configured rules is shown in your pull request.

Some other changes we made are a new cipher which is compatible with Java 12 and above. SCM-Manager instances using the old cipher will be fully supported though. We have also introduced a new “@Requires” annotation for optional dependencies. This is especially useful if you want bind plugin features only if the dependent plugin is also installed.

As usual, you can find all changes for this version in our changelog. Feel free to leave us some comments.

You can download the RC-8 here

.tar.gz (sha1: 8bf465525d5a8c5907d1f74096af1783bc0b2fa7)
.zip (sha1: f688a9dbee45f11334fafd82f72b3636f6ad58f6)

or use it via Docker

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

SCM-Manager 2.0.0-rc7

Thu, 16 Apr 2020 09:07:58 GMT

Hey there, another two weeks have passed (can you see the pattern?), and we proudly present release candidate 7 of SCM-Manager 2 to you. Besides a fix regarding repository write requests with anonymous access enabled and other small bugs, we have a new nice plugin for you: A new landing page. We call it mySCM. If you install this new plugin, you can see all these things at a glance:

your favorite repositories
latest events regarding repositories
events and pending updates from the plugin center
your open pull requests
your tasks regarding pull requests

The last two of course only with the review plugin. Expect more things here, like for example your latest build results, because this page is easily extendable by plugins.

We think it’s nice and would love to hear your opinion on that.

You can download the RC-7 here

.tar.gz (sha1: f10fa85757f952592af40cb4856d92787fd83ed1)
.zip (sha1: 8a297dc00caec4b7497605b8c0da64dbe68a5b06)

or use it via Docker

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

Change in ownership

Wed, 15 Apr 2020 16:46:19 GMT

In Fall 2018 Cloudogu and I announced a cooperation for this project. Ever since then, a lot has changed in the background. We established a permanent SCM-Manager team at Cloudogu, which I am the leader of. That allowed us to pick up speed in the development of SCM-Manager and to take care of support cases at the same time. Thanks to that the release of SCM-Manager 2.0 is closer than ever. SCM-Manager has come a long way, and I can't wait for implementing all these great ideas that we still have.

Since almost all the development capacity for SCM-Manager comes from Cloudogu, it's only fair that the company is the official owner of the project. Therefore, we agreed to make the change. A few days ago, I handed over the project to Cloudogu.

What does that mean for you?

By handing over SCM-Manager to Cloudogu we hope to continue on the prosperous path that we have been on for more than two years now. There are still many ideas and plans that we, Cloudogu and I, want to bring to live, to make SCM-Manager even more user friendly, versatile and reliable.

Everything will continue the way it has for the last couple of years: SCM-Manager is still a community Open Source project where everyone is invited to contribute ideas and feedback. The only thing that has already changed is that SCM-Manager is now licensed under the MIT license, but that should practically have no consequences, because the MIT license is even less restrictive than previously used BSD 3-clause license.

I'm looking forward to continuing the work on SCM-Manager, discussing your feedback and ideas and implementing new features.

SCM-Manager 2.0.0-rc6

Wed, 01 Apr 2020 07:45:44 GMT

One of the core features of SCM-Manager is its extensibility with plugins. Installing, updating and removing plugins requires a restart of the SCM-Manager. And to be honest, we would not have thought this would be so hard.

After trying to destroy the complete context of the server and learning a lot about class loader leaks, we now threw this all away and moved to a more fail-proof solution with 2.0.0-rc6: On POSIX systems (that is all Linuxes and Apples) we use the LIBC by default to kill the server process and replace it with a new instance. Doing so, we keep the process id and no monitoring should notice and complain about this. However there is this other operation system, Windows, where we haven’t found a good solution for, yet. So on Windows, after installing plugins or in the migration wizard, you will get a message saying that the server has to be restarted manually. Because we are not satisfied with this, we are still working on an automated solution for Windows. If you do not trust our restart solution, you can implement your own or switch to our simple exit strategy, using startup parameters.

Further changes of 2.0.0-rc6 are mostly small extensions and fixes. In 2.0.0-rc5 a README file for example could mess up the position of the navigation menu. This should be fixed now. And having talked about Windows: The build should now be possible on these machines, again.

You can download the RC-6 here

.tar.gz (sha1: f1cdbda4615c662f9e92d5707b902c12c4907800)
.zip (sha1: 961b5ba8bca98e8b376094bc60a7bb0b7c20feeb)

or use it via Docker

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

Issue restart

Tue, 24 Mar 2020 16:58:05 GMT

Over the years, SCM-Manager received a lot of attention and a lot of people had questions. Some of them led to issues on BitBucket, which were migrated to GitHub not long ago. With the release of SCM-Manager 2 getting closer, we would like to get rid of old issues, because we would like to focus on the important, still relevant ones. So we decided to use GitHub Stale, a little bot that closes issues that had no activity for quite some time. Tickets like enhancements, will not be affected by the bot, because they may take a longer than normal issues.

If you find your ticket closed, but you feel like it still persists, we would like to politely ask you to re-open it on GitHub. If you have a new issue, take a minute or two and take a look at the old ones; maybe you will find an answer there. Doing so, we will get a better overview of which issues are still relevant and we will know what to focus on.

SCM-Manager 2.0.0-rc5

Fri, 13 Mar 2020 14:32:47 GMT

Release 2 of SCM-Manager brings a lot of changes, some small, some big. Besides the most obvious change, the completely new user interface, there is the new level 3 REST API, which took us a considerable amount of effort to create.

The new REST API allows scripts and other applications to “navigate” from the top level REST resource (/scm/api/v2) to every resource available and to change them: repositories, sources, configurations, and items from plugins like pull requests. Using the editor plugin it is possible, to add or change files in repositories without checking them out, first.

OpenAPI plugin

Of course, all these possibilities can only be fully utilized when there is comprehensive documentation. The problem is, the API may change depending on your version of SCM-Manager and the plugins you have installed. So what we give you today is not a wiki page or a pdf, but another plugin: the OpenAPI plugin. This plugin adds a new link to the footer of SCM-Manager: “Rest API”.

Click the link and you will get an OpenAPI (also known as Swagger) online documentation, that tells you exactly what is possible with your current system. It will show you all possible requests and you can even try them out.

Another change that you might stumble upon, is a little triangle in the secondary navigation menus. Press this, and the menu will collapse. This is useful in particular for source and diff views.

Normal menu:

Collapsed menu:

Limitation on source view

Another little change is something you may never notice, but nonetheless it is good to have it in place: If you ever have a repository with a large number of files, SCM-Manager will not break down whenever you try to take a look at the sources. Instead, it will only read up to 100 files per request. You can choose to read more, though.

Get the new version

You can download the RC-5 here

.tar.gz (sha1: 3b2dff3fda0c46362c518be37edd4e77bccc88bb)
.zip (sha1: 1aa865ea400e8aaf08c175dbaf316c48bb066b41)

or use it via Docker

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

We migrated to GitHub

Mon, 09 Mar 2020 10:33:12 GMT

As mentioned here, we migrated the scm-manager core repository to GitHub: scm-manager/scm-manager.

We decided to do so due to the removed mercurial support from Bitbucket. This is no statement whatsoever against Mercurial, we will continue to support Mercurial, Git and Subversion.

We migrated the entire code base from Mercurial to Git
The Bitbucket Wiki is now located in the docs folder of the repository
All issues have been migrated

SCM-Manager 2.0.0-rc4

Fri, 14 Feb 2020 13:38:26 GMT

For some time, the incompatability of SCM-Manager 2 with Java 9 or above has annoyed us. Now we can happily announce, that this is history. With the new version 2.0.0-rc4 SCM-Manager can run on Java 9 and above.

A little error though has not made it into this release: If you are hosting mercurial repositories, you cannot create new commits, when XSRF protection is enabled. This is no new bug in this version and if you haven’t come accross it with previous releases, it should be of no relevance for you (this should be relevant only if you are using the editor plugin with mercurial repositories). This bug will be fixed in the next release.

Get the new version

You can download the RC-4 here

.tar.gz (sha1: 7aa87cec712335b93b0cbc49333c5fc9edd26fdc)
.zip (sha1: 603cf76d7d685951533ad19f5e1aa990607ec3bf)

or use it via Docker

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

SCM-Manager 2.0.0-rc3

Wed, 05 Feb 2020 16:26:43 GMT

Last week we stumbled upon an error in the plugin loader. If you have installed some plugins with dependencies between them, the may end up loading them in the wrong sequence and therefore running into an error. We fixed this error with SCM-Manager 2.0.0-rc3.

If your SCM-Manager 2.0.0-rc2 is starting up without problem, you can safely ignore this new release.

Get the fixed version

You can download the RC-3 here

.tar.gz (sha1: c23d8804c10e90d45832f4af3af9a1aa8658c666)
.zip (sha1: 42b3c320ff334eda7cbc0d8f56c05978dbc0840f)

or use it via Docker

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

SCM-Manager now on GitHub

Wed, 05 Feb 2020 13:15:35 GMT

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

Wed, 29 Jan 2020 16:16:16 GMT

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

Wed, 18 Dec 2019 14:14:36 GMT

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

Mon, 14 Oct 2019 09:20:01 GMT

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

Tue, 30 Jul 2019 17:13:38 GMT

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:

GoogleGroup / Mailinglist: Use this forum for general questions.
Issue tracker: Report bugs and create feature requests here.
Stackoverflow: Feel free to use Stackoverflow for your questions, but make sure to use the tag ‘scmmanager’.

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

Fri, 28 Jun 2019 18:23:51 GMT

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.

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 or the latest Docker image.

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

Tue, 25 Sep 2018 14:57:00 GMT

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

Fri, 04 May 2018 11:33:07 GMT

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.

Download: https://www.scm-manager.org/download/
Release notes: https://bitbucket.org/sdorra/scm-manager/wiki/release-notes
Getting started: https://bitbucket.org/sdorra/scm-manager/wiki/getting-started

SCM-Manager 1.59

Wed, 11 Apr 2018 11:35:16 GMT

Version 1.59 of SCM-Manager is now available for download.

SCM-Manager 1.58

Fri, 06 Apr 2018 08:57:04 GMT

Version 1.58 of SCM-Manager is now available for download.

SCM-Manager 1.57

Fri, 09 Feb 2018 08:27:27 GMT

Version 1.57 of SCM-Manager is now available for download.

SCM-Manager 1.56

Mon, 15 Jan 2018 15:32:50 GMT

Version 1.56 of SCM-Manager is now available for download.

SCM-Manager 1.55

Thu, 02 Nov 2017 11:44:27 GMT

Version 1.55 of SCM-Manager is now available for download.

SCM-Manager 1.54 with git-lfs

Tue, 06 Jun 2017 14:10:21 GMT

Version 1.54 of SCM-Manager is now available for download. This new shiny version comes with experimental support for the Git LFS.

SCM-Manager 1.53

Wed, 17 May 2017 21:49:45 GMT

Version 1.53 of SCM-Manager is now available for download.

SCM-Manager 1.52

Wed, 10 May 2017 10:41:17 GMT

Version 1.52 of SCM-Manager is now available for download.

SCM-Manager 1.51

Thu, 09 Feb 2017 16:26:10 GMT

Version 1.51 of SCM-Manager is now available for download.

SCM-Manager 1.50

Thu, 24 Nov 2016 14:57:00 GMT

Version 1.50 of SCM-Manager is now available for download.

SCM-Manager 1.49

Tue, 26 Jul 2016 13:50:25 GMT

Version 1.49 of SCM-Manager is now available for download.

Warning: Version 1.49 drops support for Java 6.

SCM-Manager 1.48

Tue, 28 Jun 2016 13:31:11 GMT

Version 1.48 of SCM-Manager is now available for download.

SCM-Manager 1.47

Tue, 31 May 2016 11:52:05 GMT

Version 1.47 of SCM-Manager is now available for download.

SCM-Manager 1.46

Sun, 14 Jun 2015 20:47:06 GMT

Version 1.46 of SCM-Manager is now available for download.

SCM-Manager 1.45

Tue, 17 Feb 2015 11:28:05 GMT

Version 1.45 of SCM-Manager is now available for download.

CVE-2014-9390

Tue, 23 Dec 2014 12:55:49 GMT

CVE-2014-9390 affects git systems on case-insensitive filesystems, such as Windows and Mac OS. For more informations of CVE-2014-9390 please have a look at the git mailing list.

There are only two parts of SCM-Manager which are affected by CVE-2014-9390, the new import (introduced with SCM-Manager 1.43) and the fork-plugin. These problems are fixed with the version 1.44 of SCM-Manager. If you are running SCM-Manager on Windows or Mac OS, we highly recommend to update to the latest version of SCM-Manager.

If your git clients run on Windows or Mac OS, you have to update your git clients too.

Download latest version of SCM-Manager.

SCM-Manager 1.44

Tue, 23 Dec 2014 12:55:39 GMT

Version 1.44 of SCM-Manager is now available for download.

SCM-Manager 2 Milestone 1

Sat, 13 Dec 2014 17:02:44 GMT

After a long development time SCM-Manager 2 reaches milestone 1. Here are the main features of the first milestone of SCM-Manager 2:

Server

With version 2 SCM-Manager will switch to Semantic Versioning. All upcoming SCM-Manager 2 versions and plugins will use the MAJOR.MINOR.PATCH scheme for their version numbers.

Repository Cleanup

Deprecated and used modules, packages, classes, methods and fields are completely removed from the repository. Some modules are renamed to match their maven artifact id. The following modules are moved to their own repositories to get the repository smaller and to improve release cycles:

scm-plugin-archetype
scm-plugin-backend
smp-maven-plugin formerly known as scm-maven-plugin

Event handling

The handling of events in SCM-Manager 2 is now controlled only by the Subscribe annotation, the old style listener classes are removed. In addition we switched from the Google Guava EventBus to Legman. Legman is a fork of the Google Guava EventBus, which fixes some problems of SCM-Manager with the Google Guava EventBus. Have a look at the list of fired events (TODO update link) by SCM-Manager all of them can be handled like below:

@EagerSingleton
public class Listener {

  @Subsribe
  public void handleEvent(PostReceiveRepositoryHookEvent event){
    // handle event
  }

}

Java and bundled Jetty (scm-server)

With version 2 we will switch to java 7, older versions of java are no longer supported. With this step we are able to use the java7 package from JGit, which should bring a performance boost for all SCM-Manager git operations. We will also update Jetty from version 7 to version 9.2.x. This update will give us opportunities like WebSockets and SPDY.

Performance, startup and appserver compatibility

We have dropped all classpath scanning operations in favor of a annotation processor. The annotation processor will store all classes which are annotated with Extension, ExtensionPoint, Subscribe or Path annotation durring the compilation. This change results in a shorter startup with a lower memory footprint, because we don’t have to load all classes from package classpath to check for annotations. The annotation processor solves also problems with the classpath scanning on some application servers.

Plugins

The plugin system of SCM-Manager 2 is completely rewritten. Here are some of the main features:

Structure and packaging

Plugins are no longer ordinary jar files. In SCM-Manager 2 plugins are packaged as a single smp file. The smp packages are containing classes, resources and all dependencies of a plugin. The structure of a smp file looks like this:

classes (classes and resources)
webapp (web resource like scripts, stylesheets and images)
lib (plugin dependencies)

The switch to smp packages allows us to drop the complex and error-prone Aether based plugin system of SCM-Manager 1.x. It also solves the problem with offline plugin installations.

Class and resource loading

SCM-Manager 2 creates an isolated classloader for each plugin, this protects us from classloading conflicts. The isolated classloaders also allows the override of core dependencies for plugins. The new plugins will also introduce WebResourceLoaders, which are able to load resources from the webapp directory for a plugin.

Plugin descriptor

Descriptors are now validated by dtd. The descriptors are now supports tags for later improvements to the plugin center.

Download

Warning: SCM-Manager 2 Milestone 1 is not compatible with SCM-Manager 1.x and it is not ready for production use. This release is only for testing purposes.

What comes next?

Milestone 2 will target the user/group management and the security system of SCM-Manager. The development of Milestone 2 is organised here.

Explore SCM-Manager Universe@Cloud

Fri, 05 Dec 2014 16:35:40 GMT

SCM-Manager has its own Universe. There it acts in the center of a bundle of ready to use open source software components.

Now the virtual appliance SCM-Manager Universe, which is developed by my partner TRIOLOGY, is available as a Cloud-Service. This highly scalable, most secure and deeply integrated Platform-as-a-Service (PaaS) makes developing software even easier.

Try out this new service completely for free and without commitment!

Are you interested? Register for a monthly trial here.

Repository Import Wizard

Tue, 02 Dec 2014 10:44:41 GMT

SCM-Manager 1.43 main feature is a new repository import wizard. This new wizard supports three import methods:

Import repositories from the repository directory (.scm/repositories/type). This method is supported by git, mercurial and subversion.
Import repositories from a remote url. This method is supported by git and mercurial.
Import repositories from a bundle/dump (svndump). This method is supported by subversion.

Note: Click on the images above to see the wizard in action.

SCM-Manager 1.43

Mon, 01 Dec 2014 16:21:58 GMT

Version 1.43 of SCM-Manager is now available for download.

scm-webhook-plugin 1.5

Fri, 21 Nov 2014 18:15:17 GMT

Version 1.5 of the scm-webhook-plugin is available for download.

Changes:

ability to send commit data as json post

Official docker image

Fri, 21 Nov 2014 17:56:55 GMT

The official SCM-Manager docker image has arrived the docker registry.

Here are some examples for the usage of the image:

# run the latest scm-manager version
docker run sdorra/scm-manager

# expose scm-manager http port
docker run -p 8080:8080 sdorra/scm-manager

# run a specific scm-manager version
# version 1.42 is currently the only available version
docker run -p 8080:8080 sdorra/scm-manager:1.42

# use a persitent volume
mkdir /var/lib/scm
chown 1000:1000 /var/lib/scm
docker run -v /var/lib/scm:/var/lib/scm -p 8080:8080 sdorra/scm-manager:1.42

SCM-Manager 1.42

Mon, 20 Oct 2014 10:01:07 GMT

Version 1.42 of SCM-Manager is now available for download.

SCM-Manager and the POODLE vulnerability

Sat, 18 Oct 2014 14:17:26 GMT

If you are using scm-server with a configured https connector, please be sure that you exclude the SSLv3 protocol to avoid the POODLE vulnerability.

Add the following xml elements to your https connector in your server-config.xml:

<Arg>
  <New class="org.eclipse.jetty.http.ssl.SslContextFactory">
    <Set name="excludeProtocols">
      <Array type="java.lang.String">
        <Item>SSLv2Hello</Item>
        <Item>SSLv3</Item>
      </Array>
    </Set>
  </New>
</Arg>

The complete connector section should now be look like the following:

  <Call name="addConnector">
    <Arg>
      <New class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
        <Arg>
          <New class="org.eclipse.jetty.http.ssl.SslContextFactory">
            <Set name="excludeProtocols">
              <Array type="java.lang.String">
                <Item>SSLv2Hello</Item>
                <Item>SSLv3</Item>
              </Array>
            </Set>
          </New>
        </Arg>
        <Set name="Port">8181</Set>
        <Set name="maxIdleTime">30000</Set>
        <Set name="requestHeaderSize">16384</Set>
        <Set name="keystore"><SystemProperty name="basedir" default="." />/conf/keystore.jks</Set>
        <Set name="password">yourpassword</Set>
        <Set name="keyPassword">yourpassword</Set>
        <Set name="truststore"><SystemProperty name="basedir" default="." />/conf/keystore.jks</Set>
        <Set name="trustPassword">yourpassword</Set>
      </New>
    </Arg>
  </Call>

More informations on how to configure https with SCM-Manager can you find here:

SCM-Manager 1.41

Sun, 28 Sep 2014 20:48:09 GMT

Version 1.41 of SCM-Manager is now available for download.

Changed to https

Sun, 28 Sep 2014 10:47:14 GMT

The following SCM-Manager pages are changed to https.

This pages are now only accessible over https (with spdy enabled). The other pages will follow later.

New Release of SCM-Manager Universe

Thu, 17 Jul 2014 07:43:05 GMT

There is a new release of SCM-Manager Universe is available now: “Draco- 14.7”. The main aspect of the release is an improved security for operating the appliance openly in the internet. Now you will for example be asked to configure the system during the first boot sequence:

the geographical region and time zone
the keyboard configuration
and the initial users of the appliance

Besides that the configuration of servers like Tomcat webapplication server or the MySQL server was modified, and tools were updated.

In addition to those changes the conditions for the update service were changed. From now on you only need to register at www.scm-manager.com to enjoy the benefits of automatic updates for the appliance SCM-Manager Universe.

Download of SCM-Manager Universe 14.7 – Draco: https://www.scm-manager.com/scm-manager-universe

Release Notes: https://www.scm-manager.com/scm-manager-universe/release-notes/

Further information (Release): https://www.scm-manager.com/2014/07/draco-protector-of-the-universe/

Further information (Update service): https://www.scm-manager.com/2014/07/new-registration-option-update-service/

Survey Software Development Teams

Thu, 10 Jul 2014 15:48:00 GMT

Hello,
currently Mr. Robert Finke, student at the technical university of Clausthal, Germany, is conducting an online survey, in the context of his bachelor thesis, about the software using behavior of software development teams.

The survey is absolutely anonymous and should not last longer than 5 to 10 minutes.

https://survey.scm-manager.com

Robert kindly asks you to participate in his survey.

Feel free to forward the link to your co-workers or friends.

Best regards

SCM-Manager 1.40

Fri, 04 Jul 2014 08:57:24 GMT

Version 1.40 of SCM-Manager is now available for download.

SCM-Manager 1.39

Wed, 02 Jul 2014 15:27:38 GMT

Version 1.39 of SCM-Manager is now available for download.

New Server

Fri, 20 Jun 2014 16:20:38 GMT

The following SCM-Manager pages has been moved to a new server:

www.scm-manager.org
download.scm-manager.org
docs.scm-manager.org
maven.scm-manager.org
plugins.scm-manager.org

This move was necessary to be prepared for the release 1.39 of SCM-Manager. Version 1.39 is the first release which will be delivered as RPM and DEB linux packages. To deliver those packages we will create a YUM repository and an APT repository on the new server.

scm-trac-plugin

Wed, 21 May 2014 16:35:37 GMT

The new scm-trac-plugin is now available over the SCM-Manager plugin center. It integrates the issue tracker of Trac to SCM-Manager. The plugin requires version 1.33 or newer of SCM-Manager.

One More Star in SCM-Manager Universe

Wed, 07 May 2014 13:04:53 GMT

The third release of SCM-Manager Universe is available now. It extends the appliance by a SingleSignOn (SSO) solution based on the tool “Central Authentication Service” (CAS). Thanks to this system you can use the connected tools without repeating login requests, because the tools are authenticating against CAS, which in turn validates users against your authentication server (e.g. LDAP or Active Directory). For example you log in to SCM-Manager, and after that you can use Jenkins, SonarQube and Bugzilla without providing your login credentials once again.

Download: https://www.scm-manager.com/scm-manager-universe/download-scm-manager-universe/

Release notes: https://www.scm-manager.com/scm-manager-universe/release-notes/

Further information: https://www.scm-manager.com/2014/05/capella-the-new-star-of-scm-manager-universe/

SCM-Manager 1.38

Sun, 04 May 2014 16:28:13 GMT

Version 1.38 of SCM-Manager is now available for download.

SCM-Manager 1.37

Mon, 21 Apr 2014 14:42:20 GMT

Version 1.37 of SCM-Manager is now available for download.

SCM-Manager 1.36

Sun, 09 Mar 2014 15:47:43 GMT

Version 1.36 of SCM-Manager is now available for download.

Warning: Versions prior to 1.36 are creating incompatible subversion repositories, if the subversion option “with 1.7 Compatible” is enabled. Those repositories have to be converted before they could be used with version 1.36 or later. read more

SCM-Manager 1.35

Mon, 30 Dec 2013 15:17:53 GMT

Version 1.35 of SCM-Manager is now available for download.

scm-youtrack-plugin

Fri, 25 Oct 2013 13:25:07 GMT

The new scm-youtrack-plugin is now available over the SCM-Manager plugin center. It integrates the issue tracker software YouTrack to SCM-Manager. The plugin requires version 1.33 or newer of SCM-Manager.

scm-fork-plugin 1.1

Wed, 16 Oct 2013 15:15:04 GMT

Version 1.1 of the scm-fork-plugin is available for download.

Changes:

Support for pull requests, see issue 189

scm-webhook-plugin 1.4

Wed, 16 Oct 2013 15:09:32 GMT

New version of the scm-webhook-plugin is available.

Changes:

Support for global webhooks, see Q8C7vBJt1SM

SCM-Manager 1.34

Sat, 05 Oct 2013 13:34:00 GMT

Version 1.34 of SCM-Manager is now available for download.

SCM-Manager Universe Expands

Wed, 18 Sep 2013 11:30:40 GMT

The first update for SCM-Manager Universe is available now. It has its focus on improving code quality by integrating the widely known code quality management tool “SonarQube” and the scm-checkstyle-plugin into the appliance. Now the programmer automatically gets the build results in Jenkins and the code analysis results in SonarQube after he pushed changes to SCM-Manager. SonarQube is integrated into the SCM-Manager Universe infrastructure e.g. LDAP and backup. Besides that all reasonable updates of tools were performed. Find out more about it here.

SCM-Manager 1.33

Thu, 08 Aug 2013 21:08:41 GMT

Version 1.33 of SCM-Manager is now available for download.

SCM-Manager gets its own universe

Wed, 26 Jun 2013 09:21:11 GMT

The virtual appliance SCM-Manager Universe, developed by my partner TRIOLOGY, is a Linux based virtual machine, which comes with a bundle of ready to use open source software components. It has a comprehensive documentation, including tutorials, a sample project and tool descriptions. All of the software development tools authenticate against a central LDAP server with reasonable default users and groups configuration. The appliance has also a simple backup mechanism, which allows regular backups of all relevant files. Explore SCM-Manager Universe here.

scm-fork-plugin

Tue, 25 Jun 2013 09:16:15 GMT

The new scm-fork-plugin is now available over the scm-manager plugin center. It allows users to fork repositories. The plugin requires 1.32 or newer of scm-manager and depends on the scm-userrepo-plugin.

Screenshots

SCM-Manager 1.32

Mon, 24 Jun 2013 16:32:47 GMT

Version 1.32 of SCM-Manager is now available for download.

scm-htpasswd-plugin

Mon, 10 Jun 2013 14:59:49 GMT

With the scm-htpasswd-plugin you can use an apache htpasswd file for authentication in SCM-Manager. More about the plugin.

New features of SCM-Manager 1.31

Sun, 02 Jun 2013 13:07:46 GMT

Remember me

The first new feature you notice when you start SCM-Manager 1.31, is the “Remember me” checkbox.

If you select this checkbox during login, SCM-Manager will remember your login information across browser sessions.

Virtual group for authenticated users

The second new feature of version 1.31 is a virtual group called _authenticated. This group is automatically assigned to every user who is logged in. With this group you can easily create a repository which is accessible for each user which is able to login to your SCM-Manager instance.

Display access permissions to the user

SCM-Manager 1.31 displays access permissions to the currently logged in user. It shows a label with Read-Only access or Read+Write access on the repository information panel.

Global permissions

You are now able to assign global permissions to users and groups. You can choose between the following permissions:

All Repositories (read) – Read-Only access to all repositories
All Repositories (write) – Read+Write access to all repositories
All Repositories (owner) – Owner permission to all repositories

With this feature you can easily allow the user of your CI system to read every of your repositories, without to adding the user manually to the permission list of every new repository.

For a complete list of new features, updates and bug fixes please have a look at the release notes.

SCM-Manager 1.31

Sat, 01 Jun 2013 16:19:02 GMT

Version 1.31 of SCM-Manager is now available for download.

scm-pushlog-plugin available

Fri, 24 May 2013 09:12:29 GMT

The new scm-pushlog-plugin is now available over the scm-manager plugin center. The scm-pushlog-plugin tracks who pushed what to a repository.

scm-bugzilla-plugin

Mon, 06 May 2013 20:21:12 GMT

The new scm-bugzilla-plugin enables the SCM-Manager to interact with the bug tracking system Bugzilla.

New support option for business-clients

Thu, 18 Apr 2013 20:43:53 GMT

You need professional support with reliable response times via phone and email? My partner TRIOLOGY offers two different support packages for business-clients – regular and advanced. This will have no effect on community support!

The experts of TRIOLOGY will assist you through installation and in all issues, which might occur when operating SCM-Manager. TRIOLOGY ensures the continuous advancement of SCM-Manager and its plugins.

So business-clients have all benefits from both worlds: free open-source software with professional support. Use the support packages of TRIOLOGY to ensure business continuity and improve the efficiency of your development process – in other words: “Open Source. More Business.”.

If you are interested in professional support or need more information about the service of TRIOLOGY read more here.

SCM-Manager 1.30

Fri, 12 Apr 2013 09:43:16 GMT

Version 1.30 of SCM-Manager is now available for download.

SCM-Manager 1.28

Sun, 17 Feb 2013 18:55:33 GMT

Version 1.28 of SCM-Manager is now available for download.

Server maintenance from 2013-02-07 to 2013-02-08

Tue, 05 Feb 2013 14:45:28 GMT

Between 2013-02-07 and 2013-02-08, we have to do some maintenance work on the server infrastructure of SCM-Manager.

The following sites are affected of the server maintenance and could be temporarily unavailable:

SCM-Manager 1.27

Fri, 25 Jan 2013 16:21:34 GMT

Version 1.27 of SCM-Manager is now available for download.

scm-archive-plugin 1.1

Thu, 24 Jan 2013 08:11:01 GMT

New version of the scm-archive-plugin is available.

Changes:

fix download archive with specified revision, see issue #316 - 'Download Archive' button problem

scm-statistic-plugin 1.2

Tue, 22 Jan 2013 15:35:22 GMT

New version of the scm-statistic-plugin is available.

Changes:

added statistic for top words from commit messages

scm-archive-plugin

Tue, 22 Jan 2013 14:24:09 GMT

The scm-archive-plugin is able to create a zip file of a repository.

SCM-Manager 1.26

Tue, 22 Jan 2013 13:53:12 GMT

Version 1.26 of SCM-Manager is now available for download.

SCM-Manager 1.25

Fri, 11 Jan 2013 16:10:28 GMT

Version 1.25 of SCM-Manager is now available for download.

scm-scheduler-plugin

Thu, 03 Jan 2013 17:06:14 GMT

The scm-scheduler-plugin provides an api for other plugins to execute scheduled
jobs. The plugin is based on the quartz project.

Wiki: https://bitbucket.org/sdorra/scm-manager/wiki/scheduler-plugin

scm-script-plugin 1.2

Thu, 03 Jan 2013 10:52:14 GMT

New version of the scm-script-plugin is available.

Changes:

Added sample scripts to the ui

scm-statistic-plugin 1.1

Wed, 02 Jan 2013 12:59:24 GMT

New version of the scm-statistic-plugin is available.

Changes:

added option for admins to manually rebuild a statistic

scm-script-plugin

Tue, 01 Jan 2013 16:45:04 GMT

Script support for scm-manager with the scm-script-plugin

Screenshots:

scm-notify-plugin 1.1

Sat, 22 Dec 2012 13:08:16 GMT

New version of the scm-notify-plugin is available.

Changes:

use version 1.0 of the new scm-mail-plugin

scm-statistic-plugin

Sat, 22 Dec 2012 12:56:36 GMT

Build statistics for every repository in SCM-Manager with the new scm-statistic-plugin.

Screenshots:

scm-mail-plugin

Thu, 20 Dec 2012 08:15:01 GMT

The scm-mail-plugin provides an central api for sending e-mails. This plugin is primarily for use by other plugins.

Wiki: https://bitbucket.org/sdorra/scm-manager/wiki/mail-plugin

Example:

/**
 *
 * @author Sebastian Sdorra
 */
public class NotificationService
{
  private static final Logger logger = LoggerFactory.getLogger(
    NotificationService.class);
  
  private MailService mailService;

  @Inject
  public NotificationService(MailService mailService)
  {
    this.mailService = mailService;
  }
  
  public void sendNotification() throws MailSendBatchException {
    if ( mailService.isConfigured() ){
      Email mail = new Email();
      mail.setFromAddress("SCM-Administrator", "admin@scm-manager.org");
      mail.addRecipient("Test User", "test.user@scm-manager.org", RecipientType.TO);
      mail.setSubject("SCM-Manager notification");
      mail.setText("Notification from SCM-Manager");
      
      mailService.send(mail);
    } else {
      logger.warn("mail service is not configured");
    }
  }
}

SCM-Manager 1.24

Sun, 16 Dec 2012 15:32:33 GMT

Version 1.24 of SCM-Manager is now available for download.

SCM-Manager 1.23

Sat, 15 Dec 2012 18:31:44 GMT

Version 1.23 of SCM-Manager is now available for download.

scm-activity-plugin 1.8

Tue, 20 Nov 2012 07:50:11 GMT

New version of the scm-activity-plugin is available.

Changes:

show changesets from git non master branches, see issue 279

scm-auth-ldap-plugin 1.18

Sat, 10 Nov 2012 14:06:54 GMT

Version 1.18 of the scm-ldap-plugin is available.

Changes:

option to configure ldap referral strategy (follow, ignore or throw)

SCM-Manager 1.22

Mon, 29 Oct 2012 15:04:01 GMT

Version 1.22 of SCM-Manager is now available for download.

scm-jira-plugin 1.7

Mon, 29 Oct 2012 08:31:44 GMT

Version 1.7 of the scm-jira-plugin is available.

Changes:

added option for explicit jira credentials, see issue 272

scm-branchwp-plugin 1.1

Mon, 29 Oct 2012 08:27:42 GMT

Version 1.1 of the scm-branchwp-plugin is released.

Changes:

allow glob syntax for branch names, see issue 271

scm-jira-plugin 1.6

Thu, 18 Oct 2012 14:49:09 GMT

Version 1.6 of the scm-jira-plugin is available.

Changes:

Execute jira hooks asynchronous
Avoid duplicate jira comments

Note:

Version 1.6 requires SCM-Manager version 1.21 or newer

SCM-Manager 1.21

Wed, 17 Oct 2012 15:31:18 GMT

Version 1.21 of SCM-Manager is now available for download.

scm-auth-ldap-plugin 1.17

Wed, 17 Oct 2012 15:30:21 GMT

Version 1.17 of the scm-ldap-plugin is available.

Changes:

follow ldap referrals
log the user object, if the returned user is not valid

scm-jira-plugin 1.4

Tue, 09 Oct 2012 21:30:28 GMT

Version 1.4 of the scm-jira-plugin is available.

Changes:

Detect issue keys automatically
Uses SCM-Manager default template engine to render issue comments
Allow global configuration and per-repository configuration

Note:

Option to transform usernames was removed
Option for project keys was removed
Version 1.4 requires SCM-Manager version 1.19 or newer

scm-gravatar-plugin 1.4

Sun, 26 Aug 2012 14:27:53 GMT

New version of the scm-gravatar-plugin is available.

Changes:

add big avatar to commit page

Screenshot

scm-branchwp-plugin 1.0

Sun, 26 Aug 2012 14:23:42 GMT

The scm-branchwp-plugin adds branch write protection for repositories to SCM-Manager.

Wiki: https://bitbucket.org/sdorra/scm-manager/wiki/branchwp-plugin

SCM-Manager 1.20

Sun, 26 Aug 2012 14:20:44 GMT

Version 1.20 of SCM-Manager is now available for download.

scm-gravatar-plugin 1.3

Sun, 19 Aug 2012 11:43:11 GMT

New version of the scm-gravatar-plugin is available.

Changes:

added small border radius to the gravatar images

scm-activity-plugin 1.7

Sun, 19 Aug 2012 11:41:12 GMT

New version of the scm-activity-plugin is available.

Changes:

use changeset panel instead of diff panel for commit views

New plugin scm-message-regex-plugin

Sun, 19 Aug 2012 11:39:44 GMT

A new plugin scm-message-regex-plugin is now available. This plugin allows to validate each commit message using a regular expression.

SCM-Manager 1.19

Sat, 18 Aug 2012 14:32:54 GMT

Version 1.19 of SCM-Manager is now available for download.

Server maintenance at 2012-08-13

Mon, 13 Aug 2012 16:36:13 GMT

The SCM-Manager services will not be available from 2012-08-13 04:00 GMT until 2012-08-13 06:00 GMT.

The following pages are affected:

SCM-Manager 1.18

Sun, 12 Aug 2012 15:25:51 GMT

Version 1.18 of SCM-Manager is now available for download.

Note: Version 1.18 requires mercurial 1.9 or newer.

Redmine plugin available

Thu, 12 Jul 2012 08:04:23 GMT

A new SCM-Manager plugin for the project management tool Redmine is now available.

Features:

Link issue id’s in commit messages to the redmine issue tracker
Create comments for issues for every commit which contains the issue id
Automatically close an issue if the issue id and a auto-close (close, fix, resolve) word is in a changeset message

scm-authormapping-plugin 1.1

Tue, 10 Jul 2012 08:14:21 GMT

New version of the scm-authormapping-plugin is available.

Changes:

Support for mapping author names on the blame view

Note: Version 1.1 requires SCM-Manager 1.17 or newer.

scm-activity-plugin 1.6

Tue, 10 Jul 2012 08:10:52 GMT

New version of the scm-activity-plugin is available.

Changes:

Small performance improvements

Note: Version 1.6 requires SCM-Manager 1.17 or newer.

scm-auth-ldap-plugin 1.15

Tue, 10 Jul 2012 08:08:13 GMT

Version 1.15 of the scm-ldap-plugin is available for download.

Changes:

fix critical bug in authentication with enabled starttls, see issue #198

scm-userrename-plugin available

Tue, 10 Jul 2012 08:06:11 GMT

Version 1.0 of the scm-userrename-plugin is now available. This plugin allows to rename a user, inclusive all permissions.

scm-auth-ldap-plugin 1.14

Tue, 03 Jul 2012 18:42:48 GMT

Version 1.14 of the scm-ldap-plugin is available for download.

Changes:

support for starttls, see issue 198

SCM-Manager 1.17

Sun, 01 Jul 2012 16:20:45 GMT

Version 1.17 of SCM-Manager is now available for download.

SCM-Manager 1.16

Sun, 03 Jun 2012 12:39:31 GMT

Version 1.16 of SCM-Manager is now available for download.

New webhook plugin available

Sun, 03 Jun 2012 12:38:52 GMT

Version 1.0 of the scm-webhook-plugin is now available. The plugin can notify a remote webserver whenever a repository is pushed to.

Wiki: https://bitbucket.org/sdorra/scm-manager/wiki/webhook-plugin

scm-activedirectory-auth-plugin 1.8

Sun, 03 Jun 2012 12:34:38 GMT

Version 1.8 of the scm-activedirectory-auth-plugin is released.

Changes:

fix login for users without mail, see issue 169

scm-jenkins-plugin 1.5

Wed, 23 May 2012 16:29:15 GMT

Version 1.5 of the scm-jenkins-plugin is available.

Changes:

Support for per repository configuration and jenkins installations with authentication

SCM-Manager 1.15

Sat, 12 May 2012 21:52:23 GMT

Version 1.15 of SCM-Manager is now available for download.

scm-auth-ldap-plugin 1.13

Sat, 12 May 2012 13:09:20 GMT

Version 1.13 of the scm-ldap-plugin is available for download.

Changes:

displays an error on the connection test if the user is not valid, see issue 147

scm-userrepo-plugin 1.3

Fri, 11 May 2012 17:45:39 GMT

Version 1.3 of the scm-userrepo-plugin is released.

Changes:

Display error if repository creation fails, see issue 143

scm-auth-ldap-plugin 1.12

Thu, 10 May 2012 07:11:06 GMT

Version 1.12 of the scm-ldap-plugin is available for download.

Changes:

Support for nested ActiveDirectory groups, see issue 123

scm-pam-plugin 1.8

Mon, 30 Apr 2012 11:00:42 GMT

Version 1.8 of the scm-pam-plugin is available.

Changes:

update libpam4j to version 1.6
added possibility to extract username and/or password from gecos field

Note:

Version 1.8 requires SCM-Manager version 1.10 or newer

Homebrew

Mon, 30 Apr 2012 09:40:36 GMT

Good news for all mac users. SCM-Manager is now available via homebrew.

Just install SCM-Manager with:

brew install scm-manager

And start it with:

scm-server

scm-activedirectory-auth-plugin 1.7

Fri, 27 Apr 2012 14:14:44 GMT

Version 1.7 of the scm-activedirectory-auth-plugin is released.

Changes:

Support for 64bit

scm-auth-ldap-plugin 1.11

Thu, 26 Apr 2012 16:39:05 GMT

Version 1.11 of the scm-ldap-plugin is available for download.

Changes:

Fix bug in ActiveDirectory profile, see issue 134

scm-auth-ldap-plugin 1.10

Sun, 22 Apr 2012 19:19:55 GMT

Version 1.10 of the scm-ldap-plugin is available.

Changes:

Improved help texts

scm-notify-plugin 1.0

Fri, 20 Apr 2012 09:19:04 GMT

New plugin scm-notify-plugin available. This plugin sends automated email notifications to a list of subscribed addresses whenever a repo has changes. The plugin requires version 1.12 or newer of SCM-Manager.

SCM-Manager 1.14

Thu, 19 Apr 2012 10:45:03 GMT

Version 1.14 of SCM-Manager is now available for download.

scm-authormapping-plugin 1.0

Sat, 07 Apr 2012 10:20:18 GMT

New plugin scm-authormapping-plugin available. With this plugin you can lookup and transform author names to the real names stored in the scm-manager user database or in a mapping table. For more information have a look at issue 102.

scm-pam-plugin 1.7

Fri, 09 Mar 2012 09:59:23 GMT

Version 1.7 of the scm-pam-plugin is available.

Changes:

Improved logging
Support multi-arch based Linux distributions

SCM-Manager 1.13

Sat, 03 Mar 2012 14:17:12 GMT

Version 1.13 of SCM-Manager is now available for download.

scm-jenkins-plugin 1.4

Wed, 29 Feb 2012 18:10:38 GMT

Version 1.4 of the Atlassian Crowd is available.

Changes:

Fix global configuration checkboxes
Fix wrong global git hook url

scm-jira-plugin 1.3

Mon, 06 Feb 2012 16:14:45 GMT

Version 1.3 of the scm-jira-plugin is available.

Changes:

Allow more than one issue key in a commit message

SCM-Manager 1.12

Sun, 05 Feb 2012 15:29:56 GMT

Version 1.12 of SCM-Manager is now available for download.

Screenshots:

scm-activedirectory-auth-plugin 1.6

Tue, 24 Jan 2012 20:38:13 GMT

Version 1.6 of the scm-activedirectory-auth-plugin available.

Changes:

Fix broken login on some systems

scm-userrepo-plugin 1.2

Mon, 23 Jan 2012 17:07:50 GMT

Version 1.2 of the scm-userrepo-plugin is available.

Changes:

Allow administrators to define a name pattern for new repositories created by normal users

With this version it is possible for users to create repositories in a scheme similar to bitbucket or github (username/repositoryname).

scm-gravatar-plugin 1.2

Thu, 19 Jan 2012 08:37:24 GMT

New version of the scm-gravatar-plugin is available.

Changes:

Support for https (use secure.gravatar.com)
Fix a bug with wrong case of e-mail addresses, see r7oJY5dSiJ4

scm-activity-plugin 1.5

Mon, 09 Jan 2012 10:01:40 GMT

New version of the scm-activity-plugin is available.

Changes:

Support for SCM-Manager 1.11

SCM-Manager 1.11

Sun, 08 Jan 2012 17:19:29 GMT

Version 1.11 of SCM-Manager is now available for download.

scm-hgnested-plugin

Tue, 03 Jan 2012 10:44:05 GMT

The new plugin scm-hgnested-plugin is now available. With this plugin it is now possible to use mercurials nested repositories with scm-manager. For more informations have a look at Mercurial subrepositories wiki page.

scm-jenkins-plugin 1.2

Mon, 02 Jan 2012 13:07:14 GMT

New version of the scm-jenkins-plugin is now available.

Changes:

Support for Mercurial/Git notifyCommit
Global configuration

For more details see Issue 81 - Support jenkins notifyCommit.

scm-activity-plugin 1.4

Mon, 02 Jan 2012 13:02:55 GMT

New version of the scm-activity-plugin is available.

Changes:

Export activities as rss and atom feeds

SCM-Manager 1.10

Mon, 26 Dec 2011 16:51:46 GMT

Version 1.10 of SCM-Manager is now available for download.

scm-auth-ldap-plugin Version 1.8

Mon, 19 Dec 2011 17:42:33 GMT

New version of scm-ldap-plugin available.

Changes:

Added method to test ldap configuration

Screenshots:

scm-auth-ldap-plugin Version 1.7

Sun, 18 Dec 2011 14:12:16 GMT

New version of scm-ldap-plugin available.

Changes:

Profile support to simplify configuration
Improve form validation
Fix bug with empty group filter
Support for ldap servers with anonymous bind

Plugin updates

Sat, 17 Dec 2011 18:24:13 GMT

New version of scm-activity-plugin and scm-ldap-plugin.

scm-activity-plugin 1.3

Fix duplicate loading bug

scm-auth-ldap-plugin 1.6

Fix broken support for member attributes

scm-activity-plugin 1.2

Sat, 10 Dec 2011 12:33:44 GMT

Version 1.2 of the scm-activity-plugin is available.

Changes:

Select activity tab after login
Added empty text, if no activities available
Refresh the activities every 5 minutes

Plugin updates

Sat, 03 Dec 2011 14:17:10 GMT

New version of the following plugins scm-userrepo-plugin, scm-activity-plugin and the scm-jira-plugin are available.

scm-userrepo-plugin 1.1

Define groups which should be able to create repositories
Choose the permission type for new created repositories

scm-activity-plugin 1.1

Fix a bug with history events

scm-jira-plugin 1.2

Create a jira comment for each changeset contains the issue id
Automatically close an issue if the issue id and a auto-close (close, fix, resolve) word is in a changeset message

SCM-Manager 1.9

Sat, 26 Nov 2011 13:48:48 GMT

Version 1.9 of SCM-Manager is now available for download.

Screenshots:

2 new plugins available

Sat, 05 Nov 2011 17:39:53 GMT

The first is the scm-pathwp-plugin, this plugin enables path write protection for repositories. The second one is the scm-activity-plugin which shows the latest activity (changesets) from your repositories. Both plugin requires SCM-Manager version 1.8 or newer.

Screenshot of the activity plugin with enabled gravatar plugin:

SCM-Manager 1.8

Sat, 22 Oct 2011 15:53:55 GMT

Version 1.8 of SCM-Manager is now available for download.

Screenshots:

New Version of Crowd Plugin

Tue, 20 Sep 2011 09:47:43 GMT

The version 1.2 of the authentication plugin for Atlassian Crowd is now available. This new version has support for the SSO mechanism of Crowd.

Bamboo Plugin

Mon, 12 Sep 2011 13:02:40 GMT

New SCM-Manager plugin for the continuous integration server Atlassian Bamboo available.

Jenkins and JIRA Plugin

Fri, 09 Sep 2011 11:13:36 GMT

There are two new plugins available. The first one is for Jenkins and will ping your Jenkins CI server when a new commit is pushed to SCM-Manager.
The second plugin is for the issue tracker Atlassian JIRA and will turn Issue-Keys into links.

New Server Part 2

Thu, 08 Sep 2011 14:23:57 GMT

The rest of the services for SCM-Manager (www.scm-manager.org, download.scm-manager.org and docs.scm-manager.org) are now moved to the new hardware too.

New Server

Thu, 08 Sep 2011 10:48:36 GMT

In the last week there were are a lot of problems with the server hosting the Plugin-Backend and the Maven-Repository. Yesterday i migrated the services to a new hardware to fix this problems.

SCM-Manager 1.7

Wed, 07 Sep 2011 14:54:12 GMT

Version 1.7 of SCM-Manager is now available for download.

Plugin for Atlassian Crowd

Tue, 16 Aug 2011 09:00:48 GMT

This plugin enables use of Atlassian Crowd as an authentication handler. The plugin requires version 1.6 or later of SCM-Manager. The source is available on scm-crowd-plugin.

Version 1.6 is available

Thu, 11 Aug 2011 12:17:28 GMT

Version 1.6 of SCM-Manager is now available for download.

Release 1.5 is now available

Sat, 09 Jul 2011 16:41:31 GMT

Version 1.5 of SCM-Manager is now available for download.

Screenshots

Version 1.4 now available

Sun, 12 Jun 2011 13:54:32 GMT

SCM-Manager Version 1.4 is now available for download. This new version is a bug-fix release.

SCM-Manager Version 1.3

Fri, 10 Jun 2011 13:34:36 GMT

Version 1.3 of SCM-Manager is now available.

SCM-Manager Version 1.2

Sun, 08 May 2011 13:39:31 GMT

The new version 1.2 of SCM-Manager is available.

SCM-Manager Blog Feed

New Plugins

Custom Properties Plugin

MCP Server

Closing Words

SCM-Manager 3.11.0

MCP Server

Marking Reviewed Files

Closing Words

SCM-Manager 3.10.0

Closing Words

SCM-Manager 3.9.0

Changes in the core

Further plugins using the new persistence layer

Closing Words

LDAP plugin account hijacking vulnerability

CAS plugin account hijacking vulnerability

SCM-Manager 3.8.0

Pushlog Plugin with SQLite Support

Export of Pushlog Entries

Commit Reverts

Configuration of JWT Lifetimes

Closing Words

JWT Configuration and SQLite Support

JWT – Flexible Lifetime Configuration

Javadoc

SQLite Support – A Work in Progress

Closing Words

SCM-Manager 3.7.0

Performance Improvements for Git Modifications

Partial clones and fetches for Git Repositories

Banner with Pull Request Suggestions

Closing Words

Potential leak of password details in trace log

SCM-Manager 3.6.0

New Layouts in the Changeset and Diff Views

New Markdown Editor

Accessibility Improvements

Closing Words

SCM-Manager 3.5.0

New File Tree in the Changeset and Diff Views

Documentation Viewer Plugin

Conflicting Files in the Pull Request Diff View

Improved Performance for Pull Request Overview

Closing Words

SCM-Manager 3.4.0

BlueSpice Plugin

Modified Files Overview in Changeset and Diff Views

Cogwheel Menu in Changeset and Diff Views

External Merge Tools

Repository Mirror Plugin

Closing Words

SCM-Manager 3.3.0 and an important vulnerability bugfix

Namespace privilege escalation

Merge Tool Detection

Closing words

SCM-Manager 3.2.0

Whitespace changes

Review Plugin

Closing words

SCM-Manager 3.1.0

Performance improvements

Mail Plugin

Readme Plugin

Upload of directories

Other changes

Closing words

SCM-Manager 3.0.0

What does this mean for you and your SCM-Manager?

Documentation

Disclaimer

Closing words

SCM-Manager 3.0.0

Why the new major version?

What will change?

Unavoidable breaking changes

New config format

Plugin Compatibility

New java version

tl;dr