In this second part we are going to setup Slack o be ready to be implemented in the pipeline that we are going to create in the next parts. We are going to create an Account,Workspace,App (a bot) and mess around a bit to get some confidence with the Slack API.

Account, Workspace and Channel Creation

If you do not have already a Slack account, just navigate to:

https://slack.com/

And we can sign up with a google account. After some possible verifications, we should be redirected to the following page:

Slack home page after logging in

Slack get-started page after signing up

Let’s click the button Create a Workspace , and name it Simple Web App :

naming workspace - screen

Naming the workspace

After clicking Next we will be prompted with a question asking us what we are currently working on. Let’s put there CI-CD Pipeline :

naming channel — screen

Put ‘CI-CD Pipeline’ in the input field, which will be converted in a channel

As we can see after hitting Next , on the left we have:

screen of the new channel just created

And this will be the channel through which we will communicate from the Jenkins server.

In the next Step we can hit Skip this step and confirm.

screen for skipping the next step

Cool, we created a workspace and a new channel. At this point, we need to create an App in order to use the Slack API.

#ci-cd-pipeline #jenkins #aws #terraform #docker #bitbucket

Build a complete CI/CD Pipeline with AWS - Jenkins - Bitbucket - Docker - Terraform
1.80 GEEK