continuous-integration

问题 I would like to setup the AutoDevops functionality of Gitlab CI/CD, and for that I am trying to setup the existing kubernetes cluster as my environment. However, the Gitlab requires Kubernetes Master API URL that uses to access the Kubernetes API. Kubernetes exposes several APIs, we want the "base" URL that is common to all of them, e.g., https://kubernetes.example.com rather than https://kubernetes.example.com/api/v1. we will get the API URL by running this command: kubectl cluster-info |

问题 I would like to setup the AutoDevops functionality of Gitlab CI/CD, and for that I am trying to setup the existing kubernetes cluster as my environment. However, the Gitlab requires Kubernetes Master API URL that uses to access the Kubernetes API. Kubernetes exposes several APIs, we want the "base" URL that is common to all of them, e.g., https://kubernetes.example.com rather than https://kubernetes.example.com/api/v1. we will get the API URL by running this command: kubectl cluster-info |

问题 I am trying GitHub Actions for CI with a Ruby on Rails application. My setup is with VM, not running the Ruby build in a container. This is my workflow yml. It runs all the way without errors until the step "Setup Database". name: Rails CI on: push: branches: - master pull_request: branches: - master jobs: build: runs-on: ubuntu-latest services: postgres: image: postgres:10.10 env: POSTGRES_USER: postgres POSTGRES_PASSWORD: postgres POSTGRES_DB: db_test ports: - 5432/tcp options: --health-cmd

问题 I've just started an open source Python project that I hope might be popular one day. At the moment to release a new version I have to do a few things. Test all the things. Edit mypackage.VERSION variable, which setup.py imports from __init__ Build packages and wheels with python setup.py sdist bdist_wheel Write a changelog entry to CHANGELOG file Commit my changes, echo some of that changelog Tag that commit as a release, copy that changelog entry over again. Drag in my built files so people

问题 According to the official gitlab documentation, one way to enable docker build within ci pipelines, is to make use of the dind service (in terms of gitlab-ci services). However, as it is always the case with ci jobs running on docker executors, the docker:latest image is also needed. Could someone explain: what is the difference between the docker:dind and the docker:latest images? (most importantly): why are both the service and the docker image needed (e.g. as indicated in this example,

问题 I am trying to work my way to have a ci/cd for the Api part of the application. I have 3 steps: 1: Source (git hub version2) 2: Build (currently has no commands) 3: Deploy(provider is code deploy(application)) Here is the screenshot of the events in code deploy. . While creating the Deployment Group. I chose the option of downloading the code deploy provider from the option(though it was necessary). While setting up the code pipeline chose Felt that was appropriate. This code pipeline has put

问题 When an action is set on pull_request in Github Actions, how to get the target branch? The use case is to retrieve the PR- (and hopefully, branch)-specific commits. 回答1: You can access the target branch with ${{ github.event.pull_request.base.ref }} . To know the full list of properties of the github.event object, try to run more $GITHUB_EVENT_PATH . 回答2: You can see all GitHub actions pull request event properties here. 来源： https://stackoverflow.com/questions/62331829/how-to-get-the-target

问题 When an action is set on pull_request in Github Actions, how to get the target branch? The use case is to retrieve the PR- (and hopefully, branch)-specific commits. 回答1: You can access the target branch with ${{ github.event.pull_request.base.ref }} . To know the full list of properties of the github.event object, try to run more $GITHUB_EVENT_PATH . 回答2: You can see all GitHub actions pull request event properties here. 来源： https://stackoverflow.com/questions/62331829/how-to-get-the-target

问题 I know that you can share artifacts between jobs of the same workflow... But how can I share artifacts across different workflows? 回答1: Probably not yet doable: After a workflow ends, you can download an archive of the uploaded artifacts on GitHub by finding the workflow run in the Actions tab. GitHub does not currently offer a REST API to retrieve uploaded artifacts. If you need to access artifacts from a previously run workflow, you'll need to store the artifacts somewhere. For example, you

问题 I know that you can share artifacts between jobs of the same workflow... But how can I share artifacts across different workflows? 回答1: Probably not yet doable: After a workflow ends, you can download an archive of the uploaded artifacts on GitHub by finding the workflow run in the Actions tab. GitHub does not currently offer a REST API to retrieve uploaded artifacts. If you need to access artifacts from a previously run workflow, you'll need to store the artifacts somewhere. For example, you