Need a strong, senior Jenkins/EKS DevOps Engineer immediately to fix and improve critical Jenkins CI environment
Budget: $1,500 – $3,000 USD
Looking for a strong, senior DevOps Engineer to fix, and then upgrade, our critical Jenkins/CI environment. We have been limping along for a while but recently Jenkins or AWS or EKS or Kubernetes or something blew up and all the configured pipelines disappeared. Restarting everything fixed nothing.
Part 1 of this project is to bring the current environment back to working order. Perhaps this will include updating Jenkins versions, plugin versions, and anything else in the environment. Part 2 of this will include a redesign and build of a parallel, updated, functional Production system.
Six months ago we ported a local Jenkins/CI environment that includes a lot of scripted pipeline code to use an AWS-based "development" EKS cluster. Pipelines are scripted (not declarative) and call directly to the nodes versus handing to Kubernetes master to schedule. Current Jenkins is linked to a GIT server.
The CI environment builds a java app that runs behind apache httpd on tomcat, with a MySQL database. It also builds a puppet-based installer for the application. Docker images are pulled from a local Nexus repository to build Pods. Many pipelines in the current environment do not call Kubernetes but deploy things directly to existing nodes. This needs to be cleaned up. EKS and Jenkins are set up to pull from Bitbucket. Will need Jenkins/EKS configuration changes. Original developers of the CI environment have left, without leaving updated configuration documentation.
Part 1 of this project is to bring the current environment back to working order. Perhaps this will include updating Jenkins versions, plugin versions, and anything else in the environment. Part 2 of this will include a redesign and build of a parallel, updated, functional Production system.
Six months ago we ported a local Jenkins/CI environment that includes a lot of scripted pipeline code to use an AWS-based "development" EKS cluster. Pipelines are scripted (not declarative) and call directly to the nodes versus handing to Kubernetes master to schedule. Current Jenkins is linked to a GIT server.
The CI environment builds a java app that runs behind apache httpd on tomcat, with a MySQL database. It also builds a puppet-based installer for the application. Docker images are pulled from a local Nexus repository to build Pods. Many pipelines in the current environment do not call Kubernetes but deploy things directly to existing nodes. This needs to be cleaned up. EKS and Jenkins are set up to pull from Bitbucket. Will need Jenkins/EKS configuration changes. Original developers of the CI environment have left, without leaving updated configuration documentation.