Author

Peter Leschev

[guest author fields > title]


Warning: Undefined array key “carousel” in /srv/users/atlassian/apps/atlassianstaging/public/wp-content/plugins/curator/dist/feed/render.php on line 68

Warning: Trying to access array offset on value of type null in /srv/users/atlassian/apps/atlassianstaging/public/wp-content/plugins/curator/dist/feed/render.php on line 68

Announcing an open source Puppet Module for Sonatype Nexus

TL;DR We’ve open-sourced a Puppet module to help manage the configuration of Sonatype Nexus instances. Check it out! The Build Engineering team at Atlassian has been running Sonatype Nexus instances for a few years now. We use Nexus for storing our public and private artifacts on https://maven.atlassian.com/ (which receives 2.6 million requests/day), publishing to maven […]

How I Discovered Rogue Processes Running on our Build Agents

In the process of digging around investigating a performance issue with our internal build agents, I discovered rogue fluxbox processes taking 100% CPU on a large number of our build agents, here’s a write up of how I found them. On a particular host you can get a vague idea of how busy a host […]

Satisfying Build Engineering Customers (Pt 2)

I’m excited! Back when I talked about Satisfying the Customers of BuildEng team I talked about ensuring that we communicate to our customers that we’ve seen the issues that they have created by Triaging those issues quickly. This is really important, it provides our customers quick feedback on the issue that they have raised so they don’t […]

Satisfying Our Internal Customers by Using Kanban and the GreenHopper Rapid Board

As an internal service group, Build Engineering, we support many different products with numerous agile development teams. We have a large set of requests that come through from infrastructure to releasing our products. It difficult to communicate to our ‘customers’ the priority of their issue and when their issue will be worked on. Satisfying our […]

Faster Bamboo builds with the Agent Smith Wallboard

With the Jira Bugfix effort using Kanban, we track a metric called Lead Time, which in our case is the period of time between the moment Atlassian decides to implement a fix (or feature) to the time it is made available to the customer. Adapting Kaizen, the culture of continous improvement, we look for waste […]