| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
for it, thanks to Vagrant
|
|
|
|
certs for the last 12 months
|
|
|
|
|
|
experimental
|
|
pbuilder/schroot/maintenance jobs for them, thanks to Vagrant
|
|
jobs) on another rasberrypi2, thanks to Vagrant
|
|
|
|
|
|
|
|
|
|
|
|
|
|
causing yum breakge"
This reverts commit de7064c18e86f9c4fb29da82023da543a60369e5.
|
|
yum breakge
|
|
|
|
|
|
pb-build3
|
|
|
|
build processes on all nodes
|
|
(for now), as this is broken in sid atm (bug about to be filed)
|
|
This reverts commit 16a1e225d72382a6c820510ac2f448b53ff67652.
Ebourg said this wasn't really needed…
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 567afbb4cc8cf8e002d0a7de9af61bc3a298751c.
|
|
|
|
|
|
https://jenkins-ci.org/content/mitigating-unauthenticated-remote-code-execution-0-day-jenkins-cli
It seems that two channels need to be secured. The first is a custom tcp
port which is firewalled anyway. The other part is urls starting with
/cli. Instead of filtering this entry point in jenkins (and thus
breaking bin/abort.sh), we apply the filtering in apache. Thus a local
execute vulnerability remains, but we didn't care about those earlier.
|
|
|
|
Even if Git can fetch the repositories, people are unhappy when they see a 403.
|
|
|
|
|
|
This reverts commit b32118218c89ad429ef26fa03ed16d55069728ac.
|
|
|
|
otherwise `pbuilder clean` removes the symlink, and the following builds won't
use the tmpfs, etc..
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|