Update pecl extensions in update.sh

[J0WI]

No description provided.

[tilosp]

I generally like the idea of automating this.

But this would cause a lot of confusing commits.
For example if the redis version is updated, we would get mutiple commits from the jenkins server that runs update.sh.
And they would be called Update to 14.0.3, Update to 13.0.7 and Update to 12.0.12.

The code that generates the commits is here https://github.com/docker-library/oi-janky-groovy/blob/master/update.sh/target-pipeline.groovy

[J0WI]

Yes, that would be the tradeoff. It's hard to change target-pipeline.groovy in a way that does not affects other repositories and I don't know if @tianon would accept such a specific change request.
See also docker-library/openjdk#246

[tilosp]

We could also use a different solution for running the update.sh script.
Especially because the current jenkins script does not handle deleted file and updates to travis.yml. See: docker-library/oi-janky-groovy#8

Maybe something similar to what i am doing for generate-stackbrew-library.sh.

[tilosp]

Btw there were also some wired commits in this repo ab3b62b...f16c857

[tilosp]

@J0WI update.sh is now done by @tilosp-bot (see for example #662) so this should be possible now

[tilosp]

LGTM