CodePush使用问题：第一次发布更新应用，提示：Error: Deployment “Staging“ does not exist.

解决AppCenterCodePushDeployment不存在错误
原创 于 2023-05-31 01:02:59 发布 · 322 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#android #react native #react.js

在尝试使用`appcentercodepushrelease-react`命令发布React应用到Android的Staging部署时遇到错误。解决方案是首先执行带有`-dstaging`参数的命令，然后使用`appcentercodepushdeploymentlist`检查可用部署。在AppCenter平台上也确认了部署的存在。

执行命令：appcenter codepush release-react -a whenGo/test133-Android
报错：Error: Deployment “Staging” does not exist.

解决办法：

第一次要执行执行命令：appcenter codepush release-react -a whenGo/test133-Android -d staging

--------------------------

然后执行命令：appcenter codepush deployment list -a whenGo/test133-Android，就会看到如下信息了：

 登录到AppCenter上，也看到了如下内容：

 

whenwhenGo
关注
File does not exist: /user/anonymous/.staging/job_1628851608378_6064/报错问题解决
石榴姐yyds
08-16 2028
user/admin/.staging/job_1571397171638_0001/job_1571397171638_0001_1.jhist 所以为什么没有下发，这里面jhist，只是被引发的错误，它还不是根本的错误。看到上面错误，我们就可以判断，这是网络问题，然而网络无非是ip地址，防火墙，端口，hosts等。我们正常的hosts是这样的。在回头复盘想想，我们找不到jhist，跟我们的网络问题二者是很难找到关联的，所以大家在遇到问题的时候，一定多排查和思考，而不是看到一个错误，就以为是它的问题。
【k8s】path does not exist, ignoring“ path=“/etc/kubernetes/manifests“
突围
06-26 4698
参考 查看kubelet日志 [root@k2c2g3m-worker0 ~]# journalctl -f -u kubelet – Logs begin at Thu 2021-06-24 21:27:40 CST. – Jun 26 00:29:35 k2c2g3m-worker0 kubelet[29398]: E0626 00:29:35.533687 29398 file_linux.go:60] “Unable to read config path” err=“path does ..
React Native发布——使用AppCenter
lk007007sclk1的博客
03-09 3828
前言 本文基于React Native开发环境搭建，默认已搭建好XXProject的react native项目。
code-push-server 安装后提示css 和 jquery 资源文件无法正常加载问题解决记录
yourgame的专栏
04-13 255
安装启动后访问 codepush 服务器 Console 报错 指向“http://xxxxx:3000/js/jquery-3.1.1.min.js”的 <script> 加载失败。 找到code-push-server/app.js 文件，注释下面2行代码 // var helmet = require('helmet'); // app.use(helmet()); 然后重新执行 npm install 重新启动 codepush 服务器 pm2 restart.
CodePush中的staging deployment如何设置
weixin_34275734的博客
01-18 574
2019独角兽企业重金招聘Python工程师标准>>> ...
微软codepush搭建服务器,通过 CodePush API 参考对本机 SDK 作出响应 - Visual Studio App Center | Microsoft Docs...
weixin_39547596的博客
08-11 607
响应 Native Client SDK API 参考02/19/2020本文内容CodePush 插件由以下两个组件组成：可以导入/要求的 JavaScript 模块，并允许应用在运行时与服务交互 (例如，检查更新、检查有关当前正在运行的应用更新) 的元数据。本机 API (目标-C 和 Java) ，它允许响应本机应用主机使用正确的 JS 包位置自行启动。以下各节将详细介绍这些 Api 的形状...
k8s: kubectl: 总结
mzhan017的博客
11-06 1103
是和apiserver之间的链接有问题。
<app-deployment> <name>myapp</name> <target>Cluster_1</target> <module-type>war</module-type> <source-path>/deployments/myapp.war</source-path> <security-dd-model>DDOnly</security-dd-model> <staging-mode>stage</staging-mode> <!-- 模式配置点 --> </app-deployment> 标签详解
05-13
raise FileNotFoundError(f"The specified application does not exist at {app_file_path}.") for server in server_names: dest_directory = stage_dir_template.format(server) # Create destination ...
#!/usr/bin/env bash # # Copyright (c) 2023, TP-Link Corporation Limited. All rights reserved. # set -o errexit -o nounset -o pipefail DIR="$(cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd)" HAWKFIRE_CONFIG="${DIR}/.hawkfire.yaml" PROJECT_NAME=$(yq r "${HAWKFIRE_CONFIG}" metadata.name) MAVEN_PROJECT_VERSION="" MICROSERVICE_K8S_VALUES="" PROG="server.sh" USAGE=" Usage: ${PROG} <command> [action] ${PROG} build # build server ${PROG} docker # actions for docker ${PROG} helm-chart # actions for helm-chart ${PROG} deploy [environment] [region] [version_override] # deploy a microservice ${PROG} --help " DOCKER_USAGE=" Usage: ${PROG} docker make # initialize distribution and artifacts directory ${PROG} docker build [version_override] # build docker container ${PROG} docker release [version_override] # release the docker container to AWS ECR ${PROG} docker --help " HELM_CHART_USAGE=" Usage: ${PROG} helm-chart build [environment] [region] [version_override] # build and package helm chart with default values from specified environment and region ${PROG} helm-chart publish [version_override] # publish the current chart to prd-tplink-nbu chart repository ${PROG} helm-chart delete [version] # deletes the version of the chart from the repository ${PROG} helm-chart --help " function error { echo -e "$1" >&2 exit 1 } function usage-help { case $# in 0) error "${USAGE}";; 1) case $1 in docker) error "${DOCKER_USAGE}";; helm-chart) error "${HELM_CHART_USAGE}";; *) usage-help;; esac ;; esac } function get-three-digit-version-number { OLD_VERSION=$1 IFS_OLD=${IFS} IFS="." VERSION_ARR=(${OLD_VERSION}) IFS=${IFS_OLD} if [[ ${#VERSION_ARR[@]} -eq 3 ]]; then echo ${OLD_VERSION} return fi if [[ ${#VERSION_ARR[@]} -gt 4 ]]; then echo ${OLD_VERSION} return fi VERSION_FIRST=${VERSION_ARR[0]} VERSION_SECOND=${VERSION_ARR[1]} VERSION_THIRD=${VERSION_ARR[2]} VERSION_FOURTH_STR=${VERSION_ARR[3]} VERSION_FORTH_NUMBER_LENGTH=${#VERSION_FOURTH_STR} VERSION_FORTH_WORD="" if [ "$VERSION_FORTH_NUMBER_LENGTH" -gt 3 ];then VERSION_FOURTH="${VERSION_FOURTH_STR%-*}" VERSION_FORTH_WORD="-""${VERSION_FOURTH_STR#*-}" else VERSION_FOURTH=${VERSION_FOURTH_STR} fi VERSION_FORTH_NUMBER_LENGTH=${#VERSION_FOURTH} if [ "$VERSION_FORTH_NUMBER_LENGTH" -eq 1 ];then VERSION_FORTH_NUMBER_NEW="00""${VERSION_FOURTH%-*}" elif [ "$VERSION_FORTH_NUMBER_LENGTH" -eq 2 ];then VERSION_FORTH_NUMBER_NEW="0""${VERSION_FOURTH%-*}" else VERSION_FORTH_NUMBER_NEW="${VERSION_FOURTH%-*}" fi local NEW_VERSION="${VERSION_FIRST}"".""${VERSION_SECOND}"".""${VERSION_THIRD}""${VERSION_FORTH_NUMBER_NEW}""${VERSION_FORTH_WORD}" echo ${NEW_VERSION} } function get-maven-project-version { if [[ -z "${MAVEN_PROJECT_VERSION}" ]]; then MAVEN_PROJECT_VERSION=$(mvn -Psmb-nexus -Pcloud-based-build -q -Dexec.executable="echo" -Dexec.args='${project.version}' --non-recursive exec:exec) MAVEN_PROJECT_VERSION_NEW=$(get-three-digit-version-number ${MAVEN_PROJECT_VERSION}) echo "# Maven Project Version NEW: ${MAVEN_PROJECT_VERSION_NEW}" fi } function get-microservice-k8s-values { local K8S_VALUES_REPO=$(printenv SMB_K8S_VALUES_REPO) if [[ -z "${K8S_VALUES_REPO}" ]]; then error "Please configure the environment variable <SMB_K8S_VALUES_REPO>" fi MICROSERVICE_K8S_VALUES="${K8S_VALUES_REPO}/${PROJECT_NAME}" if [[ ! -d "${MICROSERVICE_K8S_VALUES}" ]]; then error "The K8S-Values of Microservice does not exist! <${MICROSERVICE_K8S_VALUES}>" fi } function server-build { echo "# Server Build" mvn -T 64 clean install -Pcloud-based-build -DskipTests=true -e get-maven-project-version docker-make } function docker { local module="docker" local IMAGE_NAME="smb/${PROJECT_NAME}" local DOCKER_REPO="746166756265.dkr.ecr.ap-southeast-1.amazonaws.com/${IMAGE_NAME}" local DOCKER_LOGIN=$(aws ecr get-login --no-include-email --region ap-southeast-1 --profile prd) case $# in 0) usage-help "${module}";; *) get-maven-project-version; case $1 in make) docker-make;; build) shift; docker-build "$@";; release) shift; docker-release "$@";; *) echo "Unknown arguments: $*"; usage-help "${module}";; esac ;; esac } function docker-dev-test { local module="docker" local IMAGE_NAME="smb/${PROJECT_NAME}" local DOCKER_REPO="242777933053.dkr.ecr.ap-southeast-1.amazonaws.com/${IMAGE_NAME}" local DOCKER_LOGIN=$(aws ecr get-login --no-include-email --region ap-southeast-1 --profile dev) local DOCKER_PRD_LOGIN=$(aws ecr get-login --no-include-email --registry-ids 746166756265 --region ap-southeast-1 --profile dev) eval "command ${DOCKER_PRD_LOGIN}" case $# in 0) usage-help "${module}";; *) get-maven-project-version; case $1 in make) docker-make;; build) shift; docker-build "$@";; release) shift; docker-release "$@";; *) echo "Unknown arguments: $*"; usage-help "${module}";; esac ;; esac } function docker-make { local ARTIFACTS_DIR="artifacts" local BUILD_DIR="dist" local PROJECT_VERSION="${MAVEN_PROJECT_VERSION}" echo "# Maven Project Version: ${PROJECT_VERSION}" echo "# Initializing distribution and artifacts directory..." if [[ -d "./${BUILD_DIR}" ]]; then rm -rf "./${BUILD_DIR}" fi if [[ -d "./${ARTIFACTS_DIR}" ]]; then rm -rf "./${ARTIFACTS_DIR}" fi mkdir -p "./${BUILD_DIR}" mkdir -p "./${ARTIFACTS_DIR}" local TARGET_DIR="${BUILD_DIR}" local TARGET_LIB_DIR="${TARGET_DIR}/lib" local DISTRIBUTION_NAME="${PROJECT_NAME}.zip" echo "# Creating distribution ..." if [[ -d "${TARGET_DIR}" ]]; then rm -rf "./${TARGET_DIR}" fi echo "# Copying libraries ..." mkdir -p "${TARGET_LIB_DIR}" cp "./target/${PROJECT_NAME}-${MAVEN_PROJECT_VERSION}.jar" "${TARGET_LIB_DIR}/server.jar" local RUNTIME_SCRIPTS_DIR="./src/main/container/deploy/scripts" if [[ -d "${RUNTIME_SCRIPTS_DIR}" ]]; then echo "# Configuring runtime scripts ..." cp -a "${RUNTIME_SCRIPTS_DIR}" "${TARGET_DIR}" chmod -R +x "./${TARGET_DIR}/scripts" fi echo "# Creating distribution archive" cd "./${BUILD_DIR}" zip -dgqr -X "../${ARTIFACTS_DIR}/${DISTRIBUTION_NAME}" * cd "${DIR}" echo "# Distribution created successfully: ${DISTRIBUTION_NAME}" export DISTRIBUTION_NAME } function docker-build { docker-make local IMAGE_NAME=${IMAGE_NAME} local DOCKER_REPO=${DOCKER_REPO} local DOCKER_LOGIN=${DOCKER_LOGIN} local VERSION_OVERRIDE=false local PROJECT_VERSION=${MAVEN_PROJECT_VERSION_NEW} if [[ "$#" -gt 0 ]] && [[ -n "$1" ]]; then PROJECT_VERSION=$(get-three-digit-version-number $1) VERSION_OVERRIDE=true fi local MULTI_PLATFORM="SINGLE" if [[ "$#" -gt 1 ]] && [[ -n "$2" ]]; then MULTI_PLATFORM=$2 fi echo "# Docker login" eval "command ${DOCKER_LOGIN}" if [[ "${MULTI_PLATFORM}" = "MULTI" ]]; then echo "多平台镜像构建..." # 多平台构建镜像 echo "${IMAGE_NAME}:${PROJECT_VERSION}" command docker buildx build -t="${IMAGE_NAME}:${PROJECT_VERSION}-amd64" -f Dockerfile --platform=linux/amd64 -o type=docker . command docker buildx build -t="${IMAGE_NAME}:${PROJECT_VERSION}-arm64" -f Dockerfile --platform=linux/arm64 -o type=docker . # 给镜像打标签 command docker tag "${IMAGE_NAME}:${PROJECT_VERSION}-amd64" "${DOCKER_REPO}:${PROJECT_VERSION}-amd64" command docker tag "${IMAGE_NAME}:${PROJECT_VERSION}-arm64" "${DOCKER_REPO}:${PROJECT_VERSION}-arm64" else # 单平台构建镜像 echo "${IMAGE_NAME}:${PROJECT_VERSION}" command docker build -t="${IMAGE_NAME}:${PROJECT_VERSION}" . # 给镜像打标签 command docker tag "${IMAGE_NAME}:${PROJECT_VERSION}" "${DOCKER_REPO}:${PROJECT_VERSION}" if [[ "${VERSION_OVERRIDE}" = false ]]; then command docker tag "${IMAGE_NAME}:${PROJECT_VERSION}" "${DOCKER_REPO}:latest" fi fi echo "# Docker Built, Repo: ${DOCKER_REPO}, Version: ${PROJECT_VERSION}" } function docker-release { local DOCKER_REPO=${DOCKER_REPO} local VERSION_OVERRIDE=false local PROJECT_VERSION=${MAVEN_PROJECT_VERSION_NEW} if [[ "$#" -gt 0 ]] && [[ -n "$1" ]]; then PROJECT_VERSION=$(get-three-digit-version-number $1) VERSION_OVERRIDE=true fi local MULTI_PLATFORM="SINGLE" if [[ "$#" -gt 1 ]] && [[ -n "$2" ]]; then MULTI_PLATFORM=$2 fi local LOCAL_IMAGE_EXISTS=$(command docker images | grep "${DOCKER_REPO}.*${PROJECT_VERSION}") if [[ -z "${LOCAL_IMAGE_EXISTS}" ]]; then error "Docker image is not available locally. You may want to build it using > ${PROG} docker build [version_override]" fi if [[ "${MULTI_PLATFORM}" = "MULTI" ]]; then echo "多平台镜像推送..." command docker push "${DOCKER_REPO}:${PROJECT_VERSION}-amd64" command docker push "${DOCKER_REPO}:${PROJECT_VERSION}-arm64" command docker manifest create "${DOCKER_REPO}:${PROJECT_VERSION}" "${DOCKER_REPO}:${PROJECT_VERSION}-amd64" "${DOCKER_REPO}:${PROJECT_VERSION}-arm64" command docker manifest inspect "${DOCKER_REPO}:${PROJECT_VERSION}" command docker manifest push "${DOCKER_REPO}:${PROJECT_VERSION}" else command docker push "${DOCKER_REPO}:${PROJECT_VERSION}" if [[ "${VERSION_OVERRIDE}" = false ]]; then command docker push "${DOCKER_REPO}:latest" fi fi echo "# Docker Released, Repo: ${DOCKER_REPO}, Version: ${PROJECT_VERSION}" } function helm-chart { local module="helm-chart" local AWS_DEFAULT_REGION="ap-southeast-1" local AWS_PROFILE="prd" local CHART_ARCHIVE_DIR="${DIR}/artifacts/helm" local CHART_BUILD_DIR="${DIR}/dist/helm" local CHART_OUTPUT_DIR="${DIR}/dist/generate" case $# in 0) usage-help "${module}";; *) get-maven-project-version; case $1 in build) shift; helm-chart-build "$@";; publish) shift; helm-chart-publish "$@";; delete) shift; helm-chart-delete "$@";; *) echo "Unknown arguments: $*"; usage-help "${module}";; esac ;; esac } function helm-chart-build { local module="${module}" local ENVIRONMENT="local" local REGION="master" local PROJECT_VERSION="${MAVEN_PROJECT_VERSION_NEW}" case $# in 0) ;; 1) PROJECT_VERSION="$1";; 2) ENVIRONMENT="$1"; REGION="$2";; 3) ENVIRONMENT="$1"; REGION="$2"; PROJECT_VERSION="$3";; *) usage-help "${module}";; esac case ${ENVIRONMENT} in local|dev|dev2|pet|uat|uat2|staging|prd) ;; *) error "Unrecognized Environment: ${ENVIRONMENT}"; usage-help "${module}";; esac case ${REGION} in master|us-east-1|eu-west-1|ap-southeast-1) ;; *) error "Unrecognized Region: ${REGION}"; usage-help "${module}";; esac echo "# Environment: ${ENVIRONMENT}, Region: ${REGION}, Version: ${PROJECT_VERSION}" local CHART_ARCHIVE_DIR=${CHART_ARCHIVE_DIR} local CHART_BUILD_DIR=${CHART_BUILD_DIR} local CHART_OUTPUT_DIR=${CHART_OUTPUT_DIR} get-microservice-k8s-values local MICROSERVICE_K8S_VALUES=${MICROSERVICE_K8S_VALUES} echo "# Initializing Helm-Chart distribution and artifacts directory..." if [[ -d "${CHART_ARCHIVE_DIR}" ]]; then rm -rf "${CHART_ARCHIVE_DIR}" fi if [[ -d "${CHART_OUTPUT_DIR}" ]]; then rm -rf "${CHART_OUTPUT_DIR}" fi if [[ -d "${CHART_BUILD_DIR}" ]]; then rm -rf "${CHART_BUILD_DIR}" fi mkdir -p "${CHART_ARCHIVE_DIR}" mkdir -p "${CHART_BUILD_DIR}" mkdir -p "${CHART_OUTPUT_DIR}" echo "# Updating Helm-Chart Version to ${PROJECT_VERSION}" cp -a "${DIR}/helm/." "${CHART_BUILD_DIR}" sed -i "s/\${version}/${PROJECT_VERSION}/g" "${CHART_BUILD_DIR}/${PROJECT_NAME}/values.yaml" sed -i "s/\${version}/${PROJECT_VERSION}/g" "${CHART_BUILD_DIR}/${PROJECT_NAME}/Chart.yaml" if [[ -d "${MICROSERVICE_K8S_VALUES}" ]]; then echo "# Rendering ${ENVIRONMENT} configs to values.yaml..." RENDER_FILE_ARG="" if [[ -d "${MICROSERVICE_K8S_VALUES}/global" ]]; then RENDER_FILE_ARG+="--from-file=${MICROSERVICE_K8S_VALUES}/global " fi if [[ -d "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/common" ]]; then RENDER_FILE_ARG+="--from-file=${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/common " fi if [[ -d "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/config" ]]; then RENDER_FILE_ARG+="--from-file=${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/config " fi kubectl create configmap "${PROJECT_NAME}-config" \ ${RENDER_FILE_ARG} \ --dry-run -o=yaml \ | yq read - data \ | yq prefix - configMap.data \ > "${CHART_BUILD_DIR}/config-map-data.yaml" yq merge -i -x "${CHART_BUILD_DIR}/${PROJECT_NAME}/values.yaml" "${CHART_BUILD_DIR}/config-map-data.yaml" if [[ -f "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/values.yaml" ]]; then yq merge -i -x "${CHART_BUILD_DIR}/${PROJECT_NAME}/values.yaml" "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/values.yaml" fi else echo "# Container configs do not exist. Skip rendering..." fi echo "# Packaging Helm-Chart ${PROJECT_NAME} ..." helm package "${CHART_BUILD_DIR}/${PROJECT_NAME}" -d "${CHART_ARCHIVE_DIR}" --version "${PROJECT_VERSION}" helm template "${CHART_BUILD_DIR}/${PROJECT_NAME}" --output-dir "${CHART_OUTPUT_DIR}" } function helm-chart-publish { local CHART_ARCHIVE_DIR=${CHART_ARCHIVE_DIR} local AWS_DEFAULT_REGION=${AWS_DEFAULT_REGION} local AWS_PROFILE=${AWS_PROFILE} local NBUCLOUD_REPO=$(helm repo list | grep 'prd-tplink-nbu.*s3://prd-tplinknbu-helm-charts-repository-aps1/charts') echo ${NBUCLOUD_REPO} if [[ -z ${NBUCLOUD_REPO} ]]; then echo "Could not publish chart. 'prd-tplink-nbu' helm repository not found." exit 0 else echo "Found chart repository: ${NBUCLOUD_REPO}" fi helm-chart-build "$@" local LATEST=$(ls -t "${CHART_ARCHIVE_DIR}" | awk '{printf("%s",$0);exit}') echo "# Publishing package ${LATEST} to Chart Repository: prd-tplink-nbu" AWS_DEFAULT_REGION=${AWS_DEFAULT_REGION} AWS_PROFILE=${AWS_PROFILE} helm s3 push "${CHART_ARCHIVE_DIR}/${LATEST}" prd-tplink-nbu echo "# Chart Published." } function helm-chart-delete { local AWS_DEFAULT_REGION=${AWS_DEFAULT_REGION} local AWS_PROFILE=${AWS_PROFILE} local CHART_VERSION=${MAVEN_PROJECT_VERSION_NEW} if [[ "$#" -gt 0 ]] && [[ -n "$1" ]]; then CHART_VERSION=$1 fi echo "# Deleting Chart ${CHART_VERSION} from repository ..." AWS_DEFAULT_REGION=${AWS_DEFAULT_REGION} AWS_PROFILE=${AWS_PROFILE} helm s3 delete "${PROJECT_NAME}" --version "${CHART_VERSION}" prd-tplink-nbu echo "# Chart Deleted." } function deploy { case $# in 2|3) get-maven-project-version;; *) usage-help;; esac local ENVIRONMENT=$1 if [[ -z "${ENVIRONMENT}" ]]; then echo "[environment] is required" exit 0 fi local REGION=$2 if [[ -z "${REGION}" ]]; then echo "[region] is required" exit 0 fi local PROJECT_VERSION=${MAVEN_PROJECT_VERSION_NEW} if [[ "$#" -gt 2 ]] && [[ -n "$3" ]]; then PROJECT_VERSION=$3 fi local KUBECONTEXT="" local EXPECTED_KUBECONTEXT="${ENVIRONMENT}.${REGION}" if [[ "${ENVIRONMENT}" = "dev2" ]]; then EXPECTED_KUBECONTEXT="dev.${REGION}"; fi KUBECONTEXT=$(kubectx -c) if [[ "${KUBECONTEXT}" != "${EXPECTED_KUBECONTEXT}" ]]; then echo "Current KubeContext does not match expected Environment and Region. Expected: ${EXPECTED_KUBECONTEXT}, Current: ${KUBECONTEXT}" exit 0 fi if [[ "${ENVIRONMENT}" = "dev" ]] || [[ "${ENVIRONMENT}" = "dev2" ]] && [[ "${PROJECT_VERSION}" != *-SNAPSHOT ]]; then echo "In DEV test, expected Project Version ends with -SNAPSHOT" exit 0 fi echo "# Server Build" mvn -T 64 clean install -Pcloud-based-build -DskipTests=true -e if [[ "${ENVIRONMENT}" = "dev" ]] || [[ "${ENVIRONMENT}" = "dev2" ]] && [[ "${PROJECT_VERSION}" = *-SNAPSHOT ]]; then docker-dev-test build "${PROJECT_VERSION}" docker-dev-test release "${PROJECT_VERSION}" helm-chart build "${ENVIRONMENT}" "${REGION}" "${PROJECT_VERSION}" local DIR=$(pwd) local NEW_RELEASE_NAME="${PROJECT_NAME}-${PROJECT_VERSION,,}" local DEV_NAMESPACE=default if [[ "${ENVIRONMENT}" = "dev2" ]]; then DEV_NAMESPACE=dev2-omada-common-data-manager; fi local NAMESPACE=$(yq read ${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/values.yaml app.namespace) local PREVIOUS_DEPLOYMENT_NAME=$(kubectl get deployment -n ${NAMESPACE} | grep "${PROJECT_NAME}" | cut -d " " -f 1) local PREVIOUS_RELEASE_NAME=$(kubectl get deployment ${PREVIOUS_DEPLOYMENT_NAME} -o yaml -n ${NAMESPACE} | yq read - 'metadata.annotations."meta.helm.sh/release-name"') helm upgrade --install "${NEW_RELEASE_NAME}" "${DIR}/artifacts/helm/${PROJECT_NAME}-${PROJECT_VERSION}.tgz" --reset-values --namespace ${NAMESPACE} \ --set image.repository="242777933053.dkr.ecr.ap-southeast-1.amazonaws.com/smb/${PROJECT_NAME}" else docker build "${PROJECT_VERSION}" docker release "${PROJECT_VERSION}" helm-chart build "${ENVIRONMENT}" "${REGION}" "${PROJECT_VERSION}" local DIR=$(pwd) helm upgrade --install "${PROJECT_NAME}" "${DIR}/artifacts/helm/${PROJECT_NAME}-${PROJECT_VERSION}.tgz" --reset-values fi if [[ -f "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/networking/service.yaml" ]]; then kubectl apply -f "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/networking/service.yaml" else echo "[service.yaml] is required" exit 0 fi if [[ -f "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/networking/istio.yaml" ]]; then kubectl apply -f "${MICROSERVICE_K8S_VALUES}/${ENVIRONMENT}/${REGION}/networking/istio.yaml" else echo "[istio.yaml] is required" exit 0 fi if [[ ! -n "${PREVIOUS_RELEASE_NAME}" ]]; then echo "# No release deployed previously in the namespace" elif [[ "${PREVIOUS_RELEASE_NAME}" != "${NEW_RELEASE_NAME}" ]]; then # Wait until the new Deployment is ready by checking the MinimumReplicasAvailable condition. local READY=$(kubectl get deployment ${NEW_RELEASE_NAME} -o yaml -n ${NAMESPACE} | yq read - 'status.conditions.(reason==MinimumReplicasAvailable).status') while [[ "$READY" != "True" ]]; do READY=$(kubectl get deployment ${NEW_RELEASE_NAME} -o yaml -n ${NAMESPACE} | yq read - 'status.conditions.(reason==MinimumReplicasAvailable).status') sleep 10 done helm uninstall "${PREVIOUS_RELEASE_NAME}" --namespace ${NAMESPACE} echo "# Uninstall previous release: ${PREVIOUS_RELEASE_NAME} successfully" exit 0 fi } case $# in 0) usage-help;; 1) case $1 in build) server-build;; docker | helm-chart | deploy) usage-help "$1";; -h | --help) echo -e "${USAGE}"; exit 0;; *) usage-help;; esac ;; *) case $1 in deploy) shift; deploy "$@";; docker) shift; docker "$@";; helm-chart) shift; helm-chart "$@";; get-version) shift; get-three-digit-version-number "$@";; *) echo "Unknown arguments: $*"; usage-help;; esac ;; esac 这个文件，我执行bash ./server.sh docker build ${SERVER_VERSION} ${MultiPlatform} 的过程是怎么样的
最新发布
10-25
command docker tag ...:${PROJECT_VERSION}-amd64 ${DOCKER_REPO}:${PROJECT_VERSION}-amd64 command docker tag ...:${PROJECT_VERSION}-arm64 ${DOCKER_REPO}:${PROJECT_VERSION}-arm64 ``` > ⚠️ 要求系统支持...
命令行工具进阶之路：argparse与click构建专业CLI的8个高级用法
!...# 1. 命令行工具的核心设计理念 命令行工具（CLI）的设计远不止参数解析，其核心在于**用户意图的精准捕捉与系统行为的清晰表达**。...例如，`git` 的子命令设计（如 `git commit`、`git push`）体现了动词+对象的自
RN软件版本更新，安装react-native-code-push后运行报错
11-26 2881
关于版本更新步骤参考 https://cloud.tencent.com/developer/article/1191478 一、参考 React Native 0.60及以上版本插件安装与配置（安卓）https://github.com/microsoft/react-native-code-push/blob/master/docs/setup-android.md 二、我的环境及安装版本 node-v14.17.6 “react-native”: “0.65.1”, “react-native-cod
react-native-code-push的集成
jhonjson的博客
10-25 703
react-native-code-push 是微软提供的一套可用于React Native的热更新服务 打开终端： 1.安装 CodePush Cli npm install -g code-push-cli 2.注册CodePush 账号 code-push register 授权完成后，CodePush会显示你的Access Key，复制输入到终端即可完成注册并登陆 ...
零客户端开发经验 React Native 热更新 CodePush 打包集成指北
weixin_34044273的博客
05-09 279
本文永久地址：github.com/rccoder/blo…，其他平台可能不是最新文章。文章评论等也希望去原文进行。 一、背景 我的毕业设计是用 React Native 写一款校园 APP，服务端采用 egg + MongoDB。 选用 React Native 一来是想借助他更加的学习巩固 React、Redux 生态系统；二来是做成 APP 而不是网站会在老师面前显得不是那么的 Low，...
使用CodePush热更新ReactNative JS代码
热门推荐
oiKen的博客
12-13 1万+
纠结了半天，不知要不要用ReactNative来开发新项目， 例如本地存储，例如webView 里面js 与native 的互动，例如地图，纠结。。。 通过查看文档，一一得到答案，还是很想用ReactNative做这个项目。 最吸引我的就是传说中的热更新。但是，，具体是怎么样才能热更新啊， 看了大部分翻译文档，没说这回事啊。。。 貌似只是在开发时候，用直接连本地服务器，可以直接reloa
code-push 测试步骤
每天进步一点点……
08-09 1929
Debug环境对应Staging模式，Release包对应Production环境   一，Staging环境下测试 1，在build.gradle中根据buildtype类型配置debug和release包对应的codepush key。  buildTypes {         release {             buildConfigField "String", ...
code-push更新失败， 提示stuck
wojiamengmeng的博客
12-19 854
我使用的是ionic，把index.html中的&lt;script src="build/polyfills.js"&gt;&lt;/script&gt;放在&lt;script src="cordova.js"&gt;&lt;/script&gt;前面
code-push 常用操作
Firen的个人博客ReactNative
10-30 1237
codepush 常命令 code-push login 登陆 code-push loout 注销 code-push access-key ls 列出登陆的token code-push access-key rm &amp;lt;accessKye&amp;gt; 删除某个 access-key code-push app add 在账号里面添加一个新的app code-push app remove 或者...
Build step io.quarkiverse.mybatis.deployment.MyBatisProcessor#generateMapperBeans threw an exception: io.quarkus.runtime.configuration.ConfigurationException: Data source <default> does not exist
09-12
当Build step `io.quarkiverse.mybatis.deployment.MyBatisProcessor#generateMapperBeans` 抛出 `io.quarkus.runtime.configuration.ConfigurationException: Data source <default> does not exist` 异常时，通常是由于Quarkus应用程序在配置数据源方面存在问题。以下是一些可能的解决方法： ### 1. 检查数据源配置 确保在 `application.properties` 或 `application.yml` 文件中正确配置了默认数据源。 #### 使用 `application.properties` ```properties quarkus.datasource.db-kind=postgresql quarkus.datasource.username=your_username quarkus.datasource.password=your_password quarkus.datasource.jdbc.url=jdbc:postgresql://localhost:5432/your_database ``` #### 使用 `application.yml` ```yaml quarkus: datasource: db-kind: postgresql username: your_username password: your_password jdbc: url: jdbc:postgresql://localhost:5432/your_database ``` ### 2. 添加数据源依赖 确保在 `pom.xml`（如果是Maven项目）或 `build.gradle`（如果是Gradle项目）中添加了正确的数据库驱动依赖。 #### Maven ```xml <dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-jdbc-postgresql</artifactId> </dependency> ``` #### Gradle ```groovy implementation 'io.quarkus:quarkus-jdbc-postgresql' ``` ### 3. 检查数据源名称 如果使用了非默认的数据源名称，确保在MyBatis配置中指定了正确的数据源名称。例如，在Mapper接口上使用 `@DataSource` 注解： ```java import javax.sql.DataSource; import org.apache.ibatis.annotations.Mapper; import io.quarkus.arc.profile.IfBuildProfile; import io.quarkus.datasource.DataSource; @Mapper @DataSource("your_custom_datasource_name") public interface YourMapper { // Mapper methods } ``` ### 4. 检查Quarkus版本兼容性 确保使用的Quarkus版本与MyBatis扩展兼容。有时，版本不兼容可能会导致配置问题。 ### 5. 清理和重建项目 有时，构建缓存可能会导致问题。尝试清理项目并重新构建： #### Maven ```sh mvn clean package ``` #### Gradle ```sh gradle clean build ```
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值