DEV Community: Florian Baba

A githooks example, and how to share it with the team

Florian Baba — Sun, 14 Mar 2021 17:56:32 +0000

Introduction

Regarding githooks, I had 3 different goals:

📜 Verify that my commits respect the expected format (hook n°1)
🔧 Check unit tests are green before every git push (hook n°2)
👥 Share these hooks with my team

A bit of context

Just for the record, my project was made with Symfony/PHP, and launched via docker/docker-compose.

But since the main goal here is to use githooks, you can adapt following lines for your own context and needs 😃

ℹ️ Note: Once a git init is made on your project folder, you can find githooks examples in ./.git/hooks in folder as .sample files.

Let's do it

Step 1 - 📜 Verify commit-message format

With my team, we decided to use specific commit formats in order to facilitate the way to consult our git history.

Here are the formats:

## Example of a commit linked to a specific ticket
[PSBO-723] An amazing commit message

## Example of a commit linked to a hotfix
[hotfix] A hot message for a hot commit

First, I need to create a regex that matches only these formats:

^\[(hotfix|\w+\-[0-9]+)\]( \w+)+$

Then I have to create the githooks that will check the commit message format every time I will try to commit.

To do it I create the hook file as .git/hooks/commit-msg in my project folder:

#!/usr/bin/env bash

echo "Checking commit-message format..."

## the first arg is the path to the git commit temporary file
TEMPORARY_FILE_PATH=$1

## get commit-message from the temporary file
COMMIT_MSG=`head -n1 $TEMPORARY_FILE_PATH`

## init regex to match commit-message format
REGEX="^\[(hotfix|\w+\-[0-9]+)\]( \w+)+$"

## checking commit-message format
if ! [[ $COMMIT_MSG =~ $REGEX ]];then
    echo -e "Your commit-message format is not valid:\n$COMMIT_MSG\n"
    echo "Valid format examples:"
    echo "[PSBO-123] My commit message"
    echo "[hotfix] My commit message"
    exit 1
else
    echo "Well done! Your commit-message is valid."
    exit 0
fi

Once done, don't forget to give to the file the right to be executed.

sudo chmod +x .git/hooks/commit-msg

Let's test the hook

Now, if I try to commit with an invalid message:

git commit -m "Yehaaaa"

It returns:

Checking commit-message format...
Your commit-message format is not valid:
Yehaaaa

Valid format examples:
[PSBO-123] My commit message
[hotfix] My commit message

And the commit is canceled, as expected! 🎉

If I try to commit with a valid message:

git commit -m "[PSBO-456] It's a valid one this time"

It returns:

Checking commit-message format...
Well done! Your commit-message is valid.

And the commit is done! ✔️

Step 2 - 🔧 Launch unit tests before each `git push`

Let's do it again!
Since I want to check unit tests before pushing my code, I will create a hook file as .git/hooks/pre-push:

#!/usr/bin/env bash

echo "Checking unit-tests..."

## checking unit-tests
cd ./infra || exit
if sudo docker-compose run php bin/phpunit;then
    echo "Well done, unit-tests are green!"
    echo "'git push' is now done."
    exit 0
else
    echo "Unit-tests failed, therefore the push is canceled."
    echo "Please fix them before pushing again."
    exit 1
fi

Once again, I need to give this hook file the right to be executed.

sudo chmod +x .git/hooks/pre-push

So, let's check if it works in case my unit tests are failing.

First, I changed the code of a unit test so that it fails.
Now I try to git push to trigger the hook:

git add .
git commit -m "[hotfix] Breaking unit-tests"
git push origin develop

It returns

Checking unit-tests...
Creating infra_php_run ... done

Testing Project Test Suite
F                                                                   1 / 1 (100%)

There was 1 failure:

1) App\Tests\Util\CalculatorTest::testCalculate
Failed asserting that 15 is identical to 16.

/var/www/tests/Util/CalculatorTest.php:31

FAILURES!
Tests: 1, Assertions: 1, Failures: 1.
ERROR: 1
Unit-tests failed, therefore the push is canceled.
Please fix them before pushing again.

Tests failed, so the push is canceled, seems good! 👍

OK, this time I fixed the code of the unit test.
Then I push to trigger the hook once again:

git add .
git commit -m "[hotfix] Fixing unit-tests"
git push origin develop

It returns

Checking unit-tests...
Creating infra_php_run ... done

Testing Project Test Suite
.                                                                   1 / 1 (100%)

OK (1 test, 1 assertion)
Well done, unit-tests are green!
'git push' is now done.

Unit-tests are green, so the push was validated and done! This hook works as planned! 💃

Step 3 - 👥 Share githooks with the team

Now, my hooks are ready!

But unfortunately I can't share them with the team.

Why that?
Because githooks are ignored by git (as every other file in .git folder), therefore they can't be added to the index or be commited in anyway...

Unless we do some little magic! 🎩 🐰

ℹ️ Note: There are multiple solutions to solve this issue, I picked this one because I found it smart and easy to set up.

So to do the magic, I'm going to create my own githooks folder in the root path of the project (not in the .git folder):

## I create my own githooks folder
mkdir .githooks

## Then, move the githooks I created in this new folder
mv .git/hooks/commit-msg .githooks/
mv .git/hooks/pre-push .githooks/

## Don't forget to give "execute" right to the files, if not already done
sudo chmod +x .githooks/*

Now, I just need to tell git where to find my githooks files:

## Specify a folder for hooks (only available for git version >= 2.9)
git config core.hooksPath .githooks

And it's done!

From now one, I can commit these hooks since there are no longer ignored by git, so my teammates will be able to use them.

Conclusion

My githooks work, and I can share them with my team, it's all good! 🎉 💥

Hope this helped you find out how githooks work and how powerful they can be.

A Kubernetes memory aid for beginners

Florian Baba — Fri, 26 Jun 2020 08:52:57 +0000

Hello!
Since I'm a Kube beginner, I gradually started writing this memory aid.

It's not exhaustive at all, but it's a start :)
I hope it helps.

You'll need this alias for all the listed cmd: alias k='kubectl'

Contexts

List contexts (and show the current one)

k config get-contexts

Switch context

k config use-context <CONTEXT_NAME>

Pods

List pods

k get pod

Delete a pod

k delete pod <POD-ID>

Show pod details (and the events linked to the pod)

k describe pod <POD-ID>

Download a file from a pod

k cp <POD-ID>:<POD_FILE_PATH> <LOCAL_PATH>

Containers

Connect to a container using sh or bash

k exec -it <POD-ID> -c <CONTAINER-NAME> <sh|bash>

Logs

Show logs of a container

k logs <POD-ID> <CONTAINER-NAME> -f

Show all the logs of a deployment

k logs -f deployment/<DEPLOYMENT-NAME> --all-containers=true

Events

List events sorted by timestamp

k get event --sort-by .lastTimestamp

Secrets

Show secrets with age

k get externalsecrets

Deploys

List deploys on a cluster

k get deploy

List deploys on a cluster, with details

kubectl get deploy -o=custom-columns=NAME:.metadata.name,STATUS:.status.phase,VERSION:.metadata.labels.version

Show deploy status

k rollout status deploy/<DEPLOY-NAME>

Scale

Define the number of replicas

k scale deploy/<DEPLOY-NAME> --replicas=2

Show replicas sets

k get rs

Cron

Show cron jobs

k get cronjobs

Convert .ppk key for ssh connection on linux

Florian Baba — Thu, 18 Jun 2020 08:59:29 +0000

If you want to use a ssh key as a .ppk file (putty format) on linux, first you need to convert it.

To do it, install putty-tools:

sudo apt-get install putty-tools

Now you can convert your key from .ppk format to .key format:

puttygen <your_key_name>.ppk -O private-openssh -o <your_key_name>.key

And voilà! 😀
You can use it to open your ssh connection:

ssh -i <your_key_name>.key <user>@<server-ip>

Scrum retrospective template

Florian Baba — Fri, 12 Jun 2020 15:31:17 +0000

Date	Team	Participants	Writer	Timekeeper
2020-01-01	Team name	Camille, Fred, Paul	Camille	Fred

Sprint review

Sprint goal

Name or description of the sprint goal

Velocity

NB: Velocity = Story points done / Total presence days

Total presence days	Story points planned	Story points done	Velocity	Successful sprint goal
33	65	86	2.6	yes

Burndown chart

<-- insert burndown image -->

Sprint ROTI

Product owner	Developers
4/5	4.5/5

Demo

Audience ROTI	Link to the demo
3.9/5	<-- demo-link -->

Retrospective

Format: The boat

The boat	The island	The wind	The anchors	The reef

Thanks

Special thanks to <-- a great co-worker --> for his help during this sprint.

Chosen topics & actions

Topic	Actions
A topic	A great action linked to this topic
Another topic	A smart action

Retrospective ROTI

Team
4.3/5