Name
Invoke-JS7GitRepositoryClone
SYNOPSIS
Clones a remote Git repository to a local repository
SYNTAX
Invoke-JS7GitRepositoryClone [-Folder] <String> [-Local] [-Url] <Uri> [[-Timeout] <Int32>] [[-AuditComment] <String>] [[-AuditTimeSpent] <Int32>] [[-AuditTicketLink] <Uri>] [<CommonParameters>]
DESCRIPTION
This cmdlet clones a remote Git repository to a local repository.
The local repository is populated from the remote Git repository and
is linked to the remote Git repository.
A local directory located in JETTY_BASE/resources/joc/repositories/rollout/TestCases
is mapped to a JOC Cockpit /TestCases inventory folder.
This cmdlet corresponds to using the following Git command:
* git clone <url>
The following REST Web Service API resources are used:
* /inventory/repository/git/clone
PARAMETERS
Folder
-Folder <String>
Specifies the JOC Cockpit inventory folder that maps to the Git repository.
Required? | true |
Position? | 1 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
Local
-Local <SwitchParameter>
Specifies that a repository holding scheduling objects that are local to the environment should be used.
This corresponds to the LOCAL category. If this switch is not used then the
ROLLOUT category is assumed for a repository that holds scheduling objects
intended for rollout to later environments such as test, prod.
Required? | false |
Position? | named |
Default value | False |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
Url
-Url <Uri>
Specifies the URL of the remote Git repository, for example: git@github.com:sos-berlin/JS7Demo.git
Required? | true |
Position? | 2 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
Timeout
-Timeout <Int32>
Required? | false |
Position? | 3 |
Default value | 60 |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
AuditComment
-AuditComment <String>
Specifies a free text that indicates the reason for the current intervention, e.g. "business requirement", "maintenance window" etc.
The Audit Comment is visible from the Audit Log view of the JOC Cockpit.
This parameter is not mandatory. However, the JOC Cockpit can be configured to require Audit Log comments for all interventions.
Required? | false |
Position? | 4 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
AuditTimeSpent
-AuditTimeSpent <Int32>
Specifies the duration in minutes that the current intervention required.
This information is shown in the Audit Log view. It can be useful when integrated
with a ticket system that logs the time spent on interventions with JS7.
Required? | false |
Position? | 5 |
Default value | 0 |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
AuditTicketLink
-AuditTicketLink <Uri>
Specifies a URL to a ticket system that keeps track of any interventions performed for JS7.
This information is shown in the Audit Log view of JOC Cockpit.
It can be useful when integrated with a ticket system that logs interventions with JS7.
Required? | false |
Position? | 6 |
Default value | |
Accept pipeline input? | true (ByPropertyName) |
Accept wildcard characters? | false |
RELATED LINKS
EXAMPLES
-------------------------- EXAMPLE 1 --------------------------
PS > Invoke-JS7GitRepositoryClone -Folder /TestCases -Url git@github.com:sos-berlin/JS7Demo.git
Clones the remote Git repository to a local repository that is mapped to the /TestCases folder in the JOC Cockpit inventory.