Wikipedia:Articles for deletion/Bamboo (software) (2nd nomination)


 * The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review).  No further edits should be made to this page.

The result was redirect to Atlassian. There is consensus that references do not satisfy our requirements for companies and should not be a standalone article. A redirect to Atlassian is a valid alternative to deletion, however. Barkeep49 (talk) 02:19, 17 July 2020 (UTC)

Bamboo (software)
AfDs for this article: 
 * – ( View AfD View log  Stats )

Typical Corporate Brochure. Wiki is not White paper. No need for separate article for this product. Atlassian company page already exists to cover this. Light2021 (talk) 05:56, 2 July 2020 (UTC)
 * Note: This discussion has been included in the list of Software-related deletion discussions. Shellwood (talk) 05:59, 2 July 2020 (UTC)

Keep per the significant coverage in multiple independent reliable sources.      <li></li> <li></li> </ol>

<ol> <li> The book notes: "Bamboo is a commercial product created by an Australian company named Atlassian, also responsible for products like Confluence and, of course, Jira. If you've already been looking for a bug tracker, you've probably run into Jira at least once and may be using it at your company. If that's the case, then you will be happy to know that Bamboo is deeply integrated with Jira, making it super easy to create issues from a failing build, for example. ... If you were expecting a software based on a less-bloated platform you will be disappointed: Bamboo is written in Java. ... ...  With Bamboo, fetching the content from the repository is a task itself, a task you can configure if you want. There aren't many options for you to play with, but you can tell Bamboo to remove the content and re-clone the whole project every time you build your application. For an application as small as the GitHub Jobs one is, that would not make a huge difference but with big projects with huge resources and dependencies, this could significantly increase the duration of the build. You should leave this option unchecked for most of your builds."</li> <li> From Google Translate: "There are many CI systems in the world such as Jenkins and Travis CI, but this article focuses on Bamboo, a commercial Web application provided by Atlassian. In addition, I will explain Bitbucket and JIRA as the version control system and issue management system linked with Bamboo. ... Let Bamboo do the work Build & test  Bamboo sets up a build execution plan in a hierarchical structure called 'stages', ' jobs', and ' tasks'. This may sound a little complicated, but once you learn it, you can set the build execution plan with an intuitive UI using a Web browser, so be sure to remember it ( Fig. 1 ⁠ ). task It is a concept that refers to individual processes such as 'check out the source code' and ' build with ⁠Mavem 3.x '. Tasks cannot be executed in parallel and are executed in the set order."</li> <li> The article notes: "Atlassian Bamboo was integrated as a test harness to the heritage Test Framework for use on SPP to create, schedule and initiate execution of test suites. Bamboo also provides a mechanism to automate the configuration management repository check-out process, to provide easy accessibility to test execution reports and to disseminate execution status to test engineers. What is Atlassian Bamboo? Atlassian Bamboo is a continuous integration server used during software development to automate the release management process (e.g., compile, test, package, deploy) for software applications [8]. The Bamboo capability to trigger functional tests from a source repository is used to build and schedule SPP SpFSW test suite executions. After the test package is built and executed, the deployment feature of Bamboo is used to make the test execution artifacts available for viewing via a web server. Bamboo is also capable of generating email notifications to a distribution list containing execution status information retrieved for the completed jobs. Version and initiator information about the scheduled ‘job’ is provided on the Bamboo application interface. ... Under each Bamboo test plan there is a default job that check-outs the necessary folders from the GForge Subversion test script repository and invokes the main or application-level driver script for the desired test suite execution. For each ‘job’, relevant artifacts are generated, gathered and stored on the Bamboo Server for future use. These test artifacts are retrievable for viewing by the test engineers through the Bamboo Server web interface."</li> <li> The article notes: "Bamboo Bamboo is one of Atlassian products that support CI. It can be installed on a local machine or over the Internet. These tools are semi-paid, because it provides a trial in a few days. For GUI testing, this tool does not provide a plugin for using tools of SikuliX and JAutomate. But, there are several guides on the internet which makes Bamboo possible to perform GUI testing. It needs a deep investigation for implementing GUI testing in Bamboo with windows environment. ... Bamboo and SikuliX  Since bamboo does not provide a plugin for SikuliX, it would require further investigation regarding the combination of these tools. In some internet sources said about the possibility of testing GUI. To integrate both tools, author needs to create repository trigger in Bamboo and push the code into repository so that Bamboo can pull the code and build the code. Bamboo and JAutomate It similar with the combination of Bamboo and SikuliX, it needs deep configuration in Bamboo for implementing GUI testing. This build process is possible through the unit testing and direct from JAutomate source script."</li> <li> The article notes: "In this section, we will compare three CI solutions: Bamboo from Atlassian Tools, Travis CI from GitHub and Jenkins. All these three tools are commonly use by developers in different projects. The basic principle behind all of them is the detection of changes in the code repository and triggering a set of Jobs or tasks. ... The main concept in Bamboo build is Plan. A Plan defines everything about our continuous integration build process in Bamboo. By default, it has a single Stage, but we can use it to group Jobs into multiple stages. A Plan processes a series of one or more Stages that are run sequentially using the same repository. It also specifies how the build is triggered, and the triggering dependencies between the plan and other Plans in the Project. Every Plan belongs to a Project. A Stage maps Jobs to individual steps within a build process of Plan. For example, we may have a Plan build process that contains an Integration step followed by several Test steps and a Delivery step. We can create separate Bamboo Stages to represent each of these steps. By default, a Stage has a single Job, but we can use it to group multiple Jobs. A Stage processes its Jobs in parallel. It must successfully complete all its Jobs before the next Stage in the Plan can be processed. A Job is a single build unit within a Plan. One or more Jobs can be organized into one or more Stages. The Jobs in a Stage can all be run at the same time, if enough Bamboo agents are available. A Job is made up of one or more Tasks. A Task is a small discrete unit of work, such as source code checkout or running a script. ... A deployment project in Bamboo is a container for holding the software project which is deployed. Besides, plan branches represent a build for a branch in the version control system. When the plan branch build succeeds, it can be automatically or manually merged back into master. Bamboo deployments allow a plan branch to be deployed to a test environment and the feature source code can be tested and evaluated in a real server environment before the code is merged back to master. In Jenkins, there are available plugins to support deployment and branches as well, while in Travis they are supported by Travis’ configuration file. Concluding, all tools support deployment and branches. However, in Bamboo, when build jobs call deployments, it is not possible to go back to the build job to perform some post-deployment tasks. In addition, inability to provide input parameters, especially for deployment jobs, is a problem in Bamboo as well."</li> <li> The article notes: "Bamboo has been used with Amazon's Elastic Compute Cloud to scale large builds in a cloud environment, Atlassian said. The company also is revealing that it has acquired two plug-ins: Jira Workflow Designer, which plugs into Jira and visualizes a workflow, and Bamboo Release Management, which links to Bamboo and combines Bamboo and Jira to automate software release management. The plug-ins were acquired from Sysbliss and will now be offered for free. They had been commercially sold before."</li> <li> The article enotes: "Atlassian Bamboo offers a wealth of capabilities, ranging from building and deploying Docker containers to running applications on Amazon Web Services. Dedicated agents can be used to run hot fixes and critical builds immediately. Scalability has been viewed as a thorn in Jenkins’ side; here, Randall Ward, CEO of Appfire, an Atlassian business partner that provides add-ons and services, sees an advantage for Bamboo. ... Bamboo features code visibility, enabling users to see a full roll-up of code changes since the latest previous deployment. It integrates with other Atlassian products, including the Bitbucket Git code management solution, Jira project management solution, and HipChat team chat application."</li> </ol>

There is sufficient coverage in reliable sources to allow Bamboo to pass Notability, which requires "significant coverage in reliable sources that are independent of the subject". Cunard (talk) 08:28, 6 July 2020 (UTC) </li></ul>


 * Related AfDs of other Atlassian products: Articles for deletion/Confluence (software) (3rd nomination) and Articles for deletion/Jira (software). Cunard (talk) 08:28, 6 July 2020 (UTC)


 * As usual, are you reading those press articles yourself? Problem with this article is - it does not require separate page when the company page already exist. Wikipedia is not a Press, not a blog and definitely not a white paper or brochure for the companies. All articles are motivated by Press/ Digital marketing team. Secondly you can just mention the weblink and all people can ready them. you cover entire discussion with COPY+PASTE from the article and take the full discussion space. Thank you.

Do you call this notability of press? "Atlassian Bamboo offers a wealth of capabilities, ranging from building and deploying Docker containers to running applications on Amazon Web Services. Dedicated agents can be used to run hot fixes and critical builds immediately". Light2021 (talk) 10:28, 6 July 2020 (UTC)
 * My guess from this and other AfDs Cunard has been involved in is that the answer to your first question is a hard, resounding no. --Adamant1 (talk) 22:05, 9 July 2020 (UTC)

<div class="xfd_relist" style="border-top: 1px solid #AAA; border-bottom: 1px solid #AAA; padding: 0px 25px;"> Relisted to generate a more thorough discussion and clearer consensus.

Please add new comments below this notice. Thanks,  Sandstein   20:35, 9 July 2020 (UTC)
 * Delete Clearly a promo article that lacks the multiple in-depth reliable sources that it would need to be notable. I'm not seeing anything that would warrant not deleting it. --Adamant1 (talk) 22:00, 9 July 2020 (UTC)

<ul><li>Comment: The article is neutrally written. It has a factual description of how Bamboo works. It contains a "Comparisons" section that describes the advantages and disadvantages of using Bamboo. There is enough material about Bamboo to justify a standalone article. Bamboo has been covered in multiple books and journal articles. An editor quoted "Atlassian Bamboo offers a wealth of capabilities, ranging from building and deploying Docker containers to running applications on Amazon Web Services. Dedicated agents can be used to run hot fixes and critical builds immediately" to dispute an InfoWorld article. This is a review from the InfoWorld author and does not detract from the source's reliability. Here are additional book sources that provides analysis about Bamboo: <ol> <li></li> <li></li> </ol>

<ol> <li> The book notes: "Bamboo Bamboo is a proprietary CI server developed by Atlassian. ... Bamboo is their proposal for CI activities, and it is quite popular as it integrates fairly well with their other products. ... You can check the logs of the job to see how many tests were successful and other useful information. If you explore this even further, you can see how Bamboo also offers different types of tasks, such as mocha test runners, which allows Bamboo to understand the result of the tests. At the moment, with the current configuration, if any of the tests fails, Bamboo won't be able to understand which one failed. I'd suggest you to play around with different configurations and even different applications to get yourself familiar with it. As you can see by yourself, the interface is very friendly, and usually, it is quite simple to achieve your desired setup by creating new tasks. ... In general, Bamboo can deal with every situation, and it has adapted to the modern times: we can even build Docker images and push them to remote registries once the tests have passed in order to be deployed later on. Bamboo is also able to take actions in the post-build phase, for example, alerting us if the build failed overnight with an email or other communication channels."</li> <li> The book notes: "Bamboo Bamboo is a CI server used by software teams worldwide to automate the process of release management for applications and general software. It allows teams to establish a streamlined pipeline for build delivery. Mobile developers can deploy their apps back to the Apple store or Google Play automatically. Being an Atlassian tool, it has native support for Jira and BitBucket, and you can even import your Jenkins configurations into Bamboo easily. Its key features are as follows: <ul><li>Unlike Jenkins, Bamboo has built-in Git branching workflows</li><li>Because it is built by Atlassian, it has built-in integration for Jira and Bitbucket</li><li>Bamboo also supports automated merging to avoid conflicts and differences between the working branch and master branch</li><li>Test automation in Bamboo produces a continuous flow from build, to test, even to releasing the application to the customer when ready</li><li>Built-in support for Jira makes bug tracking in a specific release, and even builds, automated and easily trackable</li></ul>"</li></ol>

Cunard (talk) 09:21, 10 July 2020 (UTC)</li></ul>
 * Your convoluting something being written neutrally for it being written promotionally. They are two separate things, that are treated differently in Wikipedia, and I never said anything about the articles neutrality. I said it was promotional. That's it. It has nothing to do with neutrality. Also, something can be factually correct but still be an advertisement. They aren't mutually exclusive and again Wikipedia treats them differently. You mixing those things up, intentionally or not, and ref-bombing more trivial sources really isn't helpful to this in the slightest. --Adamant1 (talk) 10:04, 10 July 2020 (UTC)
 * The Spam guideline says, "Wikispam articles are usually noted for sales-oriented language and external links to a commercial website. However, a differentiation should be made between spam articles and legitimate articles about commercial entities." I reviewed the article and consider it largely not to be using "sales-oriented language". I can remove any "sales-oriented language" that editors find. Cunard (talk) 10:34, 10 July 2020 (UTC)
 * Again your miss qouting me.o one except you has said anything about the article being spam. Spam and promotion are completely different and having noyhing to do with each other. Neither does "sales-oriented language." Which again, your the only one talking about. Stop bringing up things that aren't relevant to the AfD, discussion, and no one is saying anything about. Adamant1 (talk) 11:29, 10 July 2020 (UTC)


 * Delete That there are reliable sources is not enough. The sources must provide significant coverage. For example, the book chapter cited spends one short paragraph describing Bamboo before launching into a tutorial for how to set it up. This is not enough material to write an article with. Fails WP:GNG. – <b style="color:SlateBlue">FenixFeather</b> (talk) (Contribs) 00:17, 15 July 2020 (UTC)
 * A book article and a peer-reviewed conference paper provide substantial coverage about Bamboo:<ol><li>The "Automated builds with Bamboo" chapter (pages 93–116) in the Apress book contains a tutorial for how to set up Bamboo. But it also provides commentary about Bamboo as well as discussion of its features and concepts. It is this detailed coverage, not the tutorial, that make the book a strong source, It has a section titled "Summing up the Basics", which says in part, "Let’s sum up what we’ve just did, because understanding the hierarchy and the pieces that click together is important if you wish to use Bamboo as your continuous integration platform. We created a plan for the Github Jobs for iOS application, part of the Github Jobs project. In this plan, a default stage containing a default job was automatically created. We customized this default job with multiple tasks: fetching the content from our git repository, installing the dependencies using Cocoapods and building the application using xcodebuild." Jobs and tasks are core Bamboo concepts. It has a section titled "Bamboo Power user features" where it says, "We covered a very basic use of Bamboo and went a little bit straighter to the point since we’ve already covered some part of the automatic building process in the previous chapter, when we talked about Jenkins. Bamboo is capable of so much more. Let’s have a look at some of the advanced things you can achieve with it." It discusses Bamboo's Rest API and Bamboo's Wallboards. It provides information about how Bamboo integrates with remote agents.  The book's concluding section says, "The goal of this chapter was to give you a tour of an alternative to Jenkins, because nothing is more dangerous than sticking with your favorite toys without looking at the alternatives. Once again, we didn’t want to tell you that one was better than the other; in fact both solutions come with pros and cons. By now, you should be able to choose which solution suits you best. Bamboo is a full-featured product maintained by a profitable company that comes with a nicely designed interface, powerful add-ons, and well-organized build plans." </li><li>According to this link, "IEEE requires all conference papers go through the peer review process before publication.". This IEEE conference paper provides over 700 words of discussion about Bamboo's features and concepts:  </li></ol>These two sources are sufficient to establish notability per Notability. Cunard (talk) 05:27, 15 July 2020 (UTC)


 * Comment: Deletion is not a policy-based approach per Deletion policy. If there is consensus that Bamboo is not notable, Bamboo (software) can be merged to its developer Atlassian. The content should not be deleted. Cunard (talk) 05:27, 15 July 2020 (UTC)


 * The above discussion is preserved as an archive of the debate. <b style="color:red">Please do not modify it.</b> Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.