CI/CD for Angular

With Buddy, you can create a pipeline that builds, tests, and deploys Angular applications on a push to Git. The configuration is super simple and takes 10 to 15 minutes.

Image loading...Angular pipeline example

1. Select your Git repository

Buddy supports all popular Git hosting providers, including GitHub, Bitbucket, and GitLab. You can also use your own private Git server, or host code directly on Buddy.

Image loading...Supported Git providers

2. Add a new delivery pipeline

Enter the pipeline's name, select the trigger mode, and define the branch from which Buddy will fetch your code:

Image loading...Adding new pipeline

Success

Event-based triggers allow you to run pipelines whenever a push is made to any branch in the repository, or whenever a branch, tag or a pull request is created or deleted. Image loading... On event pipeline trigger mode

3. Add actions

Buddy lets you choose from dozens of predefined actions. In this example, we'll add 4 actions that will perform the following tasks:

• Build and test Angular app: download dependencies (npm, yarn, etc.), run tests, compile assets (npm tasks, webpack, etc.)
• Upload code to server together with compiled assets
• Restart application
• Send notification to Slack

3.1 Build your Angular application

Look up and click Angular CLI on the action list to add it to the pipeline:

Image loading...Action list

The Run tab lets you determine the commands to execute. The default commands are:

bashnpm install
ng test --watch=false --browsers=ChromeHeadless$$

Image loading...Angular default build commands

3.1.2 Node version

You can change the version of Node (and thus the Angular it comes with) in the runtime environment tab:

Image loading...Angular action image

Tip

If your tests require a database to run, you can attach it in the Services tab: Image loading...Services tab

3.2 Deploy application to server

Now the application needs to be uploaded to the server. Head to the Transfer section and select your deployment action (SFTP in our case):

Image loading...Transfer action

When adding the action you can choose what and where should be uploaded:

Image loading...SFTP action configuration

3.3 Restart application

Once the app is deployed, you can run additional commands on your server with the SSH action:

Image loading...SSH action

Enter the commands to execute in Run CMDs and configure authentication details in the Target tab:

Image loading...Application restart command

3.4 Send notification to Slack

You can configure Buddy to send your team a message after the deployment. In this example we'll use Slack:

Image loading...Notification actions

Hint

If you add this action in the On Failure tab, Buddy will only send the message if something goes wrong with your build or deployment. Image loading... On failure notification

4. Summary

Congratulations! You have just automated your entire delivery process. Make a push to the selected branch and watch Buddy fetch, build, and deploy your project. With Continuous Delivery applied, you can now focus on what's really important: developing awesome apps! 🔥