DevOps on Aamnah - Frontend Web Developer

Trigger a Netlify build when a Github repo is updated

Tue, 17 Oct 2023 17:41:51 +0300

Why?

I have a separate repo linked to my Hugo site as a Hugo module. That repo contains all the content for my notes section and is separate from the repo for my main website. The main website gets automatically deployed by Netlify.

What does not happen right now is that whenever i update the content for the notes section, the main site does not get updated as a deployment is not triggered by Netlify.

Install Embedded Dart Sass on Netlify

Mon, 06 Feb 2023 15:13:13 +0500

NOTE: In 2023, the Sass team deprecated Embedded Dart Sass in favor of Dart Sass. Embedded Dart Sass is no longer a requirement since Hugo version 0.114.0.

If you have been using Embedded Dart Sass with Hugo v0.113.0 and earlier, uninstall Embedded Dart Sass, then install Dart Sass. If you have installed both, Hugo will use Dart Sass.

The old build/install script for Netlify setups is saved as a Github gist.

Setting up a sudo User with SSH key access an Azure Virtual Machine (Ubuntu)

Wed, 26 May 2021 20:21:41 +0500

You can create a new user from the Support + troubleshooting > Reset password screen. By default, it’ll update the password for the given account. But if the given account does not exist, it’ll create one, add it to sudoers list (make sure it can run sudo commands) and then set the password for it too.
The ~/.ssh folder doesn’t exist when you create a new user. So you have to create it, and the authorized_keys file to add accepted keys that can connect to the server and set the right permissions for both
Setting permissions is important because SSH will not connect if the permissions are too open
authorized_keys is where you add the contents of the .pub file of your key pair.

Set the server up to accept SSH key for the user

Doing automated Git Flow branch deploys on their own Expo release channels with Bitbucket Pipelines

Thu, 23 Jul 2020 11:12:36 +0500

background

I have an Expo based React Native app that i publish with expo publish
I follow git flow branch naming and structure
I gave multiple people working on plenty of features that we need to test separately

what i want

Publish every branch to it’s own release channel automatically

the issue

Because i’m using Git Flow, the branch naming is feature/my-awesome-branch. I can get the branch name with a built-in pipeline variable, but the / after feature doesn’t work with Expo release channel naming. You can’t have a / in a release channel name..

Notes on Bitbucket Pipelines

Thu, 02 Jul 2020 00:19:00 +0500

Container `Build` exceeded memory limit.

This can happen for large steps, in my case building an app bundle with turtle-cli. You can double the memory allocation for a step with size: 2x

Regular steps have 4096 MB of memory in total, large build steps (which you can define using size: 2x) have 8192 MB in total.

ref, ref

1- step: &turtle-build-android
2    name: Build app bundle (.aab)
3    image: ubuntu:focal
4    size: 2x # Double resources available for this step.
5    caches:
6      - npm
7    script:
8      - echo 'this is my step with 2x memory'

Get the commit message for the commit that triggered the pipeline

1pipelines:
2  default:
3    - step:
4        script:
5          - COMMIT_MESSAGE=`git log --format=%B -n 1 $BITBUCKET_COMMIT`
6          - echo $COMMIT_MESSAGE

ref

Azure DevOps Getting Started

Tue, 17 Mar 2020 00:00:01 +0500

Notes

You can only use Azure DevOps if the source repo is at Github or Azure DevOps (both Microsoft owned)
How much do repos on Azure DevOps cost? Bitbucket costs us $28 for 8 users. That’s $3/user/month. Cheaper than Github. Azure Repos is free for first 5 users and then $6 per additional user. 8 users would cost us $18/month.

Costs

Bitbucket	Azure Repos	Github
First 5 users free, then $3/user/month	First 5 users free, then $6/user/month for subsequent users	First 3 users free, then $7/user/month

14 days of DevOps

Tue, 17 Mar 2020 00:00:00 +0500

Background

I have already setup CI/CD for a React Native project, it uses Bitbucket Pipelines and deploys to different release channels on Expo
I have already setup CD for a .NET Corde project that deploys to AWS Elastic Beanstalk (EBS)

I’m not entirely new to DevOps, and i’m entirely self-taught. Google and SlackOverflow are my best friends

DevOps goals

Fast time-to-market (TTM)
Few production failures
Immediate recovery from failures

Automation leads to consistency and stability - code is built, tested and deployed the same way every time

Deploy to separate Expo release channels based on Bitbucket feature branches

Wed, 26 Feb 2020 00:00:00 +0500

What i need is to test multiple feature branches at the same time by deploying it to Expo. And i can’t be bothered with doing that manually.

$BITBUCKET_BRANCH is available, but it can not be used in custom pipelines (triggered from a commit) or used against tags. If you use it under the branches: block, it’ll fail, because those are run on commits.
You can only use it in a step that is manually triggered, inside a custom pipeline. Otherwise $BITBUCKET_BRANCH is not set. It outputs nothing in default: pipeline or branches: pipelines
First step in a pipeline can not be manually triggered
A trigger can only be executed if the previous step has successfully completed
If you use git-flow and have / in branch names (e.g. feature/profile), it will fail to work. Because Release channel name can only contain lowercase letters, numbers and special characters . _ and -

Here’s working code

Bitbucket Pipelines: Overview and Notes

Wed, 23 Oct 2019 16:30:01 +0500

So far i have used pipelines in 2 different projects. One is a .NET Core API that gets deployed to AWS Elastic Beanstalk and the other is a React Native app that gets deployed to Expo.

Here’s the tl;dr

Basically, you can use custom yaml files to describe what happens after you push code to your repository. Bitbucket will lift some instance and allocate computing power for you, for running the code you describe in the yaml, and you’re paying for the time it takes to run. You can also use some caching techniques to make sure you don’t download large libraries over and over again.

Deploy a .NET Core API to AWS Elastic Beanstalk using Bitbucket Pipelines

Wed, 23 Oct 2019 16:30:00 +0500

Artifacts
Repository Variables
Elastic Beanstalk Pipe
IAM Role

Here is my bitbucket-pipelines.yml file:

 1# Pipelines to be updated later after it has been tested
 2# more code will follow
 3image: microsoft/dotnet:sdk
 4
 5pipelines:
 6  default:
 7    
 8    - step:
 9        name: Restore packages
10        caches:
11          - dotnetcore
12        script: 
13          - dotnet restore
14
15    - step:
16        name: Build the project
17        caches:
18          - dotnetcore
19        script: 
20          - dotnet build ${PROJECT_NAME}
21
22    - step:
23        name: Run Unit Tests
24        trigger: manual
25        caches:
26          - dotnetcore
27        script:
28          - dotnet test ${PROJECT_UNITTESTS_NAME}

I’m automatically deploying the production environment as soon as a change is pushed to master
I’m adding a step to be able to manually trigger a deploy to staging when develop branch is updated. This is because develop gets frequent changes and i don’t want to run out of my build minutes (free plan has 50mins/month) by triggering a deploy every time.
For all other branches (feature/* etc.) i’m adding the ability to manually trigger a build and not deploy anything. This is because i’m not expecting to build feature branches much as they are usually tested locally
The variables are all defined under Settings > Repository variables

IAM Role

Create the following policy in IAM

Continuous Deployment for React Native app to Expo using Bitbucket Pipelines

Wed, 23 Oct 2019 16:29:59 +0500

Expo lets you deploy and test your app
Bitbucket Pipelines lets you run commands in a Docker container

`bitbucket-pipelines.yml`

bitbucket-pipelines.yml is the file that you need to commit to the root of your repo in order to enable Pipelines. I’d recommend going to the Pipelines page for your repo and generate one from there. It’ll commit it to your repo and you can edit the configuration later in your code editor.