Hey Goeff. FYI, the docker image I created [1] is only to build Brooklyn. I didn't mean to make it compatible for the release-make.sh However, having one for the release-make.sh script to work fine is IMO a great idea.
[1] https://github.com/apache/brooklyn/blob/master/Dockerfile On Mon, 9 Dec 2019 at 23:41, Geoff Macartney <geoff.macart...@gmail.com> wrote: > Hi Richard, > > Thanks for the mail; I'm building on OSX, surely I shouldn't need the gcc > toolchain? I can build Brooklyn ok with mvn clean install, it's just > failing when I run the release make script. I think you're right, the > Dockerfile we have just does a build. Maybe creating one for the release > would be a good idea! Did you get a release build to work with the Vagrant > file? > > I'll keep digging on the breakage and let you know if I work anything out. > > Cheers > Geoff > > > > On Mon, 9 Dec 2019 at 14:58, Richard Downer <rich...@apache.org> wrote: > > > Geoff, > > > > Possibly unrelated, but I've had an experience getting Brooklyn to build > > recently (haven't tried for many months!) > > > > There's a Dockerfile which spins up a container with all the required > > dependencies for a *build* - I'm not sure if it has everything required > for > > a *release* build though. > > > > However I prefer to avoid Docker and just build on my workstation - I > have > > a working build without tests but not with tests so consider this a work > in > > progress, but I believe these are the OS packages required to do a build. > > Do you have all of these installed? > > > > golang > > maven > > procps > > libpng-devel (CentOS/RHEL) / libpng-dev (Ubuntu/Debian) > > make > > automake > > autoconf > > libtool > > pkgconfig > > nasm > > gcc > > rpm-build (CentOS/RHEL) / rpm (Ubuntu/Debian) > > dpkg (CentOS/RHEL) > > > > HTH > > > > Richard. > > > > > > On Sun, 8 Dec 2019 at 22:15, Geoff Macartney <geoff.macart...@gmail.com> > > wrote: > > > > > Hi all, > > > > > > Per our chat about prepping for 1.0.0 I have created > > > https://github.com/apache/brooklyn-dist/pull/150 > > > > > > to remove MD5 and SHA-1 from the signing process. > > > > > > I've marked it Do Not Merge because I can't get the > > > make-release-artifacts.sh to work to test this. It keeps failing on > > > brooklyn-ui/ui-modules/utils with > > > > > > [INFO] > > > > ------------------------------------------------------------------------ > > > [ERROR] Failed to execute goal > > > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test > (default-test) > > > on project brooklyn-software-base: There are test failures. > > > [ERROR] > > > [ERROR] Please refer to > > > > > > > > > /private/var/folders/10/7wxypczs3ng9dny8kpnwc9nr0000gn/T/release-working-dir/source/apache-brooklyn-1.0.0-SNAPSHOT-src/brooklyn-server/software/base/target/surefire-reports > > > for the individual test results. > > > [ERROR] -> [Help 1] > > > > > > > > > Running "mvn test" in the folder works ok. I will need to take some > time > > to > > > dig into this, but might as well stick this up for review for now. > > > > > > Does anyone with more experience of the script have any ideas on what > > might > > > be up here? > > > > > > I tried to get the Vagrant setup going too but there's some > > incompatibility > > > in my conf between the gpg version in vagrant (1.4.20) and my version > > > (2.2.15), so again more digging required. Also, anyone know if gpg will > > > work inside Vagrant when I use a Yubikey? > > > > > > Geoff > > > > > > -- Thomas Bouron Senior Software Engineer *Cloudsoft <https://cloudsoft.io/> *| Bringing Business to the Cloud GitHub: https://github.com/tbouron Twitter: https://twitter.com/eltibouron
