gitlab

问题 So, in addition to GitKraken won't let me clone from a private repo on GitHub I get this screen when opening my GitLab Repo: Anyone got a solution of how to make my Repo 'non-private' or how to make GitKraken let me open this without the Pro Plan? Already tried: Generating new SSH Key in GitKraken Removing Repo, Generate new GitLab connection, Clone Repo Checked GitLab: GitKraken is an Authorized applications Git Pull via command line gives no trouble, so no permission issue ... 回答1: I had

问题 So, in addition to GitKraken won't let me clone from a private repo on GitHub I get this screen when opening my GitLab Repo: Anyone got a solution of how to make my Repo 'non-private' or how to make GitKraken let me open this without the Pro Plan? Already tried: Generating new SSH Key in GitKraken Removing Repo, Generate new GitLab connection, Clone Repo Checked GitLab: GitKraken is an Authorized applications Git Pull via command line gives no trouble, so no permission issue ... 回答1: I had

问题 So, in addition to GitKraken won't let me clone from a private repo on GitHub I get this screen when opening my GitLab Repo: Anyone got a solution of how to make my Repo 'non-private' or how to make GitKraken let me open this without the Pro Plan? Already tried: Generating new SSH Key in GitKraken Removing Repo, Generate new GitLab connection, Clone Repo Checked GitLab: GitKraken is an Authorized applications Git Pull via command line gives no trouble, so no permission issue ... 回答1: I had

问题 I have a GitLab CI build script like this: create release: stage: deploy tags: - basic only: - tags script: - GITLOG=$(echo "# Changes Log"; git log `git tag | tail -2 | head -1`..${CI_BUILD_TAG} --pretty=format:" - %s") - curl -X POST -d "private_token=$CI_BUILD_TOKEN&description=$GITLOG" "http://git.example.com/api/v3/projects/${CI_PROJECT_ID}/repository/tags/${CI_BUILD_TAG}/release" The purpose of this step is to automatically add a Changes Log from Git in the GitLab Releases section. That

问题 Which one of these lines is correct? git checkout 'another_branch' Or git checkout origin 'another_branch' Or git checkout origin/'another_branch' And what is the difference between these lines? 回答1: If another_branch already exists locally and you are not on this branch, then git checkout another_branch switches to the branch. If another_branch does not exist but origin/another_branch does, then git checkout another_branch is equivalent to git checkout -b another_branch origin/another_branch

问题 I have one runner associated with my project to avoid concurrent build. GitLab to process the complete pipeline before start a new one? concurrent is set to = 1 (config file of the runner) before_script: - echo %CI_COMMIT_SHA% - echo %CI_PROJECT_DIR% stages: - createPBLs - build - package create PBLs: stage: createPBLs script: - md "C:\HierBauen\%CI_COMMIT_SHA%\" - xcopy /y /s "C:/Bauen" "C:/HierBauen/%CI_COMMIT_SHA%" - xcopy /y /s "%CI_PROJECT_DIR%" "C:\HierBauen\%CI_COMMIT_SHA%" - cd "C:

问题 The Goal is to have everyone get a notification for every failed pipeline (at their discretion). Currently any of us can run a pipeline on this project branch, and the creator of the pipeline gets an email, no one else does. I have tried setting the notification level to watch and custom (with failed pipelines checked) at project, group and global levels without success. The help page regarding notifications says the failed pipeline checkbox for custom notification levels notifies the author

问题 I am trying to integrate Slack with GitLab. I installed a webhook in slack and copied the webhook url to GitLab's app integration. I have also enabled the Slack integration in GitLab's integration setting. However I keep getting the error: Hook executed successfully but returned HTTP 400 missing_text_or_fallback_or_attachments How can I avoid this error? 回答1: This is currently followed by gitlab-org/gitlab-foss issue 41853 It includes: Don't use the Integration part.. read further. Use Slack

问题 There is a fileA on master (say it consists of 1000 lines) We are on feature_branch , where fileA has length of say 1050 lines. On our CI pipeline, we are running coverage (it is a Python project) and it produces coverage.xml , to be used as cov input to SQ. Our SQ preview stage is as follows: - git config --global user.name "SonarQube" - git config --global user.email "sonarqube@somedomain.com" - git checkout origin/master - git merge $CI_BUILD_REF --no-commit --no-ff - sonar-scanner -Dsonar

问题 right now I'm in the middle at developing an application using Ruby and Mongo. But I got stuck when I deploy the application using gitlab-ci where it seems that mongo server doesn't start at test environment on gitlab runner. Here are my gitlab-ci.yml stages : - test - deploy services: - mongo:latest unitTest:API: image: ruby:2.6.10 stage: test cache: paths: - API/vendor/ before_script: - ruby -v - gem install bundler --no-ri --no-rdoc - bundle install --gemfile=API/Gemfile --path vendor