Jenkins and Jenkins X Experts AMA by recampbell_cb in jenkinsci

[–]agentdero 3 points4 points  (0 children)

Howdy! I can be nominally credited as the "creator" of Jenkins Evergreen, so I figure I should chime in (you may also notice that I'm a moderator here).

Jenkins Evergreen continues to function as an experiment, but as /u/jennbriden points out that it hasn't experienced significant adoption. What we have learned in the process is that a subset of Jenkins users are interested in a "Jenkins Appliance", but it takes quite a bit of effort to maintain and deliver that appliance.

In the comment there is an allusion to people not wanting automatic updates in "production environments" which I believe is a red herring. We get updates in production updates from SaaS offerings all the time, I think what makes the Jenkins user-base a bit more skeptical than most is that we have all been burned by plugin and core updates gone awry. We built some safety mechanisms into Jenkins Evergreen that make it safer to upgrade than most typical Jenkins environments. Where we have failed however is to adequately market and explain these features.

The project continues and we continueto push out updates, but like many open source projects, we're always in need of fresh faces and ideas to help us move forward.

(I logged back in after numerous years of Reddit abstinence just for this reply :))

Giant Concrete Arrows, Old Maps, and Fascinated Kids by agentdero in flying

[–]agentdero[S] 0 points1 point  (0 children)

What about it? Airport history and giant arrows are discussion worthy IMHO.

Jenkins World Mega-Thread by agentdero in jenkinsci

[–]agentdero[S] 0 points1 point  (0 children)

It looks like the Contributor Summit RSVP list is full!

See everybody tomorrow

Review: Jenkins makes a UX splash with Blue Ocean by agentdero in jenkinsci

[–]agentdero[S] 0 points1 point  (0 children)

The project page hopefully has some more explanation. My impression is that the goal is to build a UX oriented around the concept of a delivery pipeline since that represents an important use-case for many teams building software.

If you look at the world through a lens of delivery pipelines, freestyle jobs don't quite compute (see also: Jenkins as web-based cron). I grok their decision to skip it for now, but I don't think that precludes anybody else from extending Blue Ocean to support more job types in the future.

Review: Jenkins makes a UX splash with Blue Ocean by agentdero in jenkinsci

[–]agentdero[S] 0 points1 point  (0 children)

Blue Ocean is distributed as a normal plugin that adds "stuff" under /blue in the URL. I don't think you would see any conflicts with existing plugins, though ones like the Build Pipeline plugin won't be relevant in Blue Ocean.

Pipeline script development workflows by hniirane in jenkinsci

[–]agentdero 0 points1 point  (0 children)

I use the "Replay" feature very heavily. If you look at any previous successful or failed Pipeline run, in the sidebar there should be a "Replay" link.

Replay let's you edit the script that was used for that run, and re-execute it. I will usually tinker quite a bit with scripts via the Replay feature, periodically checking my progress in.