RPM builder

Author: sunsingerus

Dockerfile

@@ -0,0 +1,49 @@
+FROM centos:latest
+
+# Create work & result dirs
+RUN mkdir -p /clickhouse
+RUN mkdir -p /clickhouse/result
+
+WORKDIR /clickhouse
+
+# Install ClickHouse from local RPMs
+COPY /rpmbuild/RPMS/x86_64/clickhouse-* /clickhouse/
+RUN yum localinstall -y /clickhouse/*.rpm
+
+# Install dependencies for clickhouse-test itself
+RUN yum install -y epel-release
+RUN yum install -y python-lxml
+RUN yum install -y python-requests
+RUN yum install -y python2-pip
+RUN pip install termcolor
+
+# Install dependencies required by test scripts
+RUN yum install -y perl
+RUN yum install -y sudo
+
+# Install main script
+COPY /runscript.sh /clickhouse/
+RUN chmod a+x /clickhouse/runscript.sh
+
+
+# Launch entrypoint
+#CMD "/usr/bin/clickhouse-test > /clickhouse/result/result.txt 2>&1"
+#CMD "/bin/bash"
+CMD "./runscript.sh"
+
+MAINTAINER Vladislav Klimenko
+LABEL version="0.1"
+LABEL description="Install ClickHouse RPMs and run clickhouse-test in order to verify RPMs are operational"
+
+# IMAGE_NAME=clickhouse_test_$(date +%s)
+# sudo docker build -t $IMAGE_NAME .
+# sudo docker run -it --mount src="$(pwd)",target=/clickhouse/result,type=bind $IMAGE_NAME
+
+#/usr/bin/clickhouse-server --config=/etc/clickhouse-server/config.xml
+#/usr/bin/clickhouse-test > /clickhouse/result/out.txt
+
+
+#docker run --ulimit nofile=90000:90000 <image-tag>
+#
+#First 90000 is soft limit, second 90000 is hard limit. When you launch the container, of course with -it flag, and enter command ulimit -n you’ll see the limit is 90000 now.
+

README.md

@@ -11,30 +11,54 @@ Run `build.sh` on any RHEL 6 or RHEL 7 based distribution and get ClickHouse sou
 ```bash
 Usage:
 
-./build.sh version        - display default version to build
+./builder version
+		display default version to build
 
-./build.sh all            - most popular point of entry - the same as idep_all
+./builder all
+		install build deps, download sources, build RPMs
+./builder all --test
+		install build+test deps, download sources, build+test and test RPMs
 
-./build.sh idep_all       - install dependencies from RPMs, download CH sources and build RPMs
-./build.sh bdep_all       - build dependencies from sources, download CH sources and build RPMs
-                            !!! YOU MAY NEED TO UNDERSTAND INTERNALS !!!
+./builder install --build-deps
+		install build dependencies
+./builder install --test-deps
+		install test dependencies
+./builder install --deps
+		install all dependencies (both build and test)
+./builder install --rpms [--from-sources]
+		install RPMs, if available (do not build RPMs)
 
-./build.sh install_deps   - just install dependencies (do not download sources, do not build RPMs)
-./build.sh build_deps     - just build dependencies (do not download sources, do not build RPMs)
-./build.sh src            - just download sources
-./build.sh spec           - just create SPEC file (do not download sources, do not build RPMs)
-./build.sh packages       - download sources, create SPEC file and build RPMs (do not install dependencies)
-./build.sh rpms           - just build RPMs from .zip sourcesi
-                            (do not download sources, do not create SPEC file, do not install dependencies)
-MYSRC=yes ./build.sh rpms - just build RPMs from unpacked sources - most likely you have modified them
-                            (do not download sources, do not create SPEC file, do not install dependencies)
+./builder build --spec
+		just create SPEC file
+		do not download sources, do not build RPMs
+./builder build --rpms [--test]
+		download sources, build SPEC file, build RPMs
+		do not install dependencies
+./builder build --rpms --from-archive [--test]
+		just build RPMs from .zip sources
+		(do not download sources, do not create SPEC file, do not install dependencies)
+./builder build --rpms --from-unpacked-archive [--test]
+		just build RPMs from unpacked sources - most likely you have modified them
+		(do not download sources, do not create SPEC file, do not install dependencies)
+./builder build --rpms --from-sources [--test]
+		build from source codes
 
-./build.sh publish packagecloud <packagecloud USER ID> - publish packages on packagecloud as USER
-./build.sh delete packagecloud <packagecloud USER ID>  - delete packages on packagecloud as USER
+./builder test --docker [--from-sources]
+		build Docker image and install produced RPM files in it. Run clickhouse-test
+./builder test --local
+		install required dependencies and run clickhouse-test on locally installed ClickHouse
+./builder test --local-sql
+		run several SQL queries on locally installed ClickHouse
 
-./build.sh publish ssh - publish packages via SSH
+./builder repo --publish --packagecloud=<packagecloud USER ID>
+		publish packages on packagecloud as USER
+./builder repo --delete  --packagecloud=<packagecloud USER ID>
+		delete packages on packagecloud as USER
+
+./builder src --download
+		just download sources
 ```
 
-In most cases just run `./build.sh all`
+In most cases just run `./builder all`