Skip to content

Conversation

@kylebyrne
Copy link
Contributor

So that we can kill Buildkite once and for all we need to migrate this app over to GH actions as well

This moves our buildkite pipeline to a simple github action using Github
hosted runners.
It seems like the word token is character in some versions of JSON here,
we update the message check to not rely on this
@kylebyrne kylebyrne requested a review from a team March 11, 2025 18:50
copy_example_directory("vagabond")
subject.run
message = "unexpected token at 'This is an invalid custom type."
message_pattern = /Invalid JSON: .+ - \nunexpected \w+(?:: | at )'This is an invalid custom type\.\n'/
Copy link
Contributor

Choose a reason for hiding this comment

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

I guess this is highlighting that we don't actually control this error message, its coming from the JSON parser. Should we just assert that there is an offense, and we parrot back the invalid content.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah exactly, I wasn't really sure what level of confidence we need here so just wanted to make the spec work, think we can look later if we need to lessen further but given its working now and we barely touch this I'll just leave

@kylebyrne kylebyrne merged commit e9eaac3 into main Mar 12, 2025
1 of 2 checks passed
@kylebyrne kylebyrne deleted the van-481-clean-up-buildkite branch March 12, 2025 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

3 participants