Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: secure hermetic-build docker image #3196

Draft
wants to merge 42 commits into
base: main
Choose a base branch
from
Draft
Show file tree
Hide file tree
Changes from 24 commits
Commits
Show all changes
42 commits
Select commit Hold shift + click to select a range
5f5e0bd
chore: secure hermetic-build docker image
diegomarquezp Sep 12, 2024
15a19c5
fix python preparation
diegomarquezp Sep 12, 2024
ff0fc1a
apine image
diegomarquezp Sep 12, 2024
9a25dda
update reqs
diegomarquezp Sep 12, 2024
66d7f45
do not use BSD flags for `rm`
diegomarquezp Sep 12, 2024
d12877c
fixes to docker image
diegomarquezp Sep 16, 2024
4885459
fix reference to global site-packages
diegomarquezp Sep 16, 2024
b97c209
fix permissions
diegomarquezp Sep 17, 2024
3f94f0b
use SHAs directy
diegomarquezp Sep 17, 2024
08fe2cd
reduce image size
diegomarquezp Sep 17, 2024
539922a
use cloud build action
diegomarquezp Sep 17, 2024
1a34741
Update .cloudbuild/library_generation/library_generation.Dockerfile
diegomarquezp Sep 17, 2024
43f1ac0
update DEVELOPMENT.md
diegomarquezp Sep 17, 2024
1dc3629
use buildkit
diegomarquezp Sep 17, 2024
90dafe3
Merge remote-tracking branch 'origin/secure-hermetic-build-docker-ima…
diegomarquezp Sep 17, 2024
3f3deec
Merge branch 'main' into secure-hermetic-build-docker-image
diegomarquezp Sep 17, 2024
b730a4b
do not build image in integration test
diegomarquezp Sep 17, 2024
db2e8e7
remove wrong dependency
diegomarquezp Sep 17, 2024
fb98222
Merge remote-tracking branch 'origin/secure-hermetic-build-docker-ima…
diegomarquezp Sep 17, 2024
32fffb7
comment unwanted airlock repo
diegomarquezp Sep 17, 2024
51544a3
Update library_generation/DEVELOPMENT.md
diegomarquezp Sep 17, 2024
e9a5df4
remove redundant skipTests
diegomarquezp Sep 17, 2024
8f0ac9b
Merge remote-tracking branch 'origin/secure-hermetic-build-docker-ima…
diegomarquezp Sep 17, 2024
2c35db2
add links to confirm availablity of missing python packages
diegomarquezp Sep 17, 2024
d09124f
save point: owl-bot cli standalone and python repo using airlock
diegomarquezp Sep 17, 2024
34835a5
remove standalone executable for owlbot
diegomarquezp Sep 17, 2024
a3490e2
remove airlock registry for python
diegomarquezp Sep 17, 2024
efeff60
fix list of glibc shared objects
diegomarquezp Sep 17, 2024
ae0f349
add instructions for setting up airlock docker registry
diegomarquezp Sep 18, 2024
9177111
fix python setup
diegomarquezp Sep 18, 2024
8797e30
Revert "remove airlock registry for python"
diegomarquezp Sep 18, 2024
aa0fe85
fix integration test yaml
diegomarquezp Sep 18, 2024
bce332d
add hermetic-library-generation cloud build job
diegomarquezp Sep 18, 2024
d0a6da1
use CLOUD_LOGGING_ONLY to allow SA runner
diegomarquezp Sep 18, 2024
11a81d3
fix volumes
diegomarquezp Sep 18, 2024
565afda
retrigger build
diegomarquezp Sep 18, 2024
dd275ac
retrigger build
diegomarquezp Sep 18, 2024
2e5067d
retrigger build
diegomarquezp Sep 19, 2024
32ac053
retrigger build
diegomarquezp Sep 19, 2024
054bf42
retrigger build
diegomarquezp Sep 19, 2024
87a2e09
add python volumes
diegomarquezp Sep 19, 2024
42f331e
use cloud-sdk image for steps
diegomarquezp Sep 19, 2024
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# Copyright 2024 Google LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# This is a tentative Cloud Build workflow to replace the existing integration
# tests setup in GitHub Actions
timeout: 7200s # 2 hours
substitutions:
_IMAGE_NAME: "hermetic-build"
steps:
# Library generation build
- name: gcr.io/cloud-builders/docker
args: [
"build",
"-t", "${_IMAGE_NAME}",
"--file", ".cloudbuild/library_generation/library_generation.Dockerfile", "."]
id: library-generation-image-build
env:
- 'DOCKER_BUILDKIT=1'
waitFor: ["-"]
# Python scripts compilation
- name: python
args: [ "python", "-m", "pip", "install", "library_generation" ]
id: library-generation-python-compile
waitFor: ["library-generation-image-build"]
# Python integration tests execution
- name: python
args: [ "python", "-m", "unittest",
"library_generation/test/integration_tests.py" ]
id: library-generation-python-compile
waitFor: ["library-generation-python-compile"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the image name in this file?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this about the _IMAGE_ID of the image? We can change it, but how can we improve its name?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this about the _IMAGE_ID of the image?

Yes.

Can we create a image repo in AR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if we leave the changes related to the AR migration as a follow up? Should be a small PR.

Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,8 @@ steps:
"-t", "${_VERSIONED_IMAGE_ID}",
"--file", ".cloudbuild/library_generation/library_generation.Dockerfile", "."]
id: library-generation-build
env:
- 'DOCKER_BUILDKIT=1'
waitFor: ["-"]

images:
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
[global]
index-url = https://us-python.pkg.dev/artifact-foundry-prod/ah-3p-staging-python/simple/
# TODO: use the following index URL when `lxml` and `versions` are available in the `trusted` airlock registry
# We can confirm their availability in https://airlock.corp.goog/search?query=&type=Python
# index-url = https://us-python.pkg.dev/artifact-foundry-prod/python-3p-trusted/simple/
11 changes: 11 additions & 0 deletions .cloudbuild/library_generation/image-configuration/airlock-pypirc
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
[distutils]
index-servers = ah-3p-staging-python
# TODO: use this index instead when `lxml` and `versions` are available in the `trusted` airlock registry
# We can confirm their availability in https://airlock.corp.goog/search?query=&type=Python
# index-servers = python-3p-trusted
JoeWang1127 marked this conversation as resolved.
Show resolved Hide resolved

[ah-3p-staging-python]
repository: https://us-python.pkg.dev/artifact-foundry-prod/ah-3p-staging-python/
# TODO: use this repository instead when `lxml` and `versions` are available in the `trusted` airlock registry
# We can confirm their availability in https://airlock.corp.goog/search?query=&type=Python
# repository: https://us-python.pkg.dev/artifact-foundry-prod/python-3p-trusted/
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
/**
* @fileoverview This file contains the esbuild configuration to compile the
* owlbot-cli source code into a single bundled javascript file
* @author diegomarquezp
*/
const { build } = require("esbuild");


const sharedConfig = {
entryPoints: ["src/bin/owl-bot.ts"],
bundle: true,
minify: false,
};

build({
...sharedConfig,
platform: 'node',
format: 'cjs',
outfile: "build/bundle.js",
});
218 changes: 154 additions & 64 deletions .cloudbuild/library_generation/library_generation.Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -11,107 +11,197 @@
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Creates the owl-bot binary (no node runtime needed)

# install gapic-generator-java in a separate layer so we don't overload the image
# with the transferred source code and jars
FROM gcr.io/cloud-devrel-public-resources/java21 AS ggj-build
# node:22.1-alpine
FROM us-docker.pkg.dev/artifact-foundry-prod/docker-3p-trusted/node@sha256:487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede8 as owlbot-cli-build
JoeWang1127 marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we plan to update these base images? It might be fine to not update this one, but for the Java and Python one, we may want to update the Maven/JDK/Python version regularly.

ARG OWLBOT_CLI_COMMITTISH=ac84fa5c423a0069bbce3d2d869c9730c8fdf550

# install tools
RUN apk add git

# Clone the owlbot-cli source code
WORKDIR /tools
RUN git clone https://github.com/googleapis/repo-automation-bots
WORKDIR /tools/repo-automation-bots/packages/owl-bot
RUN git checkout "${OWLBOT_CLI_COMMITTISH}"

# Part of the code path (that we don't use) ends up touching a dependency called
# @google-cloud/datastore that tries a fs.readFileSync that is not handled by
# default by esbundle (esbundle is good a figuring out imports but doesn't
# actively scan filesystem interactions such as fs.readFileSync). This makes the
# app to fetch a file at runtime that is not available in the bundle context.
# This is why we remove this import and its usage from the entrypoint.
RUN sed -i '/testWebhook/d' src/bin/owl-bot.ts

# Bundle the source code and its dependencies into a single javascript file
# with all its dependencies embedded.
# This is because SEA (see below) cannot
# resolve external modules in a multi-file project.
# We use the esbuild tool. See https://esbuild.github.io/
COPY ./.cloudbuild/library_generation/image-configuration/owlbot-cli-build-config.js .
RUN npm i esbuild
RUN node owlbot-cli-build-config.js
Copy link
Collaborator

@JoeWang1127 JoeWang1127 Sep 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In order to create a SEA, do we have to bundle source code into a single js file?

Can we combine the two steps into one?

Copy link
Contributor Author

@diegomarquezp diegomarquezp Sep 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, bundling is necessary:

# This is because SEA (see below) cannot
# resolve external modules in a multi-file project.

From the docs: The single executable application feature currently only supports running a single embedded script using the CommonJS module system.

Can be combine the two steps?

Do you mean using a single RUN + &&?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was referring whether we can build a SEA from multiple js source code, looks like it has to be bundled together first.


# Compile the bundled javascript file into a Linux executable
# Create a Standalone Executable Application (SEA) configuration file.
# See https://nodejs.org/api/single-executable-applications.html
RUN echo '{ "main": "bundle.js", "output": "sea-prep.blob" }' > build/sea-config.json
JoeWang1127 marked this conversation as resolved.
Show resolved Hide resolved
WORKDIR /tools/repo-automation-bots/packages/owl-bot/build
RUN node --experimental-sea-config sea-config.json
RUN cp $(command -v node) owl-bot-bin
RUN npx postject owl-bot-bin NODE_SEA_BLOB sea-prep.blob \
--sentinel-fuse NODE_SEA_FUSE_fce680ab2cc467b6e072b8b5df1996b2

# move to a simple path for convenience
RUN cp ./owl-bot-bin /owl-bot-bin

# Creates the generator jar
# maven:3.8.6-openjdk-11-slim
FROM us-docker.pkg.dev/artifact-foundry-prod/docker-3p-trusted/maven@sha256:2cb7c73ba2fd0f7ae64cfabd99180030ec85841a1197b4ae821d21836cb0aa3b as ggj-build

WORKDIR /sdk-platform-java
COPY . .
# {x-version-update-start:gapic-generator-java:current}
ENV DOCKER_GAPIC_GENERATOR_VERSION="2.45.1-SNAPSHOT"
# {x-version-update-end}

RUN mvn install -B -ntp -DskipTests -Dclirr.skip -Dcheckstyle.skip
RUN cp "/root/.m2/repository/com/google/api/gapic-generator-java/${DOCKER_GAPIC_GENERATOR_VERSION}/gapic-generator-java-${DOCKER_GAPIC_GENERATOR_VERSION}.jar" \
"./gapic-generator-java.jar"
# use Docker Buildkit caching for faster local builds
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does Docker Buildkit caching mean? Since the build does not take too much time(~1.5 minute), I think it's OK to download the maven dependencies every time. What I'm trying to avoid is that we build an image with stale dependencies.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Buildkit caching allows to reuse the specified folders in the specific step. This would not impact any CI pipeline as they don't preserve any kind of cache. The main purpose is to speed up local builds for development, and can be disabled via docker build --no-cache.

My perspective is that we probably won't work on modifying the java source code when working on the Docker image, so several image builds may benefit from caching the mvn install output.

RUN --mount=type=cache,target=/root/.m2 mvn install -B -ntp -T 1.5C \
-Dclirr.skip -Dcheckstyle.skip -Djacoco.skip -Dmaven.test.skip \
-Dmaven.site.skikip -Dmaven.javadoc.skip -pl gapic-generator-java -am

# build from the root of this repo:
FROM gcr.io/cloud-devrel-public-resources/python
RUN --mount=type=cache,target=/root/.m2 cp "/root/.m2/repository/com/google/api/gapic-generator-java/${DOCKER_GAPIC_GENERATOR_VERSION}/gapic-generator-java-${DOCKER_GAPIC_GENERATOR_VERSION}.jar" \
"/gapic-generator-java.jar"

SHELL [ "/bin/bash", "-c" ]
# Builds the python scripts in library_generation
# python:3.11-alpine
FROM us-docker.pkg.dev/artifact-foundry-prod/docker-3p-trusted/python@sha256:0b5ed25d3cc27cd35c7b0352bac8ef2ebc8dd3da72a0c03caaf4eb15d9ec827a as python-scripts-build
JoeWang1127 marked this conversation as resolved.
Show resolved Hide resolved

# This will use GOOGLE_APPLICATION_CREDENTIALS if passed in docker build command.
# If not passed will leave it unset to support GCE Metadata in CI builds
ARG GOOGLE_APPLICATION_CREDENTIALS

RUN apk add bash curl

# Install gcloud to obtain the credentials to use the Airlock repostiory
RUN curl -sSL https://sdk.cloud.google.com | bash -e
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which version of the gcloud?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I'll figure this out in the follow up (enhancements) since it is now out of scope.

ENV PATH $PATH:/root/google-cloud-sdk/bin


# Configure the Airlock pip package repository
RUN pip install keyrings.google-artifactregistry-auth -i https://pypi.org/simple/
COPY .cloudbuild/library_generation/image-configuration/airlock-pypirc /root/.pypirc
COPY .cloudbuild/library_generation/image-configuration/airlock-pip.conf /etc/pip.conf
RUN chmod 600 /root/.pypirc /etc/pip.conf

COPY library_generation /src

# install main scripts as a python package
WORKDIR /src

RUN --mount=type=secret,id=credentials python -m pip install --target /usr/local/lib/python3.11 -r requirements.txt
RUN python -m pip install --target /usr/local/lib/python3.11 .

# Final image. Installs the rest of the dependencies and gets the binaries
# from the previous stages. We use the node base image for it to be compatible
# with the standalone binary owl-bot compiled in the previous stage
# node:22.1-alpine
FROM us-docker.pkg.dev/artifact-foundry-prod/docker-3p-trusted/node@sha256:487dc5d5122d578e13f2231aa4ac0f63068becd921099c4c677c850df93bede8 as final
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why can't we use a python base image?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The standalone owlbot seems to need a few runtime libraries (.so) in the linux environment that are available in the node image by default (besides the node runtime). The python image doesn't have them.
If we want to have a python image as base, I can try to use a python base and install node or whichever libraries the executable needs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From discussion with @blakeli0 and @JoeWang1127, let's use a vanilla Alpine based image.


ARG OWLBOT_CLI_COMMITTISH=ac84fa5c423a0069bbce3d2d869c9730c8fdf550
ARG PROTOC_VERSION=25.4
ARG GRPC_VERSION=1.66.0
# This SHA is the latest known-to-work version of this binary compatibility tool
ARG GLIB_MUS_SHA=7717dd4dc26377dd9cedcc92b72ebf35f9e68a2d
ENV HOME=/home
ENV OS_ARCHITECTURE="linux-x86_64"
ENV OS_ARCH="linux-x86_64"

# Install shell script tools. Keep them in sorted order.
RUN apk update && apk add \
bash \
curl \
git \
jq \
maven \
py-pip \
python3 \
rsync \
sudo \
unzip
SHELL [ "/bin/bash", "-c" ]

# Install compatibility layer to run glibc-based programs (such as the
# grpc plugin).
# Alpine, by default, only supports musl-based binaries, and there is no public
# downloadable distrubution of the grpc that is Alpine (musl) compatible.
# This is one of the recommended approaches to ensure glibc-compatibility
# as per https://wiki.alpinelinux.org/wiki/Running_glibc_programs
WORKDIR /home
RUN git clone https://gitlab.com/manoel-linux1/GlibMus-HQ.git
WORKDIR /home/GlibMus-HQ
# We lock the tool to the latest known-to-work version
RUN git checkout "${GLIB_MUS_SHA}"
RUN chmod a+x compile-x86_64-alpine-linux.sh
RUN ./compile-x86_64-alpine-linux.sh
WORKDIR /home
RUN rm -rf /home/GlibMus-HQ
# We remove some unnecessary compatibility SOs and archive files
WORKDIR /usr/lib
RUN rm -rf LibLLVM-17* libatomic.a gcc llvm17 libexec
# We also remove unnecessary programs installed by this tool
WORKDIR /usr/bin
RUN rm -rf lto-dump

# install OS tools
RUN apt-get update && apt-get install -y \
unzip openjdk-17-jdk rsync maven jq \
&& apt-get clean

# copy source code
COPY library_generation /src

# Use utilites script to download dependencies
COPY library_generation/utils/utilities.sh /utilities.sh

# install protoc
WORKDIR /protoc
RUN source /src/utils/utilities.sh \
&& download_protoc "${PROTOC_VERSION}" "${OS_ARCHITECTURE}"
RUN source /utilities.sh && download_protoc "${PROTOC_VERSION}" "${OS_ARCH}"
# we indicate protoc is available in the container via env vars
ENV DOCKER_PROTOC_LOCATION=/protoc
ENV DOCKER_PROTOC_VERSION="${PROTOC_VERSION}"

# install grpc
WORKDIR /grpc
RUN source /src/utils/utilities.sh \
&& download_grpc_plugin "${GRPC_VERSION}" "${OS_ARCHITECTURE}"
RUN source /utilities.sh && download_grpc_plugin "${GRPC_VERSION}" "${OS_ARCH}"
# similar to protoc, we indicate grpc is available in the container via env vars
ENV DOCKER_GRPC_LOCATION="/grpc/protoc-gen-grpc-java-${GRPC_VERSION}-${OS_ARCHITECTURE}.exe"
ENV DOCKER_GRPC_LOCATION="/grpc/protoc-gen-grpc-java-${GRPC_VERSION}-${OS_ARCH}.exe"
ENV DOCKER_GRPC_VERSION="${GRPC_VERSION}"

# Remove utilities script now that we downloaded the generation tools
RUN rm /utilities.sh

# Here we transfer gapic-generator-java from the previous stage.
# Note that the destination is a well-known location that will be assumed at runtime
# We hard-code the location string to avoid making it configurable (via ARG) as
# well as to avoid it making it overridable at runtime (via ENV).
COPY --from=ggj-build "/sdk-platform-java/gapic-generator-java.jar" "${HOME}/.library_generation/gapic-generator-java.jar"
RUN chmod 755 "${HOME}/.library_generation/gapic-generator-java.jar"

# use python 3.11 (the base image has several python versions; here we define the default one)
RUN rm $(which python3)
RUN ln -s $(which python3.11) /usr/local/bin/python
RUN ln -s $(which python3.11) /usr/local/bin/python3
RUN python -m pip install --upgrade pip
# Make home folder accessible for all users since the container is usually
# launched using the -u $(user -i) argument.
# Execution is needed for gapic-generator-java.jar, whereas write permission is
# needed for writing .gitconfig and creating .gitconfig.lock (postprocessing).
# Note that this is NOT a recursive permission setting.
RUN chmod 777 "${HOME}"
RUN touch "${HOME}/.bashrc" && chmod 755 "${HOME}/.bashrc"

# install main scripts as a python package
WORKDIR /src
RUN python -m pip install -r requirements.txt
RUN python -m pip install .
# Here we transfer gapic-generator-java from the previous stage.
# Note that the destination is a well-known location that will be assumed at runtime.
# We hard-code the location string so it cannot be overriden.
COPY --from=ggj-build "/gapic-generator-java.jar" "${HOME}/.library_generation/gapic-generator-java.jar"
RUN chmod 755 "${HOME}/.library_generation"
RUN chmod 555 "${HOME}/.library_generation/gapic-generator-java.jar"

# Install nvm with node and npm
ENV NODE_VERSION 20.12.0
WORKDIR /home
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash
RUN chmod o+rx /home/.nvm
ENV NODE_PATH=/home/.nvm/versions/node/v${NODE_VERSION}/bin
ENV PATH=${PATH}:${NODE_PATH}
RUN node --version
RUN npm --version

# install the owl-bot CLI
WORKDIR /tools
RUN git clone https://github.com/googleapis/repo-automation-bots
WORKDIR /tools/repo-automation-bots/packages/owl-bot
RUN git checkout "${OWLBOT_CLI_COMMITTISH}"
RUN npm i && npm run compile && npm link
RUN owl-bot copy-code --version
RUN chmod -R o+rx ${NODE_PATH}
RUN ln -sf ${NODE_PATH}/* /usr/local/bin
# Copy the owlbot-cli binary
COPY --from=owlbot-cli-build "/owl-bot-bin" "/usr/bin/owl-bot"
RUN chmod 555 "/usr/bin/owl-bot"

# allow users to access the script folders
RUN chmod -R o+rx /src
# Copy the library_generation python packages
COPY --from=python-scripts-build "/usr/local/lib/python3.11/" "/usr/lib/python3.11/"

# set dummy git credentials for the empty commit used in postprocessing
# we use system so all users using the container will use this configuration
RUN git config --system user.email "[email protected]"
RUN git config --system user.name "Cloud Java Bot"

# allow read-write for /home and execution for binaries in /home/.nvm
RUN chmod -R a+rw /home
RUN chmod -R a+rx /home/.nvm
RUN touch "${HOME}/.gitconfig"
RUN chmod 666 "${HOME}/.gitconfig"

WORKDIR /workspace
ENTRYPOINT [ "python", "/src/cli/entry_point.py", "generate" ]
ENTRYPOINT [ "python", "-m", "library_generation.cli.entry_point", "generate" ]
34 changes: 0 additions & 34 deletions .github/workflows/verify_library_generation.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -38,40 +38,6 @@ jobs:
head_repo_url: ${{ github.event.pull_request.head.repo.html_url }}
head_repo_name: ${{ github.event.pull_request.head.repo.full_name }}
base_repo: ${{ github.repository }}
library-generation-integration-tests:
runs-on: ubuntu-22.04
needs: should-run-library-generation-tests
if: needs.should-run-library-generation-tests.outputs.should_run == 'true'
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: 3.11
- name: install pyenv
shell: bash
run: |
set -ex
curl https://pyenv.run | bash
# setup environment
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
echo "PYENV_ROOT=${PYENV_ROOT}" >> $GITHUB_ENV
echo "PATH=${PATH}" >> $GITHUB_ENV

set +ex
- name: install python dependencies
shell: bash
run: |
set -ex
pushd library_generation
pip install -r requirements.txt
pip install .
popd
- name: Run integration tests
shell: bash
run: |
set -x
python -m unittest library_generation/test/integration_tests.py
library-generation-unit-tests:
runs-on: ubuntu-22.04
needs: should-run-library-generation-tests
Expand Down
Loading
Loading