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

Automate testing of the generated gem. #1787

Conversation

junaruga
Copy link
Contributor

@junaruga junaruga commented Aug 17, 2018

This is just proposal.

Related to #1711 , #1719 (comment)

I really want to promote #1719 :)

Here is the result of my repository's Travis CI.
https://travis-ci.org/junaruga/nokogiri/builds/417464683

Oh is Travis CI not used any more?

@flavorjones
Copy link
Member

@junaruga Thank you for submitting this, and apologies for my slow reply.

I've merged #1711 and #1719, which I agree were great ideas. :-D

You're correct that we're not using Travis at the moment. I've got Concourse set up which is a bit more complex, but allows us a bit more flexibility (IMHO).

I've written up some thoughts on how I'd like to test gem installation under #1845. I'd love to hear your thoughts!

In the meantime, I'm going to close this. Thanks again for your time and attention, I really do appreciate your thoughtfulness!

@flavorjones flavorjones closed this Jan 6, 2019
@junaruga
Copy link
Contributor Author

junaruga commented Jan 9, 2019

@flavorjones alright. :)

I've written up some thoughts on how I'd like to test gem installation under #1845. I'd love to hear your thoughts!

I will look at the ticket about the concourse, when I have a time.
Thanks.

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