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

chore(ci): temporarily peg greptimedb to v0.4.0 to unblock CI #18838

Merged
merged 3 commits into from
Oct 13, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion scripts/integration/greptimedb/test.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,12 @@ runner:
GREPTIMEDB_HTTP: http://greptimedb:4000

matrix:
version: ['latest']
Copy link
Member

Choose a reason for hiding this comment

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

Non-blocking: Is there a stable tag?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There isn't :/ (I also was wondering).

It's a fairly new project. I want to say we might have run into something like this with it before as well.

# Temporarily pegging to the latest known stable release
# since using `latest` is failing consistently.
version: [v0.4.0]

# changes to these files/paths will invoke the integration test in CI
# expressions are evaluated using https://github.com/micromatch/picomatch
paths:
- "src/sinks/greptimedb/**"
- "scripts/integration/greptimedb/**"
Loading