Precheck on 3.1+ - still confused!

Re: Precheck on 3.1+ - still confused!

by Tim Hunt -
Number of replies: 2

Oh drat! We just upgraded our Jobe servers yesterday and I was not paying attention. That was mainly do update the OS and PHP version, but we went to latest JOBE master branch then, and I don't want to have to do another deploy there. Therefore, I will probably just use v3.5.3, or more likely today's master branch, which seems to include some useful bug fixes.

So actually, there is not need for you to rush the release of the next version.

In reply to Tim Hunt

Re: Precheck on 3.1+ - still confused!

by Tim Hunt -
A further question about this:
With the new version of CodeRunner and Jobe, what are the rules about upgrading?
  1. Jobe and CodeRunner must be upgraded at the same time or it will break.
  2. It is fine to upgrade Jobe in first, then deploy the new CodeRunner a few days later.
  3. It is fine to upgrade CodeRunner first, and then upgrade Jobe later.
Thanks.
In reply to Tim Hunt

Re: Precheck on 3.1+ - still confused!

by Richard Lobb -

You can do the upgrades in either order. All versions of CodeRunner (within the last few years, anyway) work with all versions of Jobe.

The caveat is that there might be a performance and/or disk-space hit with CodeRunner v3.6 (which I aim to release later this week) and a non-updated Jobe over time. It depends on how much use authors make of the new feature allowing students to attach files to their submission: what size files they allow, how many students, the amount of free disk space on Jobe and the file system it's using. If authors stay with the default file size limit of 10 kB, I wouldn't expect any problems with the old Jobe for months or even years.