We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a followup of issue #10346 review comment #10346 (comment)
The Agent object is currently passed into the different PipelineAction objects and is used for 2 purposes I believe:
Agent
PipelineAction
For the agent.exclusive on pipeline initialization, which we could get rid with @yaauie suggestion in fix agent silent exit upon pipelines reloading #10346 (comment)
agent.exclusive
The use of ExecutionContextFactory in the pipeline.
ExecutionContextFactory
I think we could refactor both to get rid of the requirement of passing the whole agent.
The text was updated successfully, but these errors were encountered:
Config thread safety fixed by @yaauie in #10415
Sorry, something went wrong.
Created #10431 to remove Agent#exclusive
Created #10488 to clean unused agent from ExecutionContext.
agent
No branches or pull requests
This is a followup of issue #10346 review comment #10346 (comment)
The
Agent
object is currently passed into the differentPipelineAction
objects and is used for 2 purposes I believe:For the
agent.exclusive
on pipeline initialization, which we could get rid with @yaauie suggestion in fix agent silent exit upon pipelines reloading #10346 (comment)The use of
ExecutionContextFactory
in the pipeline.I think we could refactor both to get rid of the requirement of passing the whole agent.
The text was updated successfully, but these errors were encountered: