Build Graylog from Source and generate rpm/deb files

Hello Team,

I have used Graylog for some time and now would like to build it from source.
My end objective is to build it from source and generate rpm/deb files for distribution.

I followed the build log from here and tried to perform the below steps:

$ git clone --depth=50 GitHub - Graylog2/graylog2-server: Free and open log management Graylog2/graylog2-server
$ git fetch origin +refs/pull/3911/merge:
$ git checkout -qf FETCH_HEAD
$ export CASHER_DIR=$HOME/.casher

$ java -Xmx32m -version
java version “1.8.0_131”
Java™ SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot™ 64-Bit Server VM (build 25.131-b11, mixed mode)

$ javac -J-Xmx32m -version
javac 1.8.0_131

$ mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V
[INFO]
[INFO] — maven-archetype-plugin:2.4:update-local-catalog (default-update-local-catalog) @ graylog-plugin-archetype —
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Graylog Parent POM … SUCCESS [3.529s]
[INFO] Graylog Project Parent POM … SUCCESS [3.417s]
[INFO] AutoValue JavaBean extension … SUCCESS [9.615s]
[INFO] Graylog … SUCCESS [6:05.280s]
[INFO] integration-tests … SUCCESS [3.213s]
[INFO] Graylog Plugin Parent POM … SUCCESS [0.010s]
[INFO] Graylog Plugin with Web support Parent POM … SUCCESS [3.229s]
[INFO] graylog-plugin-archetype … SUCCESS [2.842s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 6:32.718s
[INFO] Finished at: Wed Jun 14 12:53:16 UTC 2017
[INFO] Final Memory: 73M/346M
[INFO] ------------------------------------------------------------------

Now, my next step is build a deb/rpm file. I referred GitHub - Graylog2/fpm-recipes: Graylog package build recipes but unable to move ahead.

Please suggest what am I missing here.

With which step exactly do you have issues?

In general, fpm-cookery downloads the published Graylog release tar-ball from the URI listed in https://github.com/Graylog2/fpm-recipes/blob/2.2/recipes/data.yml and builds the DEB and RPM packages from that.

See https://fpm-cookery.readthedocs.io/ for details about fpm-cookery.

Any particular reason you don’t want to use the official release artifacts?

I am planning to make changes to the UI.

I cloned fpm-recipes git and ran the below command:
$ vagrant docker-run ubuntu1404 -- fpm-cook package /vagrant/recipes/graylog-server/recipe.rb

But as you mentioned, this downloads the published Graylog tarball from the URI mentioned in data.yml.
How can I setup fpm-cookery to use my local version which I have built? Pardon me for my ignorance of fpm-cookery.

Hello team,

Please assist.

@jochen @jan

This is not a personal support channel.

If you need individual support, consider buying Graylog Enterprise: https://www.graylog.org/enterprise

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.