Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)

Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.

Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)

Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.

Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional

A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.

Slide 2
Master the art of DevOps
Master in DevOps Engineering (MDE)

Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.

Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert

Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.

Slide 3
Learn and get certified
AWS Certified DevOps Professional

Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.

previous arrow
next arrow

Disadvantages of Bamboo – Bamboo Expert Review

bamboo-disadvantage
Spread the Knowledge

bamboo-disadvantage

Bamboo Disappointment
Being a big fan of Atlassian’s Confluence and Jira, it was with much anticipation that installed Bamboo, the continuous integration (CI) engine they’ve released. Perhaps these high expectations led to my ultimate disappointment with Bamboo, but truly the features I’ve come to expect in a commercial CI product are nowhere to be found.

No concept of inherited project structure.
If you have 20 modules you would like to build, defining behavior and properties for each is a daunting task. QuickBuild and AntHillPro both allow for a hierarchal organization of modules, so that a child may inherit properties (like environmental variables, build targets, etc) of its parent. In Bamboo, when creating a “Plan”, I can clone an existing module, but that’s it. Should I have the need to change a property for all plans, I’ll be forced to configure each through the web GUI. A tedious process — even with Cruisecontrol I could search & replace config.xml in a text editor to make wholesale changes.

Alien nomenclature
In Bamboo, you have top-level “projects”, and beneath them you have “plans”, which represent the modules being built. I’ve never used the word “plan” before when describing a module’s build, and frankly the limited options offered by Bamboo to govern build behavior makes it a dubious word choice.

No passing of properties
It is sometimes desirable to direct a CI engine to pass arbitrary properties to one’s build process, and vice versa. I don’t mean “static” environmental variables, rather I refer to dynamic properties like “version number”. No such functionality is present in Bamboo. Luntbuild and Quickbuild both allow for this using OGNL expressions.

No concept of build promotion
Most commercial CI products have evolved to include “Application Lifecycle Management”, so you may describe how a build can go from being development-status to gold. Implicit in this is a workflow allowing QA to promote and release builds. None of this is even hinted at in Bamboo — it does not even tag your build.

Reference:
http://poorinnerlife.blogspot.com/2007/09/bamboo-disappointment.html

 

Facebook Notice for EU! You need to login to view and post FB Comments!
Rajesh Kumar