Thanks Cos! Looks like increasing the release number is the best way to me.
On Mon, Sep 17, 2018 at 10:29 AM Konstantin Boudnik <[email protected]> wrote: > Yes, you can. > > If you want to only reflect the patch version for Hadoop component, > you can change the either the pkg version or release number in the > hadoop section of bigtop.bom. Look for the line > > version { base = '2.8.4'; pkg = base; release = 1 } > > Alternatively, set this sys.env. BIGTOP_BUILD_STAMP to some integer. > Alternatively, you can specify 'buildstamp' in the bigtop.bom file. It > has been intended to automatically increment the versions when > packages are produced as a part of the CI/CD process and would have an > effect on all packages you build - a very different from you want, I > guess. > -- > With regards, > Konstantin (Cos) Boudnik > 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > > Disclaimer: Opinions expressed in this email are those of the author, > and do not necessarily represent the views of any company the author > might be affiliated with at the moment of writing. > > > On Mon, Sep 17, 2018 at 8:19 PM, Dagang Wei <[email protected]> wrote: > > Hi folks, > > > > Seems after applying a patch, the package versioning will not change. For > > example, if I add a patch to Hadoop 2.8.4 in Bigtop, the result package > > still gets the version 2.8.4, so it is not able to tell from the version > > number whether a package contains a patch or not. > > > > Is there a way I can add additional information to reflect the patch in > the > > version number? Thanks! >
