Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Launchpad vs GitLab CI, the Slant community recommends GitLab CI for most people. In the question“What are the best hosted version control services?” GitLab CI is ranked 7th while Launchpad is ranked 11th. The most important reason people chose GitLab CI is:
All build setup are stored in .gitlab-ci.yml file, which is versioned and stored in the project. Like Travis do.
Specs
Question Ranking
Pros
Pro Support for web based translation
Launchpad makes it easy to translate free open source projects into virtually any language in the world. Users are allowed to start working on translating any project they want just by having a Launchpad account and a web browser. Most of the time they don't have to even join a team to start working and the editor is web based, so there is no need for any special software.
Pro Integrated build/deployment system
If you use launchpad, it gives you a build system (on their platform) as well as easier deployment - user merely adds your PPA to their sources.list file. Deployment (on Ubuntu, at least - other debians as well) doesn't get simpler than this.
Pro Great bug tracking features
Launchpad is built to be used for open source projects, as such it needs a powerful bug trackers to allow developers who want to contribute to jump right in. Launchpad displays bug statistics (total number of bugs, number of bugs fixed etc...) as well. Bugs can be searched and displayed from every project hosted on Launchpad or for single projects.
Pro File based configuration
All build setup are stored in .gitlab-ci.yml file, which is versioned and stored in the project. Like Travis do.
Pro Free and open source
All of GitLab CI's code is open source and under the MIT license.
Pro Parallel builds lessen test times
Tests are parallelized across multiple machines in order to reduce test times considerably.
Pro Docker intergration
Good integration with Docker.
Pro Highly scalable
The tests of GitLab CI run parallel to each other and are distributed on different machines. Developers can add as many machines as they want or need, making GitLab CI highly scalable to the development team's needs.
Pro Quick setup for projects hosted on GitLab
Since it uses the GitLab API for setting up hooks, the setup of GitLab CI for projects hosted on GitLab can be done in one click.
Pro Kubernetes integration
Easy to test and deploy on Kubernetes.
Cons
Con The web interface is complicated and hard to use
Other project hosts such as GitHub, BitBucket or GitLab have easy, simplistic UIs that help new and experienced developers alike to browse code right through the browser. LaunchPad on the other hand is very weak at this. Most of the projects have poor (if any) documentation and no way to determine a project's worth easily. The fastest way to do so with LaunchPad would be to download the project and look through the code manually, which is quite tiresome.
Con Not lightweight
Not a lightweight solution, demanding and memory hungry.
Con Cost
Larger projects will need upgraded version
Con Security risks
Con Windows not supported
No Windows support, but it's possible to use a Bitnami stack.
