John E. Malmberg
2017-03-19 13:56:13 UTC
It turns out that the environment variable parameters for Linux Jenkins
build agents are one of the parameters that do not take effect with out
disconnecting the build agent and reconnecting it.
I use an environment variable in the Linux Jenkins build agent to tell
it how to connect to VMS. SSH for the VMS 8.4 build agents, and rsh for
VMS 8.3 and VMS 7.3 build agents.
Which means that I never tested to see if the build worked from an SSH
session from the Jenkins build agent to OpenVMS Alpha 8.3. It was still
using RSH after the upgrade.
I had to downgrade from TCP/IP 5.7-13 ECO 4 to the TCP/IP V5.6-9
supplied with VMS 8.3 Alpha though.
* SSH from a Jenkins build agent does work to VMS/Alpha 8.3 TCP/IP
5.7-13 ECO 4 though. I only tested that combination after I implemented
the solution for RSH. As each complete test build is just under 3
hours, I did not take the time to test it, since I could not use that
TCP version on VMS 8.3.
* NFS Client of TCP/IP 5.7-13 ECO 4 does not work correctly on VMS/Alpha
8.3. During my build writes to the the NFS share were failing.
%COPY-E-WRITEERR, error writing
JSTAGE_ROOT:[kit]GNV-AXPVMS-GZIP-V0107--1.PCSI;1
-RMS-F-WER, file write error
-SYSTEM-F-MEDOFL, medium is offline
%COPY-W-NOTCMPLT, STAGE_ROOT:[KIT]GNV-AXPVMS-GZIP-V0107--1.PCSI;1 not
completely copied
After downgrading to TCP/IP 5.6-9 on VMS/Alpha 8.3:
(02:16:03.84) $ copy stage_root:[kit]*.* jstage_root:[kit]/log
%COPY-S-COPIED, STAGE_ROOT:[KIT]gnv-axpvms-83-gzip-v01^.07--1.zip;1
copied to JSTAGE_ROOT:[kit]gnv-axpvms-83-gzip-v01^.07--1.zip;3 (3934 blocks)
%COPY-S-COPIED, STAGE_ROOT:[KIT]GNV-AXPVMS-GZIP-V0107--1.PCSI;2 copied
to JSTAGE_ROOT:[kit]gnv-axpvms-gzip-v0107--1.pcsi;3 (13328 blocks)
%COPY-S-NEWFILES, 2 files created
The fix to get the builds working on VMS 8.3 Alpha from Jenkins control
is to have a wrapper to the build script submit the build script to
batch and then wait for the batch job to complete.
I still do not know what the environment difference is between the RSH
environment and the interative ssh environment that GNV is not happy
with. But that no longer matters.
Regards,
-John
***@qsl.net_work
build agents are one of the parameters that do not take effect with out
disconnecting the build agent and reconnecting it.
I use an environment variable in the Linux Jenkins build agent to tell
it how to connect to VMS. SSH for the VMS 8.4 build agents, and rsh for
VMS 8.3 and VMS 7.3 build agents.
Which means that I never tested to see if the build worked from an SSH
session from the Jenkins build agent to OpenVMS Alpha 8.3. It was still
using RSH after the upgrade.
I had to downgrade from TCP/IP 5.7-13 ECO 4 to the TCP/IP V5.6-9
supplied with VMS 8.3 Alpha though.
* SSH from a Jenkins build agent does work to VMS/Alpha 8.3 TCP/IP
5.7-13 ECO 4 though. I only tested that combination after I implemented
the solution for RSH. As each complete test build is just under 3
hours, I did not take the time to test it, since I could not use that
TCP version on VMS 8.3.
* NFS Client of TCP/IP 5.7-13 ECO 4 does not work correctly on VMS/Alpha
8.3. During my build writes to the the NFS share were failing.
%COPY-E-WRITEERR, error writing
JSTAGE_ROOT:[kit]GNV-AXPVMS-GZIP-V0107--1.PCSI;1
-RMS-F-WER, file write error
-SYSTEM-F-MEDOFL, medium is offline
%COPY-W-NOTCMPLT, STAGE_ROOT:[KIT]GNV-AXPVMS-GZIP-V0107--1.PCSI;1 not
completely copied
After downgrading to TCP/IP 5.6-9 on VMS/Alpha 8.3:
(02:16:03.84) $ copy stage_root:[kit]*.* jstage_root:[kit]/log
%COPY-S-COPIED, STAGE_ROOT:[KIT]gnv-axpvms-83-gzip-v01^.07--1.zip;1
copied to JSTAGE_ROOT:[kit]gnv-axpvms-83-gzip-v01^.07--1.zip;3 (3934 blocks)
%COPY-S-COPIED, STAGE_ROOT:[KIT]GNV-AXPVMS-GZIP-V0107--1.PCSI;2 copied
to JSTAGE_ROOT:[kit]gnv-axpvms-gzip-v0107--1.pcsi;3 (13328 blocks)
%COPY-S-NEWFILES, 2 files created
The fix to get the builds working on VMS 8.3 Alpha from Jenkins control
is to have a wrapper to the build script submit the build script to
batch and then wait for the batch job to complete.
I still do not know what the environment difference is between the RSH
environment and the interative ssh environment that GNV is not happy
with. But that no longer matters.
Regards,
-John
***@qsl.net_work