drone-plugins/drone-docker

dry run fails when no repo is provided

Berjou opened this issue · 1 comments

Hi.

I was not able to make a successful dry run build without providing a dummy repo, which seems to be an odd behavior since the goal of the dry_run setting is to not push the builded image, so the repo argument should not be necessary.

Is this behavior intended, or is there some technical difficulty to provide a more logical behavior?

This is expected. The repo field is used to tag the image and if the repo is not provided, it cannot be properly tagged. The intended purpose of dry_run is to perform every task except pushing to the registry. This helps teams verify they have everything configured correctly before pushing, and also helps teams debug issues without pushing.