Springloops - an important companion for source control and application deployment
Overall Satisfaction with Springloops
It is used in our organisation to provide a central repository for a series of development projects. Since its power lies beneath existing versioning technology such as GIT and SVN all our projects are maintained under source control. Moreover, the deploying functionalities help us deploy project changes to different environments (dev, uat, prod) with ease.
Pros
- Easy of use - clear user interface
- Fast deployment to all environments
- Great combination of source control and project management
Cons
- We would love to have a more flexible management for resources (users, storage)
- More advanced web hooks would be a plus
- A total time saver - just commit changes and Springloops can handle the deployments
- Total control of source code and commits - you never have to think about those things again
Springloops has a built-in feature that is lacking from Bitbucket (at least on the out-of-the-box functionality). Deployment of projects to various servers/development stages. The process is so easy and painless that even remote servers can act as local environments. This is a feature that differentiates Springloops from other solutions that require other tools to perform the same task.
Using Springloops
6 - Our development team uses Springloops as the main code repository for our web development projects. By using SVN or GIT source control we maintain our code on a single central system. The code can be accessed from anywhere and the team keeps track of all changes throughout the development cycle. Moreover, the team can review our code online for changes and updates.
6 - Front-end developers, back-end developers, mobile developers use Springloops on a daily bases to maintain their code. Springloops is a straightforward tool to use. Most of the work is done outside Springloops using tools such as Tortoise or SourceTree. So, basic knowledge of those tools can help developers use in essence Springloops. Then within Springloops, everything is simple as using a common web browser. The UI is straightforward and easy to use - making it an ideal environment to maintain and update our code base.
- Maintaining the code base for all our projects
- Deploy code on all environments - dev, pre-prod, prod
- Source control either using GIT or SVN
- Bug tracking and fixing
- Time tracking
- Extensive use of commit commands that provide guidance to Springloops for executing commands
- Use of webhooks to perform automated actions when deployments/commits are made
- Extensive use of time tracking
- Solely use the project management features - and stop using other tools
Evaluating Springloops and Competitors
- Price
- Product Features
- Product Usability
The ability to deploy code directly to any server related to the project. The option to auto-deploy to staging or development environments is a real time saver for all members of the team. No additional time is needed to use other tools to deploy our code. No more hand picking file - just commit and everything is done by Springloops.
I would not change anything. Springloops is a must-have tool for our organization. The overall approach and implementation So, it helps us do out work faster than before. After started using the tool we never went back or had second thoughts. It really helps us achieve more and improves our day-to-day processes.
Springloops Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
One of the founders helped me over Skype on an issue I was having. The founder, not some support guy. He was available and we talked about my issue and he helped me resolve it. This is what I call 100% satisfaction and feeling that you have someone watching you at all times.
Using Springloops
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Deployment to servers
- Source preview and browsing
- Messaging within the team
- Comments on commits
- Rarely deployments get stuck - but it's only some sort of glitch of the interface
Yes, but I don't use it
Comments
Please log in to join the conversation