Allow to change entrypoint / shell for ci step

[anbraten]

Problem

Currently /bin/sh is used as entrypoint for every ci step. If an image does not contain /bin/sh it can not be used with woodpecker ATM. For example gcr.io/kaniko-project/executor:debug only ships with /bin/busybox.

// File: /pipeline/frontend/yaml/compiler/convert.go

entrypoint = []string{"/bin/sh", "-c"}
command = []string{"echo $CI_SCRIPT | base64 -d | /bin/sh -e"}

Solution

Allow to exec multiple commands with the agent instead of a single combined one. This could allow to use the default entrypoint or even a specific one. Commands could be executed with something like docker exec instead.

Workaround

Create a plugin as plugins can define their entrypoint.

[zc-devs]

As a temporary workaround we can try to create symbolic link forget, doesn't work:(

[6543]

Well from securety standpoint: as long as we handle it like normal steps there should not be a downside ... we just make sure that asap it is set ... it's not considered as a plugin usage anymore

[zc-devs]

For linux-like OS entrypoint and command look like mentioned above:

env["CI_SCRIPT"] = base64.StdEncoding.EncodeToString([]byte(generateScriptPosix(commands)))
env["HOME"] = "/root"
env["SHELL"] = "/bin/sh"
entry = []string{"/bin/sh", "-c"}
cmd = []string{"echo $CI_SCRIPT | base64 -d | /bin/sh -e"}

So, we depend on some shell and base64. Seems we can change shell only and hope image would contain base64 command. Am I right? Things are getting worse with Windows.

[6543]

....
So, we depend on some shell and base64. Seems we can change shell only and hope image would contain base64 command. Am I right? Things are getting worse with Windows.

well that's some legacy limitation we will get rid of in the near future ... it's al here only the backend's need to adopt the new capability

[6543]

beside for windows we have a powershell equivalent ...

If you want to chat ... I suggest our Matrix-Rooms/Discord-Server :)