Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Update clean lost node without requiring a instanceId #503
Update clean lost node without requiring a instanceId #503
Changes from 31 commits
a91653c
c3201ac
65bd743
40a1222
b7de0f2
e96b05a
ca8e589
7f2d305
caae499
97c74c7
fe03a64
dcda478
92bd182
e47588d
4e322d7
9c840b5
f17d80e
6315666
4cd89ca
5484655
38bb7f6
fabd527
c243b28
1071692
0a15aa7
3a8030b
012cdc7
a87a569
458b0a8
deb6d70
28cc50d
da07d6f
ee35bbb
ee6ad39
c8ec0dd
fec2061
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 180 in src/main/java/com/google/jenkins/plugins/computeengine/CleanLostNodesWork.java
ci.jenkins.io / Code Coverage
Not covered lines
Check warning on line 225 in src/main/java/com/google/jenkins/plugins/computeengine/ComputeEngineCloud.java
ci.jenkins.io / Code Coverage
Not covered lines
Check warning on line 106 in src/main/java/com/google/jenkins/plugins/computeengine/client/ClientUtil.java
ci.jenkins.io / Code Coverage
Not covered lines
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.
IIUC
google-api-java-client-services
corresponds tocom.google.api.services
packages?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.
Yep that is correct. There is the Compute, and similarly the Instance classes are there, which are the same that graphite is importing as well.
So just now I tried to check a bit on the history of these classes,
Looking at the graphite library and our usages,
ComputeClient
)So currently I am thinking like,
ComputeClient
code from graphite into this repo back (as a separate PR); theComputeClientV2
should be merged into theComputeClient
.jenkinsci
, but that means, we need to manage (possibly delete) the 5 unused client classes (and associated wrappers); which then leaves the repo with only 6 classes, so may not be a good idea to maintain a whole repo for just that.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.
If we are making any major changes to the plugin (beyond what is necessary for this PR and specifically #503 (comment)), it should be to switch to whatever Java client library Google currently recommends, rather than maintaining our own stuff for no good reason.
Check warning on line 82 in src/main/java/com/google/jenkins/plugins/computeengine/client/ComputeClientV2.java
ci.jenkins.io / Code Coverage
Not covered lines