I have a PDF with multiple admission tickets and need to send each page to a different person. It was a pretty easy process:
Updated 8/19/2017: Amazon has now updated AWS CodeBuild service to support Teams! In other words, in the 2 days since I posted this issue, it has now been fixed. Hooray! I now see my team projects in the list of repositories after linking my account. One minor nitpick though… They sort the list of repositories in the drop-down chronologically, not alphabetically. Since I have hundreds of repositories, that means in order to find a particular one I have to remember the order it was created. Hope they fix this (minor) issue too!
As a user of both Bitbucket and AWS, I was recently excited to hear Amazon had announced integration with both AWS CloudBuild and Atlassian Bitbucket. For those unfamiliar with these two products, AWS CloudBuild is part of Amazon’s suite of code automation CI/CD toolset. This service, along with the full suite, provides the ability to automate software build creation, testing, and deployment. Atlassian Bitbucket, on the other hand, is a large source code repository provider. The AWS announcement means that you can now build projects in AWS using Bitbucket repositories as the source.
Or that’s what it was supposed to mean… Apparently, no one told AWS that most professional software development companies use Bitbucket Teams to manage projects. The new AWS integration is accomplished using an OAuth authenticated sign-in from within the AWS CodeBuild project creation wizard. Unfortunately, after logging in it only allows two types of repositories to be selected: public repositories and those in your *personal* account. Most people using Bitbucket professional use teams and do not store the repositories in their personal account. The result is that no repositories are available for integration.
In other words… it’s broken. One solution would be to authenticate with the team login but Atlassian disabled the ability to login with the team account years ago. Now, Amazon only announced this feature recently, so it is possible they will get around to fixing it but in the short-term it is quite disappointing. While there are other ways to integrate AWS CodeDeploy and Bitbucket, I was looking for an all-in-one solution. In fact, when I recently tried Atlassian’s plugin to integrate one of my repositories into AWS CodeBuild, the web page just froze. Oh well, hopefully Amazon will fix this oversight soon!
By the way, you might ask, “Why I don’t just move my source code repository into AWS CodeCommit?” The answer is simple logistics. If I have hundreds of projects used by hundreds of developers, migrating them to a new repository is not easy/fun. The advantage of having this integration working is that it provides a nice, fluid transition toward migrating to AWS builds, without the commitment of actually transferring any repositories.
I was reading Deep Work:Rules for Focused Success in a Distracted World. On page 243, the author writes:
Most nonfiction authors are easy to reach. They include an e-mail address on their author websites along with an open invitation to send them any request or suggestion that comes to mind. Many even encourage this feedback as a necessary commitment to the elusive but much-touted importance of “community building” among their readers. But here’s the thing: I don’t buy it.
Scott and I are non-fiction authors of three cert books. We don’t encourage email. We do encourage communication. All three of our books encourage readers to contact us using the forums at CodeRanch.com. This works well for us because there are others who have the possibility to answer and it doesn’t come with a quick reply assumption. (Although we often do reply within a day or two if nobody else has first).
We do like hearing from readers. We like hearing about their success on the exam. We like hearing when they find an errata. (see why posting errata matters). We like hearing what they are looking for clarification.
I wonder if this comes from our domain. Computer programmers don’t write a book expecting to make loads of money. And we aren’t required to publish for our jobs. The author of this book is a professor. So I wonder if he thinks of his book differently? Or if it is that Scott and I were active on the forums before writing a book so wish to remain accessible?