Lifecycle and limits

​

Check capacity

Previews run on spare capacity in Peak’s shared bare-metal pool, at the lowest priority. CI jobs always go first. Expect Waiting for capacity while there is no room, or while CI jobs wait. Expect Peak to start the preview as soon as there is room. Expect a preview that waits 6 hours to fail with No capacity. When CI needs room, Peak stops ready previews first, the idlest one first. Open the URL to start one again. Expect a build in progress to go back to Waiting for capacity.

​

Choose which pull requests

Expect every pull request from the repository to get a preview. To preview only some, set Pull requests to Labeled in your repository’s Settings under Previews. Add the label, preview by default, to start a pull request’s preview. Remove it to close the preview. With a Render Blueprint whose previews.generation is manual, Peak starts in Labeled. Expect a title containing [render preview] to count too, as on Render.

​

Update a preview

Push to the pull request. Expect Peak to build the new head commit. Expect the current preview to serve until the new one is ready. Expect a newer push to replace a build that has not finished.

​

Wake a stopped preview

Expect a preview to stop after 60 minutes without requests. Open its URL to start it again. Expect a Starting page until it is ready. Expect a restarted preview to rebuild from the pull request’s head commit. Expect its databases to start empty again.

​

Close a preview

Close or merge the pull request. Expect Peak to remove its preview. Reopen the pull request to build a new one.

​

Check preview states

Check each preview under Previews in your repository.

​

Limits