Open source software (OSS) products are developed in an open, collaborative way, often with much faster innovation cycles than traditional products. The open-source community is driven by everyone and anyone in the community who can help inspect, modify, learn from and share code.
This highly collaborative way of working allows resources to be distributed at a scale beyond a single company and thus, leverage the talents of a larger group that might not usually collaborate. …
Continuing on our Concourse UI Explained series, this week we are taking a look at a Concourse
build page. As always, we will be using our production pipeline as a guide to connect the mapping of an element to their meaning and purpose.
As we discussed previously in the Concourse Pipeline UI Explained, Concourse helps developers visualize the flow of artifacts across
builds. Jobs determine the actions of your pipeline, how resources progress through it. Every
job has a
build plan that determines the sequence of steps to execute the job.
The Concourse UI is continuously growing and improving, and the goal of this article is to surface the latest design elements of the Concourse UI. Using our production pipeline, it will become easier to connect the mapping of an element to its meaning and purpose.
The primary function of the pipeline web view is to show the flow of versioned resources through the connected jobs that make up a Concourse pipeline.
This feature is still in the early stages of development. We are picking up from our previous sneak peak post by James Ma. If you have a comment and want to participate in the conversation please visit the issue on GitHub.
This past week a community member reached out to begin work on a PR for a UI change in Concourse. This sparked some conversations within the team about how might we support this, since a lot of our design assets are private.
We started by tagging smaller, less risky issues in the backlog with a
design-snack label. We hope that these
design-snacksmake it more welcoming for contributors begin making UI contributions into the Concourse codebase.
With the growing popularity of Concourse, we noticed that our development teams wanted to observe and monitor multiple pipelines simultaneously. This behaviour wasn’t limited to just Pivotal engineering teams; in fact, it was even more prevalent amongst our Open Source Community. Our users currently solve this by cramming multiple browser windows into TV their monitor view or they use the Concourse Summary (aka Crystal) by David Goddard of the Pivotal Buildpacks team.
So, we embarked on a deeper Discovery effort with the goal of understanding and evaluating our assumptions around how Concourse users were solving this problem today.
I currently manage the Design team focused on delivering the Developer Experience for the Tanzu Modern Applications Platform team at VMware.