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

Fix for is_offline? bug reporting all nodes as being offline #165

Merged
merged 5 commits into from
Apr 3, 2015
Merged

Fix for is_offline? bug reporting all nodes as being offline #165

merged 5 commits into from
Apr 3, 2015

Conversation

bsnape
Copy link
Contributor

@bsnape bsnape commented Jan 7, 2015

Hi,

This is a fix related to #164.

Please let me know what you think and if you'd like any changes to be made.

Ben

@arangamani
Copy link
Owner

Sorry for the delay in getting to this PR. I believe I used to get a string when I initially wrote that code. It is great if we get a boolean but I just wanted to make sure we shouldn't break any backwards compatibility with this change. We could either confirm if this behavior was not changed recently by Jenkins or check for both types. What do you think?

@bsnape
Copy link
Contributor Author

bsnape commented Jan 31, 2015

Hey, thanks for getting back to me. No problem regarding the wait - I ended up using the Jenkins API directly for my very simple use case.

Yeah I find it hard to believe that you overlooked this when you wrote this gem originally so I'm sure the API has changed in the interim. I was testing against a recent Jenkins version (~1.590) so I'm not sure about older versions but I could investigate it.

Like you mentioned, a more practical approach for now might be to change my PR to accept a string or boolean.

I think moving forward it might be a good idea to have more explicit templated API responses for use in your unit tests - obviously these require some upkeep to prevent API drift which might be costly in terms of time. Ultimately I suppose it depends how invested you want to be as the Jenkins API changes.

Ben

Steven Lu and others added 2 commits March 27, 2015 13:48
Restoring node property methods to its original logic, but handles both bool and string case
@bsnape
Copy link
Contributor Author

bsnape commented Mar 31, 2015

Hi @arangamani, can we consider merging @luchenghan's changes? Both strings and booleans are now supported like we discussed above (sorry I forgot to come back and finish this).

@arangamani
Copy link
Owner

@bsnape Sure!

arangamani added a commit that referenced this pull request Apr 3, 2015
Fix for is_offline? bug reporting all nodes as being offline
@arangamani arangamani merged commit 36e88f5 into arangamani:master Apr 3, 2015
@arangamani
Copy link
Owner

I'll release a new version in a day or two. Thanks all!

@dormfood
Copy link

dormfood commented Apr 3, 2015

Wonderful! Thanks @bsnape and @arangamani !

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.

3 participants