Gitlab CI PIP AWSCLI避免再次安装

如何解决Gitlab CI PIP AWSCLI避免再次安装

我正在使用GitLab CE,Runners Docker和AWS ECS进行部署。 我们创建了一个脚本,可以执行所需的工作,但是我们将开发的阶段和工作分开了。

问题在于,我们需要运行以下脚本以连接到AWS,并让我们注册容器并部署资源:

services:
  - docker:dind
before_script:
  - apk add build-base python3-dev python3 libffi-dev libressl-dev bash git gettext curl
  - apk add py3-pip
  - pip install six awscli awsebcli
  - $(aws ecr get-login --no-include-email --region "${AWS_DEFAULT_REGION}")
  - IMAGE_TAG="$(echo $CI_COMMIT_SHA | head -c 8)"

问题在于脚本每次随Job一起运行时,这不会成为问题,因为脚本避免了重新安装依赖项:

JOBS INSTALL ALL AGAIN

因此,我们需要知道是否可以避免这种行为,以便仅在每次工作都花很长时间完成此操作之后才运行脚本。

我们完整的脚本.gitlab-ci.yml:

image: docker:latest

stages:
  - build
  - tag
  - push
  - ecs
  - deploy

variables:
  REPOSITORY_URL: OUR_REPO
  REGION: OUR_REGION
  TASK_DEFINITION_NAME: task
  CLUSTER_NAME: default
  SERVICE_NAME: service

services:
  - docker:dind
before_script:
  - apk add build-base python3-dev python3 libffi-dev libressl-dev bash git gettext curl
  - apk add py3-pip
  - pip install six awscli awsebcli
  - $(aws ecr get-login --no-include-email --region "${AWS_DEFAULT_REGION}")
  - IMAGE_TAG="$(echo $CI_COMMIT_SHA | head -c 8)"

build:
  stage: build
  tags:
    - deployment
  script:
      - docker build -t $REPOSITORY_URL:latest .
  only:
      - refactor/ca

tag_image:
  stage: tag
  tags:
    - deployment
  script:
      - docker tag $REPOSITORY_URL:latest $REPOSITORY_URL:$IMAGE_TAG
  only:
      - refactor/ca

push_image:
  stage: push
  tags:
    - deployment
  script:
      - docker push $REPOSITORY_URL:$IMAGE_TAG
  only:
      - refactor/ca

task_definition:
  stage: ecs
  tags:
    - deployment
  script:
      - TASK_DEFINITION=$(aws ecs describe-task-definition --task-definition "$TASK_DEFINITION_NAME" --region "${REGION}")
      - NEW_CONTAINER_DEFINTIION=$(echo $TASK_DEFINITION | python3 $CI_PROJECT_DIR/update_task_definition_image.py $REPOSITORY_URL:$IMAGE_TAG)
      - echo "Registering new container definition..."
      - aws ecs register-task-definition --region "${REGION}" --family "${TASK_DEFINITION_NAME}" --container-definitions "${NEW_CONTAINER_DEFINTIION}"
  only:
      - refactor/ca

register_definition:
  stage: ecs
  tags:
    - deployment
  script:
      - aws ecs register-task-definition --region "${REGION}" --family "${TASK_DEFINITION_NAME}" --container-definitions "${NEW_CONTAINER_DEFINTIION}"
  only:
      - refactor/ca

deployment:
  stage: deploy
  tags:
    - deployment
  script:
      - aws ecs update-service --region "${REGION}" --cluster "${CLUSTER_NAME}" --service "${SERVICE_NAME}"  --task-definition "${TASK_DEFINITION_NAME}"
  only:
      - refactor/ca

解决方法

一种解决方法是仅为运行before_scriptaws ecs register-task-definition的阶段定义aws ecs update-service

另外,由于pushecs阶段访问IMAGE_TAG变量,将其存储在build.env工件上很方便,因此该阶段可以通过指定a依赖image_tag阶段。

image: docker:latest
    
stages:
  - build
  - tag
  - push
  - ecs
    
variables:
  REPOSITORY_URL: OUR_REPO
  REGION: OUR_REGION
  TASK_DEFINITION_NAME: task
  CLUSTER_NAME: default
  SERVICE_NAME: service
    
services:
  - docker:dind
    
build:
  stage: build
  tags:
    - deployment
  script:
    - docker build -t $REPOSITORY_URL:latest .
  only:
    - refactor/ca
    
tag_image:
  stage: tag
  tags:
    - deployment
  script:
    - IMAGE_TAG="$(echo $CI_COMMIT_SHA | head -c 8)"
    - echo "IMAGE_TAG=$IMAGE_TAG" >> build.env 
    - docker tag $REPOSITORY_URL:latest $REPOSITORY_URL:$IMAGE_TAG
  only:
    - refactor/ca
  artifacts:
    reports:
      dotenv: build.env 
    
push_image:
  stage: push
  tags:
    - deployment
  script:
    - docker push $REPOSITORY_URL:$IMAGE_TAG
  only:
    - refactor/ca
  dependencies:
    - tag_image

task_definition:
  stage: ecs
  tags:
    - deployment
  before_script:
    - apk add build-base python3-dev python3 libffi-dev libressl-dev bash git gettext curl
    - apk add py3-pip
    - pip install six awscli awsebcli
    - $(aws ecr get-login --no-include-email --region "${AWS_DEFAULT_REGION}")
  script:
    - TASK_DEFINITION=$(aws ecs describe-task-definition --task-definition "$TASK_DEFINITION_NAME" --region "${REGION}")
    - NEW_CONTAINER_DEFINTIION=$(echo $TASK_DEFINITION | python3 $CI_PROJECT_DIR/update_task_definition_image.py $REPOSITORY_URL:$IMAGE_TAG)
    - echo "Registering new container definition..."
    - aws ecs register-task-definition --region "${REGION}" --family "${TASK_DEFINITION_NAME}" --container-definitions "${NEW_CONTAINER_DEFINTIION}"
    - aws ecs update-service --region "${REGION}" --cluster "${CLUSTER_NAME}" --service "${SERVICE_NAME}"  --task-definition "${TASK_DEFINITION_NAME}"
  only:
    - refactor/ca
  dependencies:
    - tag_image
    

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-