New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continuous deployment should not release new version if binaries are equal #105

Closed
mockitoguy opened this Issue Oct 13, 2014 · 0 comments

Comments

Projects
None yet
1 participant
@mockitoguy
Copy link
Member

mockitoguy commented Oct 13, 2014

Continuous deployment should not release new version if binaries are equal. Sometimes we check-in code that does not require new version (for example, changes to README.md, itp). We should add some logic that prevents releasing a brand new version if the current binaries are the same as previously released.

@mockitoguy mockitoguy self-assigned this Oct 13, 2014

jerzykrlk added a commit to jerzykrlk/mockito that referenced this issue Oct 28, 2014

avoid releasing new version if binaries the same
Fixes mockito#105 (more info on this ticket).

- exposed an existing method on the RelelaseNotesBuilder
- added new task that checks equality of the binaries
- hooked up the task so that the release is not triggered if binaries the same
- some tidy-up is still needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment