Instead of always check out the arvados repository from the git server, pass
it as a build context, so changes in dev branches can easily be iterated on.
Arvados-DCO-1.1-Signed-off-by: Lucas Di Pentima <lucas.dipentima@curii.com>
sh -c 'git config --global --add safe.directory /tmp/workbench2 && make packages'
workbench2-build-image:
- (cd docker && docker build -t workbench2-build .)
+ docker build -t workbench2-build -f docker/Dockerfile ${ARVADOS_DIRECTORY}
apt-get clean
RUN /usr/bin/gem install --no-document fpm
-RUN cd /usr/src && git clone git://git.arvados.org/arvados.git && \
- cd arvados && \
+WORKDIR /usr/src/arvados
+COPY . .
+RUN cd /usr/src/arvados && \
+ test -d cmd/arvados-server || \
+ (echo "ERROR: build context must be an Arvados repository" && false) && \
GO_VERSION=$(grep 'goversion =' lib/install/deps.go |awk -F'"' '{print $2}') && \
ARCH=$(dpkg --print-architecture) && \
echo $GO_VERSION && \