Build artifacts can produce useful information, such as documentation and performance graphs. However, there are typically two different scenarios where someone wants to look at a build artifact:

I want to see how this change will modify the existing documentation/performance

I want to see the documentation/performance for the latest commit on the master branch

For either scenario, seeing the build artifacts for the latest commit on the master branch is important. However, there doesn't currently seem to be a way to expose that concept. Build artifacts are only exposed via URLs that contain the CircleCI build number.

I would like CircleCI to expose URLs that contain a branch name, instead of a CircleCI build number. This URL could be used to refer to build artifacts in an arbitrary build. When a client resolves this URL, CircleCI should issue an HTTP redirect to the most recent CircleCI build for the latest commit of that branch.

Here's a specific use case:

My project builds HTML documentation. I would like to include a link in the README to point the reader to the latest version of this HTML documentation. I would like CircleCI to build and host this documentation for me via the build artifacts feature. I need a stable URL to put in the README file, that will reliably result in the latest version of this HTML documentation.

CCI-I-228