* 10+ years technical background and 3+ years experience as a Systems Administrator of BEA * Weblogic Server 10.3 or higher, WebLogic Platform, Weblogic portal 10.3 or higher, in a Solaris environment. * Must have knowledge of Oracle Web Logic and Weblogic...
Location: Peterborough
Rates: £250-£280 Per day
Duration: 6 months
Build & Release Engineer is urgently needed for this leading blue chip, you will be responsible to perform software configuration management activities on this project.
Build & Release Engineer will act as support personnel for change management, version control, build management, release management, software handovers in the projects. Build & Release Engineer will work for software releases and prepare consistent baselines. Build & Release Engineer will perform regular status accounting checks for compliance to agreed configuration management process. Build & Release Engineer will be the part of Configuration Management Team and will report to Configuration Manager
Key Skills/Knowledge:
* Strong knowledge of version control systems like Clearcase, Subversion, CVS etc [preferably clearcase]
* Strong Knowledge of ant Scripting, maven, Shell programming and automation
* Experience in handling daily and continuous builds and maintaining/keeping track of build and process followed for deployment
* Having Knowledge of CI engines (Hudson, Cruisecontrol, Anthill, Lunt),
* Linux/Windows Administration - Basic Level
* Good understanding of software configuration management processes.(branch, tag, merge, build)
* Should be a self-starter and good team player
* Must be able to communicate and coordinate well with both engineers and managers.
Build & Release Engineer
Location: Peterborough
Rates: £250 - £280 per day
Duration: 6 months
TEKsystems has an immediate need for a Oracle PL/SQL Developer for a longterm contract position in Charlotte, NC.Description5+ years experience. Oracle Database development & support, PL/SQL, Javaapplication deployment and weblogic management experience...
Our client, a leading financial institution, is looking for a senior level Java Developer for investment banking applications. Following established written procedures, guidelines and techniques, develops, enhances, tests, supports, maintains, and debugs...
We have 5 open positions for the following skill set:Position: Java Weblogic Portal developer Location: Charlotte, NCDuration: Long termMust Have Skills:Java 1.6 J2EE, Spring 2.5, building JSF 1.1 portlets, WebLogic Portal 10.x , WebLogic Server, Web...
* Build Manager * - Clearcase, Strong SW build experience*
50- 55 EUR p/h, 6 month rolling contract, World Leader in Mobile Telecommunications
Build Manager (ClearCase) required skills:
- *Strong ClearCase expertise as user and administrator*
- *Strong SW build experience* (compile, link, pre-processing, make, etc.) preferably for ARM tools
- Good C / C++ understanding (in order to investigate SW build failures)
- Medium Scripting experience (Perl, VBS, batch files, common Unix utilities like awk, cat, etc.) in order to understand our build environment
- Unix & Windows user experience
- Fluent english spoken and written
Build Manager (ClearCase) activity description:
- Integrate SW deliveries from development. This includes labels selection, element version selection, merging, removing rules covered by new labels.
- SW generation under Unix for different configurations. In case the build fails, the reason has to be investigated down to the element version change generating the failure.
- Generate SW metrics (warnings, lines of code, memory foot print, etc)
- run static SW verification tools
- download SW onto target HW
- Check very basic functionality of the SW on target HW
- report any found issues for further investigation
Despite the job title, there is no management activity.
Build Manager, ClearCase, Configuration, Systems Integration, Sowftware, SW
If this role fits your skill set and is of interest to you then please send an up to date CV. Build Manager (ClearCase)
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.
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.
Optimize your entire Java build and release process with ClearCaseA (R), Ant, and CruiseControl Better builds mean better software. Effective, regular build processes accelerate development and improve quality, helping you identify small problems early, before they grow complex and costly to fix. Now, there's a step-by-step guide to creating Java build processes that are right for your organization. Leading build and release management expert Kevin Lee introduces best practices for integrating and using three exceptionally powerful and recognized industry standard tools: IBM RationalA (R) ClearCase software configuration management system, the open source Ant build tool, and CruiseControl for automating continuous builds. No previous build experience is necessary: Lee thoroughly explains everything from configuring SCM environments and defining build scripts through to release packaging and deployment. He offers solutions and techniques for both Base ClearCase and Unified Change Management (UCM)-IBM Rational's best practice Software Configuration Management usage model. Key techniques are presented in real-world context, through a full-fledged three-tier application case study.Whether you are a software developer, manager, or integrator, this book will help you create better builds-and reap the benefits in efficiency, traceability, quality, and speed. Coverage includes A * Ensuring that every build you create is complete, consistent, and reproducible A * Configuring a ClearCase-controlled environment to support your development organization's build and release process A * Installing Ant and configuring it to build all of your project assets A * Integrating Ant with ClearCase and effectively using them together A * Installing CruiseControl and configuring it to schedule and automate different types of builds A * Integrating CruiseControl with ClearCase to schedule builds and automate baselines and reports A * Creating custom baseline and change request reports A * Setting up automatic notification whenever build problems arise A * Creating and packaging releasable, traceable builds with ClearCase and ClearQuestaA APrice: $49.99
