Release Eng

-
What is RE - Release Engineering
Release Management
This exactly what I want to say:
things-i-love-and-hate-about-being-a-release-enginee

Comments

Post a Comment

Popular posts from this blog

How to find the source branch of a branch in git

-
Build kept failing for one of the projects that I was trying to compile and I was told that the source branch ( meaning the original branch from where my working branch got created from) just compiles fine. I had this doubt in my mind, is the branch that I'm working on is really branched from of from the same source branch that I was told? How do I figure that out..  I know, gitk right??? But, I want to see if this is possible with git log. And it turns out , its possible with git log   git log --graph --color --decorate --oneline --all And finally I figured I was given a wrong branch to work with - *smile*  
Read more

gpg: cancelled by user

-
While signing a release tar.gz with gpg key, I got into this weird issue. After digging the internet I finally got the solution. Here is the error that I got and below is the solution to this issue.  [user@host tar]$ gpg --armor --output something.tar.gz.asc --detach-sig something- .tar.gz You need a passphrase to unlock the secret key for user: "user (somthing) " 4096-bit RSA key, ID 654321, created 2012-06-22 can't connect to `/home/user/.gnupg/S.gpg-agent': No such file or directory gpg-agent[7582]: command get_passphrase failed: Operation cancelled gpg: cancelled by user gpg: no default secret key: General error gpg: signing failed: General error Initially I thought I didn't start the gpg-agent [user@host tar]$      eval $(gpg-agent --daemon) I started the gpg-agent with the above eval [user@host tar]$ gpg --armor --output something.tar.gz.asc --detach-sig something- .tar.gz You need a passphrase to unlock the secret key for user: "
Read more

yarn nodemanager doesn't start - Caused by: EPERM: Operation not permitted

-
I was dealing with this YarnRuntimeException recently and thought it might be useful for folks who encounter this situation.   Both Namenode and Datanode is up and running and it was time to start the yarn daemons. ResourceManager came up just fine while the nodemanager stalled with the following exception.  " 2014-04-19 03:46:37,595 INFO org.apache.hadoop.service.AbstractService: Service org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService failed in state INITED; cause: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Failed to initialize LocalizationService org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Failed to initialize LocalizationService         at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.serviceInit(ResourceLocalizationService.java:234)         at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)         at org.apache.hadoop.
Read more