Hello @Rafael Grisotto and welcome to the Community!
Pipes are essentially a docker image containing a script to accomplish a given task. All the Atlassian-developed pipes, such as the atlassian/renovate-scan are available in public repositories, which can be forked to make any custom changes you would like.
So in this case, if you would like to change the base image used by that particular pipe, you could fork that repository, make the changes to the Dockerfile in your fork, and then push the custom docker image to your own dockerhub registry.
Once the custom pipe image is pushed and available publicly in Dockerhub, you can refer to it in your pipeline using the following syntax :
pipe: docker://<DockerAccountName>/<ImageName>:<version>
It's important to note though, that the renovate slim image might not contain all the dependencies necessary for that pipe's script to run, so you might want to test it to see how it goes with the slim image compared to the full image.
You can also find more details on custom pipes in the Write a pipe for bitbucket pipelines documentation.
However, if you would prefer the official renovate-scan pipe to be changed to use the base image as renovate slim, please let me know so I can create a feature request for our pipe development team.
Thank you, @Rafael Grisotto !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.