|
OpenMake Meister |
- OpenMake Meister® 7.5 – fast, Intelligent and repeatable software builds
- Meister Setup and Installation
- Contact Support
- Tutorials
- Meister Architecture
- Build and CI Procedures and Usage
- Managing Users and Groups
- Reports and Logs
- Accessing the Management Control Console
- OpenMake Meister Continuous Integration and Workflow Management
- Remote Agents for Distributed Processing
- Continuous Integration for Agile Teams
- OpenMake Meister for Intelligent Builds
- OpenMake Meister for z/OS
- 667 keyword(s) found.
- $(BUILD_DATE)
- $(BUILD_DIRECTORY)
- $(BUILD_TIME)
- $(JOB_LABEL)
- $(JOB_NAME)
- $(JOB_NUMBER)
- $(LOG_URL)
- $(MACHINE_NAME)
- $(USER_NAME)
- $AllDeps
- .Net
- .NET and "Project" Dependency Directories
- Accelerating Workflows
- Accelerating Your Builds with Meister
- access privileges
- Accessing the Management Control Console
- AccuRev
- Activating Build Avoidance
- Activating Parallelized Build Processing
- Activities Tab Screen
- adding
- Adding a New Dependency Directory List Name
- Adding Activities to a Workflow Service
- Adding and Deleting Projects
- Adding Directories to your Dependency Directory List
- Adding or Removing Users from Groups
- Adding Server Pools
- Adding Targets to Your Project
- Adding Users
- Adding Workflow Activities
- Adding Workflow Services to a Workflow
- Administrator
- Administrator Group Access Privileges
- Advanced Workflow Features
- Ant and Java Build Methods
- Ant File Locations
- Ant Javac Tasks
- Ant RMIC Tasks
- Apache Archiva Repository
- Application Developer plug-in
- Archiva Configuration
- Assign Pools
- assigning
- Assigning Remote Agents to the Server Pool
- Automatically Generating Your Java Targets
- Automating Your Compile and Link Process
- Batch Build Logs
- Bill of Materials (BoM) reporting
- bldmake
- bldmake options
- Borland Build Methods
- Borland StarTeam
- Bourne Shell
- Build and CI Procedures and Usage
- Build Audits with Build Forensics
- Build Avoidance
- Build Commands
- Build Control File Syntax
- Build Control Files
- Build Control files (BCF's)
- Build Loops
- Build Machine
- Build Management
- Build Options
- Build Rules
- Build Server as a Windows Service
- Build Service Attributes
- Build Services Options
- Build Task
- Build Types
- Build Types and Methods
- Building Targets Using ISPF
- Building z/OS Targets using the Web Client
- builds
- Builds, Activities and Workflows
- CA
- case sensitivity
- Central Logging
- Chaining Workflow Activities
- Changing the Configuration
- Changing the Status of your Workflow
- CheckStyle
- Choosing a Pre-Defined Build Service
- CleanPath()
- CleanSearchPath(@list_of_directories)
- Compilers
- Components of Workflow Management
- Configure Global Environment Variable Section
- Configure Server Pool Environment Variables Section
- Configure Tab Screen
- Configure Workflow Activity Environment Variables Section
- configuring
- Configuring Microsoft Team Build
- Configuring Remote Agents for Load Balancing
- Configuring the C and C++ Eclipse Project Properties
- Configuring the Eclipse C Development Tools (CDT) Integration
- Configuring Workflow Activities
- Configuring Your Build Environment for Parallelized Builds
- Configuring Your Build Project
- Configuring your Continuous Integration
- Configuring your Workflow to use Parallelized Mode
- Connecting to an Oracle Database
- Connecting to the PostgreSQL Database
- Contact Support
- Continuous Integration
- Continuous Integration and Workflow Loops
- Continuous Integration for Agile Teams
- Continuous Integration Tab Screen
- CopyExcludeLocal( $TargetDeps, $RelDeps, $toDir, @excludeExtensions )
- Copying Targets
- CopyLocal( $FullPathDeps, $RelDeps, $toDir )
- count()
- Crap4J
- Create and Edit Your Workflow
- Creating a Java War Target
- Creating a Workflow Service
- Creating and Managing Targets
- Creating Groups
- Creating Mainframe Targets
- Creating Microsoft .NET 2003 Targets Without the Add-in
- Creating Microsoft 6.x Visual Basic Targets Without the Add-in
- Creating Microsoft Visual Studio 6.x C/C++ Targets Without the Add-in
- Creating Microsoft Visual Studio and .Net Targets Manually
- Creating Targets for C/C++ with the Eclipse CDT
- Creating Targets for Java IDEs and Developer Tools
- Creating Targets for the Microsoft Visual Studio and .Net IDEs
- Creating the C and C++ Eclipse Project Makefile
- Creating Your Build Service
- Creating Your Custom Build Services
- Custom Access Privileges
- Custom Workflow Activity Plug-ins
- customizing
- Customizing File Type Extensions
- Customizing the Build Status Values
- Customizing z/OS Scripts for New Types
- CVS
- Dataset Names and Build Rules
- Dataset Naming Conventions
- debug or release
- debugging
- Default Administrator Group
- Default File Type Extension
- Default User Group
- Defined User Privileges Report
- defining
- Defining a Private Pre-commit Workflow
- Defining Datasets Names
- Defining Dependency Directories to Support Pre-commit Builds
- Defining J2EE Deployment Descriptor Targets
- Defining Multi-Platform or Cross Language Workflows
- Defining Nested or Reusable Workflows
- Defining Targets
- Defining Workflows for Local Continuous Integration
- Defining Workflows for Team Continuous Integration
- Defining Your Program
- Defining z/OS TGTs using ISPF
- deleting
- Deleting Users
- dependencies
- Dependency Directory Usage by Project
- Dependency Scanning with OOMLOM
- Dependency Table
- Detail Attributes
- Determining the Value of OMSUBMIT_MAX_USER_PROC
- Determining User Group Assignments
- DevOps from the Web Client
- directories
- Distributed Workload Processing
- Distributed Workload Processing and Multi-platform Workflows
- Distributing the Workload of the Workflow across multiple Server Pools
- Doxygen
- Eclipse Plug-in Dependency Directories
- Eclipse RCP
- Edit Flag Detail
- Editing Targets
- Email Notifications in Your Workflow
- Emma
- Enabling and Modifying LDAP Configurations Using ompw
- Enhancing Your Continuous Integration Builds with Meister Build Services
- Environment Variables
- Environment Variables Needed for Java Builds
- ERROR 10:
- ERROR 11:
- ERROR 12:
- ERROR 130:
- ERROR 131:
- ERROR 132:
- ERROR 133:
- ERROR 134:
- ERROR 15:
- ERROR 160:
- ERROR 161:
- ERROR 19:
- ERROR 29:
- ERROR 30:
- ERROR 37:
- ERROR 38:
- ERROR 390:
- ERROR 391:
- ERROR 392:
- ERROR 400:
- ERROR 401:
- ERROR 404:
- ERROR 405:
- ERROR 406:
- ERROR 407:
- ERROR 408:
- ERROR 40:
- ERROR 42:
- ERROR 43:
- ERROR 44:
- ERROR 45:
- ERROR 48:
- ERROR 49:
- ERROR 501:
- ERROR 50:
- ERROR 52:
- ERROR 538:
- ERROR 53:
- ERROR 54:
- ERROR 55:
- ERROR 56:
- ERROR 57:
- ERROR 58:
- ERROR 60:
- ERROR 65:
- ERROR 70:
- ERROR 71:
- ERROR 72:
- ERROR 73:
- ERROR 9:
- errors
- Errors and Warnings
- Example Label Search Paths
- Example Life Cycle Search Paths
- Exclude( $pattern, @inlist )
- Execute Build Tasks
- Execute Settings Section
- Executing Builds
- Executing Builds on z/OS
- Executing on Demand Workflows from the Management Console
- Executing Pre-commit Builds Outside of Your IDE
- Executing Workflows on a UNIX Platform
- Executing your Build Definition
- Executing Your First Meister Build
- ExitScript( $RC, @doomedFiles )
- Features of Meister for z/OS
- file extensions
- Filter Workflows
- Filtering and Organizing Your Workflows
- FindBugs
- FindFlag( $flagString, @possibleFlags )
- First Found Dependency
- FirstFoundInPath
- Footprinting
- Footprinting - Embedding the DNA
- GenerateBillofMat( $BillofMat, $BillofMatRpt, $TargetFile )
- Generated Build Control Files
- GenerateFootPrint($FootPrint,$TargetFile,$FPSource,$FPObject,$CompilerFound,$FPCompilerArguments )
- Generating Build Scripts
- Generating Microsoft 2005, 2008 and 2010 Targets using the Add-In
- Generating Microsoft Visual Studio 2005 Targets
- Generating Microsoft Visual Studio 2008 Targets
- Generating Microsoft Visual Studio 2010 Targets
- Generating Targets using omNet
- get()
- get(), getDP()
- getAbsolute()
- getAbsolute, getAbsolute($anchor_dir)
- getAbsoluteList, getAbsoluteList($anchor_dir)
- getAnchor()
- GetAnt
- GetAntIncludeXML ( @items )
- getBuildTaskFiles( $BuildTask, $OptionGroup, $all)
- getBuildTaskOption( $option_name, $build_task, $option_group)
- getBuildTaskOptions( $build_task, $option_group)
- getBuildTasks
- GetClasses ( $TargetDeps )
- GetClassPath ( $TargetDeps )
- GetCompiler, get_compiler
- getDPF()
- getDPFE(), get()
- getEscaped()
- getEscapedList()
- getEscapedPath()
- getEscapedQuoted()
- getEscapedQuotedList(), getQuotedEscapedList()
- GetExcludes( $Defines )
- getExt( @ExtensionList )
- getExt(), getE()
- getExtension()
- getExtList( @ExtensionList)
- getExtQuoted( @ExtensionList )
- getExtQuotedList
- getF()
- getFile(), getFE()
- GetFlag( $flagString, @possibleFlags );
- getJavacEscaped(), getJEscaped()
- getJEscaped()
- More...
$AllDeps
Gets resolves to a list of all the dependencies throughout the whole dependency tree. This variable is space separated string.
$AllTargets
All Targets listed in the Build Control File. This variable is a space separated string.
$BillOfMaterialFile
Fully qualified name of the Build Audit Report dataset.
$BillOfMaterialRpt
Get resolved to the name of the Build Audit Report specified on the OOMLOM command line.
$BuildControlFile
Fully qualified dataset name of the Build Control File.
$BuildTask
Build Task Name
$BuildType
Gets resolved to the Build Type of the current Target.
$CFG
Contains DEBUG or RELEASE based upon the type of build being performed.
$CmdLineParmTargets
Targets listed on the command line to be built.
$CurrentStep
Gets resolved to the current number of the "Final" Targets being built. Intermediate Targets, such as objs, are not considered a "step".
$CurrentWorkingDirectory
Gets resolved to the High Level Qualifier entered using the ISPF panel.
$DebugFlags_<Target Name>_<Build Task>_BuildTaskOptions<Dependency Name>
Special characters in the target and dependency name are replaced with _ to create the variable name. The variable will contain the debug compile flags.
$DeleteLog
Delete the XML log (yes/no)
$DependencyParent<Dependency Name>
Special characters in the dependency name are replaced with _ to create the variable name. The variable will contain a list of the dependencies parent names.
$DependencyVersion<Dependecy Name>
Special characters in the dependency name are replaced with _ to create the variable name. The variable will contain the versioning information.
$ENV.<Env Name>
Each environment variable can be referenced by using $ENV.<Env Name>.
$<Env Name>
Each environment variable can be referenced by using $<Env Name>.
$FinalTarget
Gets resolved to the Final Target Name as listed in the generated build control file.
$FootPrintFile
Gets resolved to the dataset that contains the Foot Printing information.
$IntDir
Gets resolved to the Intermediate Directory location determined by the Target Intermediate Directory.
$JobDateTime
Gets resolved to the value Build Job Date Time. This value is set by -ld parameter specified on the command line.
$JobMachineName
Gets resolved to the Build Job Machine. This value is set by -lm parameter specified on the command line.
$JobName
Gets resolved to the Build Job name passed by the "JobName" environment variable. This is used when executing Build Jobs from within the Web Client. The environment variable is set by the Web Client before execution of OOMLOM. If the environment variable is not set, the JobName is derived from the Project and Search Path. Gets resolved to the Build Job Name. This value is set by -lj parameter specified on the command line.
$JobCard
Gets resolved to the name of the file that contains the job card information. The ISPF panel creates the file and saves it in: <high level qualifier>.jcllib(jobcard)
$KeepScript
Gets set to Yes or No depending on whether or not the -ks flag was passed to OOMLOM. The Yes or No value determines whether or not the target specific batch file is kept.
$LogOwner
Gets resolved to the Build Job Owner. This value is set by –lo parameter specified on the command line.
$MachineName
Gets resolved to the Computer Name where the build is being executed. Used in Foot Printing and Build Audit Reporting.
$MaxThreads
Reserved for future use. Resolves to 1.
$NewerDeps
Gets resolves to a file list of the dependencies newer than the target. This variable is space separated string.
$OutputType
Gets resolved to the screen, html, xml or both.
$Project
Gets resolved to the Project name from the Build Control file.
$ProjectDirs
Gets resolved to a string of Directories derived from the Dependencies and Target information.
$ProjectVPath
Gets resolved to the Expanded Project Search Path listed at the top of the generated Build Control file.
$PublicBuildJob
Gets resolved to the true or false based upon the -op parameter specified on the command line.
$Quiet
Gets resolved to Yes or No depending on if the –o flag has been passed to OOMLOM. The –o flag writes additional data to standard output. Gets resolved to Yes if the flag is passed.
$RelDeps
Gets resolved to a list of files for all the relative paths throughout the whole dependency tree. This variable is space separated string.
$ReleaseFlags_<Target Name>_<Build Task>_BuildTaskOptions<Dependency Name>
Special characters in the target and dependency name are replaced with _ to create the variable name. The variable will contain the release compile flags.
$RelFinalTarget
Gets resolved to the relative path name of the Final Target.
$RelTarget
Gets resolved to the relative path name to the Intermediate Target.
$RemoteMachine
Reserved for future use. Resolves to "NONE".
$Script
Gets resolved to the Script Name associated to the Build Type for the current Target.
$ScriptFooter
Gets resolved to a string that signifies the Finished Script message.
$ScriptHeader
Gets resolved to a string that signifies the Start Script message.
$ScriptName
Gets resolved to the name of the Script.
$SearchPathName
Gets resolved to the Search Path from the Build Control file.
$SubmitPDS
PDS that contains the JCL for the compile and link edits.
$Target
Gets resolved to the Target Name.
$TargetAsDep
Gets resolved to the fully qualified path of the Target if it exists in the Search Path. The value will be "" if the Target does not exist in the Search Path.
$TargetDeps
Gets resolved to a list of the Target's immediate dependencies. This variable is space separated string.
$TargetRelDeps
Gets resolved to a list of files for all the relative paths for the specific Target being built. This variable is space separated string.
$TargetSrcDeps
Target's scanned source code dependencies.
$TargetsThatAreTargetDeps
Target that are dependencies as well as targets themselves.
$TempFile
Gets resolved to the name of the temporary member name for the JCL.
$TotalSteps
Gets resolved to the total number of Targets that are determined by counting the Targets listed in the "ALL" label of the generated Build Control file.
$UserId
Gets resolved to the User ID of the person executing the build. Used in Foot Printing and Build Audit Reporting.
$ValidDatasetVPath
$ValidDatasetVPath will contain an
expanded Search Path of existing PDS names. The expanded Search
Path is derived from the combination of extensions in the scanner.ini and
the Search Path entries.
For
example:
Search Path = //USER1.SOURCE;//USER1.DOES.NOT.EXIST
scanner.ini contains .cobol and .copylib
then
$ValidDatasetVPath would equal
//'USER1.SOURCE.COBOL';//'USER1.SOURCE.H';
if USER1.SOURCE.COBOL
and USER1.SOURCE.H exist as valid PDSes.
This variable is space separated string.
$VPath
Gets resolved to the Expanded Search Path listed at the top of the generated Build Control file. This variable is space separated string.
$XmlBuildLog
XML build log PDS name.
Loading...