GitHub Actions Reviews

I use GitHub Actions as a CI/CD tool in one of my company's projects.

The most valuable feature of the solution is that it is a good product that offers stability and performance.

I feel that the product is okay for me.

Sometimes, it takes a while to deploy the product. Some of the functions of the product are hard to understand owing to its scripts or UI.

The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly.

I have been using GitHub Actions for two months.

Stability-wise, I rate the solution an eight out of ten.

I don't have a problem with the product's scalability.

There are around ten users of the product in my company. In my team, there are three or four users of the product.

I will use GitHub Actions for multiple upcoming projects in my company, which involve around 500 users.

I have contacted the solution's technical support.

The product's initial setup phase was easy.

The solution is deployed in the cloud.

You can deploy the product directly from the internet.

The solution can be deployed in a day.

In my team, the product has three or four users to deploy and maintain it, consisting of one developer, one data analyst, and one system analyst.

I took care of the deployment part of the solution by myself.

From an ROI perspective, the value offered by the product is okay.

GitLab is expensive. Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution.

I evaluated a solution named GitLab against GitHub Actions. Recently, GitLab increased the price and user limit.

I rate the overall tool a seven out of ten.

I am a freelancer working with another company. My primary role is, as a Digital Transformation project manager and consultant, project management, define and integrating solutions. 

The deployments are more confidence and secure

I am familiar with the entire life cycle of the product. While some tools work quite well with GitHub Actions, others are more challenging to implement. It's easier with custom developments but more difficult with developments over propietary software. GitHub is rated better from my experience compared to GitLab. The goal is to avoid deployment failures, which GitHub Actions assists with.

In our company, procedures or rules need to be completed, which is not a problem with GitHub Actions but with our process.

I have been using the solution for more or less five years.

The company I work with has a support team for this tool. They are covered with the technical teams.

Positive

We also work with GitLab, but GitHub is better based on our experience.

The company has technical teams and may collaborate with other companies.

We also work with GitLab.

GitHub has been a better experience compared to GitLab. I'd rate the solution eight out of ten.

We use it for the integration and release processes related to our PRCB activities.

I find it incredibly convenient and valuable for our CI/CD processes. It covers configuration, integration, and patching, as well as continuous deployment. It offers numerous built-in features for pipeline management, release management, and even work item tracking on boards, which makes it a versatile tool that seamlessly integrates with hardware and facilitates optimization.

While our current pipeline handles most of the deployment, we believe there's room for improvement, especially when it comes to generating comprehensive reports and metrics. The reporting capabilities are somewhat limited.

I have been working with it for eight years.

It offers good stability capabilities.

It provides a scalable architecture, and there's thorough documentation available.

We've been using Jenkins for continuous integration and release management, but it hasn't been providing the seamless experience we desired. While Jenkins has the potential and capabilities for these processes, it often requires piecing together multiple solutions.

The deployment process varies based on the type of project we're involved in. The execution typically takes approximately two and a half to three minutes to complete successfully.

It is quite straightforward and useful. I would rate it eight out of ten.