All geek questions in one place

How often do you update gems in an unreleased project?

I have some side projects that are either still in dev or live for friends and family. The exception ( modulecounts.com ) is pretty trivial.

At work, in a larger organization, it seems like we always make rules against updating gems too often. This will be the story that is planned for a particular sprint. It needs to be coordinated with Ops to make sure they are ready to update the production environment, etc.

All that coordination overhead has disappeared when I'm the only developer, but there is still a risk when updating gems. Perhaps these new versions will not work correctly.

So ... is it better to do this all the time? Start each dev session with "gem update" and go from there? Or should I wait while I am about to go live and make one big update, hoping that any time lost at the back end is offset by not losing time in small increments during development?

What do you do? What a happy environment?

+3
source share
2 answers

, . , . , , , gem. , , API, Facebook Twitter. API- . , , , . , :

  • gem, . . , , , .
  • gem- Gemfile. ~ > . ~ > 2.1 >= 2.1, < 2.2, , , , , , . , gem, .
  • . , gem . gem , . gem.
  • . , , , , , . , , , gem.
  • . git , , . , , , gem .

, , , , , . , , , . . Bundler , Gemfile.lock , , .

+3

, , , .

, - . . , , , , . -, , .

, , , , . , - , , , .

, , Rails . , .

0
source

Source: https://habr.com/ru/post/1791682/

More articles:


All Articles