Wacom Bamboo & Intuos5 Tablets Wireless Option - digitizer connection kit
Mfg # ACK40401
CDW # 2687554
| UNSPSC 56112005
Know your gear
More space for your life. With the Wacom wireless accessory kit, your tablet can easily connect wireless with your computer.
Enhance your purchase
Wacom Bamboo & Intuos5 Tablets Wireless Option - digitizer connection kit is rated5.00 out of5 by3.
Rated 5 out of 5 byGeoff Kirk 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 byMallardMfg from Works GreatThe wireless option with the Wacom Intuos tablet works like a charm. Downloaded a whiteboard program and we have turned our 60" conference TV into a whiteboard!
Date published: 2014-08-20T00:00:00-04:00
Rated 5 out of 5 byit_user199380 from Bamboo easily integrates into an Atlassian stack.Valuable FeaturesAbility to interface easily with other Atlassian applications.Improvements to My OrganizationIt allows a controlled process in which to build software.Room for ImprovementVersion 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 Solution3 years.Deployment IssuesYou may need to upgrade in steps if you are upgrading a relatively old version.Stability IssuesAt one time we used to have issues with system stability. You may need to tinker with your systems heap settings.Scalability IssuesYou 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 SupportAtlassian support is usually pretty good in my experience.Initial SetupThey 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 LicensingThe 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 AdvicePros:- Integrates well with Atlassian products- Nice Modern InterfaceCons:- 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 byit_user202509 from PRO: flexibility when setting up our builds. CON: lacks support for branched builds using multiple source repositoriesWhat 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 nowWhat 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 byAHMJ Tromp 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/CrucibleImprovements to My OrganizationWe have many developer teams building in Java, especially our Continuous Integration team. Bamboo has proven its value for the teams.Room for ImprovementThere are no areas that need improvement.Use of SolutionI've used it for seven years,Deployment IssuesNo issues encountered.Stability IssuesOnce, with Java 6, there were some issues, but thanks to information from Atlassian support we changed to Java 7 and it works fine.Scalability IssuesNo issues encountered.Customer Service and Technical SupportCustomer Service: I'm satisfied, 8/10.Technical Support: I'm satisfied, 8/10.Previous SolutionsWe used CruiseControl, and we switched because of better functionality in Bamboo.Initial SetupIt was straightforward, as the default agent and remote agents install out-of-the-box. Only some memory tuning was needed.Implementation TeamWe did it in-house.ROIIt's hard to say, the yearly license/support/maintenance costs are low in relation to the added functionality.Pricing, Setup Cost and LicensingI see no problem in paying for support, especially because licensing is remote agent based.Other Solutions Considered* CruiseControl* HudsonOther AdviceIt'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 byit_user293628 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 FeaturesThe Deployment ProjectImprovements to My OrganizationBamboo, 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 ImprovementThe 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 SolutionI've used it for five years.Deployment IssuesNo issues encountered.Stability IssuesEvery 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 IssuesNot really. As long as your organization is willing to pay a bit more, Bamboo can scale to meet your needs.Customer Service and Technical SupportCustomer 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 SolutionsBamboo was already being used.Initial SetupIt was pretty straightforward. Atlassian standardizes setup across products for the most part, so it was easy for us to install, configure, and navigate.Implementation TeamWe implemented it ourselves in-house.ROIWe 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 LicensingKeep 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 ConsideredWe 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 AdviceMake 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 byit_user176028 from APIs were helpful for creating customizations but there are limited options with SSH pluginsValuable Features* Integration with Atlassian products like Jira,Crowd, and Stash* Easy to setup* PriceImprovements 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 itUse of SolutionTwo to three years.Deployment IssuesNo issues with deployment.Stability IssuesYes, Regular server/agent being down.Scalability IssuesYes, 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 SupportCustomer Service: Never used it. Had a decent responses from open forum.Technical Support: Never used it.Previous SolutionsYes. since we wanted to keep Atlassian suite all-around.Initial SetupEasy. Just like other Atlassian products.ROIWe got the product for a cheap price, so its alright.Pricing, Setup Cost and LicensingWe initially got 5 agents for around $2000 excluding infrastructure setup. Now we are using docker containers to maximize the mileage on them.Other AdviceIf 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