continuous-integration

问题 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

问题 CDK Pipelines is great, specially for cross-account deployments. It enables the developers to define and customize the CI/CD pipeline for their app to their heart's content. But to remain SoC compliant, we need to make sure that necessary controls like below are validated/enforced A manual approval stage should be present before the stage that does the cross-account deployment to production Direct deployment to production bypassing dev/staging environment is not allowed Test cases (Unit tests

问题 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

问题 I am looking for an API to add build information to JIRA issues. My CI is Jenkins. I would assume it would behave in the same manner as Bamboo builds I have been searching in here: https://developer.atlassian.com/cloud/jira/platform/rest/ https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/ https://jenkinsci.github.io/jira-steps-plugin/ and I haven't found anything. Is this feature reserved for Bamboo? 回答1: I think you need to install jira plugin and that will enable you to use JIRA

问题 I am looking for an API to add build information to JIRA issues. My CI is Jenkins. I would assume it would behave in the same manner as Bamboo builds I have been searching in here: https://developer.atlassian.com/cloud/jira/platform/rest/ https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/ https://jenkinsci.github.io/jira-steps-plugin/ and I haven't found anything. Is this feature reserved for Bamboo? 回答1: I think you need to install jira plugin and that will enable you to use JIRA

问题 I'm using CircleCI for the first time and having trouble publishing to Azure. The docs don't have an example for Azure, they have an example for AWS and a note for Azure saying "To deploy to Azure, use a similar job to the above example that uses an appropriate command." If anybody has an example YAML file that would be great, if not a nudge in the right direction would be handy. So far I think I've worked out the following. I need a config that will install the Azure CLI I need to put my

问题 I'm using CircleCI for the first time and having trouble publishing to Azure. The docs don't have an example for Azure, they have an example for AWS and a note for Azure saying "To deploy to Azure, use a similar job to the above example that uses an appropriate command." If anybody has an example YAML file that would be great, if not a nudge in the right direction would be handy. So far I think I've worked out the following. I need a config that will install the Azure CLI I need to put my

问题 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":