Bamboo is a continuous integration (CI) server that can be used to automate the release management for a software application, creating a continuous delivery pipeline. Bamboo is a commercial product from atlassian. BAMBOO has multiple plugins to customize its usage. Further one can also extend the functionality  by writing its own plugins using the SDK’s provided. Some good points are that  Bamboo is an atlassian product, the integration of JIRA issue tracker and Clover, the code coverage tool, becomes easy with bamboo. However, the Automatic Branching/Merging backing makes Bamboo a far more pleasant work process for engineers.

It is a very popular dev tool company.It out of the box supports for Java, .NET, PHP, Javascript among others tools and completely automated with slick web UI. Bamboo has the ability to deploy parallel builds to multiple agents and build pipelines make it easy to create workflows. The analytical tools help highlight what went wrong. Few more things about Bamboo:

• Supports programmed stretching and combining
•  Integrates with many source control systems. Integrates well with rest of Atlassian suite. So on the off chance that you utilize Jira for bugs and story administration, and intersection for documentation, it’s anything but difficult to get bamboo to auto close stories/bugs as they’re sent, and overhaul conjunction documentation with each finished story.
• Has some cool extravagant accessories like recognizing if an arrangement is as of now halted.
• It’s elusive plugins for non-regular assignments or setup.
• It’s less well known than Jenkins. Hard to discover different clients to talk shop or request help.

Share

The post Continuous integration(CI) tool :: Bamboo appeared first on Blog.

JENKINS is a Continuous Integration (CI) server or tool which is written in java. It provides Continuous Integration services for software development. Its an “Open source community with many plugins & flexibility as an automation platform. Also, it is a free software to download and install. To pass your code into production as soon as one check in the code into VCS without anybody’s involvement is what Jenkins does. It Builds  code, performs test cases, Builds  artifacts and publishes it into the production. Jenkins can help one to execute a build on every change in version control system, git/subversion. It is a good tool for automating the execution of one’s build script. It can also build periodically so one will know that the build works even when the source code hasn’t changed. The build script has to do all steps needed, compile, test, package, acceptance tests and so forth. The build script must be possible to execute from a command line.

Some advantages of using Jenkins::
– Building/testing software projects continuously. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project. The automated, continuous build increases the productivity.
– It is easy to install.
Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine.
• It has 1000+ plugins to ease your work.
• It is built with Java and hence, it is portable to all the major platforms.
• It is also used for deployment of released artifact with custom scripts.
• It provides continuous integration pipeline support for establishing software development life cycle work flow.
• It also provides support for scheduled builds & automation test execution.
• One can configure Jenkins to pull code from a version control server like GitHub, BitBucket etc. whenever a commit is made.
• Whenever a commit is made to the source code, in the shared repository, like GitHub, Jenkins server will pull that code and trigger a build.
• Once it is compiled, Jenkins will then deploy that build application on the test servers for testing.

Share

The post The Best CI Tool :: Jenkins appeared first on Blog.