Does anybody can tell me what are the task and responsibility of build/release engineer in QA deperatment.I know that build/release engineer is neither development person nor QA person. He is the interface between two. So please tell me what it means when he is involved in QA dept.
Anybody with the same role in this group.I am asking this because one job profile with title as test engineer but required to perform build/release task
In our company we have build masters in QA dept. It means the primary job is build process: it could everything: working with CVS, builds, smoke tests, communicating developers when build brakes, sending notifications, burning CDs, etc. depends on how much of build process is automated. Meanwhile, the person sometimes (when there is a little build-related tasks) get involved into other activities: test environment, testing itself. It depends a lot.
Ok confusion here is because most people probably have not worked on the scale where a release manager is required.
Mary has mentioned that they have 3 QA environments.... this is nothing. Some companies may have 50+ database environments and 50+ web environments. This is where the build manager will come in. Once a release stream has gone to production it is their job to update all environments to mimic production. They will move code between environments. Build managers actually fall under the category of configuration managment.
A release manager is the person in charge of getting a project into production. He will communicate with the teams (all teams, not just QA and development) and make sure they are meeting deadlines and know what needs to be done.
There is also a third related role - that of change manager (this is job I have performed at a bank). The change manager is in charge of every change that moves to production. We are not talking a few code changes, you are literally bombarded with lots of changes, that may or may not effect your area. If you have never worked for an I.T department that runs into it's thousands it really is hard to imagine just how different things are.
Here is a link that will explain the key functions of the roles:
I'll second Turbo's observations and add this one - like most HR titles, the job of "build/release engineer" can vary from company to company. And as far as who they report to? Again, every company will be different.