Share to: share facebook share twitter share wa share telegram print page

 

Build automation

Part of a series on
Software development
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Practices
Tools
Standards and bodies of knowledge
Glossaries
Outlines

Build automation is the practice of building software systems in a relatively unattended fashion. The build is configured to run with minimized or no software developer interaction and without using a developer's personal computer. Build automation encompasses the act of configuring the build system as well the resulting system itself.

Build automation encompasses both sequencing build operations via non-interactive interface tools and running builds on a shared server.[1]

Tools

Build-automation tools allow for sequencing the tasks of building software via a non-interactive interface. Existing tools such as Make can be used via custom configuration file or command-line parameters. Custom tools such as shell scripts can also be used.

Some tools, such as shell scripts, are task-oriented declarative programming. They encode sequences of commands to perform with usually minimal conditional logic.

Some tools, such as Make are product-oriented. They build a product, a.k.a. target, based on configured dependencies.[2]

Servers

A build server is a server setup to run builds. As opposed to a personal computer, a server allows for a more consistent and available build environment.

Traditionally, a build server was a local computer dedicated as a shared resource instead of used as a personal computer. Today, there are many cloud computing, software as a service (SaaS) web sites for building.

Without a build server, building generally depends on developers to use their personal computers which has many drawbacks, including but not limited to: The developers who know how to build may be on vacation. The developer's machine may have an issue that prevents building. The developer's machine may have other software installed that conflicts with building properly.

A continuous integration server is a build server that is setup to build in a relatively frequent way – often on each code commit. A build server may also be incorporated into an ARA tool or ALM tool.

Typical build triggering options include:

  • On-demand: requested by a user
  • Scheduled: such as a nightly build
  • On-commit: building on every commit to a version control system

Continuous integration and continuous delivery

Automating the build process is a required step for implementing continuous integration and continuous delivery (CI/CD) – all of which considered best practice for software development.[3][how?]

Advantages

Pluses of build automation include:[4]

  • Can save time and money in the long run
  • Enables continuous integration, delivery and testing
  • More consistent build process
  • Can optimize the build process; reducing time and redundant tasks
  • Reduces dependency on key personnel and their personal computers
  • Can automate collection of build history

See also

References

  1. ^ Ceruzzi, Paul E. (2003). A history of Modern computing. The MIT Press. ISBN 978-0-262-53203-7.
  2. ^ Clark, Mike (2004). Pragmatic Project Automation: How to Build, Deploy, and Monitor Java Apps. The Pragmatic Programmers. ISBN 978-0-9745140-3-1.
  3. ^ Bashan, Shmuel; Bellagio, David E. (2011). Work Item Management with IBM Rational ClearQuest and Jazz: A customization Guide. IBM Press. ISBN 978-0-13-700179-8.
  4. ^ "Archived copy" (PDF). Archived from the original (PDF) on 2008-11-23. Retrieved 2008-09-19.{{cite web}}: CS1 maint: archived copy as title (link)
Kembali kehalaman sebelumnya