-
Notifications
You must be signed in to change notification settings - Fork 5
ENG-1730 Remove use of imp-tool-bootstrap #43
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
Conversation
Corresponding JIRA ticket: https://improbableio.atlassian.net/browse/ENG-1730 |
46ee7df
to
4fdde57
Compare
4fdde57
to
6c83881
Compare
@@ -1,5 +1,3 @@ | |||
pinned_tool: | |||
- tool: "imp-ci" | |||
version: "20200206.175502.ed41e47ac7" | |||
- tool: "imp-tool" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this required? IMO, we should keep tools pinned if possible. We've had our CI break in the past because of issues in newer versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The imp-tool
specifically should no longer be pinned. It is baked into agents now. We are in the process of clearing this up by also removing it from toolshare itself to some degree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So would an imp-tool
upgrade require an agent re-bake?
From the ticket, I guess
was required for our agents? |
No it was not. The issue I was having initially with the PR is that the agents are (obviously) not dockerised (because Mac) and had a lingering toolshare subscription on There is no |
No description provided.