GitHub Actions Reviews

We are using GitHub Actions to enhance our CI/CD processes within an AWS environment. Our primary use cases include the deployment of infrastructure, authentication against AWS, GitHub, and Databricks, implementing security checks, and conducting QA tests. 

We utilize the tool for deploying Databricks within AWS and migrating repositories from GitHub. We also use GitHub Actions for setting up centralized workflows, monitoring, Terraform deployment, and security checks.

The automation using GitHub Actions has optimized our workflow by streamlining processes and establishing standardized practices across the organization. It allows our team to work more efficiently by reducing complexities in deployment and integrating enhanced security checks.

The most valuable features of GitHub Actions include its seamless integration within GitHub, which simplifies the CI/CD pipeline setup. The scalability of using different types of runners—both public and private runners—enhances deployment flexibility. The ease with which pipelines can be learned and implemented is also a key feature. GitHub Actions provides a wide range of available services and community actions that cater to various needs.

Improvements could be made in terms of time-saving capabilities and resolving potential complexities in centralized workflows. The challenge lies in maintaining centralized workflows given the potential for outdated or non-functional community actions.

I have been working with GitHub Actions for two years.

The stability of GitHub Actions is commendable, with few downtimes experienced. Issues, when they occur, are typically resolved quickly.

GitHub Actions proves to be scalable, with the ability to edit pipelines easily and address scalability challenges effortlessly.

I have not utilized GitHub Actions' technical support, as most issues can be solved with available resources online.

Positive

Previously, we used Jenkins and AWS CICD automation before switching to GitHub Actions for centralized integration within GitHub and improved efficiency in managing automation.

Setting up GitHub Actions initially was challenging as it required learning a new CI/CD tool and adapting from previous tools. However, the documentation is comprehensive and helpful.

The deployment involved a team of about five people. Two or three people continue to maintain the processes post-deployment.

The solution is open source, making it cost-effective for individual users. However, company usage may depend on its scale and specific requirements.

We chose GitHub Actions as a company standard.

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.

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.

It works excellently. Instead of having an additional CI/CD tool, we find this specific data backend tool highly beneficial. Within this data backend tool, we possess data burners, such as DNS hit creation, and within these data burners, we can conduct all build and release tasks, except for the more complicated ones like clicking. This provides a significant advantage, allowing us to automate and script processes across various environments effortlessly. I highly recommend using data backend actions for these purposes.

Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform.            

We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution.

Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter.

We have been using GitHub Actions for sometime.

The solution is stable so I would rate it 10 out of 10. 

It is highly scalable, so I would rate it 10 out of 10. 

Technical support is good but it can be improved. 

Neutral

There are several steps in our process that need to be followed. First, we perform local testing on our proprietary branches. Then, we transition to the development phase, where we create a full request and merge it into the main branch. Following that, we move to the release branch after review and discussions. Once it's uploaded, the main branch becomes the pre-release branch, and similar teams across the globe apply their changes. Every fifteen days, in line with agile practices, we conduct a COC meeting to discuss and deploy to the main branch. Once everything is in order within the release branch, we proceed to the production environment within the AWS cluster.I would rate the solution 8 out of 10, so it is easy. 

It is free and open platform, so I would rate it 1 out of 10. 

I would rate the overall solution 10 out of 10. 

I use the platform to automate my CI/CD pipelines, specifically to deploy code once merged.

The solution significantly impacts our work operations by automating tasks that might not have been considered for automation before, reducing the need for manual intervention.

The product's most beneficial feature is the ability to create workflows within the solution. This helps quickly set up an efficient automation system, and the problem-finding process is easier than other CI systems.

There could be more integration options with different platforms.

I have used GitHub Actions for personal projects for approximately two to three months.

The platform is stable. 

The platform is scalable. 

We haven't contacted the technical support team. There is plenty of documentation available. Also, some searching usually solves any issues.

The product is slightly more expensive than some alternatives, like Bitbucket, but the additional cost is minimal.

The solution works effectively for source code management. It is suitable for users working on open-source projects. It is a great platform for understanding and contributing to open-source communities.

I rate it an eight out of ten. 

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.

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.