Fix alpha build error message when generate version object from version string

[mushao999]

Class org.elasticsearch.Version provides the method public static Version fromString(String version){...} to generate version object from version string . In this method, alpha build requires a build number below 25. So in assertion

assert build < 25 : "expected a beta build but " + build + " >= 25";

at line 328, what really exceped is alpha build not beta build.

[elasticcla]

Hi @mushao999, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

[elasticmachine]

Pinging @elastic/es-core-infra

[mushao999]

@javanna Cloud you please review this PR? This is my first OS contribution, though it is really a small one.

[tvernum]

@elasticmachine test this please

[mushao999]

@tvernum @elasticmachine I got the following error while build elasticsearch-ci/1

==> krb5kdc: Waiting for machine to boot. This may take a few minutes...
    krb5kdc: SSH address: 127.0.0.1:2222
    krb5kdc: SSH username: vagrant
    krb5kdc: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within

the configured ("config.vm.boot_timeout" value) time period.
> Task :plugins:repository-hdfs:krb5kdcFixture FAILED

Cloud you please help me with this ?

[mushao999]

@tvernum hi, this PR did not pass the elasticsearch/cli check yesterday, the error message showed it had something to do with the network of test machine. So I made a force push in order to invoke the recheck which didn't work. Could you please help me to start the check again. Thank you very much.

[mushao999]

ping @tvernum @javanna @colings86 @elasticmachine

[tvernum]

@elasticmachine test this please

[mushao999]

@tvernum @javanna @colings86 @elasticmachine Why is a small pull request so difficult to be accepted?

[rjernst]

@mushao999 I apologize for the long delay. Your change looks fine. Getting CI to pass is sometimes difficult, and even for innocuous changes we require passing that before merging.

It looks like your PR is a month behind master. Can you update that please? There have been many CI stabilization improvements in the last month. I would then be happy to quickly drive this through CI to get it merged. Also, I recommend not opening PRs based on your master branch. If you had a branch off of master, I would have tried syncing it up myself, but I do not want to touch your copy of master.

[mushao999]

@rjernst Hi, thank you for your help. I have updated the master branch in my repository. Please help me to pass the checks.

[rjernst]

@elasticmachine test this please

[rjernst]

Thanks for the contribution @mushao999!