The difference between jazz source control and command line
Here, In continuous build, we test two solutions in the build definition configuration:
1, use jazz source control to update the codes automatically
2, use pure CLI accept command to update the code.
But we find there have below difference:
a, when using 1, each time it will take at about 30 minutes to update the code, and the size
of .jazz5 folder is bigger than that using 2 (at about 600 M bigger);
b, when using 2, each time it will only take at about 10 minutes to update the code, and the size
of .jazz5 folder is smaller.
c, but when we just use pure CLI command to update the code, in build result view, there
can not display the change sets and their related work items, also the person who deliver the codes
is not able to receive the mail although we have configured that.
The codes we used in the test contain 215 components, totally with at about 7G size.
1, use jazz source control to update the codes automatically
2, use pure CLI accept command to update the code.
But we find there have below difference:
a, when using 1, each time it will take at about 30 minutes to update the code, and the size
of .jazz5 folder is bigger than that using 2 (at about 600 M bigger);
b, when using 2, each time it will only take at about 10 minutes to update the code, and the size
of .jazz5 folder is smaller.
c, but when we just use pure CLI command to update the code, in build result view, there
can not display the change sets and their related work items, also the person who deliver the codes
is not able to receive the mail although we have configured that.
The codes we used in the test contain 215 components, totally with at about 7G size.