blog/Dockerfile

FROM ubuntu:latest

RUN apt-get update && apt-get upgrade -y && apt-get install -y curl jq rsync

RUN curl -sL `curl -s https://api.github.com/repos/roswell/roswell/releases/latest \
    | jq -r '.assets | .[] | select(.name|test("deb$")) | .browser_download_url'` \
    --output roswell.deb \
    && apt install -y ./roswell.deb

RUN ros install coleslaw-org/coleslaw
ENV PATH="/root/.evm/bin:/root/.roswell/bin:$PATH"
RUN coleslaw --help 2>&1
Add Dockerfile and Jenkinsfile This is the first step in improving my coleslaw builds. For this commit the only thing that it does is build the project into a staging directory. 2020-12-28 02:05:58 +01:00			`FROM ubuntu:latest`

			`RUN apt-get update && apt-get upgrade -y && apt-get install -y curl jq rsync`

			RUN curl -sL `curl -s https://api.github.com/repos/roswell/roswell/releases/latest \
			\| jq -r '.assets \| .[] \| select(.name\|test("deb$")) \| .browser_download_url'` \
			`--output roswell.deb \`
			`&& apt install -y ./roswell.deb`

Don’t install Emacs, call coleslaw after setting PATH I don’t need Emacs in this container, I can use a different container. I can’t run ‘coleslaw’ if the executable isn’t in the PATH variable. 2020-12-28 09:49:10 +01:00			`RUN ros install coleslaw-org/coleslaw`
Add Dockerfile and Jenkinsfile This is the first step in improving my coleslaw builds. For this commit the only thing that it does is build the project into a staging directory. 2020-12-28 02:05:58 +01:00			`ENV PATH="/root/.evm/bin:/root/.roswell/bin:$PATH"`
Send coleslaw error output to stdout I think Jenkins might fail my build because ‘coleslaw --help’ prints to stderr, which it might interpret as errors. So I’m going to try printing help to stdout instead. 2020-12-28 10:01:49 +01:00			`RUN coleslaw --help 2>&1`