Comment

Comment by chrisanthropic

The best Jenkins advice I ever received was from here: https://medium.com/mindera/jenkins-a-la-travis-6c5a8debbb5b

On setting up Jenkins Job Builder using a 'seed job'. This setup allows you to add a .jenkins directory to you project, define a yaml based jenkins job inside that directory, push to github, and Jenkins will create the job you defined - NO web UI required.

In other words you make Jenkins behave like Travis.

Set this up with your first job being a job to backup Jenkins to S3 and things aren't as bad to manage.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton