-
Notifications
You must be signed in to change notification settings - Fork 30
Rsh/get version script #39
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
Conversation
|
|
||
| #If the api calls return empty then this library cannot be compared to the online versions | ||
| #may proceed with the pull request | ||
| if(($mavenVersion -eq $null) -and ($bintrayVersion -eq $null)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: should we use -or instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure here either. Initially I was thinking -or also, however I was think this would only lead to another error if there's a version conflict with either the Maven or Jcenter version and we allow it to proceed. With -and we only allow it to proceed if it has not been published to either repository.
add "Scripts/*" in pr: - paths: - exclude: within prValidate.yml
I added the script 'getLatestVersion' to retrieve version in the Gradle.Properties file. The script was also included in the artifact so that it may later be accessed in the Java-Core release pipeline. This script is used to auto-tag the GH releases in the Java-Core release pipeline.
Also updated the validateMavenVersion script to take into account the case where we may not have published anything to either the Jcenter or Maven repos. This is more so a provision for any future scenarios which may occur.