Amazon CodeCatalyst now helps GitLab and Bitbucket repositories, with blueprints and Amazon Q characteristic growth
|
I’m blissful to announce that we’re additional integrating Amazon CodeCatalyst with two in style code repositories: GitLab and BitBucket, along with the prevailing integration with GitHub. We deliver the identical set of capabilities that you simply use as we speak on CodeCatalyst with GitHub to GitLab.com and Bitbucket Cloud.
Amazon CodeCatalyst is a unified software program growth and supply service. It permits software program growth groups to rapidly and simply plan, develop, collaborate on, construct, and ship purposes on Amazon Internet Companies (AWS), decreasing friction all through the event lifecycle.
The GitHub, GitLab.com, and Bitbucket Cloud repositories extension for CodeCatalyst simplifies managing your growth workflow. The extension means that you can view and handle exterior repositories instantly inside CodeCatalyst. Moreover, you possibly can retailer and handle workflow definition information alongside your code in exterior repositories whereas additionally creating, studying, updating, and deleting information in linked repositories from CodeCatalyst dev environments. The extension additionally triggers CodeCatalyst workflow runs robotically upon code pushes and when pull requests are opened, merged, or closed. Moreover, it means that you can instantly make the most of supply information from linked repositories and execute actions inside CodeCatalyst workflows, eliminating the necessity to swap platforms and maximizing effectivity.
However there’s extra: beginning as we speak, you possibly can create a CodeCatalyst venture in a GitHub, GitLab.com, or Bitbucket Cloud repository from a blueprint, you possibly can add a blueprint to an present code base in a repository on any of these three methods, and it’s also possible to create customized blueprints saved in your exterior repositories hosted on GitHub, GitLab.com, or Bitbucket Cloud.
CodeCatalyst blueprints assist to hurry up your developments. These pre-built templates present a supply repository, pattern code, steady integration and supply (CI/CD) workflows, and built-in concern monitoring to get you began rapidly. Blueprints robotically replace with greatest practices, protecting your code fashionable. IT leaders can create customized blueprints to standardize growth on your group, specifying know-how, entry controls, deployment, and testing strategies. And now, you need to use blueprints even when your code resides in GitHub, GitLab.com, or Bitbucket Cloud.
Hyperlink your CodeCatalyst area with a git repository internet hosting service
Getting began utilizing any of those three supply code repository suppliers is simple. As a CodeCatalyst area administrator, I choose the area the place I need to configure the extensions. Then, I choose Settings, and within the Put in extensions part, I choose Configure to hyperlink my CodeCatalyst area with my GitHub, GitLab.com, or Bitbucket Cloud account.
This can be a one-time operation for every CodeCatalyst area, however you may need to join your area to a number of supply suppliers’ accounts.
When utilizing GitHub, I additionally must hyperlink my private CodeCatalyst person to my GitHub person. Below my private menu on the highest proper facet of the display, I choose My settings. Then, I navigate right down to the Private connections part. I choose Create and observe the directions to authenticate on GitHub and hyperlink my two identities.
This can be a one-time operation for every person within the CodeCatalyst area. That is solely required while you’re utilizing GitHub with blueprints.
Create a venture from a blueprint and host it on GitHub, GitLab.com, and Bitbucket Cloud
Let’s present you create a venture in an exterior repository from a blueprint and later add different blueprints to this venture. You need to use any of the three git internet hosting suppliers supported by CodeCatalyst. On this demo, I selected to make use of GitHub.
Let’s think about I need to create a brand new venture to implement an API. I begin from a blueprint that implements an API with Python and the AWS Serverless Software Mannequin (AWS SAM). The blueprint additionally creates a CI workflow and an concern administration system. I would like my venture code to be hosted on GitHub. It permits me to instantly use supply information from my repository in GitHub and execute actions inside CodeCatalyst workflows, eliminating the necessity to swap platforms.
I begin by deciding on Create venture on my CodeCatalyst area web page. I choose Begin with a blueprint and choose the CodeCatalyst blueprint or Area blueprint I need to use. Then, I choose Subsequent.
I enter a reputation for my venture. I open the Superior part, and I choose GitHub as Repository supplier and my GitHub account. You may configure further connections to GitHub by deciding on Join a GitHub account.
The remainder of the configuration depends upon the chosen blueprint. On this case, I selected the language model, the AWS account to deploy the venture to, the identify of the AWS Lambda perform, and the identify of the AWS CloudFormation stack.
After the venture is created, I navigate to my GitHub account, and I can see {that a} new repository has been created. It comprises the code and sources from the blueprint.
Add a blueprint to an present GitHub, GitLab.com, or Bitbucket Cloud venture
You may apply a number of blueprints in a venture to include useful parts, sources, and governance to present CodeCatalyst initiatives. Your initiatives can help varied components which are managed independently in separate blueprints. The service documentation helps you be taught extra about lifecycle administration with blueprints on present initiatives.
I can now add a blueprint to an present venture in an exterior supply code repository. Now that my backend API venture has been created, I need to add an internet software to my venture.
I navigate to the Blueprints part within the left-side menu, and I choose the orange Add blueprint button on the top-right a part of the display.
I choose the Single-page software blueprint and choose Subsequent.
On the subsequent display, I be certain that to pick my GitHub connection, as I did once I created the venture. I additionally fill within the required data for this particular template. On the best facet of the display, I evaluation the proposed adjustments.
Equally, when utilizing CodeCatalyst Enterprise Tier, I can create my very own customized blueprints to share with my teammates or different teams inside my group. For brevity, I don’t share step-by-step directions to take action on this put up. For extra data, see Standardizing initiatives with customized blueprints within the documentation.
When CodeCatalyst finishes putting in the brand new blueprint, I can see a second repository on GitHub.
Single or a number of repository methods
When organizing code, you possibly can select between a single massive repository, like a toolbox overflowing with every part, or splitting it into smaller, specialised ones for higher group. Single repositories simplify dependency administration for tightly linked initiatives however can grow to be messy at scale. A number of repositories supply cleaner group and improved safety however require planning to handle dependencies between separate initiatives.
CodeCatalyst enables you to use the very best technique on your venture. For extra data, see the part Retailer and collaborate on code with supply repositories in CodeCatalyst within the documentation.
Within the instance I confirmed earlier than, the blueprint I chosen proposed to use the second blueprint as a separate repository in GitHub. Relying on the blueprint you chose, the blueprint might suggest that you simply create a separate repository or merge the brand new code in an present repository. Within the latter case, the blueprint will submit a pull request so that you can merge into your repository.
Area and availability
This new GitHub integration is obtainable at no further price within the two AWS Areas the place Amazon CodeCatalyst is obtainable, US West (Oregon) and Europe (Eire) on the time of publication.
