GitLab CI vs PHPCI

Overview

PHPCI

Stacks5

Followers9

Votes0

GitHub Stars2.4K

Forks433

GitLab CI

Stacks2.3K

Followers1.6K

Votes75

GitHub Stars0

Forks0

GitLab CI vs PHPCI: What are the differences?

### Key Differences between GitLab CI and PHPCI

Integration with GitLab and GitHub: GitLab CI is tightly integrated with GitLab, allowing direct access to repositories and simpler configuration, while PHPCI can work with both GitLab and GitHub, providing flexibility for users who utilize multiple platforms.
Hosted vs. Self-hosted: GitLab CI is generally hosted by GitLab, offering a cloud-based solution, whereas PHPCI is self-hosted, allowing users to have full control over their infrastructure and data security.
Ease of Use: GitLab CI is known for its user-friendly interface and simple setup process, making it accessible to developers of all levels, while PHPCI may require more technical expertise for configuration and deployment.
Scalability: GitLab CI is designed to handle larger projects and teams with ease, offering scalability features such as parallel and distributed builds, whereas PHPCI may struggle to maintain performance with a high volume of build processes.
Docker Support: GitLab CI has robust Docker support, making it easy to containerize build environments and improve consistency across different stages of the CI/CD pipeline, whereas PHPCI may have limited or less intuitive Docker integration capabilities.
Community Support: GitLab CI benefits from a large and active community of developers and contributors, providing a wealth of resources, plugins, and support forums, whereas PHPCI may have a smaller community presence, resulting in potential challenges with troubleshooting and customization.

In Summary, GitLab CI and PHPCI differ in their integration options, hosting models, usability, scalability, Docker support, and community resources.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on PHPCI, GitLab CI

Stratos

Jan 13, 2020

Needs advice

We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.

Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.

We primarily need:

Fast SBT builds (caching)
Low maintenance overhead (ideally serverless)
Everything as code

Ease of use

181k views181k

Comments

Anonymous

Feb 14, 2020

Decided

Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like:

Add repo
Click - Click - Click
You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.

157k views157k

Comments

Detailed Comparison

PHPCI	GitLab CI
It is a free, open source, continuous integration software written in PHP and designed specifically for PHP projects. Integrates PHPUnit, PHPMD, PHPCPD, PHPCS and more.	GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
Clones your project from Github, Bitbucket or a local path; Allows you to set up and tear down test databases; Installs your project's Composer dependencies; Runs through any combination of the supported plugins	-
Statistics
GitHub Stars 2.4K	GitHub Stars 0
GitHub Forks 433	GitHub Forks 0
Stacks 5	Stacks 2.3K
Followers 9	Followers 1.6K
Votes 0	Votes 75
Pros & Cons
No community feedback yet	Pros 22 Robust CI with awesome Docker support 13 Simple configuration 9 All in one solution 7 Source Control and CI in one place 5 Easy to configure own build server i.e. GitLab-Runner Cons 2 Works best with GitLab repositories
Integrations
PostgreSQL Deployer HipChat PHP SlackTextViewController MySQL Grunt Codeception Behat Mac OS X	GitLab

What are some alternatives to PHPCI, GitLab CI?

Jenkins

In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Related Comparisons

GitLab CI vs PHPCI: What are the differences?

### Key Differences between GitLab CI and PHPCI

Integration with GitLab and GitHub: GitLab CI is tightly integrated with GitLab, allowing direct access to repositories and simpler configuration, while PHPCI can work with both GitLab and GitHub, providing flexibility for users who utilize multiple platforms.
Hosted vs. Self-hosted: GitLab CI is generally hosted by GitLab, offering a cloud-based solution, whereas PHPCI is self-hosted, allowing users to have full control over their infrastructure and data security.
Ease of Use: GitLab CI is known for its user-friendly interface and simple setup process, making it accessible to developers of all levels, while PHPCI may require more technical expertise for configuration and deployment.
Scalability: GitLab CI is designed to handle larger projects and teams with ease, offering scalability features such as parallel and distributed builds, whereas PHPCI may struggle to maintain performance with a high volume of build processes.
Docker Support: GitLab CI has robust Docker support, making it easy to containerize build environments and improve consistency across different stages of the CI/CD pipeline, whereas PHPCI may have limited or less intuitive Docker integration capabilities.
Community Support: GitLab CI benefits from a large and active community of developers and contributors, providing a wealth of resources, plugins, and support forums, whereas PHPCI may have a smaller community presence, resulting in potential challenges with troubleshooting and customization.

In Summary, GitLab CI and PHPCI differ in their integration options, hosting models, usability, scalability, Docker support, and community resources.

GitLab CI vs PHPCI

Overview