GitHub has updated its products for importing repositories and CI pipelines. GitHub Enterprise Importer can now be used to import from Bitbucket, and GitHub Actions Importer can now be used for Atlassian's CI/CD products.

The need for the additional support to the products was driven by the fact that Atlassian will no longer offer technical support, security updates or vulnerability fixes from next February for their server products including Bitbucket Server and Bamboo Server.

The updated tools from GitHub make it easier to switch from the Atlassian products to GitHub Enterprise Cloud and GitHub Actions. GitHub Enterprise Importer (GEI) now supports migrations from Bitbucket Server and Bitbucket Data Center, and GitHub Actions Importer now allows you to move from any of Atlassian's CI/CD products–Bitbucket, Bamboo Server, and Bamboo Data Center–to GitHub Actions.

To migrate a repository, all you need to do is install GitHub's extension for the GitHub CLI and then run a single migrate command.

Alongside the GitHub Enterprise Importer, GitHub has also updated GitHub Actions Importer, a migration tool that GitHub says helps you plan, forecast, and automate your CI migrations. In addition to BitBucket and Bamboo, GitHub Actions Importer already supports migrations from Azure DevOps, CircleCI, GitLab, Jenkins, and Travis CI.

GitHub Actions Importer is designed to help organizations when manual migration is not feasible. Describing the new products, GitHub's Tim Rogers and Melody Mileski said:

"For organizations with large and sophisticated infrastructure, CI migrations are often a manual and time-intensive endeavor. GitHub Actions Importer speeds up this process while minimizing cost and the potential for error. In fact, since its inception, GitHub Actions Importer has helped thousands of users evaluate and test the migration of nearly a quarter million pipelines."

GitHub Actions Importer uses a phased approach to simplify the migration process, starting with planning and building a roadmap for your migration. The testing phase is used to carry out dry-run migrations to validate that the converted workflows function the same as existing pipelines. GitHub Actions Importer supports unlimited iterations in this step so you can be sure you've captured any "custom behaviors" in your new GitHub Actions workflows. The final migration phase generates validated workflows and opens pull requests to add them to your GitHub repository.

GitHub Enterprise Importer and GitHub Actions Importer are available now. 

More Information

GitHub Enterprise Importer

Related Articles

GitHub Enterprise Server Adds Projects Support

GitHub Enterprise Adds Centralized User Accounts

Visual Studio Integrates GitHub Accounts

GitHub Enterprise 2.14 Adds Unified Search 

To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Twitter, Facebook or Linkedin.

Comments

Make a Comment or View Existing Comments Using Disqus

or email your comment to: comments@i-programmer.info