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

[TT-1981] use chainlink cli in the keystone smoke test #16146

Open
wants to merge 85 commits into
base: develop
Choose a base branch
from

Conversation

Tofel
Copy link
Contributor

@Tofel Tofel commented Jan 30, 2025

disclaimer: idk why we see such a long commit history, it's completely out of whack. This PR adds but 4-5 new commits.

changes:

  • use chainlink-cli by default in the CI
  • call chainlink-cli using it's absolute path
  • detect os/arch before downloading chainlink-cli (it executes on host machine, so we need to support darwin/arm64 for local execution and linux/amd64 for the CI)
  • make chainlink-cli and capabilities version to use a configurable setting

@Tofel Tofel requested review from a team as code owners January 30, 2025 14:50
Base automatically changed from tt-1847-keystone-smoke-use-chainlink-deployment to develop January 30, 2025 16:44
@Tofel Tofel requested review from a team, AnieeG and kylesmartin as code owners January 30, 2025 16:44
@cl-sonarqube-production
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@Tofel Tofel enabled auto-merge January 31, 2025 15:36
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