Launch jobs in TAC while Nexus repository is offline
Is it possible to work around failed job starts in TAC when the Nexus3 repository is offline?
We are using a high availability setup for TAC and Jobservers to allow for downtime of individual servers but the Nexus repo is a standalone install. We do not use the "Use latest version"-feature but it seems the TAC will still need to connect to the Nexus when launching a job.
Is there a way to update/reboot the Nexus-server and still have the jobs unaffected?
for artifact task, the checksum of the job ( zip) is checked from nexus for every run, regardless if use latest version is ticked or not.
with patch TPS-5995, and with setting this tac parameter (configuration.properties) : use.local.job.when.download.failed.from.artifact.repository = true,
if you have a local copy of the job in the generatedJobs folder, the local copy will be used, and the task will run, even if nexus is down.
The only way the TAC would not have to reach out to the Nexus, if your instance, is if the aritfact still exists in the "generatedJobs" folder and hasn't been cleared out. If the version doesn't change and the artifact still exists in the above mentioned folder, the TAC shouldn't be required to fetch a new copy of the specific artifact.
What your team can do is to increase the cleaning parameters for the Job Conductor side of TAC to a really high number, or set it to 0; depending the amount of space that your team has on the instance.
Looking into our configuration we have set the number of retained jobs to 3 and the period to 0 (unlimited). This appears to result in 3 retained jobs per task when I look into the folder.
Checking on our test instance there was one scheduled job that failed during our Nexus-outage and that had older generated jobs in the folder.
So that doesn't seem to do what I need.
Checked further and verified that the Tac will check the Nexus even if the files are present on both Tac-server and Jobserver. The files does not get updated however.
for artifact task, the checksum of the job ( zip) is checked from nexus for every run, regardless if use latest version is ticked or not.
with patch TPS-5995, and with setting this tac parameter (configuration.properties) : use.local.job.when.download.failed.from.artifact.repository = true,
if you have a local copy of the job in the generatedJobs folder, the local copy will be used, and the task will run, even if nexus is down.
