Archives/ohwgiles_laminar
1
0
Fork 0
mirror of https://github.com/ohwgiles/laminar.git synced 2024-09-28 22:40:45 +00:00
Code Issues Projects Releases Wiki Activity
cd64be2cea
ohwgiles_laminar/pkg/centos7-x86_64.sh

82 lines
2.1 KiB
Bash
Raw Normal View History

docker scripts: cache the build environment
2018-05-14 18:15:53 +00:00
#!/bin/bash -e
add docker scripts
2015-11-26 07:41:06 +00:00
OUTPUT_DIR=$PWD
move packaging scripts into pkg directory This helps avoid confusion with the 'docker' directory. Also restore the debian9 scripts which may be useful for a while longer, update the names of the scripts and update the README accordingly.
2019-11-01 08:24:03 +00:00
SOURCE_DIR=$(readlink -f $(dirname ${BASH_SOURCE[0]})/..)
add docker scripts
2015-11-26 07:41:06 +00:00
pkg: mark ~upstream version in centos rpm
2019-11-01 18:36:57 +00:00
VERSION=$(cd "$SOURCE_DIR" && git describe --tags --abbrev=8 --dirty | tr - .)~upstream_centos7
use git describe instead of hard-coded version number in build scripts
2017-08-19 07:47:27 +00:00
docker scripts: cache the build environment
2018-05-14 18:15:53 +00:00
DOCKER_TAG=$(docker build -q - <<EOS
FROM centos:7
use promises to control job runs This is a refactor that more cleanly uses the kj framework for handling processes spawned by Runs. This obviates the workaround introduced back in ff42dae7cc3, and incidentally now requires c++14. Part of #49 refactor
2018-07-20 11:15:59 +00:00
RUN yum -y install epel-release centos-release-scl && yum-config-manager --enable rhel-server-rhscl-7-rpms && yum -y install rpm-build cmake3 make devtoolset-7-gcc-c++ wget sqlite-devel boost-devel zlib-devel
docker scripts: cache the build environment
2018-05-14 18:15:53 +00:00
EOS
)
add docker scripts
2015-11-26 07:41:06 +00:00
docker scripts: cache the build environment
2018-05-14 18:15:53 +00:00
docker run --rm -i -v $SOURCE_DIR:/root/rpmbuild/SOURCES/laminar-$VERSION:ro -v $OUTPUT_DIR:/output $DOCKER_TAG bash -xe <<EOS
use promises to control job runs This is a refactor that more cleanly uses the kj framework for handling processes spawned by Runs. This obviates the workaround introduced back in ff42dae7cc3, and incidentally now requires c++14. Part of #49 refactor
2018-07-20 11:15:59 +00:00
# for new gcc
export PATH=/opt/rh/devtoolset-7/root/usr/bin:\$PATH
add docker scripts
2015-11-26 07:41:06 +00:00
mkdir /build
cd /build
use capnproto 0.7.0 in build scripts
2018-09-14 07:50:09 +00:00
wget -O capnproto.tar.gz https://github.com/capnproto/capnproto/archive/v0.7.0.tar.gz
update dependencies to latest versions
2017-07-31 05:58:06 +00:00
wget -O rapidjson.tar.gz https://github.com/miloyip/rapidjson/archive/v1.1.0.tar.gz
add docker scripts
2015-11-26 07:41:06 +00:00
md5sum -c <<EOF
use capnproto 0.7.0 in build scripts
2018-09-14 07:50:09 +00:00
a9de5f042f4cf05515c2d7dfc7f5df21 capnproto.tar.gz
update dependencies to latest versions
2017-07-31 05:58:06 +00:00
badd12c511e081fec6c89c43a7027bce rapidjson.tar.gz
add docker scripts
2015-11-26 07:41:06 +00:00
EOF
tar xzf capnproto.tar.gz
tar xzf rapidjson.tar.gz
use capnproto 0.7.0 in build scripts
2018-09-14 07:50:09 +00:00
cd /build/capnproto-0.7.0/c++/
update dependencies to latest versions
2017-07-31 05:58:06 +00:00
cmake3 -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=off .
add docker scripts
2015-11-26 07:41:06 +00:00
make -j4
make install
update dependencies to latest versions
2017-07-31 05:58:06 +00:00
cd /build/rapidjson-1.1.0/
cmake3 -DRAPIDJSON_BUILD_EXAMPLES=off .
add docker scripts
2015-11-26 07:41:06 +00:00
make install
cd
cat <<EOF > laminar.spec
Summary: Lightweight Continuous Integration Service
Name: laminar
Version: $VERSION
Release: 1
License: GPL
BuildRequires: systemd-units
Replace boost/filesystem with kj/filesystem Lose the boost dependency since recent versions of capnproto's kj also provide a nice filesystem library. Take the opportunity to refactor the Run object to become more than POD and to encapsulate some of the functionality that was done in the Laminar class Part of #49 refactor
2018-09-28 07:36:10 +00:00
Requires: sqlite zlib
add docker scripts
2015-11-26 07:41:06 +00:00
%description
Lightweight Continuous Integration Service
%prep
%build
cmake: more appropriate use of CMAKE_INSTALL_PREFIX CMAKE_INSTALL_PREFIX is supposed to be used to set an install prefix of e.g. /usr or /usr/local. Because we need to install files to /etc, we had been requiring CMAKE_INSTALL_PREFIX=/ and installing using relative paths. The best practice method is to install to /etc using absolute paths, and then allow CMAKE_INSTALL_PREFIX to set where the final binaries actually go. Now that it actually has some meaning, the systemd service is generated to incorporate that path. Those wishing to use "make install" to install laminar to a subdir should use "make DESTDIR=path/to/subdir install" and NOT modify CMAKE_INSTALL_PREFIX. Documentation and packaging scripts updated accordingly.
2020-06-20 03:59:35 +00:00
cmake3 -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr -DSYSTEMD_UNITDIR=%{_unitdir} %{_sourcedir}/laminar-$VERSION
add docker scripts
2015-11-26 07:41:06 +00:00
pwd
make
%install
%make_install
%files
%{_bindir}/laminarc
centos pkg fix: laminard in sbin minor packaging fix for laminard move made in 304ef797b
2019-12-31 18:12:50 +00:00
%{_sbindir}/laminard
add docker scripts
2015-11-26 07:41:06 +00:00
%{_unitdir}/laminar.service
%config(noreplace) %{_sysconfdir}/laminar.conf
Install bash/zsh completions in correct locations
2018-10-16 17:20:43 +00:00
%{_datarootdir}/bash-completion/completions/laminarc
%{_datarootdir}/zsh/site-functions/_laminarc
add docker scripts
2015-11-26 07:41:06 +00:00
%post
echo Creating laminar user with home in %{_sharedstatedir}/laminar
useradd -r -d %{_sharedstatedir}/laminar -s %{_sbindir}/nologin laminar
Replace nodes/tags with contexts The nodes/tags system has not been particularly successful, it's not as intuitive as it could be, and in an attempt to be a single feature to address many use cases, ends up addressing none of them particularly well. This commit replaces nodes and tags with contexts. Each job may define which context(s) the job may be associated with. Laminar will only pop the job off the waiting queue when it can be assigned to a context. A context defines an integer number of executors, which represents how many runs can be simultaneously assigned to it. A context may provide extra environment variables. Essentially, a context replaces a node, and tags are gone. You just assign jobs to contexts directly, and you can use a glob expression. This should be more intuitive. For grouping jobs in the WebUI, a separate mechanism called "groups" is provided.
2019-12-13 08:42:22 +00:00
mkdir -p %{_sharedstatedir}/laminar/cfg/{jobs,contexts,scripts}
add docker scripts
2015-11-26 07:41:06 +00:00
chown -R laminar: %{_sharedstatedir}/laminar
EOF
rpmbuild -ba laminar.spec
zlib dep, build script fixes, v0.2
2015-12-06 13:07:16 +00:00
mv rpmbuild/RPMS/x86_64/laminar-$VERSION-1.x86_64.rpm /output/
correct postinst dir install path, force bash on ubuntu
2015-12-06 10:41:46 +00:00
EOS
Reference in New Issue Copy Permalink