Learning GitHub Actions

Chapter 14. Migrating to GitHub Actions

As you’ve seen throughout the book, GitHub Actions provides a powerful platform for integrating automation with GitHub. The workflows and actions can be used to do any of the typical types of tasks, such as CI/CD, that you may currently be doing with another tool or platform. And, when you are using a different platform, migrating to GitHub Actions can seem like a daunting proposition.

In this chapter, I’ll cover the basics you need to know to work on migrating from a set of selected CI/CD platforms to GitHub Actions. I’ll also show you how to use a new tool—the GitHub Actions Importer—that can help get you part of the way there with automation.

GitHub Actions can be implemented to replace any current automation framework, though some may need more customization than others. As a general rule, if you are using one of these six options, the migration is more straightforward. The importer tool is also specifically designed to work with pipelines in these platforms:

• Azure DevOps
• Bamboo (in beta, see note)
• CircleCI
• GitLab
• Jenkins
• Travis CI

Support for Bamboo

Support for Atlassian Bamboo was added after this chapter was written and is currently in beta as of the time of this writing. For these reasons, details of migrating from it are not fully covered here. For more information on it, see the documentation.

There isn’t time and space in this chapter to cover all of the details. But I’ll give you enough to get going; refer to locations in ...