Last week I spent most of my time at Container Camp, and while I don’t think I missed any important news I didn’t pay close attention either. Therefore, a couple of older items concerning the release of Sumerian and Atlassian’s Escalator as well CodeBuild’s new support for Windows builds.
AWS CodeBuild Windows
Last week, CodeBuild finally added support for Windows containers. As I explained in a video, you can use CodeBuild to have a serverless build pipeline1, but this was limited to applications you could run on Linux.
The introduction of doing this for Windows builds fills an obvious gap here. By default there is a base container that has build tools such as MS Build installed, but you can build your own containers on top of this or separately. An example of this can be found in a blog post by AWS. Personally I can see this replacing Windows build machines, particularly in environments that are predominantly Linux based.
Of course, not everything is perfect. As usual, this is currently only available in a couple of regions and these don’t include Sydney2. Which is what you get for living far away from the rest of the world.
Sumerian is GA
Amazon Sumerian, the tool for building AR, VR, and 3D experiences is now generally available. Since it was announced at the last re: Invent this had become one of Amazon’s favourite demo tools at their events.
Whether you want to use it to have an avatar3 speak, or to show off something using AR, Sumerian should be able to handle it. While I haven’t tried it yet, from what I’ve heard it’s fairly easy to get something basic up and running.
When they introduced Bitbucket Pipelines, Atlassian execerbated an issue they already had with their internal builds: scaling.
In their introduction post for Escalator, they explain the issues they had. In short, it took too long for new nodes to come up in their Kubernetes cluster and too long for old nodes to be removed.
Escalator was built to solve this, and for their use at least it seems to work much better as it preemptively scales up and marks empty nodes as tainted quickly. As they use an AWS stack that is what this is designed for, so if you run into similar issues with the standard autoscaler it might be worth looking into it.
- There are still a number of requirement around it though. Not in the least that the subnet you build in needs to be connected to the internet through a NAT Gateway. [return]
- In case you suddenly wonder why I might care about this, I do work with clients who use Windows applications and this would make my life easier. [return]
- Host in Sumerian lingo, which is a terminology that sounds familiar… [return]
- Admittedly at this point a very low bar. [return]
Related content you might like:
- Week 32, 2018 - Istio 1.0; AWS CDK
- Week 25, 2018 - AKS; Daemons in ECS; Docker Application Designer; Private API Gateways
- Week 23, 2018 - Amazon Neptune; ALB Built-in Authentication; Helm in CNCF
- Week 14, 2018 - Jenkins X; Windows Server 2019; Azure Serial Console; Cloudflare Workers
- Week 49, 2017 - re:Invent 2017; macOS root bug