GitLab

GitLab CI allows us to test execution and build tasks that enables faster feedback and reduce validation time by distributing tests among multiple runners or stages we can optimize resource utilization and decrease the overall build and validation time. This helps us to get more quickly and deliver code changes to production faster.

We have used CI/CD before with Bitbucket and Bamboo, but now it is easier to have both functionalities within the same tool (GitLab). You can create test plans using code (in Bamboo you used the GUI) and it makes it easier to understand what the test plan does. But there are other things that you miss like in Bamboo you were able to see what a Bamboo agent was doing in real time from the UI; in GitLab you can't.

In Drupal.org the built ni GitLab CI runs the tests every time a new merge request is added. This makes a huge amount of time to the Drupal module maintainers. Also, testing a PHP Drupal module on several PHP or MySQL versions is crucial for the module development and its adoption.

We have a lint job in integrate stage in gitlab-ci.yml of our projects and that job continuously lints code on feature branches before build and this process doesn't lets the code which is faulty and it did reduced validation issues in protected and default branches as validation problems are fixed within the feature branches itself.

Yes, it's a feature that is really important in the software building lifecycle and it made CI/CD so much easier.

It executes tests on all commits, allowing us to ensure quality and reduce test flakiness.

1. It has great features where one can share code.
2. If I have to leave comments and show it to someone, I can share the link of the comment and on cliking of this link, it takes me direct to the mentioned scoll area of the =comment
3. My team is very happy top use this

Shared repos, especially using triggers, works well. It also keeps individual project YAML files well isolated.

CI tests run any time a PR is raised, ensuring that several checks like linting, tests, sonar checks are all configured and passed before a PR is available for approval, meaning that a lot of manual effort is saved. It can save hours of development time. We can also allow auto merge settings to ensure we have separate branches based on release versions

Sure, we are using CI feature and it helps us to reduce validation problems at least by 50%.

GitLab's continuous integration feature makes it easy for our team to share code in a shared repository. It automates the process of merging code changes and running tests, reducing validation problems and catching errors early. It promotes collaboration and ensures that our shared codebase stays stable and reliable.

As stated, our code reviews are much faster with this integration; our unit tests and integration tests are triggered and reported back to GitLab, so we have all the information related to a code change in one spot rather than chasing pieces of information down to figure out what happened.

We are not using this feature from Gitlab. We have continued to use Jenkins.

GitLab provides a shared repository where my team members get to collaborate on code. This shared repository acts as a central hub for all code changes, allowing team members to easily access and contribute to the codebase. By having this single source of truth ( centralized code hub ) , we are able to avoid versioning conflicts and ensure that everyone is working with the latest code.

The continuous integration opportunities GitLab provides give an excellent environment for our developers and engineers to share projects and code with each other. By operating on branches adjacent to the Master branch our engineers can be certain that our infrastructure ansible scripts are good to go and are tested. On the other hand, our developers can simultaneously use a stable master branch to perform dev testing before it all gets wrapped up into the stable prod environment.

As i said it s a part of our release process but the pipeline in our company is managed by jenkins

We use GitLab to precisely share code and manage versions of IaC in AWS and applications for our clients. The ability to merge requests and manage versions makes it easy for our team to reduce redundancy in our code and efficiently manage progress of our applications. It has also been an essential tool to manage applications in different stages of development (Dev, Prod...).

With the feature to automatically build, test and deploy code changes, we have reduced validation problems because of automated tests. Every new build is being tested - this way we see problems before deploying our code changes and the validation phase is also much shorter because we don't have to test ourselves and have the risk to oversee anything.
Also the features merge requests and approvals ensure that our changes are compatible with the rest of the codebase which makes the collaboration easy.

Continues Integration is one the critical feature required in today's Engineering Team.
First, with CI code commit can be done in seconds.
Second, once everyone used to it, there will highly fewer chances from resources losing the code in case of the local machine is corrupted.

We used Gitlab CI to execute all of our pipelines. We used to include main templates in several repositories so that everything is centralized. It is also enabled at the Merge Request level so once an MR is submitted, the pipeline is running and the code is merged only if tests are okay and if there there is no issues.

It helps us to identify conflicts between teams that may be touching the same components faster, thus allowing us to carry out rapid coordination and not fall on top of each other's changes.This helps to solve the problems faster and not to be looking for what caused the affectation.

This is the main feature our team uses for day to day activities. All the projects are made in GitLab and their version control is done in GitLab only. all the branches are made in GitLab and merge requests process fleo from creation to review is done in GitLab. Auro pipelines are also triggered in GitLab.

It was great to work with my teammates in a GitLab repository.

GitLab features helps the teams in the development collaborate with sharing code all the more effectively and decrease approval issues via testing and combination cycles and getting mistakes prior in the advancement/deployment cycle. Therefore, when you are till working and managing client changes and requests if sudden prior to the publishing, one team can easily operate and update on one task simultaneously while the other team is doing the other task related to the same task with constant updates from each other.

This has vastly helped us improve our production and deployment process. We currently have not integrated testing as part of the CI/CD but we hope to do so soon in order to reduce validation problems.