github-release-resource

github-release-resource copied to clipboard

I recently ran into an issue where I am trying to run my pipeline through for the very first time, and because there is no release in github yet, a...

JohnAJimenez

Create release as a pre-release, upload all files, then change to published release

2

The moment that a release is created (non pre-release) then any other concourse pipeline that watches it can trigger - except that the release might not yet be finished. If...

drnic

Non-idempotent releases with same tag should fail

3

We have the following snippet in our pipeline ``` yaml plan: - get: gpos_src passed: - gpos_centos5_release - get: bin_gpos_centos5_release passed: - gpos_centos5_release trigger: true - task: gpos_publish_tag file: gpos_src/concourse/publish_tag.yml...

xinzweb

Unusual version filtering/ sorting

5

While using this resource with the [BOSH](https://github.com/cloudfoundry/bosh) releases, old versions are getting discovered as latest. Where the `latest` release is `v263` the release being detected is `stable-3363.24`. After doing some...

sambryant4

We've had issues that the `get` of the resource caches an incorrect value for the assets. For example: ``` $ echo '{"source":{"user":"pivotal-cf-experimental","repository":"concourse-windows-worker-release"}, "version": {"tag":"3.3.3"}}' | /opt/resource/in /tmp $ cat /tmp/resource.tgz...

jtarchie

Failing with return code 413 when uploading blob

2

Error: `error running command: POST https://uploads.github.com/repos/pivotal-cf/concourse-olm/releases/6990340/assets?name=olm-0.26.0.tar.gz: 413 []` Seems to fail with Request entity too large code. But when uploading the file manually through github.com UI it seems to publish...

adi-mishra