Share your experience using Plutora

My main use case for GitLab is as a version control system that we are using. Currently, I am working on an end-to-end AI pipeline, and I have deployed my whole code using GitLab so that all things are utilized for version control for my back-end AI and front-end team. We merge all the Git codes into GitLab, and my CI/CD, issue tracking, security, and monitoring is maintained inside GitLab.

We try to collaborate with all the teams together on different features. Within GitLab, we are not utilizing Jenkins or any product management tools because it perfectly renders all the information. It maintains the version control system, which is very helpful to containerize and deploy all services, allowing us to have everything together in production.

CI/CD is the most important feature that I am utilizing with version control and security as well, and all things are very useful inside GitLab.

CI/CD helps my workflow by allowing me to integrate any new changes or any new version that I want to deploy in the whole ML lifecycle, which I implement through new integration phases and identify updates in the deployment scripts. We generate YAML manifest files, add dependencies, and deploy them utilizing GitLab's versioning system, identifying any security patches that need to be added or incidents that need to be managed, triggering the workflow. We try to manage the perfect scenarios.

GitLab has impacted my organization positively in terms of version control systems, providing many smart features and reducing the sharing of dependencies compared to what we used to do previously. It has helped the organization merge and collaborate within the team on the level of code accesses and identify how actionable insights can be inputted within the whole pipelining mechanisms, allowing us to easily perform actions on CI/CD. My organization has adapted this and resulted in more productive work.

There are many improvements that GitLab can implement, such as addressing the issue of caching. Currently, when I have multiple tasks to merge or attempt multiple merges, the CI/CD and overall GitLab processes get slower. Implementing caching to allow parallel jobs to execute together would optimize the solution and enhance efficiency.

The UI is not user-friendly compared to how GitHub Actions operates. If we could customize the UI interface or have options for plugin-based mechanisms, that would be more suitable and increase DevOps in enterprises.

I have been using GitLab for around three years.

GitLab is stable.

GitLab's scalability is good, allowing multiple employees to work together, change code collectively, and perform all kinds of CI/CD regardless of impacts from bug fixes.

I have not reached out to customer support currently, but email support is very good, although I have not interacted with any call-based mechanisms or voice call systems.

I was using GitHub and GitHub Actions prior to this. While GitHub Actions provided good CI/CD operations, GitLab has added smart features, such as a graphical view of branches in version control mechanisms and tracking changes made by authors at specified times. Everything is maintained perfectly in my codebase, and I can easily track buggy code, identifying issues with excellent visibility. This visibility compared to GitHub and GitHub Actions is what led me to switch to GitLab.

The setup cost for GitLab is minimal since the team has its own minimal resource balancing. The costing falls into an intermediate stage and is impactful across all results within the team. It allows for CI/CD stages and addition of security patches smoothly, with only a slight charge that is not significant. Everything related to scripting, processing, management, and deployment works fine.

I have seen a return on investment with increased collaboration within the team resulting in more productive work and a reduction in time based on prior experiences, which emphasizes GitLab's usefulness.

The setup cost for GitLab is minimal since the team has its own minimal resource balancing. The costing falls into an intermediate stage and is impactful across all results within the team. It allows for CI/CD stages and addition of security patches smoothly, with only a slight charge that is not significant. Everything related to scripting, processing, management, and deployment works fine.

Before choosing GitLab, I evaluated options like GitLens and Bitbucket. I have tried those tools prior to this project, but ultimately, I chose GitLab as the foremost solution for version control mechanisms.

Since using GitLab, we have experienced fewer errors in identification, and any incidents coming out at the production level can be maintained to facilitate complete results, ensuring that collaboration works fine and deployment scripts remain easily executable, maintaining all services perfectly. Any impactful scripts work fine, whether making minor or major version updates.

I recommend GitLab if you are looking for a good graph-based solution or any impeccable solution for version mechanisms. I would rate this product a 9 out of 10.

AWS CodeDeploy is a deployment service that automates application deployments to various compute services. My main use cases include automated application deployments to Amazon EC2 instances, on-premises servers, AWS Lambda, and Amazon ECS.

In my projects, I have deployed backend services through AWS CodeDeploy to EC2 instances. For every release and pre-development release planned for production, I use AWS CodeDeploy to deploy to all four AWS EC2 instances, which allows me to achieve the desired output.

The primary use case for AWS CodeDeploy is automatic application deployment, which I consider the best aspect of the service.

AWS CodeDeploy offers several valuable features, including deployment to fleets of EC2 servers, on-premises servers deployed to data center infrastructure, AWS Lambda for serverless function updates, and Amazon ECS for containerized applications.

The feature I use most frequently is deployment to Amazon EC2 instances, where I deploy backend services to EC2 servers, enabling zero-downtime deployment. AWS CodeDeploy supports rolling updates, blue-green deployments, and canary deployments to minimize or eliminate downtime. Additional standout features include consistent deployments across environments, the ability to deploy to development, staging, and production environments, centralized control, integration with CI/CD pipelines, and automatic rollback.

AWS CodeDeploy has positively impacted my organization by significantly reducing deployment times to achieve zero downtime during deployments. Generally, it takes very little time for backend services to be deployed to EC2 instances.

AWS CodeDeploy can be improved by optimizing deployment strategies using blue-green deployments, configuring appropriate minimum health hosts to balance speed with reliability, enhancing the AppSpec file, keeping lifecycle hooks efficient and lightweight, improving monitoring and feedback, speeding up deployments, strengthening CI/CD integrations, and improving reliability while using best security practices.

Deployments can be accelerated much more by reducing artifact size through excluding unnecessary files, using S3 Transfer Acceleration for large deployment packages, pre-installing dependencies in AMIs rather than during deployment, and running deployment scripts in parallel where possible.

I have been using AWS CodeDeploy for the past six years.

AWS CodeDeploy is quite stable.

AWS CodeDeploy's scalability is quite good. I can definitely scale it to a much higher extent whenever required and can downgrade when needed, as its features support scalability with infrastructure.

The customer support has been excellent. I have faced some issues and they were resolved very quickly.

Previously, I was using Azure for deployments, but I switched to AWS CodeDeploy because of the pricing, features, and performance it provides, including improved monitoring and feedback available in AWS CloudWatch.

I have definitely seen a return on investment. The time saved is the main advantage, and I can realize many benefits such as accelerated deployments and reasonable costs overall.

The time saved is the main advantage of AWS CodeDeploy, and the costs have been quite reasonable.

The pricing for AWS CodeDeploy has been quite reasonable. It is better compared to peers like Azure, and the licensing cost and setup cost are both quite good for AWS.

Before choosing AWS CodeDeploy, I evaluated Azure as an alternative. However, AWS CodeDeploy's performance and its features, including best practices for security, reliability, and CI/CD integration as well as deployment speed and strategies, have been quite strong.

My advice to others looking into using AWS CodeDeploy is to use it to maximize capabilities in terms of reducing deployment times. It scales with infrastructure so you can deploy to one instance or thousands without issues.

I have already explained numerous features and aspects of AWS CodeDeploy, including scalability benefits, multi-environment support, concurrent deployments, blue-green deployment at scale, autoscaling integration, and core scalability features. I would rate this product a 9 out of 10.