Community
Participate
Working Groups
Build Identifier: The Add/Remove dialog, and the remove action and the run on server action should have the IServer as their scheduling rule. Reproducible: Always Steps to Reproduce: 1. Add 3 applications to the server 2. While the applications are still publishing, remove one of the three publishing applications from the server. The modifyModules is executed and changed the modules structure on the server. The Remove publish job is pending at this moment. 3. Now, the first Add publish jobs finishes, and tries to create ModulePublishInfo. Since there's only two modules on the server now, the pending removed module doesn't get its ModulePublishInfo created. This means in the WTP server framework that, this application is not published. But in reality, it's published. Then the pending Remove publish job gets executed, and since the WTP server framework thinks the application is not published, no remove delta is sent, and then this application is not removed.
Maybe the Start/Stop/Restart actions for the modules should have IServer as their scheduling rule as well? Just a thought.