-
Notifications
You must be signed in to change notification settings - Fork 18
Automate Ruby Code Library Release #13
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
|
@vilyapilya, I see that you introduced/added |
Remove unnecessary use of cat.
mindjiver
left a comment
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.
From the CircleCI changes I'm pretty happy, looking as nice and clean as we can get without code sharing via an Orb. For the Ruby part I think there are people more suited with stronger/better opinions.
Thanks, @mindjiver, we are gonna have a separate meeting for discussing this! |
…o initial_release_pipeline
dchai76
left a comment
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.
@smusali - as a general rule don't get hung up on Rubcop's suggestions. It's not like e.g. PEP8 for Python - there is no single standard for Ruby style and Rubocop will enforce a ton of things according to your preference - it can enforce opposite styles. That's why rubocop's yamls are typically massive - everybody customizes it. E.g. I like to enforce parens for all method calls; others prefer the opposite. There's no single "right" way in Ruby so let's go with what we feel reads best.
That's right! I will revert my codebase changes back - touching codebase isn't part of this |
|
@vilyapilya, reverted codebase changes back but removed And I used |
|
@dchai76 @vilyapilya, this |
dchai76
left a comment
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.
I'll approve this but we need to followup with the Rubocop issues. Part of it is we're not specifying the version of Rubocop to use anywhere; I'm accustomed to listing that in the Gemfile but I've not dealt with public Ruby libs before so it may not fit in. Let's discuss the specific rules in #integrations.
The purpose of this
Pull Requestis to automate the release pipeline:logdna.gemspecLICENSE.txtwith the newerLICENSERakefileand.rspecsince there is no structured example or test suitetest.rbsince it is integration testing without checking the end resultCircleCI Configby creating the following pipeline in a tagged build:test: right now, it's running onlyRuboCopbuild: it createsgemfile to be usedrelease: it creates a newGitHub Releaseand uploads thegemfile created in the second stepapprove: it is approval stage before release jobpublish: it pushes thegemfile toRubyGems