Build Environment Variables and how to manage the details

Build Environment Variables are part of the build process

Build Environment Variables are critical, detailed pieces of the over build process. If you are using OpenMake Meister to manage your build you can also manage specific Environment Variables for each step or define Global variables for all steps. In both the Configure Machine Environment and Configure Activity Environment fields of OpenMake Meister, you can define either variables and/or scripts to configure the environment that your machine or Workflow Activity work within. Global configuration settings are the default for all Workflow Activities on all machines unless you override them at this level.

Configurations set at the machine level will be the default for all Workflow Activities on that machine unless you override them at the Workflow Activities level. You can set both machine- and Workflow Activities level configurations on the Activities Tab screen.  When you select a machine, Configure Machine Environment appears; likewise, when you select a Workflow Activity listed under the machine, Configure Activity Environment appears.

So in summary, you can set Environment Variables at 3 levels, the highest level is the Global setting.  Defines the Variable for all machines and Workflow Activities.  Secondly, you can define them at the machine or Server Pool level, and all Activities running on that machine or Server Pool will use those variables.   And within an Activity, you can assign Variables to that specific  Activity.   In our 7.5 release we will be adding an Environment Library so you can store configurations in the library and assign the library name at the Global, Workflow Activity or Machine (Server Pool) level. This allows you to more easily manage the Environment Variables and reuse them across Activities and Servers.

Environment Variables are also critical in the software release process. OpenMake Release Engineer handles this detail and integrates with Ansible for infrastructure configuration management.





Ms. Ragan has had extensive experience in the development and implementation of DevOps for large organizations. She began her consulting career in 1989 on Wall Street specializing in build, testing and release management for the distributed platform. It was during her consulting experiences that Ms. Ragan recognized the lack of standardized development procedures on open systems that were common on the mainframe. In the years leading to the creation of OpenMake Software she worked with development teams in implementing a community driven standardized build and deploy process that enabled frequent builds and releases, automated around version control. Her knowledge and experience contributed to the creation of OpenMake Meister, the first commercial Build Automation solution. Ms. Ragan served on the Eclipse Foundation Board of Directors as an Add-in Provider Representative for 5 years. She has been published on numerous occasions and regularly speaks at conferences including CA World where she presented for 15 consecutive years. She holds a BS Degree in Business Administration, Computer Technology from California State University, Pomona.

Related Posts


Are micro-services and applications independent of each other?

Typically, micro-services are used for the back-end database interactions. For example, user profile micro-service would handle the Create, Retrieval, Update and Deletion of the user profile data. In theory, there should be one micro-service for Read more...


Agent-based or Agentless Release Automation Solution?

Agentless Release Automation is the new way of Managing Software Deployments Many enterprise software systems can be categorized as either “Agent-based” or “Agent-less”. This blog is going to discuss why any organization would choose to Read more...


Application Release Automation integrated with IT Engines such as Chef, Puppet and Ansible

Companies shopping for Application Release Automation solutions often confuse the functionality of IT Engines such as Ansible, Chef and Puppet as potential tools to address the ARA challenge. IT Automation engines are designed to automate Read more...