Browse Prior Art Database

Automated/Restartable Software Build Process

IP.com Disclosure Number: IPCOM000115277D
Original Publication Date: 1995-Apr-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 73K

Publishing Venue

IBM

Related People

Heyman, JM: AUTHOR [+2]

Abstract

A program is disclosed that allows for the automating of a software build process. Along with the automating, a failure of the build process can be automatically restarted at the point of failure. This invention allows a naive user to type 'build' at the command line, answer the prompts and not have to intervene again.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Automated/Restartable Software Build Process

      A program is disclosed that allows for the automating of a
software build process.  Along with the automating, a failure of the
build process can be automatically restarted at the point of failure.
This invention allows a naive user to type 'build' at the command
line, answer the prompts and not have to intervene again.

      Using the Configuration Manager/Version Control (CMVC) system
to create a successful software build level requires issuing of
several distinct commands in a prescribed order.  A failure of any of
the commands precludes the continuation of the process and forces the
user to repeat the failed step (or go back to the start of the
process) before they can continue.  These steps are:
  o  Create the build
  o  Add defects/features to the build
  o  Check to see that all defects/features in the build are complete
  o  Commit the build
  o  Extract the build
  o  Compile and test
  o  Publish (complete)

      This disclosure describes an automated way to do each of the
steps listed above, and leaves the user without needing to know all
the intricate command line options to issue the necessary commands.
The user is prompted for the name of the build and what defects and
features are to be included.  Automatically, each of the unique
commands is executed by the automated system.

      After the user has answered the questions, a new object is
created in a lightweight object-oriented database that retains all
the user information along with the state of the last successful
command executed.

      If a build failure occurs, the user can issue a 'restart' and
provide a build name and the build will begin at the point of
failure.  State information supports this restart with no further
user input.

Following is an example of an entry in the database:
  plato022892:
    defects = "1234 21432 98709"
    features = "34562"
    status = CREATE

      Note tha...