Essential skills in order of importance:
* Team Foundation Server
* Repository Administration experience
* Basic UNIX command knowledge
* Scripting skills (Perl, Ant )
* ClearCase / Quest
Candidates with experience of designing and documenting technical processes will be viewed advantageously. Skills in TFS are a necessity.
If you do meet all the requirements, we respectfully request that you submit your Word CV for initial consideration. We aim to respond to all such candidates as quickly as possible.
Thank you.
http://www.technojobs.co.uk/job.phtml/484350Configuration Management Engineer
Job Description:
Deliver consistently high quality product builds to the Technology Team during the development life of a software product.
Job Duties (include but not limited to):
Deliver consistently high quality product builds to the Technology Team during the development life of a software product
Maintain the machines, scripts and tooling required to build the product including software version control and maintenance
Design and develop tools to increase the efficiency on all aspects of Configuration Management, Automation and Source Control
Using Clearcase, maintain a working history of all files used to create the product
Be available for engineers and internal end user questions and recommend a logical solution and/or corrective action for possible problems that may occur
Recommend avenues to improve build and/or development process
Document and maintain documentation on the current process for accuracy in an ever changing and dynamic process
Job Requirements:
Bachelor's degree in Computer Science or related field
Knowledge of Windows, Unix, TCP/IP, Perl, Batch programming, Microsoft Visual Studio, ODBC, Web Publishing and Drive Image all plus s
Must have the ability to track and maintain the status of several different projects
Strong oral and written communication skills in English
Strong analytical skills
Ability to quickly learn the build process and become a contributing member of the Build and Configuration Management team in a global software development company
Ability to analyze a process and recommend improvements
Ability to interact and maintain productivity of personnel from different backgrounds in an environment where time and customer satisfaction is critical
Hands on experience with Source Control Infrastructure (Rational Clearcase, CVS) a plus
Working experience in the R&D department of a commercial software company
Knowledge in System Administration (Windows and Unix)
Programming experience using Perl, Java, InstallShield, Batch File Programming
Jim Shemroske
Interface with customer, technology and business contacts to define requirements, customer challenges and integration requirements. Design, implement and optimize technology or process solutions to meet customer requirement for Web application build,...
The successful candidate will have a through knowledge of SCM tools such as ClearCase and Team Foundation Server complimented with excellent interpersonal skills. Any experience of designing and documenting configuration processes is highly advantageous.
Essential skills include:
* Clearcase /Quest
* Team Server Foundation
* Perl / Ant scripting skills
* Basic UNIX command knowledge
Configuration Management Analyst (Hardware/Infrastructure), Reading, Excellent salary and company benefits on offer
My highly renowned IT Services client is offering an exciting opportunity to join a dynamic and forward-thinking team, focused on delivering first-class infrastructure configuration management solutions within the defence sector. We are looking for flexible, pro-active, highly communicative candidates who enjoy working both autonomously and as part of a team, who strive for high-quality solutions in all their work.
The Role:
You will be actively involved in managing, monitoring and verifying Hardware and Infrastructure changes through the whole Release & Deployment life-cycle, for one of the largest programmes in Europe.
You will undertake verification & audit processes across the development and operational IT infrastructure phases of projects, reporting on finding, and ensure all releases meet the high quality standards expected by the team.
You will play an integral part in establishing system and component baselines within the Configuration Management tools used and will control and verify the configuration of project development and operational IT infrastructure.
The Candidate:
Suitable candidates will have a strong background working within an ITIL v3 network Configuration Management environment, with a precise working knowledge of hardware and infrastructure configuration management, using tools such as Serena Dimensions, ClearCase, PVCS, StarTeam, SourceSafe Assist, HP Service Manager etc.
Competency within audit and automated discovery, audit reporting and discrepancy handling is desirable, along with a background and knowledge of Data Centre CM, including virtual and physical servers, power usage and capacity planning.
You will be pro-active in suggesting process improvements and negotiate development of new ideas, particularly in the automation of process and development of configuration management tool-sets.
Candidates are required to have a strong competency of working to ITIL standards (ideally version 3) within large scale implementations, and will ideally possess ITIL qualifications
This role will involve some work outside core business hours, so flexibility and a previous background of early/late and weekend working is ideal.
Candidates should be willing to undergo security clearance processes.
If you are a good match then please apply with a CV to learn more about this truly fantastic opportunity to work for an expanding market leader who has an enviable reputation
Project People Ltd is acting as an Employment Agency in relation to this vacancy.
Software Confirguration Manager
My client, a leading financial services organisation has a new requirement for a Software Configuration Manager to join their busy team provding support to the development and test teams across the Europe offices.
You will be responsible for providing admistration of the ClearCase environment, which is heavily centralised on a Unix solution. The department also includes end user support and mentoring for these tools as well as others in the Rational Suite to include Rose and Requisite Pro.
Main responsibilities of the role include but are not limited to the following;
*Administration of IBM Rational ClearCase, ClearQuest, and HP Quality Centre
*Reviewing and amending Perl and Shell scripts
*Liaison with peers and other areas of the business
*Drive process enhancements and liaise with architecture group to ensure strategy is being followed and adhered to
*24x7 support on a rota basis
Skills required for the role;
Essential
*Rational Toolset
*Shell Scripting error investigation, and Unix operationg system issues
*Knowledge of Unix (Solaris and AIX)
*Perl programming
*Unix Shell scripting
*Ability to build and maintain relationships with customers
*MS Office suite
*HP Quality Centre
*Experience working in an analytical and diagnostic role
Desirable
*DB2 and Oracle
*MS Windows Server
*ITIL and/or ISO2000
*Agile
*HTML
*Maven/Ant
*Remedy call logging
If you feel you have the skills to perform this role, please send your CV in today for review.
Rational ClearQuest administration (creating VOBs, UCM projects, triggers, etc.) in a large Windows environment... Rational ClearCase administration with the ClearCase thick client and CCRC (ClearCase Remote Client)... Serve as the PM/Lead to produce...
The problem is probably in the question, and more precisely in the 'is' predicate.
SCM is about management, and shouldn't make sense unless it would be itself manageable. Thus it has to take responsibility for its presentation of reality: it cannot accept arguments of authority. Thus nothing is unless we want it and know why.
The special kind of sophisticated SCM I'd wish to achieve/evolve (trying to avoid the word 'build'), based on concepts taken from clearmake, would reverse the terms of the assertion: SCM is a by-product of Build Management.
I have already attempted to develop this idea, e.g. in: DO Management, or in: DO as CI, but here is a new bit of argument: identification makes only sense for stable artifacts. Unless the SCM/build tool provides a way to promote, save, and share derived objects, the only stable artifacts are (hand-produced, and thus slowly changing) 'sources'. But as soon as the life-time of DOs gets extended, it becomes possible to base the whole identification on them, and this makes much more sense than the traditional state-of-things.
This is because DOs have more intrinsic value, because they have a structure (based on dependency graphs), and because they may typically be run (they don't need to be painstakingly interpreted).
Marc
I guess will have to agree to disagree. But keep this in mind, I say as a CM person I typically don't do that many CM activities, it is either done by developers or testers. Now they may or may not know they are doing CM things but they are. So if you look at CM activities I would go so far as to say that Developers do about 50% of all CM activities and testers about 40% and CM folks about 10% at least that's been my experience.
Regards,
Joe
Jobfox currently requires Microsoft Internet Explorer version 5.5 or later, or Mozilla 1.0 or later, or Firefox 1.0 or later, or Apple Safari 1.2 or later to run properly.
JavaScript should be enabled, and cookies must be accepted for optimum experience.
must be at clearcase administrator level and able to perform all server administration/architecture/support/install, user support, multisite replication, merging/branching, Vobs/Views administrations, Triggers,... Application + Software Source Code Version...
You mention that determining which components (and versions of those components) should be used is the job of people. That should be true, until the people decide that there are obvious rules like "Use the latest version of the logging library approved by the security team" or "Latest build of that other related project".
Once there are rules, the mundane work of actually looking up the correct version and provisioning it into the build workspace can, and should, be handled by the build system. All mundane, repetitive, rule based work should be pushed to automation if possible to free up smart, creative, and less consistent people to work on interesting things - like defining the darn rules in the first place.
I suspect the SVN folks are used to working in a straight forward environment where clear rules made it easy to offload the work to automation. If the rules aren't defineable in your environment, the first question to ask is "why?". Is it because it's hard to formally track what's approved / released / built from various teams? You can fix that. It's possible that things are genuinely hard and human intervention is required. That tends to slow things down and I try to drive it out of the process where possible.
Keep in mind that there is a difference between a build tool like Make and Ant which are compile / package tools and larger build management frameworks which handle component provisioning, etc.
Job Description:
The Configuration Management Subject Matter Expert (SME) provides clear direction and policy for the implementation of Configuration Management processes within Air Systems. The role requires the candidate to join an established team of configuration management practioners and provide leadership at both the team and project/programme level.
The configuration management team is a flexible team focused on the delivery of a configuration management service supporting product development, release and in-service support.
Air Systems provides developed software products to the Military Aviation Industry and as such must adhere to specific process requirements to ensure the deliery of an Airworthy product. Experience and an understanding of working within an Airworthy environment is essential to this role.
Successful candidates need to be extensivly experienced in the development and implementation of configuration management policy and process within a software development environment, including the management of COTS hardware. Experience of IBM Rational configuration management tools (ClearCase and ClearQuest) would be a distinct advantage.
Day to day responsibilities:
Preparation, maintenance, update and enforcement of the Air Systems Configuration Management Plan
Definition of Air Systems Configuration Management processes and preparation of the procedure and work instruction documentation
Provision of team leadership to the Air Systems Configuration Management Team
Provision of Configuration Management expertise and direction to the Office of the Chief Engineer and all Air Systems projects
Performance of Configuration Management audits, including Functional and Physical Configuration Audits
Definition and documentation of the usage of all configuration management tools (Rational ClearCase and ClearQuest)
Essential Skills:
Extensive experience and knowledge of the definition and implementation of configuration management policy and supporting processes for both hardware, software and system type products, including the production of defining documentation (CM Plans, Procedures and Work Instructions). Specific areas within configuration management are identified as:
? Data and Document Management
? Configuration Management Planning
? Configuration Identification
? Configuration Change Management
? Configuration Status Accounting and Reporting
? Configuration Audit
Experience of implementing configuration management withini the Military Aviation Industry, including experience and knowledge of Defence Standard 05-123 and 05-57
Experience of implementing configuration management within a product development and service support environment.
Experience of leading a configuration management team within a project focused organisation
Extensive experience and ability to communicate at all levels, including the production and delivery of training for configuration management policy and process.
Experience and skills in the configuration, maintenance and support of Rational ClearCase and ClearQuest (including Base and UCM configurations)
Experience and knowledge of the implementation of complex configuration management processes within workflow tools (Rational ClearQuest)
Experience performing configuration audits of hardware, software and systems
Experience of supporting bid production and the production of configuration management resource estimates
Desirable skills:
Experience of software / hardware development including agile development practices
Experience of process training, including the production of training material and delivery.
Experience of other Configuration Management tools for application development (in addition to Rational tool suite)
Lead of a CM team in already approved DO.
Personal Skills:
• Strong interpersonal skills
• Strong communication and meeting skills
• Problem solving
• Analytical skills
• Methodical approach, pragmatic
• Ability to challenge, structured interaction
• Proactive, self motivated and self starting
• Time management
Our client is a leading Defence I.T company
It's that simple: Build Management is a part (a subset) of Software Configuration Management, not vise versa. Thus, you cannot make SCM "a build system's job". You'll have source code management (version control), build management, issue tracking etc. - combined together. You'll even have some ALM solution, but it's NOT build systems' job to handle the whole SCM.
It's like somebody say "it's the engine transporting me and my car is my engine"... absurd, isn't it? Your car has an engine, but it's not all, you got lots of other parts combined together.
P.S. And the subject defenetly has nothing to do about SVN or CVS 
Build is in essence the action taken to translate man-readable material (source) into machine-readable material (executable).
Determining the components to include, which versions of the components, which set of build instructions, and which build engine is the responsibility of someone such as the team lead or PM. Putting the package together for the build and delivering it to the Build Engineer (BE) is the role of the CM specialist. Those duties are not part of actually performing the build.
Now often the person who is assigned to the role of CM Specialist is also assigned to the role of BE. Why? Probably because it is cheaper. You don't have to hire and pay for the benefits of a separate BE.
With all that said, it may be that the build system contributes to CM activities if the system has features that normally are done by other means. For example, in the old days, versioning/revisioning was done by hand. Someone finally automated that so that a CM tool would do it as updated files were checked in. Now if you have a build system that contributes to that, then you could claim that the system contributes to CM activities. But that is a long stretch from saying that either one is a part or subset of the other.
Price:
SOLSTICE INTEGRA and GREENHAT TesterSystems Tester needed for all in-house developed systems written in JAVA/J2EE and SQL programming languages, upgrades provided by third party vendor TIBCO , documentation of all systems test scenarios, test cases, test...
