Buildbot VS Oxidized

Buildbot is a versatile CI framework designed to automate all aspects of the software development cycle, enhancing efficiency and reliability. As an open-source platform, it is highly customizable, allowing teams to tailor the automation process to their specific needs. Buildbot excels in integrating various stages of development, from code integration, testing, to deployment, ensuring a seamless and coherent... - Source: dev.to / 4 months ago

If you want more than the builtin CIs in Github and Gitlab, https://buildbot.net is the way. Source: about 1 year ago

If you don't have one already integrated with your source control, buildbot is pretty nice and doesn't force you to use docker like most others. Source: over 1 year ago

Https://buildbot.net/ existed before Jenkins Hudson and was quite well known. Source: over 1 year ago

I have used python based CI tool buildbot which is a great tool but we want to move away from buildbot only because in some scenarios we want to compile low-level microseconds which are in c++ to a different architecture. Buildbot doesn't have such a feature. - Source: dev.to / almost 2 years ago

Or run a decent setup to keep backups, like this one: https://github.com/ytti/oxidized. Source: about 1 year ago

You didn't mention about brand of the switches, but majority of vendors is covered with Oxidized: https://github.com/ytti/oxidized Just configure it with git backend, and you have version control and device backups. Also, if you wish, there are bundled sone extra scripts that could report git changes via email. Source: about 1 year ago

RANCID was great before Oxidized ;) Https://github.com/ytti/oxidized From description of Oxi: Oxidized is a network device configuration backup tool. It's a RANCID replacement! Source: over 1 year ago

If you're just looking to backup/inventory configs, give Oxidized a try https://github.com/ytti/oxidized. Source: over 1 year ago

What about the tried and trusted oxidized? Source: over 1 year ago