[JENKINS-6156] postbuild-task no longer runs at the END, just near the end.

Hello!

We've been using the postbuild-task plugin to help faciliate auto deployments, and we have been triggering off of an scp string (provided by the scp plugin.) With the newest upgrade of Hudson, the postbuild-task runs before the scp plugin. This used to not be the case ... it seems it would make sense for the post-build task to run after all other tasks.

I guess this part is more of a feature request ... but one should be able to choose the order in which plugins are executed....(and or we should be able to make assumptions that the plugin-execution-order will not change between upgrades of versions of hudson)

Thanks,

---
Originally reported by nwheeler, imported from: postbuild-task no longer runs at the END, just near the end.

• status: Open
  
• priority: Major
  
• component(s): postbuild-task-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 4
  
• imported: 20251223-222157
  

Raw content of original issue

Hello!


  We've been using the postbuild-task plugin to help faciliate auto deployments, and we have been triggering off of an scp string (provided by the scp plugin.) With the newest upgrade of Hudson, the postbuild-task runs before the scp plugin. This used to not be the case ... it seems it would make sense for the post-build task to run after all other tasks.


  I guess this part is more of a feature request ... but one should be able to choose the order in which plugins are executed....(and or we should be able to make assumptions that the plugin-execution-order will not change between upgrades of versions of hudson)


Thanks,

• environment: Hudson ver. 1.353