continuous-deployment

问题 I am currently working on enabling review apps in gitlab. In order to do that I need to deploy an app for every merge request/ branch. Which means I need to find open ports where I can deploy to. Usually this issue would be solved by the answers to this question. But as the Gitlab Runner is itself a docker container with docker.sock mounted, I can not simply execute a script on the host to find empty ports. So I am looking for an elegant solution. I could of course always ssh into the host to

问题 My dev ADF has pipeline triggers that are Active and set to run every hour. Using devops repos & CI/CD, I deployed these triggers from our dev to test ADF environments. The pipeline triggers were successfully created in my test environment, but they are inactive. Why are these not coming over in a 'Started' status. The ARM template shows the trigger as Started These need to be turned on automatically after deployment as I don't have rights to turn these on manually. I can't tell if this is a

问题 My dev ADF has pipeline triggers that are Active and set to run every hour. Using devops repos & CI/CD, I deployed these triggers from our dev to test ADF environments. The pipeline triggers were successfully created in my test environment, but they are inactive. Why are these not coming over in a 'Started' status. The ARM template shows the trigger as Started These need to be turned on automatically after deployment as I don't have rights to turn these on manually. I can't tell if this is a

问题 I'm having some trouble setting up a proper build chain for me and some friends. So, I forked two repos, the official ghidra and ghidra-ci. ghidra-ci is an repo which builds your fork of ghidra, when you cherry-pick some pr's so, you can add some things which aren't added to the official ghidra repo yet. So, ghidra-ci should build the ghidra repo when the ghidra repo is updated. So far I managed to get it to build when ghidra-ci itself is updatet. I used name: Ghidra Build on: [push, pull

问题 Currently I'm using Cloud Build to produce some artifacts that I need to deploy to GCE instance. I've tried to use gcloud builder for this purpose with the following args: - name: 'gcr.io/cloud-builders/gcloud' args: ['compute', 'scp', '--zone=<zone_id>', '<local_path>', '<google compute engine instance name>:<instance_path>'] and build fails with the following error: ERROR: (gcloud.compute.scp) Could not SSH into the instance. It is possible that your SSH key has not propagated to the

问题 I'm using semantic-release to automatically define the next version, update package.json and push to git . However, I'm facing a problem where it stop me from direct pushing to master . I'm using GitLab . my release.config.js module.exports = { "plugins": [ "@semantic-release/commit-analyzer", "@semantic-release/release-notes-generator", "@semantic-release/changelog", "@semantic-release/npm", ["@semantic-release/git", { "assets": ["dist/**/*.{js,css}", "docs", "package.json"], "message":

问题 Are there any technologies I can use to find all tests in a solution that are annotated as a test ( [TestMethod] , [Fact] , [Theory] ...)? Context: I am quite new to all this but attempting to iron out a continuous deployment strategy. I want to find and run all tests in a solution during/following a release process. These are not build dependent unit tests, these are part of end to end solution tests. Please let me know if my thinking is away from the right track. 回答1: So if you want a tool

问题 I have configured and scheduled only release definition on VSTS for Azure solution deployment which is having PowerShell tasks. But I want to open a bug or work item in VSTS if release/ deployment fails. Is it possible in VSTS. 回答1: Yes, it’s possible for VSTS to create a bug if a release failed. Add another PowerShell task in the end of your release definition to create a bug if the previous task fails. Detail settings for the PowerShell task as below: Select Only when a previous task has

问题 In my jenkins pipeline I am working with properties stored in file. I can read properties from file and add new items to the map using this code, but I do not understand how to persist my changes. node('hozuki-best-girl') { def propertiesPath = "${env.hozuki_properties}" def props = readProperties file: propertiesPath props['versionCode'] = 100500 } What should I do in order to persist my changes? There is no writeProperties method here https://jenkins.io/doc/pipeline/steps/pipeline-utility

问题 I'm trying to deploy my nodejs backend with codeship to elastic beanstalk. But everytime I get the following error: bcrypt@1.0.3 install /tmp/deployment/application/node_modules/bcrypt node-pre-gyp install --fallback-to-build module.js:471 throw err; ^ Error: Cannot find module '../' at Function.Module._resolveFilename (module.js:469:15) at Function.Module._load (module.js:417:25) at Module.require (module.js:497:17) at require (internal/module.js:20:19) at Object.<anonymous> (/tmp/deployment