|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
it works with executor 2. Is this expected behavior? If so then it is good to have option called serial and concurrent. If the option is serial then jobs should get triggered in the order as mentioned in the projects list serially one after another once the job is completed. When option is concurrent then it is not required to maintain the project order given that executor is set more as per the requirement.