Tag / continuous-integration

    Loading posts...
  • Inspecting changes locally before pushing

    If you work on your branch you run into the situation that you would like to push your changes to the remote repository. CI will then pick up your changes and run the linting and code quality checks on it. Afterwards, you will see whether you improved the quality. But perhaps there are some new violations that crept into the code? Happens to all of us!

    I usually like to see and check if any new issues might come up on CI. This lets me improve them before I push.

  • What role does CI/CD play in your PR?

    My guideline for development workflows leans heavily on having a CI/CD server that orchestrates the whole workflow. CI/CD means continuous integration and continuous deployment. There is a lot to CI, and why…

  • Computer says “no”

    […] we do have formal rules that we should obey when writing code. A team has rules, and new team members need to learn them before trying to write any code. That’s…

  • Did you see it?

    The last few days I wrote about continuous integration without a branching model. I told you who coined the term and who wrote the book about it. I don’t know about you,…

  • Disadvantages of CI without branches

    Bonus, a third advantage: Your team would tend to favour pair programming. For the simple reason that you wouldn’t have pull/merge requests. I gave you this statement at the end of last…

  • Advantages of CI without branches

    Yesterday I wrote about what continuous integration means in its purest form. Today I want to share one or two ideas on how that might be good for you. If you do…

  • Build Server or Continuous Integration?

    CircleCI, Jenkins, TravisCI (recently acquired), GitLab CI. You know how they work, I believe. If you want to do Continuous Integration, almost all of us are doing it wrong. (Of course, it…