continuous-integration

问题 I am working on Github integration with Checkmarx, which is used for code safety scan. This method works just fine for the repository hosted on github.com ( External repository ), but does not work on internal repository hosted inside our company (github.XXX.com), in fact the connection always failed (cannot pass the repository authorization on Checkmarx). I have checked both repository (internal and external) settings, they look the same to me. What is the difference between these two

问题 I'm trying to config automatically build iOS apps using Expo through Gitlab-CI . This are the commands that I am using: expo login -u expo_user -p expo_pass expo build:ios --non-interactive --apple-id my_id@domain.com --clear-dist-cert --clear-provisioning-profile --dist-p12-path "path_to_file.p12" --provisioning-profile-path "path_to_file.mobileprovision" I am already passing the respective values of this env vars: EXPO_APPLE_PASSWORD EXPO_IOS_DIST_P12_PASSWORD During the 2nd command

问题 Nowhere in Codeclimate docs written how to specify coverage formatter. But when I'm trying to send coverage to Codeclimate: ./cc-test-reporter before-build ./cc-test-reporter after-build It is failing: Error: could not find any viable formatter. available formatters: simplecov, lcov, coverage.py, clover, gocov, gcov, cobertura, jacoco I have gocov installed. Also I generated a report with goconv : gocov test -coverprofile=out And I tried to specify the report file to Codeclimate in various

问题 I have a CI-pipeline that builds a docker image for my app for every run of the pipeline (and the pipeline is triggered by a code-push to the git repository.) The docker image consists of several intermediate layers which progressively become very large in size. Most of the intermediate images are identical for each run, hence the caching mechanism of docker is significantly utilized. However, the problem is that the final couple layers are different for each run, as they result from a COPY

问题 Currently I have a batch file that sets all the environment variables needed before starting the build process. It's a must to use the same bat for setting the env variables. I tried to use EnvInject Plugin, didn't have any success. Also tried "Execute Windows batch command" before running msbuild. e.g. start mybat.bat - this didn't seem to work either How can I integrate the same bat file to set the variables? 回答1: Each Jenkins "build step" has it's own environment, I explained this in

问题 In an environment where multiple builds (release candidate packages) can be created daily but only one a month gets promoted to production, I think storing every build in Git would be wasteful but there should be a short term location that the last few builds are published. I'm currently publishing these to a shared directory. I have see IVY used for this sort of binary publishing in the past. Git seems like overkill as it would bloat due to it's model of never delete anything. Is there an

问题 In an environment where multiple builds (release candidate packages) can be created daily but only one a month gets promoted to production, I think storing every build in Git would be wasteful but there should be a short term location that the last few builds are published. I'm currently publishing these to a shared directory. I have see IVY used for this sort of binary publishing in the past. Git seems like overkill as it would bloat due to it's model of never delete anything. Is there an

问题 In an environment where multiple builds (release candidate packages) can be created daily but only one a month gets promoted to production, I think storing every build in Git would be wasteful but there should be a short term location that the last few builds are published. I'm currently publishing these to a shared directory. I have see IVY used for this sort of binary publishing in the past. Git seems like overkill as it would bloat due to it's model of never delete anything. Is there an

问题 I have a Azure DevOps pipeline with a local nuget package to a local artifact repo, and then a push to nuget.org. It however is not updating the version and remains at 1.0.0-{build_ver} in the local azure DevOps project artifacts (whilst version is stuck the build_ver of the package increments as expected), but when it tries to push to nutget it fails as its the same 1.0.0 version and ignores the 1.0.1 in the project file. Any pointers please - how can i get the version defined in the csproj

问题 I'm having a set of Terraform files and in particular one variables.tf file which sort of holds my variables like aws access key, aws access token etc. I want to now automate the resource creation on AWS using GitLab CI / CD. My plan is the following: Write a .gitlab-ci-yml file Have the terraform calls in the .gitlab-ci.yml file I know that I can have secret environment variables in GitLab, but I'm not sure how I can push those variables into my Terraform variables.tf file which looks like