5 ms·
Bob CD
- olodus 4y agoNo real critique against this project but where I work we have an in-house build system called Bob and I've heard several other companies that have systems named the same. The Bob the builder reference is too easy to pick up I guess. We need to get more creative with our project names nowadays people. Things with too obvious references are usually not smart enough.
- nyanpasu64 4y agoI had thought this would be Microsoft Bob shipped on a CD-ROM ;)
- froggertoaster 4y agoMe too! What a 90's throwback.
- Aloha 4y agoWasn't it shipped in a CD in the first place?
- lostgame 4y agoWas mildly disappointed when I found out it had nothing to do with MS Bob, not going to lie. What a strange and weirdly beautiful piece of misguided computing history.
- garduque 4y agoThat's why I clicked. Ah well.
- antihero 4y agoHow does this compare with Concourse?
- twic 4y agoMy question too! They say a goal is [1]: > Be more extensible than great things like Concourse.ci There's a "Bob vs the rest of the CI tools" section in the docs, but none of it really applies to Concourse. [1] https://bob-cd.github.io/pages/why-bob.html https://bob-cd.github.io/pages/why-bob.html
- lipsyclouds 4y agohello! the author here! this has been pretty much made with the intention of me trying to address some of the shortcomings i experienced in the kind of tooling ive used over the years as an infra/sre person. never made it with the intention of making it general enough tool for everyone but more as a manifestation of what i think tools could've been like. it draws a lot of inspiration from concourse but improves on aspects like decoupling the way one can describe things for instance in YAML like concourse, no central controller in the cluster and things like being designed for being cloud native upfront by having rootless unprivileged runners etc. the way i see it concourse is a production ready, general version of this and other people like the idea of bob, it could be too by evolving more on the ideas of concourse.
- codeulike 4y agoPeople should expand acronyms at least one place somewhere on the page. I'm now three clicks deep and looking through the youtube comments and still a bit vague as to what this is. CI/CD? Thats continuous integration right? Should everyone know thats what CI stands for? I'm sure its a very useful thing but I havent personally ever used it even though I've been a programmer for 40 years. So I'm not that famailiar with the acronyms. My point being - our industry is big and not everyone uses every thing, or knows what it is, so its useful to expand acronyms somewhere in the description.
- ranger_danger 4y agoI assume it's mainly targeted at devops people who absolutely know what CI/CD is and use it all the time.
- cassianoleal 4y agoEvery person involved in software engineering should be aware of CI/CD and use it all the time, not only "devops people".
- senand 4y agoAgreed. However, I still believe explaining acronyms is good practice.
- bajsejohannes 4y agoEvery person who should be aware of CI/CD needs to learn it at some point.
- codeulike 4y agoI'm in software engineering and I'm aware of continuous integration but rarely use it and when I see CI its not the first thing that springs to mind. Any questions?
- capableweb 4y agoThis case is a special though, as Bob CD is not a 100% complete package for doing CI/CD, it is one fundamental building piece for building your own CI/CD solution on top of. So devops people would use Bob CD to build their in-house solution for it, and everyone would be using that, without actually using Bob CD directly.
- bheadmaster 4y agoFinally, we can use Bob to automate build of Vegana [0]. [0] http://biodiver.bio.ub.es/vegana/WhatsVegAna.htm http://biodiver.bio.ub.es/vegana/WhatsVegAna.htm
- LocalH 4y agoFinally a valid use case to request someone open them
- throwawaaarrgh 4y agoThe use of XTDB and RabbitMQ is annoyingly overcomplicated. Why have a central database? Why not use a simpler more standard storage mechanism, or just pluggable storage for each component? Why not just use HTTP calls to static nodes instead of RabbitMQ?
- capableweb 4y agoI don't know much about RabbitMQ, but with XTDB, it basically runs in the application already (akin to sqlite) while using another DB engine for the actual storage. So with XTDB you can store things in memory, on disk via rocksdb, or JDBC connection (whatever that supports, MySQL, PostgreSQL and so on)
- lipsyclouds 4y agohello! the author here! the primary reason for going with this architecture is to make it scale well with off the shelf production ready tooling. RabbitMQ was chosen to provide a scalable durable queue for backpressure support and load balancing across runners, error handling etc. it adds onto the infra weight a bit but seems to be a simpler choice to program against and use libraries. The reasons for XTDB are mainly 2: it provides a temporal immutable store, hence the whole state of the CI system can immutably evolve like a git repo hence the whole thing can be inspected at a previous time. Bob treats time as a first class thing and not just build logs but you should be able to see the whole cluster at a past time and debug it fully as all of the state is the DB. The second reason is like @capableweb said, it decouples storage from compute so that we can have a pluggable storage and not a central point of compute.
- XCSme 4y ago> Everything should be made as simple as possible, but no simpler I would rather have the hero text describe what the product is/does instead of it being an inspirational quote.