Hello dear developers, contributors, maintainers,
We recently (last week) migrated all the agent container-based on ci.jenkins.io <http://ci.jenkins.io/> to Kubernetes instead of ACS (Azure Container Services). This change should be functionally transparent (as almost all the pipelines on ci.jenkins.io <http://ci.jenkins.io/> are expected to use "labels"). But of course, we saw some hiccups (performances where not really good at first) that we fixed on the go, but some of your builds might have been impacted. If it is the case, feel free to let us know by either answering to that email, or opening an issue on https://issues.jenkins.io/browse/INFRA <https://issues.jenkins.io/browse/INFRA>, or contacting us in the IRC #jenkins-channel or on the community forum at https://community.jenkins.io/ <https://community.jenkins.io/> . The rationale behind that change is that ACS is costly and we wanted to decrease the costs of this workload. Using Kubernetes requires a bit more maintenance than a "container as a service" such as ACS but allows us a finer tuning. More details can be found on https://issues.jenkins.io/browse/INFRA-2918 <https://issues.jenkins.io/browse/INFRA-2918>. Thanks to all the contributors involved in this change, from reviews, tips, contribution, issue openers! For the infra team, Damien DUPORTAL -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/281464DD-0989-4608-9C4A-4349753548DE%40gmail.com.
