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.

Sign up for GitHub

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

Jump to bottom

Tests - Use base image for frontend tests #190

Merged
merged 10 commits into from
Oct 23, 2019
Merged

Tests - Use base image for frontend tests #190

merged 10 commits into from
Oct 23, 2019

Commits on Jun 19, 2019

  1. Tests - Use base image for frontend tests

    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    bf343fd View commit details
    Browse the repository at this point in the history

  2. Moved the base image to ml-pipeline-test bucket. 

    The ml-pipeline-staging bucker is inaccessible by the image-builder container.
    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    5108a2e View commit details
    Browse the repository at this point in the history

  3. Moved the gcloud installation to the base image

    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    b616b04 View commit details
    Browse the repository at this point in the history

  4. Setting correct user for /src

    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    7d8d73a View commit details
    Browse the repository at this point in the history

  5. Trying to chown the directory using a different technique.

    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    d2cc06d View commit details
    Browse the repository at this point in the history

  6. GCP SDK is now in /tools/

    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    eb42c21 View commit details
    Browse the repository at this point in the history

  7. Using the official gcloud install method 

    See https://github.com/GoogleCloudPlatform/cloud-sdk-docker/blob/master/debian_slim/Dockerfile
    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    eb36096 View commit details
    Browse the repository at this point in the history

  8. Running gcloud only under the seluser user

    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    0f4a05f View commit details
    Browse the repository at this point in the history

  9. COPY --chown=seluser 

    For some reason the root, not the active user owns the data copied using COPY
    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    2d40ae6 View commit details
    Browse the repository at this point in the history

  10. No need to run apt-get update again. 

    Cleaning files before committing the layer.
Installing pip using apt-get (it's no longer in python-setuptools)
    @Ark-kun
    Ark-kun committed Jun 19, 2019
    Configuration menu
    Copy the full SHA
    84e6a89 View commit details
    Browse the repository at this point in the history