< Back
New-BMApplication
Post
NAME New-BMApplication
SYNOPSIS
Creates an application in BuildMaster.
SYNTAX
New-BMApplication [-Session] <Object> [-Name] <String> [[-ReleaseNumberSchemeName] <String>]
[[-BuildNumberSchemeName] <String>] [-AllowMultipleActiveBuilds] [[-ApplicationGroupId] <String>]
[<CommonParameters>]
DESCRIPTION
The `New-BMApplication` function creates an application in BuildMaster. This function uses the native BuildMaster
API, which can change without notice between releases. Only a name is required to create an application. The name
must be unique and not in use.
These parameters are also available:
* `ReleaseNumberScheme`: sets the release number scheme to use when you create a new release for the application.
Options are `MajorMinorRevision`, `MajorMinor`, or `DateBased`.
* `BuildNumberScheme`: sets the build number scheme to use when creating new packages/builds for an application.
Options are `Unique`, `Sequential`, `DateBased`.
* `AllowMultipleActiveBuilds`: a flag that indicates if the application is allowed to have multiple active builds.
PARAMETERS
-Session <Object>
A session object that represents the BuildMaster instance to use. Use the `New-BMSession` function to create
session objects.
Required? true
Position? 1
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Name <String>
The name of the application.
Required? true
Position? 2
Default value
Accept pipeline input? false
Accept wildcard characters? false
-ReleaseNumberSchemeName <String>
The name of the release number scheme. Should be one of:
* `MajorMinorRevision`
* `MajorMinor`
* `DateBased`
Required? false
Position? 3
Default value
Accept pipeline input? false
Accept wildcard characters? false
-BuildNumberSchemeName <String>
The name of the build number scheme. Should be one of:
* `Unique`
* `Sequential`
* `DateTimeBased`
Required? false
Position? 4
Default value
Accept pipeline input? false
Accept wildcard characters? false
-AllowMultipleActiveBuilds [<SwitchParameter>]
Allow multiple active builds.
Required? false
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters? false
-ApplicationGroupId <String>
The application group to assign. By default, the application will be ungrouped.
Required? false
Position? 5
Default value
Accept pipeline input? false
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
OUTPUTS
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>New-BMApplication -Session $session -Name 'MyNewApplication'
Demonstrates the simplest way to create an application. In this example, a `MyNewApplication` application will be
created and all its fields set to BuildMaster's default values.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>New-BMApplication -Session $session -Name 'MyNewApplication' -ReleaseNumberSchemeName MajorMinor
-BuildNumberSchemeName Sequential -AllowMultipleActiveBuilds
This example demonstrates all the fields you can set when creating a new application. In this example, the new
application will be called `MyNewApplication`, its release number scheme will be `MajorMinor`, its build number
schema will be `Sequential`, it will allow multiple active releases, and it will allow multiple active builds.
RELATED LINKS
SYNOPSIS
Creates an application in BuildMaster.
SYNTAX
New-BMApplication [-Session] <Object> [-Name] <String> [[-ReleaseNumberSchemeName] <String>]
[[-BuildNumberSchemeName] <String>] [-AllowMultipleActiveBuilds] [[-ApplicationGroupId] <String>]
[<CommonParameters>]
DESCRIPTION
The `New-BMApplication` function creates an application in BuildMaster. This function uses the native BuildMaster
API, which can change without notice between releases. Only a name is required to create an application. The name
must be unique and not in use.
These parameters are also available:
* `ReleaseNumberScheme`: sets the release number scheme to use when you create a new release for the application.
Options are `MajorMinorRevision`, `MajorMinor`, or `DateBased`.
* `BuildNumberScheme`: sets the build number scheme to use when creating new packages/builds for an application.
Options are `Unique`, `Sequential`, `DateBased`.
* `AllowMultipleActiveBuilds`: a flag that indicates if the application is allowed to have multiple active builds.
PARAMETERS
-Session <Object>
A session object that represents the BuildMaster instance to use. Use the `New-BMSession` function to create
session objects.
Required? true
Position? 1
Default value
Accept pipeline input? false
Accept wildcard characters? false
-Name <String>
The name of the application.
Required? true
Position? 2
Default value
Accept pipeline input? false
Accept wildcard characters? false
-ReleaseNumberSchemeName <String>
The name of the release number scheme. Should be one of:
* `MajorMinorRevision`
* `MajorMinor`
* `DateBased`
Required? false
Position? 3
Default value
Accept pipeline input? false
Accept wildcard characters? false
-BuildNumberSchemeName <String>
The name of the build number scheme. Should be one of:
* `Unique`
* `Sequential`
* `DateTimeBased`
Required? false
Position? 4
Default value
Accept pipeline input? false
Accept wildcard characters? false
-AllowMultipleActiveBuilds [<SwitchParameter>]
Allow multiple active builds.
Required? false
Position? named
Default value False
Accept pipeline input? false
Accept wildcard characters? false
-ApplicationGroupId <String>
The application group to assign. By default, the application will be ungrouped.
Required? false
Position? 5
Default value
Accept pipeline input? false
Accept wildcard characters? false
<CommonParameters>
This cmdlet supports the common parameters: Verbose, Debug,
ErrorAction, ErrorVariable, WarningAction, WarningVariable,
OutBuffer, PipelineVariable, and OutVariable. For more information, see
about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).
INPUTS
OUTPUTS
-------------------------- EXAMPLE 1 --------------------------
PS C:\\>New-BMApplication -Session $session -Name 'MyNewApplication'
Demonstrates the simplest way to create an application. In this example, a `MyNewApplication` application will be
created and all its fields set to BuildMaster's default values.
-------------------------- EXAMPLE 2 --------------------------
PS C:\\>New-BMApplication -Session $session -Name 'MyNewApplication' -ReleaseNumberSchemeName MajorMinor
-BuildNumberSchemeName Sequential -AllowMultipleActiveBuilds
This example demonstrates all the fields you can set when creating a new application. In this example, the new
application will be called `MyNewApplication`, its release number scheme will be `MajorMinor`, its build number
schema will be `Sequential`, it will allow multiple active releases, and it will allow multiple active builds.
RELATED LINKS