Sanjeeb Kumar Sahoo wrote:
>> How about a file that's part of each module that contains only the build
>> number?
>
>
> Why per module? Won't a file in glassfish/bootstrap dir be enough?
Probably. I guess *everyone* needs that directory, even if they
have only one module.
>> When a build is promoted, the file could be updated in all
>> modules automatically.
>
>
> Do we not have to update the file just after the code is checked out for
> a promoted build? I say this because we don't lock the workspace while a
> build is being promoted and promotion process takes 3~4 hours to finish.
That's probably better, assuming you handle failure cases appropriately.