Mårten Svantesson

Seems like `--filter=blob:none` doesn't work on BitBucket Cloud: https://jira.atlassian.com/browse/BCLOUD-19847 On BitBucket DataCenter it is supported: https://jira.atlassian.com/browse/BSERV-11639 GitLab supports `--filter=blob:none` and also `--filter=sparse:oid:...` which could be used instead of the git...

The real gain is achieved when server side filtering is supported on the git server. On github it does.

I don't think there is much point in spending time on adding this feature to jenkins-x/updatebot. I have added support to jenkins-x-plugins/jx-updatebot and you can achieve the same with that...

An open question is wether we should have some central config (in jx-requirements.yaml) to enable sparse checkout or if it suffices to have configuration for the different tools.

No, not build pods. Build packs. Taking maven as an example the labels app and version are missing from the deployment here https://github.com/jenkins-x-buildpacks/jenkins-x-kubernetes/blob/master/packs/maven/charts/templates/deployment.yaml I'm not running serverless, but I don't...

Right. The headline in the istio document was misleading: "Deployments with app and version labels". But it really is the pods that should have the labels. I'll reword this story....

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle rotten