Extend the build and release process to the developer's desktop
When your developer and CM processes become silo'd, software quality, team
productivity and time-to-delivery are undermined. Developers avoid check-in's
for fear they'll break the build. Unpredictable errors can surface further
downstream in the software lifecycle resulting in finger pointing, last-minute
fire fighting, and schedule slips. What's more, development progress - or the
lack of it - is directly tied to the bandwidth of the CM team to run builds,
identify errors, and provide results. And then, there's the time it takes for
compiling. Long builds stall the entire process while teams sit idle waiting
for feedback.
At the end of the day, all developers really want is the freedom and
flexibility to use the right tool, script or whatever it takes to get the job
done - and what they really need is the chance to test their code in a highly
reliable environment before nightly runs.
You can do it with IBM Rational Build Forge
IBM Rational Build Forge allows developers to access the standard build and
release processes right from their IDE. You can access project build results so
you won't have to chase down build managers to determine what happened in the
last build. Best of all, the pre-commit build feature means you can do a
pre-flight build for the code you've been working on using a separate
pre-configured build environment, right from your desktop IDE, so you can
check-in with confidence.
Eliminate the chaos of different build environments
For managers and executives, this means you can eliminate the chaos of
different build environments and workarounds on every developer's workstation.
You can empower your developers to leverage the controlled build environment
set up by your build and CM team. This also means you can forget build
bottlenecks and finger pointing. And most importantly, it means you can improve
software quality as your developers run pre-commit builds to catch any build or
dependency errors earlier in the cycle.
Build and configuration managers become proactive instead of reactive
With IDE plug-in's, build and configuration managers grant the development
team controlled access to build projects so you can reduce the amount of time
you spend manually responding to build requests and notifying developers of
their status. You spend more time proactively setting up and optimizing your
build and release projects and processes and less time reacting. Since the
environment is controlled by role-based security, developers have read access only
to the projects that you authorize - keeping your build scripts and projects
intact. Developers are no longer throwing code "over the wall"
Developer Self-Service
IBM Rational Build Forge allows developers to view and build IBM Rational
Build Forge projects within a controlled environment from directly within their
IDE. Capabilities are limited to viewing build results, initiating new builds,
and viewing the status of currently running builds. IBM Rational Build Forge
users cannot create new projects, delete projects, or alter existing project
step data. System-level permissions and access to projects are honored within
IBM Rational Build Forge, so users can only view and run projects they are
granted permission for.
Trackback(0)
Comments 
Write comment
 |
Articles 
TrackBack URI for this entry
Subscribe to this comment's feed