Jenkins Upgrade Cycle

[prudhvigodithi]

Is your feature request related to a problem? Please describe

Consider frequently upgrading Jenkins by coming up with a Jenkins Upgrade Cycle. This can be manual or an automation if possible. Having this upgrade cycle would always keep the Jenkins up-to date and limits the security vulnerabilities. Frequently upgrading Jenkins would also limit breaking changes and issues with the upgrade.

Describe the solution you'd like

Solution 1) A automated workflow, a blue-green type deployment. Create latest version Jenkins, migrate jobs and switch the URL.
Migrating jobs with huge data is not always feasible so to achieve this following is a solution

• Use 2 EFS systems.
• First EFS mount at the job folder level: /var/jenkins_home/jobs.
• Second EFS mount the global folder: /var/jenkins_home.
• During the blue-green just re-use the /var/jenkins_home/jobs to the new jenkins and allow other files in /var/jenkins_home to be created by the jenkins.

sudo mount efs_server1:/exported_dir1 /var/jenkins_home/jobs
sudo mount efs_server2:/exported_dir2 /var/jenkins_home

Solution 2) Perform a series of steps based on defined upgrade cycle and upgrade the same Jenkins.

Describe alternatives you've considered

No response

Additional context

No response

[peterzhuamazon]

Is your feature request related to a problem? Please describe

Consider frequently upgrading Jenkins by coming up with a Jenkins Upgrade Cycle. This can be manual or an automation if possible. Having this upgrade cycle would always keep the Jenkins up-to date and limits the security vulnerabilities. Frequently upgrading Jenkins would also limit breaking changes and issues with the upgrade.

Describe the solution you'd like

Solution 1) A automated workflow, a blue-green type deployment. Create latest version Jenkins, migrate jobs and switch the URL. Migrating jobs with huge data is not always feasible so to achieve this following is a solution

* Use 2 EFS systems.

* First EFS mount at the job folder level: `/var/jenkins_home/jobs`.

* Second EFS mount the global folder: `/var/jenkins_home`.

* During the blue-green just re-use the `/var/jenkins_home/jobs` to the new jenkins and allow other files in `/var/jenkins_home` to be created by the jenkins.

sudo mount efs_server1:/exported_dir1 /var/jenkins_home/jobs
sudo mount efs_server2:/exported_dir2 /var/jenkins_home

Solution 2) Perform a series of steps based on defined upgrade cycle and upgrade the same Jenkins.

Describe alternatives you've considered

No response

Additional context

No response

So @prudhvigodithi if I understand correctly you want the jobs efs to be unmount during upgrade to make sure no alternations to the job setups, but only mount the home efs to ensure Jenkins can upgrade successfully?

Once complete, just mount the jobs efs back?

Thanks.

[peterzhuamazon]

Need to also upgrade the Jenkins with monitoring plugin:

• Jenkins main node has very high cpu and mem usages #346 (comment)