GitHub Actions Reviews

I use GitHub Actions for CI/CD pipelines. I automate infrastructure, deployment, and all processes. Most companies use CI/CD pipelines, and GitHub Actions is one of the tools available for this purpose.

The most valuable feature of GitHub Actions is that it is completely free. It can be integrated with different environments and cloud providers, supporting all major cloud providers. 

Additionally, it improves efficiency as it involves no downtime and is managed by GitHub.

The main improvement would be to add support for more programming languages and frameworks. Currently, only six to seven languages are supported, so increasing this would be beneficial.

I have been using GitHub Actions for almost five years, working as a consultant.

I find GitHub Actions to be really stable as it is entirely managed by GitHub. I would rate its stability ten out of ten.

I rate scalability as ten out of ten because it has no downtime and is fully managed by AWS.

I have not interacted with technical support for GitHub Actions. It might be because the free version does not typically offer technical support. There is a paid version available for business enterprises.

Positive

Many of my customers have switched from Jenkins, Bitbucket, and AWS to GitHub Actions because it is easy to set up and it's free.

The initial setup can be slightly challenging at times, especially for complex use cases. You need basic knowledge of YAML scripting to set up GitHub Actions. However, following official documentation for a simple setup is really easy.

GitHub Actions is completely free for most customers, which is a significant factor for adoption.

I usually convert customers from Jenkins, Bitbucket, and AWS to GitHub Actions.

Overall, I rate GitHub Actions ten out of ten. 

For new users, I advise understanding your requirements thoroughly and using GitHub Actions accordingly. Keep in mind that there's a limited number of CI/CD pipeline hours available in the free edition monthly.

I use GitHub Actions to automate my development workflows, primarily focusing on tasks such as automating backups by zipping repositories and uploading them to OneDrive. 

Additionally, I use it for unit testing, static code analysis, software composition analysis, and automating Continuous Integration (CI) and Continuous Deployment (CD) pipelines. 

I also use it to deploy Docker applications to AWS Elastic Container Registry (ECR) and automate deployments with Kubernetes.

The most valuable feature of GitHub Actions is the ability to automate various tasks, such as backups and deployments, to ease the development workflow. 

GitHub Actions allow the use of custom runners, which accommodate a range of tasks. Additionally, storing secrets securely via GitHub Secrets ensures safe access to credentials when running pipelines.

The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket. I had to conduct extensive research to find a solution using RClone for configuration. Focusing on making integrations smoother would be beneficial.

I started using GitHub Actions this year, in either January or February.

GitHub Actions is mostly stable, but I did face an issue two weeks ago when GitHub Actions services were down for about six hours, impacting my task timelines. However, such downtimes are expected with cloud platforms.

GitHub Actions operates independently of user management within my projects. The management of GitHub Actions, even with new users coming in, follows the company’s set rules, making scalability efficient with no noticeable limitations.

I used to be a GitLab person, utilizing GitHub when collaborating with an organization last year. However, since my tasks mostly involved source code management, transitioning to GitHub and utilizing GitHub Actions fit my needs better.

I am exploring Jenkins and considering Sequoia CI solutions. I haven't fully explored them enough to provide a detailed comparison.

The initial setup was straightforward, especially when using Visual Studio Code for my Versus Code setups. While starting from the GitHub GUI was a bit confusing initially, I got accustomed to it after a few steps.

There are pricing considerations where exceeding the free hours given in a month incurs additional costs. GitHub provides a free version with certain hours, which seems reasonable for my usage.

I recommend GitHub Actions because it is widely used by organizations for source code management. It is an open-source tool that supports collaboration and offers comprehensive documentation. 

Overall, I would rate GitHub Actions nine out of ten.

Our primary use case for GitHub Actions is for continuous integration and continuous deployment (CICD). Our application is mostly based on Java, and our codes are on GitHub. We have set up a pipeline for CICD that automatically deploys to our test server. We integrated GitHub with Jenkins using GitHub Webhook to take builds and pass parameters, such as push parameters, to trigger jobs.

GitHub Actions has improved team productivity significantly. It has reduced the manual intervention needed, saving both time and effort. The automation of tasks allows our developers to focus more on new tasks rather than repetitive testing phases. It also makes our workflows more efficient, as it automates unit and integration testing, which helps us avoid wasting time.

The most valuable feature of GitHub Actions is its ability to automate processes, eliminating the need for manual interventions. It is user-friendly, with clear and organized processes, making it easy to navigate and work with. Its integration with Jenkins helps streamline our code-building process, ensuring everything is in order without interruptions.

Sometimes it is quite complex to commit code from our local system to the GitHub repository; creating a folder in GitHub can be tedious. Integration with SSH keys in the GitHub account setup could be improved to be more straightforward from a user perspective.

I have been working with GitHub Actions for one or two years.

I have not experienced any downtime or stability issues while using GitHub Actions. It has been stable and reliable.

GitHub Actions is scalable and highly available. We don't face any issues with scalability or downtime.

We have not needed to raise any questions with GitHub technical support, suggesting that the system has been self-sufficient and straightforward.

Positive

I have worked with both GitHub Actions and Jenkins. I didn't get the chance to work with other tools, so I continue to work with these.

The initial setup was easy and straightforward. With all the available plugins for GitHub integration, setting it up with Jenkins was manageable and didn't take much time.

I was responsible for implementing and setting up GitHub Actions in our environment.

I highly recommend GitHub Actions for managing development workflows because it is easy to set up, saves time, and can handle complex tasks efficiently.

I'd rate the solution ten out of ten.

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.

I am currently using GitHub Actions as a tool for our CI/CD pipeline. I was engaged in an e-commerce project where I used GitHub Actions and stored secret data within GitHub Actions secrets and variables.

GitHub Actions streamline our workflows by allowing us to manage production, testing, and live environments in a single directory. It helps automate processes efficiently without much manual intervention.

We can use secrets and variables within GitHub Actions while managing our source code. We can trigger files manually or automate processes. GitHub Actions fit seamlessly with our CI/CD needs, integrating well with other tools we use.

GitHub sometimes makes it difficult to debug actions. Improvements in debugging could enhance its usability greatly.

I am currently using GitHub Actions.

There are frequent stability issues with GitHub, particularly when managing data sets and ensuring all components function correctly. Troubleshooting is sometimes necessary.

GitHub Actions are scalable as we can use them for scalability protocols.

As a technical support approach, issues are addressed directly through client communication. We manage issues arising from clients via direct mail correspondence, thereby handling problems as they occur.

Positive

GitHub Actions provides an easy-to-use interface suitable for beginners, free runners for CI/CD, third-party actions, and cost-effectiveness. Troubleshooting can be challenging, requiring technical knowledge.

The initial setup involves creating a workflow directory and writing YAML files to manage resources, security, and monitoring. We work closely with the development team during setup.

The deployment requires collaboration between frontend, backend, and database teams, along with the use of Terraform and monitoring tools like CloudWatch for effective management.

GitHub Actions can be compared with Jenkins for CI/CD purposes.

I recommend GitHub Actions to other users due to its user-friendly nature, free runner availability, and effective secret management.

I'd rate the solution eight out of ten.

Our primary use case for GitHub Actions is for continuous integration and deployment within our repository. We utilize it to build packages and create binaries.

GitHub Actions has improved our organization by being readily available within our repository. It is widely used, and we can easily integrate straightforward YAML, providing clear status updates on failures.

GitHub Actions is valuable for its ease of use and integration. Additionally, we can use our own GitHub runner to perform many tasks such as building packages and creating binaries.

The only issue I have faced is with authorization, particularly when configuring the GitHub token correctly.

I have been using GitHub Actions for approximately three years now.

I have not faced any stability issues with GitHub Actions. It has been reliable without any notable problems.

The scalability of GitHub Actions is good, and we have not faced any issues regarding scalability.

I was using a previous solution before GitHub Actions and switched since GitHub Actions is more favorable in terms of features and integration.

I would advise new users to ensure their secret keys are safe and to set up authorization carefully with GitHub Actions to prevent exposure.

I'd rate the solution nine out of ten.

It's part of an automation process. We develop code in GitHub and use Google Cloud Platform. To do that, we leverage GitHub Actions, which automatically interacts with GitHub, the source code repository, and automates our build, deployment, and deployment processes.

GitHub Actions have been pivotal for automating our software development processes.

We develop in GitHub. Once a feature is built and tested, different Actions help us deploy it to our test environment. We test again, and then with GitHub, we deploy to production with just a click.

The integration is excellent. Having the source code in GitHub and seamlessly using Google Cloud is smooth and secure.

The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency

The UI could be better. 

I have been using it for two years. 

It's very stable. I would rate the stability a nine out of ten. We haven't encountered any major issues.

It is very scalable. We deploy quite large systems successfully.

There are around 200 end users using this solution. 

I used Jenkins before.

The initial setup can require some knowledge, but there are helpful tutorials, examples, courses, and other resources. Overall, it's manageable.

The process varies depending on what's being deployed (data, services, etc.). We use multiple environments with different ports for each microservice. 

It's a complex infrastructure with databases and other components, but Actions makes scaling it up and down and managing its overall complexity surprisingly easy.

Deployments are quick, usually taking a few minutes, up to ten minutes at most. They're one-time jobs, though they might run multiple times a day.

GitHub Actions is our CI/CD tool. We actually use TerraForm for deployment.

It's actually quite user-friendly. Teams can manage it themselves without needing dedicated IT professionals.

The level of automation it offers makes it worth the investment. 

Overall, I would rate the solution a nine 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.