concourse

问题 How can I set an email to be sent upon completion or failure of a job in Concourse? 回答1: You can use https://github.com/pivotal-cf/email-resource along with the on_failure step: https://concourse-ci.org/on-failure-step.html 来源： https://stackoverflow.com/questions/39752360/how-to-send-email-via-concourse-ci-pipeline

问题 How can I set an email to be sent upon completion or failure of a job in Concourse? 回答1: You can use https://github.com/pivotal-cf/email-resource along with the on_failure step: https://concourse-ci.org/on-failure-step.html 来源： https://stackoverflow.com/questions/39752360/how-to-send-email-via-concourse-ci-pipeline

问题 I'm moving from Jenkins to using using Concourse CI to run my Sauce labs e2e tests. Sauce labs groups tests together that have the same build number string: name: 'Chrome XS', browserName: 'chrome', tunnelIdentifier: process.env.TUNNEL_IDENTIFIER, build: process.env.JENKINS_BUILD_NUMBER, platform: 'Windows 10', shardTestFiles: true, maxInstances: 20, How can I pass the build number to my script using an environment variable as shown above. The Concourse GUI uses name #number . Is there any

问题 I'm receiving the following error when the runner is trying to retrieve a resource: checking failed - Expected to find variables: git my resource looks similar to: - name: resource-repo type: git source: uri: https://[url] branch: master tag_filter: '*' username: ((git.username)) password: ((git.password)) my values.yaml for the helm chart includes: rbac: create: false credentialManager: kubernetes: namespacePrefix: concourse (regardless, the release name is concourse) under namespace

问题 I have concourse 3.8.0 running on my workstation which is Ubuntu 17.04 and here is my pipeline definition: --- jobs: - name: job-docker-image-resource public: true plan: - get: "golang_tools_docker_image" - task: docker-image-resource config: platform: linux image_resource: type: docker-image source: {repository: busybox} run: path: echo args: [docker-image-resource] resources: - name: "golang_tools_docker_image" type: docker-image source: repository: "golang" tag: "1.9.2-alpine3.7" resource

问题 I'm following Stark & Wayne tutorial and got into a problem: Pipeline fails with hijack: Backend error: Exit status: 500, message {"Type":"","Message": " runc exec: exit status 1: exec failed: container_linux.go:247: starting container process caused \"exec format error\"\n","Handle":""} I have one git resource and one job with one task: - task: test file: resource-ci/ci/test.yml test.yml file: platform: linux image_resource: type: docker-image source: repository: busybox tag: latest inputs:

问题 I've already done a google search to find a way to setup a custom resource in concourse pipeline but the answers/documentation do not work. Can someone provide a working example of custom resource type that is pulled from a local registry and used in a build plan? For example, say I were to clone the git resource and slightly modify it and pushed it to my local registry. The git resource image would be name: localhost:5000/local_git:latest How would you be able to use this custom resource

问题 I am trying to trigger a Concourse job with a web hook on my Git server. Following this issue on Github I found an endpoint definition. So I tried curl http://10.20.30.101:8080/api/v1/pipelines/helloworld/resources/resource-tutorial/check -X POST where helloworld is the name of my pipeline and resource-tutorial is the name of the resource for which I want to trigger a check. But Concourse returns 404 page not found What am I doing wrong? Can someone point me to the correct endpoint? 回答1: For

问题 I'm trying to build a java project with gradle 3.4.1 and concourse using the vagrant concourse/lite box ( v2.7.4 ) and the docker image gradle/3.4.1-jdk8 My pipeline.yml is --- resources: - name: devoxx-talks-src type: git check_every: 1m source: uri: https://github.com/pomverte/devoxx-talks branch: concourse-ci jobs: - name: devoxx-talks-build plan: - get: devoxx-talks-src trigger: true - task: devoxx-talks-gradle file: devoxx-talks-src/ci/task-gradle.yml task-gradle.yml : --- platform: