Air Commands
- To checkin full project : -
- To checkin specific artifact : -
- To checkin full project and resolve conflicts : -
- To checkin specific artifact and resolve conflicts : -
- To checkin specific artifact with required files :-
- To checkout full project : -
- To checkout specific artifact : -
- To checkout full project and resolve conflicts : -
- To checkout specific artifact and resolve conflicts : -
- To checkout a new project which has common sandboxes : -
- To checkout a new project artifacts along with common sandbox artifacts :-
{ { -object object | -project project | -user username } ... | -all }
[ -quiet ]
[ -breakable | -unbreakable ]
[ -auto-release | -manual-release ]
[ -modify attribute ] ...
{ -object object } ...
air lock break
{ { -object object | -project project | -user username } ... | -all }
[ -quiet ]
e.g., air lock break -project dev_project -user Alberto -user Sarah
e.g., air lock break -object /Projects/class/maths/dml/xyz.dml
[ -project-only | -all-required | -exact ]
[ -dry-run ]
[ -exclude rpath ... ]
[ -add ]
[ -strict ]
[ -no-annotations ]
[ -ignore-generated-by ]
[ -analysis-only-datasets ]
[ -exclude-tests ]
[ -full-commons | -no-full-commons ]
[ { -comment comment | -comment-file comment-filename }
[ -overwrite-comment ] ]
[ -include-commons ]
[ -rtag { rtag-name | version } ]
-project-only | -all-required | -exact --> Specifies which objects should be tagged along with the primary object (specified by rpath or -file file-list). You can specify one of the following:
-project-only (or -p) — Includes only required objects in the same projects as the objects specified by rpath or -file object-list.
-all-required (or -all) — Includes all objects required by the objects to be tagged (specified by rpath or -file object-list).
-exact (or -e) — Includes only the objects specified by rpath or -file object-list. This argument does not tag objects that these objects depend on. If the object to be tagged is a directory, the command recursively tags its contents.
If none of these arguments are specified, the air tag create command uses -exact by default.
-strict --> Treats any warning situations encountered during the discovery of required objects as errors. For example, if a record format (.dml) file required by a graph were missing or had syntax errors, this argument would generate an error.
-include-commons --> When you are tagging a project, include the full contents of all common projects. Using this option automatically creates an exact tag.
Examples:1. This example adds the prod456_tag tag to the /Projects/production project and all its required files:air tag create prod456_tag /Projects/production -all-required
2. This example adds the prod457_tag tag to only the POC project’s mp directory:
air tag create prod456_tag /Projects/customer/POC/mp -exact
3. This example passes a file to the command that lists the two graph objects to be tagged:
air tag create prod458_tag -file tagfile
The tagfile file contains the following lines:
/Projects/test/mp/devo4.mp
/Projects/test/mp/devo5.mp
[-latest | -list-order]
tag1 tag2 ...
Examples:
1. To create a new tag called prod that has the same contents as an existing tag dev, use the -create option to create prod and then specify dev as the only tag to “combine”:
air tag combine -create prod dev
2. In this example, the command automatically resolves any object conflicts by adding the most recent version of that object to the new tag:
air tag combine -create super-tag -latest prod12 prod14 prod16
If the tag prod 14 contains the latest version of my-graph.mp, it will be used instead of the object in prod16.
3. In this example, the command automatically resolves any object conflicts by using the version of that object found in the left-most tag.:
air tag combine -create super-tag -list-order prod14 prod12 prod16
If my-graph.mp exists in prod14, that tagged version is used even if a more recent version exists in prod12 or prod16. If my-graph.mp exists in prod12 or prod16 but not in prod14, the object in prod12 is used because it is the left-most tag in the list.
air tag delete [-q] tag-name
-q --> Suppresses error if the tag does not exist.
Example: air tag delete -q super-tag
air tag diff tag-dir1 tag-dir2
The output lists each tagged object where the version differs. The first specified tag (tag-dir1) is V1, and the second (tag-dir1) is V2. In the output below, b.txt does not exist in tag-dir1, so V1 is blank.
Object V1 V2
/dir/a.txt 308 310
/dir/b.txt 310
A frozen tag cannot be unfrozen, so this command should be used with caution.
air tag duplicate tag-name new-tag-name [-update-to-current] [-comment comment | -comment-file comment-filename] [-exclude rpath ...] [-exclude-tests]
Argument | Description |
---|---|
tag-name | Name of an existing tag you want to duplicate. |
new-tag-name | Name of the new tag. |
-update-to-current | Specifies that the new tag will have all primary objects moved to the current version and that all secondary objects will be recomputed at the current version. |
-comment comment | -comment-file comment-filename | You may choose one of these:
|
-exclude rpath ... | If the -update-to-current argument is present, the command ignores the specified objects or any objects contained in the specified directories when it recomputes which secondary objects to tag. |
-exclude-tests | If specified, test objects are not included in the tag. Test objects are technical repository elements whose class is testobj (for example, graph unit test (.tst) files). You can view an object’s class by using air object ls. |
-l — Lists user and time information about the tag tag.
-o — Lists all the tags on the object object.
-c — Lists the comments on the tag tag.
-p — Lists the primary tagged objects in the tag tag.
-e — Lists everything tagged by the tag tag (at the domain level).
-n — Lists only the names of the objects in the tag tag.
-t — Lists the type and state of tag tag. F
-s — For tags that were created by loading a save file, lists information about the source tag.
air object changed [ rpath ... ]
[ -root1 eme1 ] [ -branch1 branch1 ] [ {-version1 v1 | tag1 | timestamp1} ]
[ -root2 eme2 ] [ -branch2 branch2 ] [ {-version2 v2 | tag2 | timestamp2} ]
[ -show-all ]
[ -tagged-only ]
[ -diff [ -terse | -verbose | -wizard ] [ -ignore-param-order ] [ -text ]
[ -ignore-dep-analysis ] [ -original-format ] ]
[ -files-with-diff [ -terse | -verbose ] ]
[ -m ] [ -dml ]
air object changed /Projects/myproj -version1 4849
The output shows among other things that transform.xfr and mygraph.mp have not changed between version 4849 and the latest version, whereas records.dml was added after version 4849 and .project.pset has been modified:
A dml/records.dml
S xfr/transform.xfr
S mp/mygraph.mp
M .project.pset
2. The following command determines the differences between the latest versions of the myproj project on two different branches in the same technical repository — release-20150428 and main:
air object changed /Projects/myproj \
-branch1 release-20150428 -branch2 main
A dml/stuff.dml
M mp/output_data.mp
M mp/process_data.mp
air promote load graph1.save -history-file history-graph1 -comment "load of graph1" -no-analyze
air tag remove -q my_first_tag /Projects/xyz/sandbox/mp/abc.mp
air tag diff my_first_tag my_second_tag
air tag rename my_second_tag my_other_tag
Comments
Post a Comment