continuous-integration

来源： https://stackoverflow.com/questions/59073731/set-default-timeout-on-github-action-pipeline

来源： https://stackoverflow.com/questions/59073731/set-default-timeout-on-github-action-pipeline

来源： https://stackoverflow.com/questions/63348442/how-do-i-run-my-docker-image-from-gitlab-ci-yml-after-building-the-image

来源： https://stackoverflow.com/questions/33011816/why-travis-ci-org-always-show-build-failing-badge

问题 Is there a way to access the current tag that has been pushed in a Github Action? In CircleCI you can access this value with the $CIRCLE_TAG variable. My Workflow yaml is being triggered by a tag like so: on: push: tags: - 'v*.*.*' And I want to use that version number as a file path later on in the workflow. I have included my final solution based on the chosen answer as another answer below: https://stackoverflow.com/a/58195087/756514 回答1: As far as I know there is no tag variable. However,

问题 Is there a way to access the current tag that has been pushed in a Github Action? In CircleCI you can access this value with the $CIRCLE_TAG variable. My Workflow yaml is being triggered by a tag like so: on: push: tags: - 'v*.*.*' And I want to use that version number as a file path later on in the workflow. I have included my final solution based on the chosen answer as another answer below: https://stackoverflow.com/a/58195087/756514 回答1: As far as I know there is no tag variable. However,

问题 I've started doing some testing using multi-stage pipelines to be able to have the pipeline as code, but I'm getting a bit confused about the usage of the pipeline considering we have Release pipeline as well, and multi-stage pipeline currently can do the release pipeline's job with gates and multiple environments, just in a code based pipeline which I would prefer. My question is when should each of them be used? 回答1: When should each of them be used? Here, very agree iberodev and Daniel's

问题 I am working on CICD and for some reason, we want to trigger a job on another job failure. In yaml file, I have specified "when: on_failure" but I am not able to find a solution to specify job name. Something like: "when: on_failure: Job_Name". Now, my 'on failure' job runs on any job failure. 回答1: If job1 is the first job which may fail and job2 is the next one which should be triggered then I'd suggest the following plan: execute job2 always with no regards if any of previous jobs failed or

问题 I am working on CICD and for some reason, we want to trigger a job on another job failure. In yaml file, I have specified "when: on_failure" but I am not able to find a solution to specify job name. Something like: "when: on_failure: Job_Name". Now, my 'on failure' job runs on any job failure. 回答1: If job1 is the first job which may fail and job2 is the next one which should be triggered then I'd suggest the following plan: execute job2 always with no regards if any of previous jobs failed or

问题 I want to run different test suites on my helm release in different (partly manual) CI jobs. How do I best execute these test suites from a CI job? Details: With a single test suite, helm test is very helpful. But how can I easily tell helm test which test suite to execute? Currently, I have only two test suites A and B and an environment variable SUITE I inject via helm install. The test job decides based on the value of SUITE which test suite to execute. But this injection is complex and I