I’m out of the office for a little while, but I’m hearing reports from another developer of individual dependency scripts unilaterally deciding to release jobs in spite of the presence of either other dependency scripts or actual job dependencies.
In one case, a job has two different dependency scripts attached to it, but it sounds like the job is being released as soon as one of them returns True.
In the other case, a job has one dependency script and several job dependencies, but again, it is being released as soon as the script returns true.
These dependency scripts have been working fine on their own, but this is the first time we have combined them with each other or with job dependencies, so we wouldn’t have noticed an issue here before now.
Is this a known issue, or is there any possible explanation for what could be going on here other than a bug? We are still on 7.0.2.3, but I couldn’t find anything in the 7.1 release notes about big fixes related to dependency scripts.
That should definitely not be happening. Can you verify if the dependent job, once submitted, shows all the expected dependencies? I’m going to try to test this internally to see what I can find. Could you share one of your dependency scripts?
So I did some internal tests with a very basic script, and first tested a scenario where the script definitely should have triggered the release of the pending job, and it was successful, releasing the job as per the console logs. Next, I ran the same job, 3 job dependencies and 1 script dependency, and began to go through, first with 0 jobs complete, then 1, and 2, and each time I got roughly:
It wasn’t until I had all 3 job dependencies completed that the pending job scan returned the following
Therefore at this time I cannot reproduce this. Could you have someone, since I understand you are out of the office, do a similar test to verify? Jsut to advise, the script I am using is the identical one from docs.thinkboxsoftware.com/produc … cy-scripts with the only change is that it says “releaseJob = True”.
I pointed someone at your reply, so if they get around to testing this, I will follow up. Otherwise, I will look into it when I am back in the office on the 18th.
So I have been investigating this, and I can’t reproduce it with a simple test scenario either. I need to audit the real dependency scripts that are being used for logic problems, but for now, I would say this was probably a false alarm.