GitHub Actions Reviews

I use the solution in my company for DevOps-related purposes. Our company uses it as our DevOps repository. All our codes and development happen using GitHub Actions. In our company, it was a collective decision to use GitHub Actions.

The solution's features are meant for DevOps. In our company, we use it for a code repository, then build code using the solution, and then deploy it, so that is the typical day for us.

My company would want to see some AI features in the tool as it can add value to the product.

I have been using GitHub Actions for about two years. My company is just an end user of the tool.

It is a very stable solution as we have not faced any issues.

In terms of the product's scalability features, I can say that the tool is serving our purpose, so it is good enough for us. Scalability-wise, I rate the solution a seven to eight out of ten.

In my company, we never had a reason to make a request with the product's support team. I have never contacted the tool's support team.

I have not been using any other tools.

The product's deployment phase is taken care of with the help of Docker. Everything is containerized, and our deployments happen through Docker.

The solution can be deployed in half an hour.

The tool's price is okay and reasonable.

So far, we are satisfied with the product in our company since we have not faced any issues with it.

My company does not use the product since we have some favorite features in it. The product offers utility and serves our purpose, which is why we are continuing with GitHub Actions in our company.

My company has not integrated the product with third-party solutions. I was looking at a few of the options against GitHub Actions, and I think that is why I browsed through PeerSpot's website.

The good thing about the tool that I like personally is that it has both GUI and a command-line interface, making it possible for us to integrate it in our scripts and to use it when we want to visualize something.

The tool's documentation is good. If any help is required, we can refer to the product's documentation and get it done. I need to actually check with my team if they had faced any issues with the tool.

At the moment, there is no need to maintain the product.

My company would need to use the tool's AI feature in the future.

The tool is able to serve our company's purpose, so I would say it is a good product.

I rate the tool a six to seven out of ten.

GitHub Actions was used as the main CI/CD component to manage the deployment of a new application in the cloud and the release of new code.

GitHub Actions can be easily configured, especially for environment variables and secrets. The UI is understandable and user-friendly for setting up CI/CD pipelines. I prefer tools like GitLab, where the pipeline starts quickly and is accessible near the commits for easy access. However, many CI/CD tools are interchangeable due to similar features of GitHub Actions and other similar tools.

The minor drawback of GitHub Actions is the management of the dashboard and pipeline runs, which needs improvement. The dashboard for running pipelines could be better.

I have been using GitHub Actions for more than a year.

In terms of stability, it is stable based on my experience. I would rate the stability a seven out of ten, but there might be more stable options like Jenkins.

GitHub Actions handles the scalability demands of my projects through various jobs, making it easy to scale between workloads.

Overall, I rate GitHub Actions ten out of ten.

Although the dashboard for running pipelines could be better, the primary tool is quite good. I would recommend this tool for those considering GitHub Actions.

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.