continuous-integration

问题 Based on this answer https://stackoverflow.com/a/27908019/5156317 I have a follow up question: What makes an app different that speaks for product flavours? I am trying to compare this with my XCode setup which is as follows: Dev App that uses test backend Dev App that uses production backend Test App that uses test backend (enterprise distribution) Test App that uses production backend (enterprise distribution Live App that uses production backend (app store distribution) My thoughts for the

问题 I have successfully deployed an app using gitlab auto devops on GKE. How can I set environment variables for my app containers? Variables like PORT, DB_URL, 3rd party services etc ... 回答1: I am deploying to GKE from GitLab but without AutoDevops, but in k8s the env vars are defined in the deployment yaml. If you want to set them from GitLab and you want them to be different between deployments (production / dev etc.) then I recommend using Helm and passing --set to the helm install/upgrade

问题 I have successfully deployed an app using gitlab auto devops on GKE. How can I set environment variables for my app containers? Variables like PORT, DB_URL, 3rd party services etc ... 回答1: I am deploying to GKE from GitLab but without AutoDevops, but in k8s the env vars are defined in the deployment yaml. If you want to set them from GitLab and you want them to be different between deployments (production / dev etc.) then I recommend using Helm and passing --set to the helm install/upgrade

问题 I have successfully deployed an app using gitlab auto devops on GKE. How can I set environment variables for my app containers? Variables like PORT, DB_URL, 3rd party services etc ... 回答1: I am deploying to GKE from GitLab but without AutoDevops, but in k8s the env vars are defined in the deployment yaml. If you want to set them from GitLab and you want them to be different between deployments (production / dev etc.) then I recommend using Helm and passing --set to the helm install/upgrade

问题 Let's have something like this in role defaults/main.yml: num: 0 config: 0: a: true b: 'x' 1: a: false b: 'y' 2: a: false b: 'z' Now I send -e num=1 in playbook call, and I want to use values a and b based on this value somewhere else in the role, something like: aValue: '{{config[num].a}}' bValue: '{{config[num].b}}' How do I do that? I tried aValue: '{{config[num].a}}' but got an error: 'dict object' has no attribute u'1' aValue: '{{config["num"].a}}' but got an error: 'dict object' has no

问题 In Countinous Delivery book, it's recommended to keep everything - including CI scripts - in the version control. Actually, current CI systems like gitlab CI already follow this rule of thumb and search for CI scripts in the same codebase. On the other hand, we are versioning our codebase (and it's built artifacts) whenever it changes. And we follow semantic versioning for that; incrementing patch field for bugfixes, minor for non-breaking features, and so on... And we make sure the version

问题 Using CI/CD approach, one of the principle mentioned, here: Automate wherever possible Merging can be done two ways, based on the scenario: 1) Fast-forward merge 2) 3-way merge Does it make sense to think about automating merge conflicts? 回答1: No. A merge conflict is literally the end result of a failure to automate. Remember: Git is doing its best to ensure that it doesn't lose any data, and a merge conflict is Git telling you in its standard, paranoid fashion that it could lose data and it

问题 I am very much new on docker technology, I am getting the build error while creating the .Net Core 3.1 on Azure DevOps CI pipeline on Docker image tasks: Step 7/17 : COPY ["API2/API2.csproj", "API2/"] COPY failed: CreateFile \?\C:\ProgramData\docker\tmp\docker-builder021493529\API2\API2.csproj: The system cannot find the path specified. My default docker file is FROM mcr.microsoft.com/dotnet/core/aspnet:3.1-nanoserver-1809 AS base WORKDIR /app EXPOSE 80 EXPOSE 443 FROM mcr.microsoft.com

问题 We currently have a repo containing 24 integration/*.js files. We are successfully running Cypress tests via our TeamCity CI workflow, however, I am unable to get the tests to run in parallel. By way of configuration, we have the repo/tests wired up to an org in dashboard.cypress.io. Along with the dashboard key, we are calling Cypress in a TeamCity build step via npm run with the following configs in our package.json scripts{} : "cypress:run:qa": "cypress run -c cypress.qa.json --record -

问题 I configured my Jenkins server to only use HTTPS and enabled security. As well I don't like anybody who's not logged on to see the Dashboard (even if it would be empty). Here for I disabled the 'read' access for 'anonymous'. So far all this works exactly to my likings :) But wanting to add some build notification functionality to remote clients by e.g. using something like 'CCtray' I run into trouble. The access to the https://<SERVER>/cc.xml now only works for logged in users. Where I would