I get that that is a better way of limiting the number of instances than
using executor counts. Thanks for that.
I still don't see a good way to schedule the jobs. Set a cron entry in the
job so they all get scheduled once a day and then let all but one sit idle
waiting on the resource lock?
Hi
Jenkins is reporting that the Release plugin
(https://plugins.jenkins.io/release/) has a Stored XSS vulnerability
(https://www.jenkins.io/security/advisory/2020-10-08/#SECURITY-1928) meaning it
may not be safe to use. Given this plugin appears to have not been updated in
2 years, I'm not
Great and if it again works on older CentOS then please try to update your
alpine to latest version.
I am sure then it will start working on latest CentOS too.
We recently faced similar issue with elasticsearch 7 and then it got fixed
after we updated Alpin.
On Sat, 5 Dec 2020, 19:06 Mohan,
Acutally have tried with Ubuntu-16.04-LTS image aswell even in that also
same issue.
Sure next will try with K8s host's native OS CentOS- 7.8(It was working
earlier).
On Sat, 5 Dec 2020, 6:45 pm Ujjawal Khare, wrote:
The issue may be because of kernel version. Old alpine seems to be having
>
The issue may be because of kernel version. Old alpine seems to be having
issue with it.
Can you try same on an older version of CentOS..?
Or try to use latest version of alpine.
Regards,
Ujjawal
On Sat, 5 Dec 2020, 09:19 Mk, wrote:
> *Environment: *
> Jenkins - Version 2.235.5
Background:
In our lab we host range of projects from public open source to sensitive
private customer projects. Because our Jenkins install works with all of them,
we have never got around to making it externally accessible. We hacked up a
reverse proxy to expose a single project via our
