Pushing new builds: What's your procedure?

Classic Servoy
1

We export and release new builds of our solution quite often. This is the protocol we follow:

  1. Make sure all developers have quit Developer so all changes have been saved to the development repository.

  2. Start developer and export solution, creating and activating new development release after export.

  3. Send message to all clients that the server will be unavailable for roughly 10 minutes while upgrades are being performed.

  4. Close all clients.

  5. Restart the Servoy application server.

  6. Shutdown headless clients.

  7. Import new solution.

  8. Restart server.

  9. Test new release by opening client.

That’s a lot of steps!

The reason that we started disconnecting all the users and then rebooting the server before importing was because we had a spell there where we couldn’t get new solutions to import (they were hanging), and someone thought it might be because users had locks that the import was waiting for them to release. (Although, I’ve never seen any locks showing up in Servoy Admin.)

From what I’ve read in the Servoy manuals, you should be able to upload new releases without having to close all clients, rebooting, and all of that mess. Then, the next time the clients log in, they will get the new software. This methods sounds much less disruptive to our user’s workflow. Is this possible?

How do you do it?

2

From what I’ve read in the Servoy manuals, you should be able to upload new releases without having to close all clients, rebooting, and all of that mess. Then, the next time the clients log in, they will get the new software. This methods sounds much less disruptive to our user’s workflow. Is this possible?

Yes, absolutely!

How do you do it?

  • go to web admin pages
  • upload solution
  • activate solution

The process is quite intuitive and you are asked everywhere what and if you want to do including a message if you want to inform your clients…

Hope this helps

3

Has anyone been able to perform a “live” update with 20+ users connected? It used to work fine for me when I had only a couple people on, but now the update never finishes unless I go through a process like the one described in the first post.

Maybe a more detailed progress meter during the upload would be helpful in assessing whether the import is hung or just very slow because of all the other server activity.

4

There were issues in the beginning but since 2.1 they are gone. It can take long but I am not aware of anything ‘hanging’. The solution I frequently update has something like 13 users attached normally…

5

IT2Be:
There were issues in the beginning but since 2.1 they are gone. /quote]

Not true! :frowning:

Sebster and I where debugging something (not so long time ago) and the log-stacktrace presented us a ‘dead-lock’

Only happens when (lot) users accessing the repository.
Do not know what the status is, right now.

Maybe Seb, can tell us more.