blob: 14f0ba94d2c9914ae45d8ca2f63ce4c17f3842d4 [file] [log] [blame]
E. Scott Daniels5f75c082019-10-04 09:07:42 -04001# vim: ts=4 sw=4 noet:
2
3# -------------------------------------------------------------------------------
4# Copyright (c) 2018-2019 AT&T Intellectual Property.
5#
6# Licensed under the Apache License, Version 2.0 (the "License");
7# you may not use this file except in compliance with the License.
8# You may obtain a copy of the License at
9#
10# http://www.apache.org/licenses/LICENSE-2.0
11#
12# Unless required by applicable law or agreed to in writing, software
13# distributed under the License is distributed on an "AS IS" BASIS,
14# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
15# See the License for the specific language governing permissions and
16# limitations under the License.
17# -------------------------------------------------------------------------------
18
19# CAUTION: This file eventually should exist in the ci directory, however until
20# this can be confirmed, and the .yaml file(s) in the ci project changed
21# to indicaate that ci/Dockerfile should be used, this is here with minor
22# changes needed to exist at the root.
23# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
24
25# CI to verify the MC application components
26# Inherits C toolchain from buildpack-deps:stretch then adds cmake and better shell(s).
27
28# It is assumed that this docker file is used with a build command run at the
29# root level of the repo (directory containing the ci directory). E.g.
30# docker build -f ci/Dockerfile .
31
32FROM buildpack-deps:stretch
33
34RUN apt-get update && apt-get -q -y install cmake ksh
35
36# stuff our repo things into a scratch area
37RUN mkdir /playpen
38ADD . /playpen
39
40
41# add any unit test scripts that need to be driven, e.g.
42# RUN ksh test/mcl_unit_test.ksh
43
44# This is a final/only script which might print useful things to the log and ALWAYS succeeds.
45RUN ksh /playpen/ci/stats.ksh
46
47# there is no cmd; the build/verification assumes that if the image is created
48# successfully, e.g. none of the previous run commands fail, that the environment
49# is successfully vetted.