Skip to content
Snippets Groups Projects

Features/docker

Closed jp requested to merge jp/pleroma-fe:features/docker into develop
3 unresolved threads

Add Dockerfile.

Adds container support to gitlab-ci. Automate deployment of containers on develop/master branches.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
4 image: node:8
1 image: node:10-alpine
2
3 variables: &global_variables
4 DOCKER_DRIVER: overlay2
5 DOCKER_HOST: unix:///var/run/docker.sock
6
7 cache: &global_cache_policy
8 key: '$CI_COMMIT_SHORT_SHA'
9 policy: pull-push
10 paths:
11 - node_modules/
12 - build
5 13
6 14 stages:
7 - lint
  • HJ
    HJ @hj started a thread on the diff
  • 1 # This file is a template, and might need editing before it works on your project.
    2 # Official framework image. Look for the different tagged releases at:
    3 # https://hub.docker.com/r/library/node/tags/
    4 image: node:8
    1 image: node:10-alpine
  • Maintainer

    I really feel like docker is an overkill for it, but at least it's not running a dev server.

  • HJ
    HJ @hj started a thread on the diff
  • 72 before_script: &before-docker
    73 - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
    74 - docker pull $IMAGE_TAG_SLUG || true
    75 - export CI_JOB_TIMESTAMP=$(date --utc -Iseconds)
    76 - export CI_VCS_REF=$CI_COMMIT_SHORT_SHA
    77 allow_failure: true
    78 script:
    79 - docker build --cache-from $IMAGE_TAG_SLUG --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP -t $IMAGE_TAG -t $IMAGE_TAG_SLUG -t $IMAGE_TAG_LATEST .
    80 - docker push $IMAGE_TAG
    81 - docker push $IMAGE_TAG_SLUG
    82 - docker push $IMAGE_TAG_LATEST
    83 tags:
    84 - dind
    85 only:
    86 - develop@pleroma/pleroma-fe
    87 - /^(features|ci)\/.*/@jp/pleroma-fe
  • Maintainer

    Biggest problem - where will it be deployed? Not being able to target it to some specific instance kinda sucks for testing.

  • No development on this, purpose is unclear, so closing for now.

  • closed

  • Please register or sign in to reply
    Loading