Notifications
Notifications
CDW Logo

Wacom Bamboo digital pen nib

Mfg # ACK20610 CDW # 4495201 | UNSPSC 43211726

Quick tech specs

  • Digital pen nib (pack of 2)
  • Solo 3Gen
  • for Bamboo Duo 3Gen
View All

Know your gear

Wacom Bamboo Stylus replacement carbon fiber nibs fits 3rd generation stylus. These carbon nibs easily attach to your Bamboo Stylus.

This item was discontinued on September 01, 2021

Enhance your purchase

Wacom Bamboo digital pen nib is rated 3.80 out of 5 by 19.
Rated 5 out of 5 by from Reliable, great technical support, and scalable What is our primary use case? Bamboo is an automation tool. What needs improvement? Bamboo is a bit complicated to use compared to other solutions, such as GitLab. You have to integrate different actions that are difficult that could be made easier. For how long have I used the solution? I have been using Bamboo for approximately eight months. What do I think about the stability of the solution? Bamboo has been stable. What do I think about the scalability of the solution? In my experience Bamboo is scalable. I work for an insurance company and our whole company uses Bamboo. How are customer service and support? The technical support provided by Atlassian is very good. Which solution did I use previously and why did I switch? I have previously used Gitlab. What's my experience with pricing, setup cost, and licensing? There is a subscription required to use Bamboo. What other advice do I have? I would recommend this solution to others. I rate Bamboo an eight out of ten. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2021-10-29T00:00:00-04:00
Rated 5 out of 5 by from Data solution that integrates with Jira and Bitbucket for the convenient deployment of apps What is our primary use case? We use Bamboo to deploy our apps to local test servers and then to production. What is most valuable? The most useful feature of Bamboo is its integration with other solutions such as Jira and BitBucket, also offered by Atlassian. It is easier to use tools all provided by one vendor. What needs improvement? We are considering moving to a cloud solution and to use Bitbucket pipeline because of the features it offers. From a hosting perspective, it's easier to make use of solutions that are hosted in the cloud rather than to maintain the tool on-premise. This is not feasible with Bamboo. A feature I would like to see added is the integration with quality assurance reports when you run automated tests such as a Selenium test. It would be great to have the results visualised to understand the quality of a build. It is possible to do this manually but it requires a lot of configuration. What do I think about the scalability of the solution? Scalability depends on the use case. If it is really a big customer with a lot of tests, it might not be a scalable option for them. One of our enterprise customers were not satisfied with the scalability of the solution. This customer wanted to develop a financial system and needed to run an enormous amount of tests automatically which resulted in some problems. How are customer service and support? In some countries, the local or technical support for some solutions from Atlassian is not present. You need to go to the community to write your question or write a ticket to Atlassian to access their support team. Their response is not always very useful. Some of the questions they have answered quickly and correctly; other questions have taken longer. How would you rate customer service and support? Positive How was the initial setup? The initial setup was straightforward but we are an IT company so did this easily with the resources we have. What's my experience with pricing, setup cost, and licensing? The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money. What other advice do I have? I would advise those investigating this solution to start small with a step-by-step approach and adapt as their experience grows. I would suggest that you start with the build, and once you master the build, focus on deployment. It is important to consider whether an on-premise or cloud solution is best suited before getting started. Which deployment model are you using for this solution? On-premises Disclaimer: My company has a business relationship with this vendor other than being a customer:PARTNER
Date published: 2022-04-11T00:00:00-04:00
Rated 5 out of 5 by from Useful segregated application building, reliable, and good support What is our primary use case? Bamboo is used for different Java and Angular applications. What is most valuable? In Bamboo, build and deployment have been segregated. The build plan and deployment plan are different. When comparing Bamboo to other solutions, the native feature you will not find in another tool, such as Jenkins. They have segregated the build and deployment plan. This means, building the application and deploying it are two separate parts in Bamboo, they have segregated it apart from the UI. This makes the tool a bit better compared to other tools. What needs improvement? Bamboo can improve by providing more with scripting, such as they have with Jenkins. Bamboo is more UI-driven at this time, Jenkins is going in that direction too. For how long have I used the solution? I have been using Bamboo for approximately five years. What do I think about the stability of the solution? Bamboo has been stable in our experience. What do I think about the scalability of the solution? The solution is scalable. We have approximately 15 people using this solution in my organization. How are customer service and support? We have escalated some questions to the Atlassian support team. They have a good team for support. I would rate the technical support of Bamboo a four out of five. How was the initial setup? If we compare the initial setup of Bamboo's with Jenkins, Jenkins's setup is easier. Bamboo comes with more configuration when you start setting it up. However, Bamboo is more of an enterprise tool as compared to Jenkins because it supports different databases. You can configure Bamboo with MySQL, Oracle, or any database. This is why the setup, requires more configuration, but the setup is straightforward. It is not that complex, once a person has done it they become aware of it and can do it again with less trouble. What about the implementation team? We did the implementation of the solution ourselves. We have a team that does the maintenance of the solution. What's my experience with pricing, setup cost, and licensing? If Bamboo could provide more flexibility on pricing, that would help. On the agent side, if you want to increase the number of agents it should be less expensive. If they can provide some better pricing model, it will help, whether we are going to use it or are already using it. We have a standard license to use the solution. There can be some additional cost if we use some commercial plugins. Which other solutions did I evaluate? I have evaluated other solutions such as, Jenkins. What other advice do I have? I rate Bamboo an eight out of ten. Which deployment model are you using for this solution? On-premises Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-02-17T00:00:00-05:00
Rated 5 out of 5 by from High availability, helpful support, and plenty of plugins available What is our primary use case? We utilize Bamboo to automatically deploy multiple applications that manage various aspects of our department across several environments, including testing and production. By employing the same pipeline for each application, we can effectively manage and automate the process. As a result, we've pursued Kubernetes training to develop scalable applications. I have worked on both on-premise and cloud deployments of Bamboo. What is most valuable? The most valuable features of Bamboo are its performance and UI. Additionally, there are a lot of useful plugins, integration with other solutions, such as Bitbucket and Jira, and a helpful online community. What needs improvement? Bamboo could improve by having compatibility with GitLab. It would be better to have this platform for deploying code and storing container registries. Bamboo does not have a container registry. Additionally, there could be more features added. For how long have I used the solution? I have been using Bamboo for approximately three years. What do I think about the stability of the solution? The stability of Bamboo is excellent. I rate the stable of Bamboo a ten out of ten. What do I think about the scalability of the solution? I worked on a project which had 2,000 developers using the solution. The solution is best suited for enterprise companies. The solution is scalable. I rate the scalability of Bamboo an eight out of ten. How are customer service and support? The support for Bamboo is great. They have been helpful and they provide a high-level service. Additionally, they are quick to respond. How would you rate customer service and support? Positive Which solution did I use previously and why did I switch? I have used Jenkins and I found that Bamboo is more powerful and easier to use. How was the initial setup? I have used Google Cloud Platform and Amazon AWS for implementing Bamboo. It is not difficult to complete. The length of time it takes for deployment depends on a lot of variables, such as how the pipeline is deployed and what type of infrastructure is present. However, it typically takes only hours not days. I rate the setup of Bamboo a nine out of ten. What about the implementation team? I did the implementation of the solution. What's my experience with pricing, setup cost, and licensing? The price of Bamboo is reasonable. What other advice do I have? There is maintenance needed for keeping track of the nodes and making sure the agents are live. However, the solution does not require a lot of effort for maintenance of the solution. We use two people for the maintenance. I would recommend this solution to others. I rate Bamboo a nine out of ten. Disclaimer: My company has a business relationship with this vendor other than being a customer:Integrator
Date published: 2023-04-08T00:00:00-04:00
Rated 5 out of 5 by from Useful connector marketplace, customizable, and highly scalable What is our primary use case? I implement this solution for clients. The primary function of Bamboo is to facilitate the creation of a CI/CD pipeline, which is the main use case for the tool. Its main purpose is to automate the pipeline, enabling a DevOps approach for both the client and the company. What is most valuable? One of the significant benefits of Bamboo is its built-in support for numerous clients and the ability to tailor its capabilities to your specific requirements. This high level of customization enables you to create pipelines that are ideally suited to your needs, making it an invaluable tool for conducting advanced testing. The marketplace offers a wide range of pre-tested connectors that are readily available for use in your builds. However, if you cannot find a suitable connector, Bamboo also supports the integration of APIs, allowing you to seamlessly incorporate custom solutions into your system. What needs improvement? One area that could be enhanced is the governance process, particularly with regard to building approvals and transitions between stages. In comparison to other solutions, such as Jira, which features a workflow that supports approval processes, this capability is not natively available in Bamboo. To implement this functionality, integration with other solutions, such as GSM may be necessary. Although some add-ons, such as Adaptavist ScriptRunner, are available in the market to circumvent this limitation, they may not offer the exact functionality needed. Therefore, there is certainly room for improvement in this area. Currently, Atlassian University does not offer a dedicated course for learning Bamboo. If you wish to embark on a learning journey to acquire knowledge about the solution, your only recourse is to seek out experienced users who are willing to share their expertise on learning platforms like LinkedIn or Udemy. However, this falls short of a structured classroom-based approach, which Atlassian should consider incorporating into their official university platform to provide a comprehensive learning experience for users. However, there is a lot of documentation, but this is not the same as training. This lack of training might be due to the focus that Atlassian has on the cloud platform rather than on-premise. For how long have I used the solution? I have been using Bamboo for a couple of years. What do I think about the stability of the solution? Bamboo is highly stable, as long as the compatibility and upgrades of relevant libraries and dependencies remain untouched. It can become problematic if upgrades or updates are made to dependent libraries or other software. If, for example, Java is updated to an unsupported version, this needs to be communicated clearly to the customer. Such updates usually fall under the purview of security and operations teams, who check for patches and other necessary updates. These factors can have a significant impact on performance. However, overall, Bamboo performs very well and is highly robust. I rate the stability of Bamboo an eight out of ten. What do I think about the scalability of the solution? Bamboo is scalable and it is easy to do. Theoretically, you can add as many nodes as you want. You don't need to incur additional licenses for the additional nodes added which is a large benefit. We have clients that are small to large-scale enterprises. However, most of our clients are enterprise-sized, such as government entities. Approximately 40 percent of our clients are SMBs and 60 percent are enterprises. I rate the scalability of Bamboo a nine out of ten. How are customer service and support? Improvement in Bamboo support is needed, particularly regarding security-related inquiries. Responses to security questionnaires required by the customer's security team are often delayed. However, regarding technical support, their responsiveness is generally good, depending on the severity of the issue. They can also provide direct support sessions when necessary. Nevertheless, our experiences vary when it comes to security, particularly from the PC side, where we typically face delays in obtaining answers to questionnaires provided by the customer's security team. I rate the support from Bamboo a six out of ten. How would you rate customer service and support? Neutral How was the initial setup? The complexity of implementing Bamboo varies based on the client's specific needs. Installing and obtaining basic information is simple, but building a pipeline can be more challenging. This task is typically handled by a DevOps engineer. Unless requested by the client, the implementation would not be handled by the partner, which can be quite challenging. The installation and configuration can be straightforward. Excluding the pipeline, the full implementation can be done in two days. Typically, the implementation process involves setting up the infrastructure and ensuring that all prerequisites are met, including the necessary platforms and versions compatible with Bamboo. The deployment complexity varies depending on whether it's done on Linux or Microsoft Windows OS. The deployment process on Microsoft Windows OS is relatively straightforward, requiring the installation of prerequisites and a supported DB server. If deployed on a PC, a shared network folder with the appropriate security access is also necessary. These steps are well-documented, making them easy to follow. Therefore, deployment is not overly challenging. However, configuring the system from within can be more complicated. I rate the initial setup from Bamboo a seven out of ten. What other advice do I have? My advice is that if you intend to implement Bamboo, you should consider it as part of a complete DevOps solution. You must think about the other applications natively integrated with it, such as Jira, JSM, and Bitbucket. Bamboo's true power is realized when it is combined with these other solutions from the Atlassian suite. In this way, you can achieve much better value. I rate Bamboo an eight out of ten. I provided my rating of Bamboo based on its strong scalability and overall quality. While its support could be better, its performance is quite robust. However, there is a learning curve to understand how to set it up, making it challenging for new users. Nevertheless, for experienced DevOps engineers, it is pretty straightforward to set up. Disclaimer: My company has a business relationship with this vendor other than being a customer:
Date published: 2023-04-02T00:00:00-04:00
Rated 5 out of 5 by from The solution can be used for PCA compliance, but it needs a more containerized deployment model What is most valuable? We are using Bamboo for CICD, where you need to build Java architect and boot application architect. Then, we deploy that into some Comcast web servers. Bamboo was used extensively in our organization for PCA compliance. What needs improvement? It would be great if Bamboo could introduce a more containerized deployment model. Bamboo should also provide more user-friendly flexibility. For example, if we want to maintain the Bamboo job configuration, we need to export the configuration to Java. However, it would be good if the coding syntax could be simplified. For how long have I used the solution? I have been using Bamboo for one and a half years. What do I think about the stability of the solution? I rate Bamboo a seven out of ten for stability. What do I think about the scalability of the solution? I rate Bamboo a seven out of ten for scalability. What other advice do I have? Overall, I rate Bamboo a seven out of ten. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-08-28T00:00:00-04:00
Rated 5 out of 5 by from Fairly stable, scalable, and does CI pipeline well, but requires a lot of integration and not easy to use and learn What is our primary use case? We are using it to push and pull containers and other data via CI/CD pipeline. How has it helped my organization? It didn't help me as such. It was just a part of the project. What is most valuable? It can do the CI pipeline well. What needs improvement? It should be much easier to use. It shouldn't require a lot of reading to be able to use it. It should have just two or three screens rather than hundreds of screens requiring a lot of clicking. It also requires a lot of integration. It has a steep learning curve. It takes a lot of time to understand and put in the data. There is also no proper training. For how long have I used the solution? I have been using this solution for three months. What do I think about the stability of the solution? It has a steep learning curve, but it is fairly stable. What do I think about the scalability of the solution? Based on my understanding, it is scalable. How are customer service and technical support? There is limited technical support. How was the initial setup? Its initial setup is complex. What about the implementation team? We have a separate team that takes care of it. What other advice do I have? I am not completely satisfied with this solution. It performs one function well, but it requires so much integration. I would advise others to use a better-integrated system rather than Bamboo. We'll be moving to XebiaLabs, now known as Digital.ai, for production and other environments. XebiaLabs is a bit better than Bamboo in some aspects. I would rate Bamboo a six out of ten. It is okay to use, but there is a lot of room for improvement. Which deployment model are you using for this solution? Hybrid Cloud Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2021-03-28T00:00:00-04:00
Rated 5 out of 5 by from PRO: flexibility when setting up our builds. CON: lacks support for branched builds using multiple source repositories What is most valuable? We are very fond of the flexibility it offers in terms of setting up our builds. We have a wide variety of components we need to build which often require custom actions or manipulations using in house technology. Bamboo allows us to set this up quite easily by the flexible configuration features it includes. Secondly we really like the integration of the build aspect and deploy aspect. One of the recent major releases included this feature to link build and deploy projects together allowing a deployment pipe-line to be setup completely in Bamboo. This makes the status of deployments very visible and also allows for easy follow up and even rollback in case a deployment causes too much havoc. How has it helped my organization? Thanks to Bamboo we are able to build changes made by development quite quickly and allow them to deploy to our internal environments when needed (as well as automated during the night). This significantly reduces the effort required to get something into test. The fact that all builds use a unified setup and infrastructure makes it much easier to control and adapt the ever increasing number of builds. What needs improvement? We are lacking proper support for branched builds using multiple source repositories. The current approach is quite clunky (or non-existent) but it seems there is something in the pipe line for the end of the year according to a recent post on the Bamboo Jira. For how long have I used the solution? We have been using Bamboo for about 6 years now What was my experience with deployment of the solution? Not at all, over all those years we only had a handful of issues and that's probably because we always take each new update directly. What do I think about the stability of the solution? No, we never encountered any serious regression. For the few cases we encountered bugs they were fixed in a reasonable time interval. What do I think about the scalability of the solution? Scaling out a build system is not always easy, but thanks to the remote agent technology we are able to scale out and add nodes in a transparent way. How is customer service and technical support? Customer Service: We use a 3d party for our license management, which makes it hard to judge this but we never had direct interactions with Atlassian Customer support. Technical Support: Pretty good once you get trough the initial levels of the support team, it can take a while before you are able to prove that there's a genuine issue. Which solutions did we use previously? We came from Jenkins back in the day, I recall our most important reasons to switch where the enterprise readiness of Bamboo and its integration in the Atlassian stack (Jira and others). How was the initial setup? Bamboo is very easy to deploy, all it takes is extracting the distribution and a JRE to run it. This also goes for the remote agents which install by running a JAR which already contains the configuration for communicating with its master. What about the implementation team? We implemented in house. What was our ROI? That would be 100%, the time saved in development is enormous. What's my experience with pricing, setup cost, and licensing? We started out using only a number of agents and moved to a bigger setup using many remote agents over the years. The cost depends on the agents used and amount of boxes deployed to run them on. Which other solutions did I evaluate? Only Jenkins, see previous answer. What other advice do I have? Plan before you start, Bamboo is 'only' that which automates. One should have a decent design of how the build needs to work internally and have that (scripts, servers, descriptors ...) in order before attempting to automate on a large scale. Secondly, don't be afraid to change things to you application or pipeline to help the automation to be more efficient - for example we replaced massive chunks of hard SQL from the build scripts by a webservice to avoid dependencies to JDBC in our builds. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2015-03-10T00:00:00-04:00
Rated 5 out of 5 by from Bamboo easily integrates into an Atlassian stack. Valuable Features Ability to interface easily with other Atlassian applications. Improvements to My Organization It allows a controlled process in which to build software. Room for Improvement Version control for plans is currently not really possible. This is pretty much the deal breaker for me and why I'm moving away from Bamboo. The Upgrade process is also clumsy and requires manual steps. I'm not a fan of tarballs. Use of Solution 3 years. Deployment Issues You may need to upgrade in steps if you are upgrading a relatively old version. Stability Issues At one time we used to have issues with system stability. You may need to tinker with your systems heap settings. Scalability Issues You are limited by the number of agents you are willing to buy. This means all your teams end up building on the same agents or worse, the master itself. This is the second deal breaker for me and why I'm currently advocating to move to a different build system. Customer Service and Technical Support Atlassian support is usually pretty good in my experience. Initial Setup They need to work on their upgrade paths and deployments. If you fall to a few versions behind you may end up doing a multi-version installation. Not fun. Pricing, Setup Cost and Licensing The license is the worst. It costs the most. In addition to that we run it on a very beefy server (HP DL360 G8 with 24G of ram). I would not run this software on subpar hardware. Other Advice Pros: - Integrates well with Atlassian products - Nice Modern Interface Cons: - Agents are limited by the license - No method to provide version control for Build Plans - It's expensive - Most plugins cost $$$ Personally I'm in the process of moving away from Bamboo. Sure it looks nice, but I need flexibility. If you plan on creating a build server for each of your teams or projects, don't use Bamboo and use Jenkins instead. It has a richer plugin base, no limit on agents, and allows version control of plans and configuration easily. It's also open source software so the cost is much lower. Maintaining Bamboo is also a chore, not so with Jenkins which is distributed as a RPM, DEB, and now Docker container. Bamboo I'm still stuck downloading a tarball. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2015-02-24T00:00:00-05:00
Rated 5 out of 5 by from APIs were helpful for creating customizations but there are limited options with SSH plugins Valuable Features * Integration with Atlassian products like Jira,Crowd, and Stash * Easy to setup * Price Improvements to My Organization * With Bamboo's integration with Jira, we were able to update build status and test reports to Jira bugs/tasks. * In Stash, we were able to improve the pull request review standards by being able to review the build and test reports. * Integration with Artifactory, helped us in auto updated libs and artifacts. * APIs were helpful for creating customizations. Room for Improvement * Ease of use. * It needs "re-build/Trigger build" switch from Stash Pullrequest. * More 3rd party plugins to support IDEs. * Integration of older plugins with newer version of Bamboo. * More options for deployment plans * Configuring tools to agents (Had to do it manually). It would be nice have sharing from server. * -Docker support * Limited options with SSH plugins, can't use options to it Use of Solution Two to three years. Deployment Issues No issues with deployment. Stability Issues Yes, Regular server/agent being down. Scalability Issues Yes, It needs to allow multiple plans to run on a agent(at same time). Dedicating one whole agent isn't fair, I know we have to buy more agents, but in-terms buying and maintaining more infrastructure isn't scalable either. . Customer Service and Technical Support Customer Service: Never used it. Had a decent responses from open forum. Technical Support: Never used it. Previous Solutions Yes. since we wanted to keep Atlassian suite all-around. Initial Setup Easy. Just like other Atlassian products. ROI We got the product for a cheap price, so its alright. Pricing, Setup Cost and Licensing We initially got 5 agents for around $2000 excluding infrastructure setup. Now we are using docker containers to maximize the mileage on them. Other Advice If you are looking for good integration with Atlassian products and then this is the tool. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2015-01-14T00:00:00-05:00
Rated 5 out of 5 by from There are some stability issues with Java 6, but it offers build agents for Windows and Linux. Valuable Features * Multiple build agents for both Windows and Linux * Automatic branch building - same build plan for trunk and branches * Connections with other Atlassian tools - JIRA and FishEye/Crucible Improvements to My Organization We have many developer teams building in Java, especially our Continuous Integration team. Bamboo has proven its value for the teams. Room for Improvement There are no areas that need improvement. Use of Solution I've used it for seven years, Deployment Issues No issues encountered. Stability Issues Once, with Java 6, there were some issues, but thanks to information from Atlassian support we changed to Java 7 and it works fine. Scalability Issues No issues encountered. Customer Service and Technical Support Customer Service: I'm satisfied, 8/10. Technical Support: I'm satisfied, 8/10. Previous Solutions We used CruiseControl, and we switched because of better functionality in Bamboo. Initial Setup It was straightforward, as the default agent and remote agents install out-of-the-box. Only some memory tuning was needed. Implementation Team We did it in-house. ROI It's hard to say, the yearly license/support/maintenance costs are low in relation to the added functionality. Pricing, Setup Cost and Licensing I see no problem in paying for support, especially because licensing is remote agent based. Other Solutions Considered * CruiseControl * Hudson Other Advice It's dependent on how many build teams you have. For small development sites, Hudson or Jenkins will suffice, I think. Because we’re building our main applications in-house, we always choose supported and licensed tools. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2015-07-29T00:00:00-04:00
Rated 5 out of 5 by from The REST API for our deployment project is still very basic, but with Bamboo, we've been able to implement an on-demand, push-button release strategy. Valuable Features The Deployment Project Improvements to My Organization Bamboo, along with its integrated deployment and release pipeline, enabled us to go from a monolithic, once a month release cycle, with many post-release incidents to an on-demand, push-button release strategy where we deployed over 200 times a month with very few to no release-related incidents. Using this tool, we were able to empower the dev teams to push their own changes to production rather than rely on the operations or release teams to release it. Room for Improvement The REST API for our deployment project is still very basic and lacks the ability to provide a decent amount of custom automation. For many things, we had to resort to direct database queries simply because certain data was not exposed via the API. Use of Solution I've used it for five years. Deployment Issues No issues encountered. Stability Issues Every once in a while deployments would hang and we weren't able to clear them without restarting the service. It didn't happen a lot and it may have been due to how we configured the app on the server. Scalability Issues Not really. As long as your organization is willing to pay a bit more, Bamboo can scale to meet your needs. Customer Service and Technical Support Customer Service: 7/10 - sometimes you just want to talk to someone over the phone, but this isn't very easy with Atlassian. They have a ticket support system that's pretty good at connecting you with a customer service rep, but sometimes this means you have to go back and forth, waiting for the representative to reply on the issue in order to isolate a problem. Technical Support: 7/10 - sometimes you just want to talk to someone over the phone, bu this isn't very easy with Atlassian. They have a ticket support system that's pretty good at connecting you with a customer service rep, but sometimes this means you have to go back and forth, waiting for the representative to reply on the issue in order to isolate a problem. Previous Solutions Bamboo was already being used. Initial Setup It was pretty straightforward. Atlassian standardizes setup across products for the most part, so it was easy for us to install, configure, and navigate. Implementation Team We implemented it ourselves in-house. ROI We got a ton of product and development time back across the board, which could be translated to several tens of thousands of dollars. Pricing, Setup Cost and Licensing Keep in mind that Bamboo pricing is based on number of remote agents. Agents are what you used to load balance build and deployment tasks, so depending on how large your development shop is, what your software architecture looks like, and how often you intend to build and deploy new versions of software, it can get fairly pricey to support a higher volume pipeline. Other Solutions Considered We evaluated Jenkins and Thoughtworks Go. At the end of the day, Bamboo just integrated better with the other tools we were already using - JIRA, Stash, Confluence - and provided better push button deployment control. Bamboo provided such a seamless delivery pipeline and visibility to all stakeholders through its easy integrations with our already existing toolset. Other Advice Make sure you don't become dependent on the tool for basic delivery of software. And this goes for any tool you use for automating the building and deploying of your apps. Meaning, if Bamboo were to go down for whatever reason, you want to make sure you can still build and deploy software. To avoid Bamboo becoming a single point of failure, have all of your script tasks run a file that is managed in a repository instead of writing it in line in Bamboo. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2015-08-20T00:00:00-04:00
Rated 5 out of 5 by from Has good integration, is efficient, and doesn't take up other resources What is our primary use case? This is a part of the CI/CD. We use this tool to move into production. How has it helped my organization? It does automation which saves time so that people don't have to waste time. We save around 20% on time. What is most valuable? It's one of the best solutions in this line of work. We have many Atlassian products. We use Bamboo, JIRA, Service Desk, and some other Atlassian plugins. We like that it's easy to integrate into each other. It's a suite of services. It doesn't take up other resources. It's very efficient. What needs improvement? It's a little outdated. It's three years old. For how long have I used the solution? I have only used Bamboo at my current company and I've been there for a year now. What do I think about the stability of the solution? It is very stable. We have experienced issues but there is alway support. What do I think about the scalability of the solution? We are upgrading to the latest version because of the scalability. How are customer service and technical support? I usually solve any problems we have by myself. If for whatever reason there isn't any information available online we contact their support and they get back to us within hours. I opened around five to ten tickets with them. What's my experience with pricing, setup cost, and licensing? They have very stable pricing. The license is 120,000 per year for the license and maintenance. What other advice do I have? I would rate it an eight out of ten. Not a ten because the GUI is old I always have to find the right plugin. My advice to someone considering this solution is that if you have the money, buy it. Which deployment model are you using for this solution? On-premises Disclaimer: I am a real user, and this review is based on my own experience and opinions.Customer
Date published: 2019-12-31T00:00:00-05:00
Rated 5 out of 5 by from Good compiling and deployment features that are ideal for open-source development What is our primary use case? We use Bamboo as our continuous integration server. How has it helped my organization? We have a project based on AWS and Java, and Bamboo is the solution that fit our needs. What is most valuable? The most valuable features are compiling and deployment. What needs improvement? The performance around the deployment feature could be improved. For how long have I used the solution? We have been using Bamboo for three years. What do I think about the stability of the solution? We have experienced a couple of crashes, which is why we have upgraded to new versions as they are released. It seems now that everything is okay. We have 70 people who use this solution, most of which are developers using it for compilation. There are two or three system integrators. What do I think about the scalability of the solution? In the context of our project, scalability is enough for our purposes. How are customer service and technical support? I have not personally been in touch with technical support. One of my colleagues may have been, but I haven't heard any feedback. How was the initial setup? The initial setup was a lovely experience for us because the first time we tried it, it was ok. Which other solutions did I evaluate? We did not evaluate other options because we primarily use Microsoft development technology and we have only a few targets that are not supported. We had done some research and found the Microsoft Azure DevOps VSTS was not competent enough to support Core Java lambda functions, so we picked up Atlassian Bamboo and we are happy with it. What other advice do I have? Bamboo is a solution that I recommend, especially for open-source development organizations that use all open-source tools. Atlassian suite is the best partner for such organizations. I would rate this solution an eight out of ten. Which deployment model are you using for this solution? On-premises Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2020-01-31T00:00:00-05:00
Rated 5 out of 5 by from Good system customization, with good overall features and functionality What is most valuable? I find the solution quite easy to use. One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system. The fact that it's integrated within Oracle products, and that it can be managing statutory people in our organization, and the features and functionality are all huge selling points. We felt Bamboo was a simple overall tool, and that it was also cheaper than Oracle's products at the time, which is why we chose it. What needs improvement? The solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance. For how long have I used the solution? I've been using the solution for about a year. What do I think about the stability of the solution? The solution is pretty stable. What do I think about the scalability of the solution? The solution is scalable. We have about 400+ users on it currently. We use it on a daily basis, but I don't know if we plan to increase usage at this time. How are customer service and technical support? We have our own in-house team that helps troubleshoot any issues we might have. If they can't resolve it, they may go to the Bamboo help desk. How was the initial setup? I wasn't really involved in the implementation process so I can't really comment on it. We have two administrators on the solution currently. What other advice do I have? We use the cloud deployment model. I'd recommend that solution. Everything structure and systems-wise is quite customizable. I'd rate the solution eight out of ten. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2019-11-29T00:00:00-05:00
Rated 5 out of 5 by from The new Salesforce plugin looked interesting despite the fact you had limited control on how the SF package is deployed. Valuable Features: The deployment mechanism was neat, and I liked how it allowed you deploy the same release to multiple environments. I also thought the ability to branch build and deployment jobs without needing to use templates or updating job configuration could be useful. Plus the new Salesforce plugin looked interesting despite the fact you had limited control on how the SF package is deployed. Room for Improvement: * Logging, no integration with Octopus * Build time variables did not have ability to select from a list of value * No ability to customize Build version * TFS plugin had no local workspace editing of checked out files, as all files coming from TFS have read-only attribute turned on by design * No history view column adjustment * Password variable values were not concealed within GruntJS logs * Watching build log GUI loses focus at build completion making debugging difficult * Mediocre .Net Code Coverage support and reporting. Use of Solution: These observations were part of a multi-department, one month evaluation where we decided to go with a different product in the end. Deployment Issues: No issues encountered. Stability Issues: No issues encountered. Previous Solutions: We were using TFS for build automation. TFS proved to administrative to maintain and customize build templates. Plus we were planning to move to Git and found Git's interface within TFS/Visual Studio lacking in comparison to other Git clients. Initial Setup: It was straightforward, although, Bamboo initially creates its main install folder in the home directory of the current user. Even though Bamboo has a 'bamboo.home', Bamboo organizes its different library/build-time/resource component folders separately in the configuration and modifying those proved intensive in comparison to TeamCity and Jenkins where there's is only one 'Home' folder. Implementation Team: In-house. Other Solutions Considered: We evaluated TeamCity and Octopus. Other Advice: While the community may grow over time, please ensure your current/future processes are not hindered by Bamboo's faults. Bamboo is likely to improve with time, it may be advisable to use a different solution until the product grows a bit more mature. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2015-02-16T00:00:00-05:00
Rated 5 out of 5 by from Provides an automated data backup feature, but its technical support services need improvement What is our primary use case? We use Bamboo for data replication, backup, and recovery. How has it helped my organization? The platform helps us with automated and timely backup. It provides data replication as well. What is most valuable? The product’s most valuable feature is its ability to work with VMware and Hyper-V. What needs improvement? Bamboo’s technical support services, in terms of speed of response, need improvement. They should work on providing faster backup replication as well. For how long have I used the solution? We have been using Bamboo for almost a year. What do I think about the stability of the solution? The product could be more stable. I rate its stability five out of ten. What do I think about the scalability of the solution? I rate Bamboo’s scalability a six out of ten. It doesn’t work well in all environments. It has some drawbacks and challenges. Also, fixing them takes a long time due to the technical support team's slow response time. How are customer service and support? The technical support services could be better. How would you rate customer service and support? Neutral Which solution did I use previously and why did I switch? I have used Veeam and NetApp before. How was the initial setup? The initial setup is easy. I rate the process an eight out of ten. What's my experience with pricing, setup cost, and licensing? I rate the product’s pricing a five out of ten. What other advice do I have? I rate Bamboo a six out of ten. It suits small and medium businesses with brand-new servers, up-to-date operating systems, and good network switches. I would not recommend it for large organizations. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-10-13T00:00:00-04:00
Rated 5 out of 5 by from A good tool for CI/CD integration with a helpful technical support team What is our primary use case? Bamboo is a CI/CD tool for low-cost teams in my company. Some of my company's customers come to us with a certain level of comfort they experience, and we help them continue with that. What is most valuable? The most valuable feature of Bamboo is that it is a good tool for CI/CD integration. Bamboo is not a tool like Jira, which is mostly a ticketing system. What needs improvement? People know more about Jira than Bamboo. In general, people should know that Jira and Bamboo are similar solutions. The marketing strategy of Bamboo is an area of concern where improvements are needed. I believe that Bamboo should provide some support as there are too many scripts when we try to do something in GitHub. Every tool has its own style of automation, which is something I would like to be standardized so that the tools become more friendly when it comes to porting so that I can use Bamboo or GitHub Actions freely. I want all the tools to have the same standards, which would help our company. I feel there is always a scope for improvement in the product's initial setup phase. Bamboo should provide a permanent free tier, not a time-bound one for startups, as it helps users know if something works well and is utilized or not. Bamboo should offer some permanent free trial for one user or ten users, whatever it is. For how long have I used the solution? I have been using Bamboo for almost eighteen months. What do I think about the stability of the solution? Most of the time, our scripts were bad. There were also some memory issues and delays around building scripts. My company could handle script issues since most of them were because of the problems at our end. Apart from the aforementioned area, we found no issues with the product. What do I think about the scalability of the solution? My company has been happy with Bamboo's scalability options, especially considering that more developers have joined my company. Scalability-wise, I rate the solution a seven to eight out of ten. One of my company's clients has 15 users of the solution. How are customer service and support? The solution's technical support is good since my company hasn't had any issues with them. My company's interaction with Jira's support was more compared to Bamboo. My company doesn't have issues with Bamboo's quality or response time. Most of the time, my company interacted via Bamboo's online forums, and we used to get answers. Which solution did I use previously and why did I switch? My company can be described as a diverse company, so we use what our customers use. I have experience with Bitbucket, CircleCI, and GitHub. How was the initial setup? The product's initial setup phase is okay for us since our company is an expert in it. The solution is deployed on the cloud. What other advice do I have? For those who have a suite from Atlassian, my company would prefer them to use Bamboo. My company doesn't want our clients opting for one tool for CI and another tool for ticketing. Generally, we prefer to go with the corresponding solutions offered by a vendor. GitHub is always good, but it is limited as it is a free tool. Bamboo should offer products for free to startups or the first ten users, rather than just thirty days, an approach through which it can hook people. There should always be a free tier of products, and as Bamboo grows, I think its costs would be nothing, considering the value it gives users. I never heard about Bamboo in the past as much as Jira or Confluence. I came to know of Bamboo through meetings or emails in my company with our customers. It doesn't seem like Bamboo is digitally marketed very well. With DevOps becoming popular, products like Bamboo have so much to offer. I rate the overall tool an eight out of ten. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-11-20T00:00:00-05:00
Rated 5 out of 5 by from A solution to maintain sales process and continuous integration What is our primary use case? We use Bamboo to maintain the sales process and ensure continuous integration. This involves integration with Bitbucket as the deployment server. How has it helped my organization? Some of my recent projects have been built on a microservices architecture that utilizes microservices. This stream works, running a big e-commerce solution, and is containerized. Bamboo has helped us to make this process perfect by reducing the risk of failures on production deployments, making the changes deployed into production much smaller, thereby reducing errors and easing the sign-up process for the release itself. It generally makes the solution flexible and helps maintain information about what has been deployed and what hasn't. It's much easier to manage. Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process. What is most valuable? Bamboo allows for any customization made. It provides tools to configure the process as much as you need and want. Then, it helps to run big IT projects, scale them as much as you need, and utilize the process that the client is used to. What needs improvement? The tools and capabilities of the system are extensive. It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand. For how long have I used the solution? I have been using Bamboo for ten years. What do I think about the stability of the solution? The stability of the solution is good. What do I think about the scalability of the solution? The solution’s scalability is excellent. Around 200-500 users are using this solution. I would rate the solution’s scalability a ten out of ten. How are customer service and support? There is quite a large community around Atlassian's Bamboo. Most issues can be solved by browsing through the documentation or forums. Almost every problem you encounter has likely been experienced by someone else in the past, and with such a large community, finding solutions is generally straightforward. Atlassian has an advanced approach to solving issues. If it's very systematic, you can always stay updated about the resolution of the problem. Which other solutions did I evaluate? What other advice do I have? We've never really utilized different tools extensively. Bamboo works efficiently from a management perspective. If you need to inform a developer to deploy a particular version, it handles this task seamlessly. Any potential miscommunication or oversight is mitigated using Bamboo, provided it's correctly configured. It automatically provides the necessary information without excessive emails or phone calls to confirm whether something has been deployed. It's crucial to understand the business process and operations of the client thoroughly. Ultimately, deploying the software aims to fulfill the needs of the business itself. No tool can effectively handle that volume without understanding how the business operates, its expectations, and its processes regarding deploying software into production. Everything begins with understanding the client's business or the business purpose behind the configuration of Bamboo and essentially any step within the development process. Once you grasp this understanding, you can configure Bamboo properly, leveraging its capabilities to support various business processes, which is commendable. The configuration possibilities are pretty endless. It provides space for fewer issues you may experience due to misconfiguration. Any problems are not about the system itself but rather misconfiguration, which can sometimes be hard to identify. The components you wish to deploy haven't been deployed for some reason, and then you must determine why it didn't happen. Overall, I would rate the solution an eight out of ten. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-03-28T00:00:00-04:00

This page was printed on 4/18/2024 8:28:42 PM.