gitlab-ci

Deploy docker private image to compute engine instance by using GCP

帅比萌擦擦* 提交于 2020-12-08 00:43:00
问题 stages: - build - docker-push - deploy cache: paths: - node_modules/ build: stage: build image: node:latest script: - yarn install - npm run build artifacts: paths: - dist/ docker: stage: docker-push image: docker:18.09.7 services: - docker:18.09.7-dind script: - docker login --username=$DOCKER_USERNAME --password=$DOCKER_PASSWORD - docker tag $DOCKER_REPOSITORY:$CI_RUNNER_ID $DOCKER_REPOSITORY:latest - docker push $DOCKER_REPOSITORY test: stage: deploy image: google/cloud-sdk:latest script:

Gitlab-CI (under gitlab.com) “system failure” starting container process

扶醉桌前 提交于 2020-12-06 08:20:28
问题 This is my 1st try to set up a basic CI workflow on gitlab.com . The concerned project is a basic static website, and I wanted to run some npm install and gulp build directly on gitlab. I created a .gitlab-ci.yml file, which is recognized and launched. But firsts implementations failed, so I came back to the more basic CI script ever, as follows: image: debian:jessie stages: - build build: stage: build script: echo "Building the app" Even in this case I encounter the same error: ERROR: Job

Gitlab ci run job on master with release tag only

情到浓时终转凉″ 提交于 2020-12-06 06:52:46
问题 I would like to build docker image on master branch only when release tag is set. This is my .gitlab.ci : build: rules: - if: '$CI_COMMIT_TAG != null && $CI_COMMIT_REF_NAME == "master"' script: - echo "Building $IMAGE:${CI_COMMIT_TAG}" This does not work, I merged to master and release tag, but the build job did not even start. I also tried with only section: build: only: - master - tags script: - echo "Building $IMAGE:${CI_COMMIT_TAG}" This run everytime, even when CI_COMMIT_TAG does not

“Error while loading shared libraries: libnss3.so” while running Gtlab CI job to perform automated testing using webdriverio

随声附和 提交于 2020-12-05 07:16:35
问题 I'm setting up the CI job for automated testing in selenium inside Gitlab CI, but the test is failing due to the issue. 019-09-27T11:03:17.404Z INFO @wdio/cli:Launcher: Run onPrepare hook /builds/shauryav/test-react-ci-cd/node_modules/chromedriver/lib/chromedriver/chromedriver: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory I have tried numbers of solutions like installing package "@wdio/cli": "^5.13.2", "webdriverio": "^5.13.2" but

“Error while loading shared libraries: libnss3.so” while running Gtlab CI job to perform automated testing using webdriverio

╄→гoц情女王★ 提交于 2020-12-05 07:16:09
问题 I'm setting up the CI job for automated testing in selenium inside Gitlab CI, but the test is failing due to the issue. 019-09-27T11:03:17.404Z INFO @wdio/cli:Launcher: Run onPrepare hook /builds/shauryav/test-react-ci-cd/node_modules/chromedriver/lib/chromedriver/chromedriver: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory I have tried numbers of solutions like installing package "@wdio/cli": "^5.13.2", "webdriverio": "^5.13.2" but

How to resolve “Function calls are not supported in decorators but 'StoreModule' was called.”

て烟熏妆下的殇ゞ 提交于 2020-12-04 05:02:21
问题 I've an angular (7) project. In my package.json, I've a command defined: { "name": "xxx", "version": "0.1.0", "scripts": { "ng": "ng", "start": "ng serve", "build": "ng build", "build-prod": "ng build --prod", "test": "ng test", "test-ci": "ng test --no-watch --no-progress --browsers=ChromeHeadlessNoSandbox", "e2e-ci": "ng e2e --protractor-config=e2e/protractor.conf.js", "deploy": "firebase deploy --token $FIREBASE_TOKEN --non-interactive", "lint": "ng lint", "e2e": "ng e2e" }, [...] } When I

How to resolve “Function calls are not supported in decorators but 'StoreModule' was called.”

和自甴很熟 提交于 2020-12-04 05:00:14
问题 I've an angular (7) project. In my package.json, I've a command defined: { "name": "xxx", "version": "0.1.0", "scripts": { "ng": "ng", "start": "ng serve", "build": "ng build", "build-prod": "ng build --prod", "test": "ng test", "test-ci": "ng test --no-watch --no-progress --browsers=ChromeHeadlessNoSandbox", "e2e-ci": "ng e2e --protractor-config=e2e/protractor.conf.js", "deploy": "firebase deploy --token $FIREBASE_TOKEN --non-interactive", "lint": "ng lint", "e2e": "ng e2e" }, [...] } When I

Gitlab:Peer's Certificate issuer is not recognized

随声附和 提交于 2020-12-02 06:53:27
问题 I get this error on a fresh install of gitlab. The message looks like: fatal: unable to access 'https://gitlab-ci- token:xxxxxxxxxxxxxxxxxxxx@gitlab.example.com/something.git/': Peer's Certificate issuer is not recognized.ERROR: Job failed: exit status 1 Any suggestions on how to fix it? 回答1: Had faced the same problem after enabling verbose mode by following command export GIT_CURL_VERBOSE=1 and found the following issue: NSS error -8179 (SEC_ERROR_UNKNOWN_ISSUER) Found this following site

GItlab CI :- How to create the multiple apk(like development, staging and production) in Android using the Gitlab-CI?

吃可爱长大的小学妹 提交于 2020-11-25 03:58:33
问题 I am able to create the single build(apk) like debug.apk using the Gitlab-CI by below approach in Gitlab. Inside my .gitlab-ci.yml , I have done this entry.Please check it once, image: jangrewe/gitlab-ci-android stages: - build before_script: - export GRADLE_USER_HOME=$(pwd)/.gradle - chmod +x ./gradlew cache: key: ${CI_PROJECT_ID} paths: - .gradle/ build: stage: build tags: - dev-ci script: - ./gradlew assembleDebug artifacts: paths: - app/build/outputs/ And I have created the docker image