Page History
...
Stores scheduling objects from the JS7 inventory to a local Git repository .
SYNTAX
Set-JS7RepositoryItem [[-Path] <String>] [[-Type] <String[]>] [[-Folder] <String>] [-Recursive] [-Local] [[-ControllerId] <String>] [-Valid] [-NoDraft] [-NoDeployed] [-NoReleased] [-Latest] [[-AuditComment] <String>] [[-AuditTimeSpent] <Int32>] [[-AuditTicketLink] <Uri>] [-WhatIf] [-Confirm] [<CommonParameters>]
...
This cmdlet stores JS7 scheduling objects to a local Git repository. The JS7 settings
determine which object types such as schedules, workflows are considered for a repository
of category LOCAL and of category ROLLOUT respectively.
The following REST Web Service API resources are used:
* /inventory/deployable
* /inventory/deployables
* /inventory/releasable
* /inventory/releasables
* /inventory/repository/store
PARAMETERS
Path
-Path <String>
Specifies the folder, sub-folder and name of the scheduling object, for example a workflow path,
that should be stored to the repository.
...
-Type <String[]>
Specifies the scheduling object type that is one or more of:
* Deployable object types:
** WORKFLOW
** FILEORDERSOURCE
** JOBRESOURCE
** NOTICEBOARD
** LOCK
* Releasable object types:
** INCLUDESCRIPT
** SCRIPTINCLUDEJOBTEMPLATE
** WORKINGDAYSCALENDAR
** NONWORKINGDAYSCALENDAR
** SCHEDULE
** REPORT
If no object type is specified then any object types will be used.
| Required? | false |
| Position? | 2 |
| Default value | |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
Folder
-Folder <String>
Specifies the inventory folder for which items should be stored to the Alternatively to use of -Path the parameter specifies a JOC Cockpit inventory folder to be used to
store objects to a local Git repository.
| Required? | false |
| Position? | 3 |
| Default value | |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
...
-Recursive <SwitchParameter>
Specifies that any all sub-folders should be looked up if the -Folder parameter is used.
By default no sub-folders will be looked up.
...
-Local <SwitchParameter>
Specifies that a repository holding local 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.
...
Valid
-Valid <SwitchParameter>
Limits the scope to valid schedudling objects only.
| Required? | false |
| Position? | named |
| Default value | False |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
...
-NoDeployed <SwitchParameter>
Specifies that no previously deployed objects should be stored.
| Required? | false |
| Position? | named |
| Default value | False |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
NoReleased
-NoReleased <SwitchParameter>
Specifies that no previously released objects should be stored.
...
-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, however, the JOC Cockpit can be configured to enforce require Audit Log comments for any all interventions.
| Required? | false |
| Position? | 5 |
| Default value | |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
...
-AuditTimeSpent <Int32>
Specifies the duration in minutes that the current intervention required.
This information is visible with shown in the Audit Log view. It can be useful when integrated
with a ticket system that logs the time spent on interventions with JobSchedulerJS7.
| Required? | false |
| Position? | 6 |
| Default value | 0 |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
...
-AuditTicketLink <Uri>
Specifies a URL to a ticket system that keeps track of any interventions performed for JobSchedulerJS7.
This information is visible with shown in the Audit Log view of JOC Cockpit.
It can be useful when integrated with a ticket system that logs interventions with JobSchedulerJS7.
| Required? | false |
| Position? | 7 |
| Default value | |
| Accept pipeline input? | true (ByPropertyName) |
| Accept wildcard characters? | false |
...
-------------------------- EXAMPLE 1 --------------------------
PS > Set-JS7RepositoryItem -ControllerId testsuite,standalone -Path JSRepositoryItem -Folder /TestCases/sampleWorkflow_001 -Type 'WORKFLOW'sampleWorkflows -Recursive
Stores any scheduling objects of the indicated folder and sub-folders to the repository of category ROLLOUTDeploys the specified workflow from the indicated path to both Controller instances.
-------------------------- EXAMPLE 2 --------------------------
PS > Set-JSRepositoryItem JS7RepositoryItem -ControllerId testsuite,standalone -Folder Path /TestCases/sampleWorkflowssampleWorkflow_001 -Type 'WORKFLOW'
Stores the workflow from the specified path to the local repository of category ROLLOUT provided that the workflow has previously been deployed to both indicated Controller instancesStores any scheduling objects previously deployed to the indicated Controller to the repository.
-------------------------- EXAMPLE 3 --------------------------
PS > Set-JS7RepositoryItem -ControllerId testsuite -Folder /Samples -NoDraft
Stores any deployable objects such as workflows, resource locks etc from the specified folder to the repository of category ROLLOUT. No sub-folders and no draft versions of objects are considered.
-------------------------- EXAMPLE 4 --------------------------
PS > Set-JS7RepositoryItem -ControllerId testsuite -Folder /Samples -Recursive -Local
Stores any deployable objects such as workflows job resources and schedules from the specified folder recursively to the repository of category LOCAL. Deployable objects are considered only if previously deployed to the indicated Controller.
Overview
Content Tools