That is really good news.
But the question still stands... What did not go right? Is there a
gap/blind-spot/root-cause/something that prevented this test from being
in the test suite that is used to validate a build as "promotable"?
If there was "something"; will the addition of this test, "use asadmin
deploy without the port option specified" going to address that
"something" completely, or do we need to add some more test to "close
the gap"?
I was very surprised to see this issue in the promoted build, partially
because I know the number of folks testing the application server
produced from the Project GlassFish code-base and the HUGE number of
automated test that the code gets subjected to (on a near continuous
basis)....
vbk
Judy Tang wrote:
> I talked with SQE and developer and we plan to add a QL test to test
> asadmin deploy command
> without giving --port option.
>
> Thanks,
> Judy
>
> vince kraemer wrote:
>
>> Over on the dev alias there are reports of an issue that seems like
>> it would have prevented the build from being promoted...
>>
>> https://glassfish.dev.java.net/servlets/ReadMsg?list=dev&msgNo=2792
>>
>> The issue did not stop the build from being promoted.
>>
>> How can we improve the promotion process to prevent an issue like
>> this from being present in the promoted build in the future?
>>
>> Is it worth doing?
>>
>> thanks,
>> vbk
>