Skip to content

Release is now including md5 checksum for archives #354

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

Merged
merged 2 commits into from
Jun 14, 2017
Merged

Release is now including md5 checksum for archives #354

merged 2 commits into from
Jun 14, 2017

Conversation

jgebal
Copy link
Member

@jgebal jgebal commented Jun 14, 2017

- added .md5 files generation.
- added .md5 files upload with release
- fixed upload of archive files (was using bad/old names)
@jgebal jgebal added this to the v3.0.1 milestone Jun 14, 2017
@coveralls
Copy link

coveralls commented Jun 14, 2017

Coverage Status

Coverage remained the same at 91.697% when pulling 60914a1 on jgebal:feature/md5_on_release into 7dcd62c on utPLSQL:develop.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 91.697% when pulling 60914a1 on jgebal:feature/md5_on_release into 7dcd62c on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 91.858% when pulling 7cf7725 on jgebal:feature/md5_on_release into aa134be on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jun 14, 2017

Coverage Status

Coverage remained the same at 91.708% when pulling 7cf7725 on jgebal:feature/md5_on_release into aa134be on utPLSQL:develop.

@Pazus Pazus merged commit dd2a492 into utPLSQL:develop Jun 14, 2017
@Pazus Pazus removed the in progress label Jun 14, 2017
@jgebal jgebal deleted the feature/md5_on_release branch June 14, 2017 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add MD5 checsum to release builds
3 participants