Changes in pulse web services 5.2 vs 6

Deadline
1

Hi
We developed app that communicates with deadline through pulse web services. We noticed that some of the queries gives us diferent responses in deadline 6 eg. when we ask for job that was deleted this is what we get :
query :
pulseadrress/GetJob%3F999_050_999_522e1420
pulse 5.2 response :
Error: can’t load from disk, IOException: job was deleted, jobDirectory: /mnt/deadline/jobs/999_050_999_522e1420/999_050_999_522e1420.job (Job has been corrupted, it is recommended that this job be removed from the repository: 999_050_999_522e1420) (Deadline.Jobs.JobCorruptedException)

pulse 6 response :

Is there any documentation of the changes in pulse web services ? As we need to re-code the app for new web services behavior - and it would be nice to do it once - not through constant checking what the pulse response :smiley:
Thanks in advance !
Grzegorz

2

Hello Grzegorz,

Was my reply to your ticket helpful?

Cheers,

Dwight

3

I’m sorry for spamming the forum - but I can’t get a mail from you from few days - any news at that topic ?

4

We don’t have any documented changes at this point. In this case though, this was actually a change to deadlinecommand’s GetJob option (as that’s what you’re calling directly in this case). This function now returns an empty string if the job doesn’t exist, rather than return an error message. Most behavior should be consistent between the two versions, but if you do come across any other cases where the behavior is different, let us know, and we can check if it’s a bug or by design.

Cheers,

  • Ryan
5

So there is no option to get list what was changed by design ? That would probably significantly shorten the testing period on our side.

6

The GetJob example is an edge case. The change was made in the lower level data access code to no longer throw an exception when a job doesn’t exist, which had an indirect impact on how the GetJob command works now. Most, if not all, of the other commands should function the same, as it was never our intention to change their behavior. But if you do come across another command that functions differently, please let us know!

Cheers,

  • Ryan