CI/CD

 What I learned today:





CI/CD stands for continuous integration and continuous delivery. It is a set of practices and tools to streamline and improve the process of software and delivery. Specifically, we are talking about doing the build, deploy and test phases in small frequent steps. Overall, CI/CD make delivery more efficient and reduces the manual overhead involved.


Continous Integration - Automating the frequent merging of code, often many times a day. An important part of this process is version control using a shared repository like git to catch merge conflicts before we ship it. The next step after merge is to compile, test the code(Ideally, this is what we should do but I have worked in repos where we didn't do testing but we were siloed so I couldn't do much) and build


Continous Delivery - automates the deployment process so that changes to the codebase can be automatically released. Once the code passes all the tests, the pipeline automatically deploys to a staging or production environment. 


Benefits of CI/CD: 

  • Faster Time to Market.
  • Improved Code Quality: testing can catch things earlier
  • Lower Risk: Frequent integration and deployment makes it easier to catch any issues during the process
  • Better Collaboration: Everyone can see the status of the integration and deployment at any time.


Comments

Post a Comment

Popular posts from this blog

Lifecycle of React components

 What I learned today : how to use lifecycle of React components without using class When we talk about the lifecycle of react components, we are talking about Mounting Unmounting Updating The reason it is important to understand is because there are side effects that we need to perform during the lifecycle of a component such as api calls, initialization, and cleanups(release resources like event listeners). 1) mounting - when a component is first is injected into the DOM and rendered for the first time 2) unmounting - when a component is removed from the DOM and is no longer being rendered 3) Updating - when a state inside the component changes or prop is passed into the component The useEffect hook is useful and can run in all of these different lifecycles. import { useEffect } from 'react' The basic syntax takes in a callback function: useEffect (() => {   //code }) this will run everytime a component mounts or updates. In order to run only when the component mounts:
Read more

Styled Components

Image
 What I learned today: Styled-components provide several advantages, particularly in component-based web development To get started install the 'styled-components' package. Then you can optionally create a directory to contain all of your styled components Then you can define it like this for example: const Wrapper = styled . div `   position : relative ;   .logout-btn {     display : flex ;     align-items : center ;     justify-content : center ;     gap : 0 0.5rem ;   }   .img {     width : 25px ;     height : 25px ;     border-radius : 50% ;   } And then you can apply your CSS by simply wrapping it around your React components.   return (     < Wrapper >         < button type = 'button' className = "btn logout-btn" />       </ Wrapper >   ) Some advantages of styled components: Scoped Styling : Styles are scoped to specific components, ensuring they don't leak into other parts of the application. This prevents style conflict
Read more

e-commerce website built with React.nodejs

Image
            This is a responsive e-commerce website I built with React and Nodejs. Users can browse, add goods to the cart, and checkout with a valid credit card number Live Demo    (you can use this test credit card #: 4242 4242 4242 4242)            Repo frontend           Repo backend                 First things first - creating a landing page        I wanted to spend some time making the marketing page look good because I felt like an ecommerce site should look as attractive as possible. Styling was done with vanilla css. I made sure this site was responsive using media queries.       Creating the backend   I didn't think I would need my own backend for this project but I couldn't find an API that fit the type of products I wanted to "sell". So I created my own. Two notable features I used are: JWT authentication and Stripe (to process the payment by customers). The backend is set up  so that users can login or checkout as guests and it will handle the payments
Read more