Deployment trigger scheduler should have option to not deploy the same code

I would like an option on the deployment plan's scheduler to not trigger a deployment if there has been no new code updates to the parent plan.

Current world, if I set up a cron trigger to deploy hourly from FOO-BAR build plan, it will continue to deploy every hour even if there is no change to FOO-BAR. (Essentially, deploying FOO-BAR-12 artifact over and over and over)

I see how this may be desirable for some users, but our use case for this improvement is that a deployment to our QA environment leads to about 5 mins of downtime as the servers all re-initialize. We want to only incur that cost if there is something new to deploy, and know through cron that it will only happen at most on the hour every hour.