veyepar: Jenkins 2.0. What's inside?

Author(s):	Oleg Nenashev
Location	F2.01
Date	apr Fri 29	Days Raw Files
Start	17:00	First Raw Start	error-in-template
Duration	01:00:00	Offset	None
End	18:00	Last Raw End
Chapters
Total cuts_time	None min.

382
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Jenkins_20_Whats_inside.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Jenkins originally founded in 2006 as "Hudson", is one of the leading automation servers available. Using an extensible, plugin-based architecture developers have created hundreds of plugins to adapt Jenkins to a multitude of build, test, and deployment automation workloads. Jenkins core is open-source (MIT License). In 2015, Jenkins surpassed 100,000 known installations making it the most widely deployed automation server.
<p/>
In 2016 the Jenkins project is planning to release Jenkins 2.0. This is a major effort targeting the user experience, which is known to be one of the main Jenkins weaknesses. It includes not only user interface changes, but also availability improvements and major new features. The activity involves all components of Jenkins: core, plugins, website and internal automation infrastructure.
<p/>
The talk addresses major changes in Jenkins 2.0:
<ul>
 <li/>Jenkins positioning shift: it goes beyond Continuous Integration (in particular, to Continuous Delivery and DevOps areas) 
 <li/>User documentation and website improvements
  <li/>User experience improvements: Installation experience, configuration pages, etc.
  <li/>Pipeline-as-code: Ecosystem, which allows describing jobs in Groovy DSL located in SCMs 
<ul/>
<p/>
After the talk there will be a Q&A and live demo session regarding the incoming Jenkins features.

Comment:

production notes