Skip to content

[chore]: Migration of Pipeline Executor #216

Open
0 of 5 issues completed
Open

Description

@SuvabrataChowdhury

Chore Description

The current executor have a very naive logic. It simply sequentially runs stages as os bash scripts which are provided by the user. This is a huge security risk!! It is basically running the user provided scripts in the OS itself. This way the user can run arbitrary scripts which will definitely compromise the server.

The fix is to move away from the manual naive execution of scripts to a more robust executor which runs steps in isolated environments i.e., in containers/pods. This way even if the attacker writes malicious scripts and tries compromising the server, it will only affect the cheap container running at that point of time. This is way safer and easily maintainable because the runner can be made configurable and it can come from an open-source executor. Few such executors are listed below,

The Idea is to make AutoBuild the ci orchestrator which will build these pipelines easily across the desired runner of the user. In future we can provide our own runner as well. Introduce a new service to do the same job as com.autobuild.executor.

Benefit hypothesis

  • Includes containerised steps and removes the major security vulnerability.
  • Drastically improves maintaining the Executor module.
  • Opens door for a whole lot of new, useful features in future.

Chore importance

Very High

Additional comments

No response

Metadata

Metadata

Labels

choreSome tasks, other than core application development, which helps the application's development.epic

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions