Build and Release Management
Description
A place for people interested in build and release management tools and processes to meet up, make announcements or start discussionsAnnouncements
Discussions
Wall
Primary Responsibilities:
- Coordination of developers check-ins, maintenance/enhancements of build scripts and builds execution
- Release installations and trouble shooting
- Development Integration Testing of Platform deliverables
- Servers resources mgmt for build/DIT/release installations
- Provide trouble shooting support of DIT issues
- Responsible for managing the source control and build/DIT environments
- Responsible for support and implementation of continuous integration in DIT environments
Excellent verbal and written communication skills
• Bachelor's Degree in Computer Science or related field
• Experience with ClearCase, Cruise Control, Sonar, Maven
• Experience with scripting languages (Python, Windows/DOS, Unix Shell, ant etc)
• Knowledge of Java programming language
• Experience with Windows OS, IBM WebSphere Application Server environment, Oracle DB
rachel.wiesman@citi.com
thanks folks!
Please help me any one ,developers created snapshot view and they done reserved checkout in the elements and they deleted the created view , how to access those reserved checkout elements.
please help me.......
hey I had this problem before. what I do is I login as root and unco the reserved co by using the UUID. pretty easy.
http://www-01.ibm.com/support/docview.wss?rcss=ccna0704&uid=swg21122515
In recent years ,Build and Release Management process has picked a great pace.
Today ,alomost every MNC's are following a robust build process and a seperate team is specifically assigned for this task.This team has the responsibility to coordinate with the development as well the Testing team. Deciding the change management strategy ,compilation and packaging and Release are some of the areas a build and release engineer would be required to work on mostly.
An agile build and release management strategy would offer following features:
• Provide development management with key status information and data.
• Automate everyday build and versioning tasks, and provide quick access to
file and version information.
• Support end-to-end tracking of defects and enhancements against previous
file versions.
• Be agile and robust enough to easily adapt controls to changing project
conditions.
• Make it is easy to do the right things and hard to do the wrong things.
I totally agree with that. point number 2 is the primary task. done that and the rest should be easy.
