gitlab-ci-runner

问题 I am working on a Flask Application with a Postgres database. When I run nose tests locally everything works fine, but when I upload the code to GitLab this happens in my pipeline. I am using gitlab-ci . Any suggestions on how to solve this issue are welcome. $ nosetests --with-coverage --cover-package=app EEEEE ====================================================================== ERROR: Failure: TypeError (can't apply this __setattr__ to DefaultMeta object) ---------------------------------

问题 I am working on a Flask Application with a Postgres database. When I run nose tests locally everything works fine, but when I upload the code to GitLab this happens in my pipeline. I am using gitlab-ci . Any suggestions on how to solve this issue are welcome. $ nosetests --with-coverage --cover-package=app EEEEE ====================================================================== ERROR: Failure: TypeError (can't apply this __setattr__ to DefaultMeta object) ---------------------------------

问题 I'm testing gitlab ci/cd and I'm trying to build a signed APK but my script failed. What should I change or add? I add variables KEYSTORE_FILE, KEYSTORE_PASSWORD, KEY_ALIAS, KEY_PASSWORD with values. assembleRelease: stage: release script: - echo $KEYSTORE_FILE | base64 -d > my.keystore - ./gradlew assembleRelease -Pandroid.injected.signing.store.file=$(pwd)/my.keystore -Pandroid.injected.signing.store.password=$KEYSTORE_PASSWORD -Pandroid.injected.signing.key.alias=$KEY_ALIAS -Pandroid

问题 I registered the VirtualBox CI runner using gitlab-runner register and by choosing virtualbox as an executor. However, if I start the runner pipeline in Gitlab, it fails with the following error: What would be causing this error and how to fix it? Here's a link mentioned in the error message: https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading P.S: I'm using macOS 10.15.5 and the VirtualBox runs Ubuntu 20.04 LTS. 回答1: The documentation mentions: For certain executors, the

问题 I registered the VirtualBox CI runner using gitlab-runner register and by choosing virtualbox as an executor. However, if I start the runner pipeline in Gitlab, it fails with the following error: What would be causing this error and how to fix it? Here's a link mentioned in the error message: https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading P.S: I'm using macOS 10.15.5 and the VirtualBox runs Ubuntu 20.04 LTS. 回答1: The documentation mentions: For certain executors, the

问题 I'm trying to build the CI pipeline in GitLab. I'd like to ask about the docker for work in GitLab CI. from this issue : https://gitlab.com/gitlab-org/gitlab-runner/issues/4501#note_195033385 I'm follow the instruction for both ways. With TLS and not used TLS. But It's still stuck. Which in same error Cannot connect to the Docker daemon at tcp://localhost:2375/. Is the docker daemon running I've try to troubleshooting this problem. follow by below, 1) enable TLS Which used .gitlab-ci.yml and

问题 I have a job that requires more memory than the default configuration to compile a large project. I use hosted shared runners. Is there a way to specify in gitlab-ci.yml the required memory per job ? 回答1: This feature is not currently available, and the development is being tracker in https://gitlab.com/gitlab-org/gitlab-runner/issues/2902 来源： https://stackoverflow.com/questions/60114468/how-to-specify-in-gitlab-ci-yml-the-memory-for-a-job

问题 I have a job that requires more memory than the default configuration to compile a large project. I use hosted shared runners. Is there a way to specify in gitlab-ci.yml the required memory per job ? 回答1: This feature is not currently available, and the development is being tracker in https://gitlab.com/gitlab-org/gitlab-runner/issues/2902 来源： https://stackoverflow.com/questions/60114468/how-to-specify-in-gitlab-ci-yml-the-memory-for-a-job

问题 I am using Lerna to manage a multipackage repository and in my deployment job I use Lerna's publish command. For me if code is changed in a package it should always publish a new version to our Artifactory and fail the job if nothing was published, but the publish command will exit with success code (I guess it's 0 code) even when no packages where published: $ npx lerna publish from-package --yes lerna notice cli v3.13.1 lerna info ci enabled lerna notice from-package No unpublished release

问题 I am using Lerna to manage a multipackage repository and in my deployment job I use Lerna's publish command. For me if code is changed in a package it should always publish a new version to our Artifactory and fail the job if nothing was published, but the publish command will exit with success code (I guess it's 0 code) even when no packages where published: $ npx lerna publish from-package --yes lerna notice cli v3.13.1 lerna info ci enabled lerna notice from-package No unpublished release