GitLab

GitLab is used to host all of our codebase repositories. It addresses our need to collaborate and maintain a visual history of changes made to the codebase, while also enabling us to trigger website deployment through CI/CD integrations.

To host the jombay application codebase and collaboration with the team.
Developers fork the repos and send Pull Requests for merging code

Since the beginning, Gitlab was heavily used to manage since the software development process, tracking issues, deployment automations and source-control. It is a complete all-in-one tool that can be easily adopted across the an entire product division. I have used it with Abtz Labs and also introduced it to other companies where I've been working as consultant.

For people who are software developers, GitLab is top tier. In our office, where software development is a skill that is not our specialty, the UI of GitLab helps out immensely for projects big and small, and important and not. It can manage our product and automating deployment with very few, if any, errors. It's very useful to brings members of the team together for one project.

Used the GitLab solution whithin many clients information systems for :
- code management / code repository
- Continuous Integration / Continuous Delivery
I also installed GitLab as a self hosted service on-premise, on the cloud and also use the SaaS version

Gitlab is a great tool for the GIT repository and Continuous Integration/ Continuous Deployment. We normally use this for keeping track of the website changes, automated testing, and deployment of the site on the server. The automated build process also helps to integrate recent technologies easily, with seamless team collaboration.

Started working with GitLab since 2017 to solve the deployment and regular build related issues. Git help us to automate Deployment with Less build error. Earlier we're using SVN and every time Deployment was taking too much time.

We used GitLab for VCS, Project Management, Continuous Integration, Continuous Deployment and Continuous Delivery - CI/CD Of Dev-Ops practice in agile method to execute the complex software development solution implementation to manufacturing industry with multiple stakeholders (end user, BA, Solution Architect, PMO, Developer, Tester, Deployment Engineer) bring every one same page on the progress of the project. This is one stop solution for VCS, CI/CD and DevOps requirements

We mainly use it for store front end code and Web app source code. Gitlab has good ui which is more developer & collaborators friendly. its support unlimited private directory also have lots of options for automation for front end framework like angular, next ,react etc

We use GitLab in our organization to host our code repositories. We maintain repositories at the team level, and these repos can be accessed by anyone in the team. But, apart from the team repos, every individual can also create a GitLab project and create private/internal repository. I personally, maintain a lot of private/internal repositories to push my POC/Reusable Artifacts code.

We are using GitLad for the version control of multiple projects. It helps us to allow managing the delivery of multiple versions of a product by using in-build pipelines. In addition, code quality control is also done using GitLad by implementing quality gates alongside of merge requests and by peer review in the merge requests. My personal experience has been very good with GitLad as I use the features like cherry-picking commits from one versions of the product into some other version of the same product.

GitLab we are used in our organization as a versioning tool to manage the code repository and maintain the version of the files.

We built our own GitLab environment on premise several years ago to meet the needs of code development, version control, and change management of code for a small subset of applications we run in-house. We have a small group of users who check in, check out, review code, and make enhancements as necessary. Documentation for such code is also warehoused in GitLab.

GitLab is an incredibly useful tool that I use for version control within my organization. There are several projects I work on with thousands of lines of code each. Trying to manually track and manage changes in these codebases would be a nightmare. GitLab allows me to easily track and manage all of my changes, and easily collaborate with other developers on projects.

Gitlab is a popular repository hosting platform that provides a cloud-based repository for project collaboration. We are using it to manage daily version controlling of the software we are developing that is git and using GitLab as a cloud source where we store all of our code since while building software we need to maintain different versions and GitLab uses the concept of branches to store different versions other things it does better is the security of our code!

I have been using GitLab in my team for more than 4 years, and the experience has been amazing. We started using it primarily for version management for our codebase. Gradually it gave newer updates and features and we also started using most of the features of GitLab. Now we use it for code versioning, project repository, CI/CD pipelining, infra activities, etc.

We create different projects and within each one, we generate issues as tasks, both for customer success and for the development area. The tool solves very well the communication between the different teams and gives visibility on what topic each person in the team is working on. We also make available information about the project and relevant internal topics from the wiki.

We use GitLab mostly for Version Control and CICD pipelines. All our projects are stored on the GitLab repo. Gitlab makes it easy for us to collaborate on the same product code, run CICD pipelines with a few clicks, etc. It is also pretty fast, and the best part is that it is free to use (which is why a lot of companies go with this option). We also use GitLab clients to clone projects, take a pull, push our code, etc.

Gitlab is used as version control for all our software development activities. We handle all the development processes including code check-in, issue tracking, and code review in it. GitLab is also used for our Continuous integration and continuous deployment activities in a production environment. It has a very good user-friendly interface and CI/CD infrastructure which fulfills almost all our requirements.

We use GitLab to manage the source code of all applications. It replaced an old CVS. We needed a more modern tool with greater integration for developers. We also needed a fully integrated tool for code reviews and issues management. For two years, GitLab replaced Jenkins for building pipelines and ci/cd.

I have been using GitLab for 3 years as a version control software for our product. Maintaining project code with multiple developers gets easy with GitLab. Generating pull requests for different branches and solving conflicts among branches is easy using GitLab, and the main benefit is GitLab is open source, so it is cost effective to use.

Gitlab is a key tool within my organisation, as far as software development operations is concerned. We use it for collaboration purposes, issue tracking/software maintenance purposes and for security/compliance reasons. It is secured, reliable , comparatively easy to use and comes with very intuitive documentations as well. Ultimately for me personally, I have found Gitlab to be very valuable , especially as it relates to integrating Ci/CD pipelines into our software development workflow, for improved code quality and faster deployment.

We are GitLab for storing our all code base on a server. It is very easy and convenient to use. It is the best tool for source code management. It has east CI/CD integration where we can directly deploy and build our application on the go. It is an open-source, secure, and reliable tool for any organisation. Its integration with Kubernetes and Jenkins is easy to process. There are a variety of runners to run pipelines jobs with visual status and progress. It comes with easy and understandable documentation. It is the most widely used source management tool.

Gitlab features development repository branches which enables our team to create many different software load sets to meet different customers' mission requirements while maintaining a consistent product architecture. Gitlab tracks and stores all our development changes and commits for the latest software versions on respective branches. The branches are easily accessible for pulling and pushing changes.

I have used it for managing different repositories of our project. Multiple developers manage their branches here and it is also helpful for Jenkin integration. We can manage roles also so that we can give correct access to the right person.