Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PP-8729: Fix github release resource #538

Merged
merged 1 commit into from
Sep 30, 2021

Conversation

katstevens
Copy link
Contributor

Fixes the resource check error we were seeing: illegal base64 data at input byte 2

Github recently changed their Graphqa release formatting behind the scenes (see concourse/github-release-resource#107). The fix has been pushed for the Concourse github-release-resource, but this is not available in the version of Concourse that BigConcourse is currently running (v7.2.0). Given it may be 'a while' before BigConcourse reaches 7.5.0+, we can instead pin to the version of the resource repo that contains the fix, and specify this as a resource_type.

The naming of the resource type is a bit clumsy but I want it to be clear that this is a version of the resource, not the bleeding edge of the repo. Suggestions for a better name welcome.

Tested this on the pipeline already - the resource (v21 of the smoke tests code) is fetched successfully, and the release tag is pinned to 1.5.5 (click the cogs on the right of the check: smoke-tests-git-release bar).

Github recently changed their release formatting behind the scenes (see concourse/github-release-resource#107). The fix has been pushed for the Concourse github-release-resource, but this is not available in the version of Concourse that BigConcourse is currently running (v7.2.0). Given it may be 'a while' before BigConcourse reaches 7.5.0+, we can instead pin to the version of the resource repo that contains the fix, and specify this as a resource_type.

The naming of the resource type is a bit clumsy but I want it to be clear that this is a version of the resource, not the bleeding edge of the repo. Suggestions for a better name welcome.
Copy link
Contributor

@jfharden jfharden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree the naming is a bit clumsy, but it marks it as both different, and as a real released version, so I think this is good

@katstevens katstevens merged commit 766e5c0 into master Sep 30, 2021
@katstevens katstevens deleted the PP-8729-fix-github-resource-version branch September 30, 2021 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants