Search

This feature has been in the plugin for sometime now. Configure the Integration Point parameters and the plugin will use a local integration point. You need to make sure the Integrity Client is running at all times.

Thanks for the clarification! You are right.
IntegrationPointFactory.createLocalIntegrationPoint(...) actually does call createIntegrationPoint(127.0.0.1, 0, ...).

Currently, I do this to test the mksapi.jar:

IntegrationPointFactory ipf = IntegrationPointFactory.getInstance();
IntegrationPoint intPt = ipf.createLocalIntegrationPoint(4, 10);
intPt.setAutoStartIntegrityClient(true);
CmdRunner cmdRunner = intPt.createSession(..., ...).createCmdRunner();
cmdRunner.setDefaultHostname(...);
cmdRunner.setDefaultPort(7001);
// Set command defaults
String[] cmd = new String[]

;
Response execute = cmdRunner.execute(cmd);
System.err.println(execute.getExitCode());

Can we also specify, that the client is started automatically by jenkins, via the API call "setAutoStartIntegrityClient"?

Also, "createLocalIntegrationPoint" wants to connect to port 0 (which is not actually a valid port of course). Seems like the port is figured out somehow? But in the APISession, the local client is only used if ipPort > 0.
Do you know which port to set then and why we cannot use 0?

Thanks!

No, you cannot specify the client is started automatically as the implementation of the local integration point is done using the "Client as a Server" architecture.

In this scenario, the client must be started separately and the listening Integrity Client daemon port (default 31000 on Windows - can be set to a default on UNIX as well) should be provided to the Jenkins plugin as the Integration Point Port parameter.

On UNIX the Integrity Client port is set to 0, but the port is then dynamically assigned. To prevent the dynamic assignment, you can set IntegrityClient.port=PORTNUM in $HOME/IntegrityClient.rc. On Windows, the IntegrityClient port is defaulted to 31000, but again you can change it by setting the value in %USERPROFILE%\IntegrityClient.rc

NOTE! There is currently an issue with the core product that FSA cache is not used when the Integrity Client is used as the Integration Point. So, if you're hoping to use that efficiency, you'll need to make sure your request is posted with Integrity Customer Support.

Cletus

Hi,

even though this item was closed long ago, I'm not sure where else to ask the related question..

My setup is as follows:

IntegritySCM: 1.19
Server: MKS Integrity 2009 (4.10.0.5679)
Client: MKS Source 2009 Build: 8.10.0.5679 Service Pack: 004-01

IntegrityClient.port is set to 3100 in $HOME/.IntegrityClient.rc and an instance is started by running "si about" once before trying to use IntegritySCM plugin.
------

On polling/checkout, I only get an "API Exception" without further meaningful errors in the log:

[DEBUG] IntegritySCM - Start execution of checkout() routine...!
[DEBUG] IntegritySCM - buildEnvVars() invoked...!
[DEBUG] IntegritySCM - Creating Integrity API Session...
[INFO] IntegritySCM - API Exception caught...
[INFO] IntegritySCM - Failed to establish a session: OK
[DEBUG] IntegritySCM - returned exit code -1
[DEBUG] IntegritySCM - buildEnvVars() invoked...!

I tried snooping on the TCP connection and got the following from tcpdump -nKvvX -i lo port 3100:

15:58:11.666383 IP (tos 0x0, ttl 64, id 48635, offset 0, flags [DF], proto TCP (6), length 60)
127.0.0.1.37696 > 127.0.0.1.3100: Flags [S], seq 1564421816, win 32792, options [mss 16396,sackOK,TS val 408261443 ecr 0,nop,wscale 6], length 0
0x0000: 4500 003c bdfb 4000 4006 7ebe 7f00 0001 E..<..@.@.~.....
0x0010: 7f00 0001 9340 0c1c 5d3f 2eb8 0000 0000 .....@..]?......
0x0020: a002 8018 fe30 0000 0204 400c 0402 080a .....0....@.....
0x0030: 1855 9343 0000 0000 0103 0306 .U.C........
15:58:11.666408 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
127.0.0.1.3100 > 127.0.0.1.37696: Flags [S.], seq 299930233, ack 1564421817, win 32768, options [mss 16396,sackOK,TS val 408261443 ecr 408261443,nop,wscale 6], length 0
0x0000: 4500 003c 0000 4000 4006 3cba 7f00 0001 E..<..@.@.<.....
0x0010: 7f00 0001 0c1c 9340 11e0 9279 5d3f 2eb9 .......@...y]?..
0x0020: a012 8000 fe30 0000 0204 400c 0402 080a .....0....@.....
0x0030: 1855 9343 1855 9343 0103 0306 .U.C.U.C....
15:58:11.666423 IP (tos 0x0, ttl 64, id 48636, offset 0, flags [DF], proto TCP (6), length 52)
127.0.0.1.37696 > 127.0.0.1.3100: Flags [.], seq 1, ack 1, win 513, options [nop,nop,TS val 408261443 ecr 408261443], length 0
0x0000: 4500 0034 bdfc 4000 4006 7ec5 7f00 0001 E..4..@.@.~.....
0x0010: 7f00 0001 9340 0c1c 5d3f 2eb9 11e0 927a .....@..]?.....z
0x0020: 8010 0201 fe28 0000 0101 080a 1855 9343 .....(.......U.C
0x0030: 1855 9343 .U.C
15:58:11.667391 IP (tos 0x0, ttl 64, id 48637, offset 0, flags [DF], proto TCP (6), length 298)
127.0.0.1.37696 > 127.0.0.1.3100: Flags [P.], seq 1:247, ack 1, win 513, options [nop,nop,TS val 408261443 ecr 408261443], length 246
0x0000: 4500 012a bdfd 4000 4006 7dce 7f00 0001 E..*..@.@.}.....
0x0010: 7f00 0001 9340 0c1c 5d3f 2eb9 11e0 927a .....@..]?.....z
0x0020: 8018 0201 ff1e 0000 0101 080a 1855 9343 .............U.C
0x0030: 1855 9343 4845 4144 202f 6963 6170 6920 .U.CHEAD./icapi.
0x0040: 4854 5450 2f31 2e31 0d0a 5072 6f74 6f63 HTTP/1.1..Protoc
0x0050: 6f6c 2d76 6572 7369 6f6e 3a20 312e 310d ol-version:.1.1.
0x0060: 0a43 6f64 6550 6167 653a 2055 5446 2d38 .CodePage:.UTF-8
0x0070: 0d0a 5469 6d65 5a6f 6e65 3a20 4575 726f ..TimeZone:.Euro
0x0080: 7065 2f42 6572 6c69 6e0d 0a41 7574 686f pe/Berlin..Autho
0x0090: 7269 7a61 7469 6f6e 3a20 4261 7369 6320 rization:.Basic.
0x00a0: 5a32 3930 6148 4e6c 4d54 706b 5457 677a Z290aHNlMTpkTWgz
0x00b0: 6247 7730 4951 3d3d 0d0a 4150 4956 6572 bGw0IQ==..APIVer
0x00c0: 7369 6f6e 3a20 342e 3131 2030 3030 2d30 sion:.4.11.000-0
0x00d0: 3020 300d 0a41 7070 5365 7373 696f 6e3a 0.0..AppSession:
0x00e0: 206e 6577 0d0a 5573 6572 2d41 6765 6e74 .new..User-Agent
0x00f0: 3a20 4a61 6b61 7274 6120 436f 6d6d 6f6e :.Jakarta.Common
0x0100: 732d 4874 7470 436c 6965 6e74 2f33 2e31 s-HttpClient/3.1
0x0110: 0d0a 486f 7374 3a20 3132 372e 302e 302e ..Host:.127.0.0.
0x0120: 313a 3331 3030 0d0a 0d0a 1:3100....
15:58:11.667432 IP (tos 0x0, ttl 64, id 313, offset 0, flags [DF], proto TCP (6), length 52)
127.0.0.1.3100 > 127.0.0.1.37696: Flags [.], seq 1, ack 247, win 512, options [nop,nop,TS val 408261443 ecr 408261443], length 0
0x0000: 4500 0034 0139 4000 4006 3b89 7f00 0001 E..4.9@.@.;.....
0x0010: 7f00 0001 0c1c 9340 11e0 927a 5d3f 2faf .......@...z]?/.
0x0020: 8010 0200 fe28 0000 0101 080a 1855 9343 .....(.......U.C
0x0030: 1855 9343 .U.C
15:58:11.670000 IP (tos 0x0, ttl 64, id 314, offset 0, flags [DF], proto TCP (6), length 69)
127.0.0.1.3100 > 127.0.0.1.37696: Flags [P.], seq 1:18, ack 247, win 512, options [nop,nop,TS val 408261444 ecr 408261443], length 17
0x0000: 4500 0045 013a 4000 4006 3b77 7f00 0001 E..E.:@.@.;w....
0x0010: 7f00 0001 0c1c 9340 11e0 927a 5d3f 2faf .......@...z]?/.
0x0020: 8018 0200 fe39 0000 0101 080a 1855 9344 .....9.......U.D
0x0030: 1855 9343 4854 5450 2f31 2e31 2032 3030 .U.CHTTP/1.1.200
0x0040: 204f 4b0d 0a .OK..

Then i get the API exception logged followed by eternal silence..
I suspect an API missmatch, but is there any way i can mitigate that without changing Integrity Client or Server versions?

Thanks in advance!

The mksapi.jar that is shipped with the plugin is as of version 10.3. So, trying to connect to the older client using the Integration Point feature will not work. You'd need to use a 10.3 client or newer.

Ok, thank you very much for the clarification.
It might be helpful to put that information on the wiki page.
But I'm leaving that decision to you as you would probably be the one who would have to maintain it...