I’m blissful to announce that we’re additional integrating Amazon CodeCatalyst with two well-liked code repositories: GitLab and BitBucket, along with the present integration with GitHub. We convey 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 improvement and supply service. It allows software program improvement groups to rapidly and simply plan, develop, collaborate on, construct, and ship functions on Amazon Net Providers (AWS), lowering friction all through the event lifecycle.
The GitHub, GitLab.com, and Bitbucket Cloud repositories extension for CodeCatalyst simplifies managing your improvement workflow. The extension means that you can view and handle exterior repositories immediately inside CodeCatalyst. Moreover, you’ll be able to retailer and handle workflow definition recordsdata alongside your code in exterior repositories whereas additionally creating, studying, updating, and deleting recordsdata in linked repositories from CodeCatalyst dev environments. The extension additionally triggers CodeCatalyst workflow runs routinely upon code pushes and when pull requests are opened, merged, or closed. Moreover, it means that you can immediately make the most of supply recordsdata from linked repositories and execute actions inside CodeCatalyst workflows, eliminating the necessity to change platforms and maximizing effectivity.
However there’s extra: beginning as we speak, you’ll be able to create a CodeCatalyst mission in a GitHub, GitLab.com, or Bitbucket Cloud repository from a blueprint, you’ll be able to add a blueprint to an current code base in a repository on any of these three programs, and you may as well 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 routinely replace with finest practices, holding your code fashionable. IT leaders can create customized blueprints to standardize improvement on your workforce, specifying expertise, entry controls, deployment, and testing strategies. And now, you should utilize 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 straightforward. 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.
It is 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 consumer to my GitHub consumer. Underneath my private menu on the highest proper facet of the display, I choose My settings. Then, I navigate all the way down to the Private connections part. I choose Create and observe the directions to authenticate on GitHub and hyperlink my two identities.
It is a one-time operation for every consumer within the CodeCatalyst area. That is solely required if you’re utilizing GitHub with blueprints.
Create a mission from a blueprint and host it on GitHub, GitLab.com, and Bitbucket Cloud
Let’s present you the best way to create a mission in an exterior repository from a blueprint and later add different blueprints to this mission. You should utilize 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 mission 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 mission code to be hosted on GitHub. It permits me to immediately use supply recordsdata from my repository in GitHub and execute actions inside CodeCatalyst workflows, eliminating the necessity to change platforms.
I begin by deciding on Create mission on my CodeCatalyst area web page. I choose Begin with a blueprint and choose the CodeCatalyst blueprint or House blueprint I need to use. Then, I choose Subsequent.
I enter a reputation for my mission. I open the Superior part, and I choose GitHub as Repository supplier and my GitHub account. You’ll be able to 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 mission to, the identify of the AWS Lambda operate, and the identify of the AWS CloudFormation stack.
After the mission is created, I navigate to my GitHub account, and I can see {that a} new repository has been created. It comprises the code and assets from the blueprint.
Add a blueprint to an current GitHub, GitLab.com, or Bitbucket Cloud mission
You’ll be able to apply a number of blueprints in a mission to include useful elements, assets, and governance to current CodeCatalyst initiatives. Your initiatives can help numerous components which might be managed independently in separate blueprints. The service documentation helps you be taught extra about lifecycle administration with blueprints on current initiatives.
I can now add a blueprint to an current mission in an exterior supply code repository. Now that my backend API mission has been created, I need to add an online software to my mission.
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 ensure to pick out my GitHub connection, as I did once I created the mission. I additionally fill within the required info for this particular template. On the correct facet of the display, I evaluation the proposed modifications.
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 publish. For extra info, 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’ll be able to select between a single giant 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 turn into messy at scale. A number of repositories provide cleaner group and improved safety however require planning to handle dependencies between separate initiatives.
CodeCatalyst permits you to use the most effective technique on your mission. For extra info, 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 current 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 out there at no further price within the two AWS Areas the place Amazon CodeCatalyst is out there, US West (Oregon) and Europe (Eire) on the time of publication.










