• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Pipeline as Code: CI/CD for a very small team/project?

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello Mr. Mohamed Labouardy,

My question is: In a very small team of 3 developers, for a very small project and company/organization, do you really need the complexity of a CI/CD workflow? If you do, how much expertise is required?
Thanks.
 
Greenhorn
Posts: 18
Java ME Quarkus Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The author may have a different opinion on this, but I would still use CI if more than 2 people are involved in touching the same codebase and potentially "stepping on each other's toes". Even if you implement simple workflow like "You push your code to GitHub" -> "GitHub triggers CI to test & build" -> "Your build passed!", it immediately gives you more efficiency without much expertise. For this simple scenario, I would probably use something like Travis CI if you don't want to manage another tool in your arsenal.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic