rin_ne commented on New Feature JENKINS-24313

I think that data exchange between plugins should be done by internal communication through extension or Jenkins instance.

I already found a issue on your mentioned solution.

  • Job A and B: export-params
    • Checked "Export file to the master"
    • File path: /path/to/same/file
  • Job C: EnvInject
    • Checked "Load files from the master"
    • File path: /path/to/same/file
  • Job pipeline: C -> A

Build C#1 is started from Job C then kicks build A#1 from Job A. A#1 exports parameters to /path/to/same/file then finish. After that, C#1 reads parameters from /path/to/same/file.

In this case, C#1 might expect that /path/to/same/file is generated by A#1. But if build B#1 from Job B is also started at the same time, B#1 also exports parameters to /path/to/same/file. It means that it has possibility that C#1 reads parameters from "/path/to/same/file" which was generated by B#1.

That's leak. I would not implement such weakness feature any more.

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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to