IT department really wanted to use their snake oil antivirus enterprise super secure hackproof™ software everywhere.
So it was installed on the CI servers.
Fastforward a few months and we were wondering why one build agent was no longer picking up jobs.
After a day of debugging we found out that a certain snake oil sofware tampered with a single machine internal TCP conncetion and somehow fucked it up in a way that all packets in one direction just vanished.
Disabling the snake oil software magically fixed the problem.
It is good to have a build method that doesn’t require network access; at one time that used to be required for Debian builds. However, for a variety of reasons, most CI servers do have access to the network, even if there’s a firewall (or NAT) between them and the Internet.
Comments
IT department really wanted to use their snake oil antivirus enterprise super secure hackproof™ software everywhere.
So it was installed on the CI servers.
Fastforward a few months and we were wondering why one build agent was no longer picking up jobs.
After a day of debugging we found out that a certain snake oil sofware tampered with a single machine internal TCP conncetion and somehow fucked it up in a way that all packets in one direction just vanished.
Disabling the snake oil software magically fixed the problem.
Should a CI server even have access to the Internet and need antivirus software? Maven access I guess.
It is good to have a build method that doesn’t require network access; at one time that used to be required for Debian builds. However, for a variety of reasons, most CI servers do have access to the network, even if there’s a firewall (or NAT) between them and the Internet.
Sign in to comment. Sign in