Jenkins in Guardian environment.

If an application runs on OSS, its easy for Jenkins. Because it has been setup to run things directly in Shell like below.

• Add a Shell step to a job.
• Put the command in you want to execute.
• If the step fails, Job fails.
• And turns RED in the control panel.

This works the same whether you are using a local Jenkins or whether you have a Controller/Agent Situation.

What About Guardian?

In Guardian environment, you have to use Controller/Agent Architecture.  But there would be 2 potential issues.

1. OSS Pseudo Terminal is NOT available for 100% of functions in GUARDIAN’s programs and Vice Versa.

• For this issue, Program must NOT attempt to read it from TERM. You should have a macro to redirects the TERM through OSSTTY.  Keep in mind that terminal handling between OSS and GUARDIAN is never be clean. 

       2. GTACL and SSH both use the PWD variable, So we could have a conflict.

          This issue would happen when you have remote situation. To run a GUARDIAN from OSS, where Jenkins lives, you need to use GTACL which uses PWD environment variable to decide where to start.  In a remote situation, create a TACL macro wrapper where we pass in the desired volume and subvolume.