Phil Dobbin wrote:
> On 02/05/2013 05:49 PM, Karanbir Singh wrote:
>> On 02/05/2013 05:38 PM, Phil Dobbin wrote:
>>> Would you mind if I passed on this information to Michal Papis who's
>>> one of the lead developers of RVM? He's always on the lookout for
feedback
>>> &
>>
>> absolutely.
>>
>> Its not rvm thats at fault, its the build-from-source in changing
>> environs that breaks down any level of trust you can have in that binary
>> build.
>>
>> ofcourse, that isnt a problem in dev environments or when one dev is
>> looking at testing multiple ruby versions etc.
>
> OK. That's great. I will make him aware of the misgivings concerning
> production deployment.
>
Phil, let me add this: I don't know you, or what environment you work in,
but I've worked in a lot of environments, and in a large organization that
has a really professional environment, developers *NEVER* get to touch
production. They provide the software to testing, and testing provides it
to whoever the gatekeeper is for production, usually the production
admins. They move the package(s) into the right place. In addition, the
package(s) should be 100% reproducable... and back outable at a moment's
notice, should a show-stopping problem suddenly appear.
Under no circumstances should it be "we'll have to rebuild the
environment". Building in production means that every minute it takes,
that's another minute that the organization is offline, and you can
imagine management's reaction.
mark