GitLab Alternatives

Over the past 3+ years, Bitbucket has become our standard code collaboration platform. The pull request workflow-with inline reviews, required approvals, branch protection, and merge checks-has clearly improved code quality and reduced late-stage defects. The tight integration with Jira gives us full traceability from work item to commit and deployment, which is invaluable for audits and incident reviews. Overall, bitbucket has helped us standardize our development process, increase transparency, and support a more reliable, repeatable delivery pipeline.

Honestly, switching our main automation test framework over to GitHub has been a total game changer for my team. I've used a lot of older tools in the past, but nothing matches the reliability and convenience GitHub offers. Sorting all our Java and Selenium test code in one spot means everyone's on the same page and collaboration just happens more smoothly. I'm a big fan of pull requests too, it really streamlines code reviews for our scripts, making it so simple to track feedback and improvements. Plus. Having a clear, well-organized history of every single change brings real peace of mind. If anything ever goes sideways, it is so easy to revert back to a version that we know works. And then there is the Agent, this is not the basic auto complete tool from a year ago. Now, I just ask it to handle tasks like refactoring page objects or generating new test suites for specific cases, and it coordinates updates across various files. When running in agent mode, it even takes things a step further by executing the tests in the terminal. And if something fails, it tries to troubleshoot and sort it out on its own until everything passes. That level of self-healing really does feel like having an extra set of hands on the team If I'm dealing with a flaky test or a weird timeout in my REST Assured code, I just tag the agent. It digs into the logs to find out what went wrong and actually points out possible fixes. There was even a time last month when it noticed a race condition in our framework that I'd probably have spent hours, maybe even a whole day trying to isolate on my own. The amount of time it saves me, both in writing and debugging scripts, has made this the MVP in our current toolset.

The AAP has significantly reduced the number of terminal connections our team needs to make, along with less coding knowledge dependency. Whereas before we had to manage all of our playbooks exclusively with Github Actions, now we can do more with the playbooks than just triggering them through a pipeline or directly through the CLI; we get to schedule when certain routine playbooks are run, and the inventory is so much easier to manage than maintaining a text file. Overall, it reduced the amount of knowledge our new team members of the team must have to maintain inventory by simplifying our procedures.

Honestly, having everything under one roof in Azure DevOps has been a massive change for our team. Managed to get all our dev and test code into Azure DevOps Git repos and it just makes version control so much smoother since it is all linked. We use the Sprint Boards daily to track our progress from the dev side over to the test side and it is great because I can see exactly which user story a bug belongs to without jumping between tools. Managing the PBIs and features in the same place where we write our test plans just makes the lifecycle feel very connected. The way Azure Test Plans and Pipelines talk to each other is easily the best part for me. Since our test plans are right there, we can trigger our pipelines and see the results update our test suites automatically. It is so much better than the old way of manually updating the spread sheets or the test cases or trying to sync up different platforms. I can create a bug directly from a failed test run in the pipeline and it automatically links the logs and the specific PBI we were testing. It gives our team a single source of truth which has really helped with our sprint planning and making sure we don't miss any edge cases. It's also not perfect all the time because when you have so much data in one place the interface can get a little overwhelming. Sometimes, it feels like there is a big of a lag when I am trying to load a large backlog or a complex test plan with hundreds of cases. Also, permission management is still a bit of a headache, just like it was with the agents, because there are so many levels of access across boards and repos. But overall, I would never go back to using separate tools for everything. Having the requirements and the test code in one place just makes us way more efficient, especially when we’re trying to hit those tight sprint deadlines.

Great automation tool, our company uses it everyday and it has been pleasant to use. There are a few UI preferences I prefer differently, but overall it is working great for our company to ship our products out. They have great and prompt response when attention is needed.

It is an incredibly robust continuous delivery platform that handles complex, multi-tiered architecture with ease. It successfully bridges the gap between development output and our live infrastructure, provided the deployment targets are logically grouped and maintained.

Our experience with the use of cloud formation has been great, especially when it comes to maintaining the entire real estate via infrastructure as code (IAS). There are a variety of ways in which it can be used, which makes it very flexible and importantly eliminates the need for manual resource management.

As a iOS app developer, my experience with Bitrise is smooth with CI/CD, and their dashboard GUI to maintain CI/CD is easy to access and develop. It has accessibility for Xcode and Fastlane which makes the setup straightforward and also the automation makes the process faster.