[
https://ovirt-jira.atlassian.net/browse/OVIRT-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25307#comment-25307
]
Barak Korren commented on OVIRT-853:
------------------------------------
I have it running in a test container...
It required Jenkins 2.7 and up.
It run side-by-side with the old Jenkins UI.
Its quite good at showing results of pipelines.
Some terms important for the analysis below:
* *Pipeline stage:* Created with the '{{stage}}' block - collects build steps
together and gives then a title.
* *Pipeline build step:* Created with commands like '{{sh}}' and {{scm}}. Does
actual work like running scripts.
The older pipeline stage view (The table we see in the status screen of
pipeline jobs) can already show pipeline stages and let you see the logs of
separate build steps separately, but its not very good when the pipeline does
things in parallel - it just shows the steps one after another.
Blue Ocean knows how to show things that happened in parallel separately.
Its important to note that both plugins assume that pipeline stages never
happen in parallel. This means that debugging complex stuff that happens in
parallel can be difficult, since it can be hard to tell separate build steps
apart (Most of them are simply called 'Shell script') and we can't give then
names by using stages.
Both Blue Ocean and the old pipeline stage view do not show the names of the
nodes things are running on, this can make some things harder to debug.
When pipeline jobs run other jobs - both plugins are not good at showing that,
they do not provide clear indication about what is going on or provide links to
the invoked jobs.
Blue ocean knows how to show the running time of a given piepline, but not of
stages inside that pipeline. The pipeline view can show both, so its better for
debugging slowness... Blue ocean also cannot show runtime trends.
Blue Ocean is not good at showing results of freestyle (old) jobs:
* The logs of all build steps are shown together - like in the console view
* There is no results screen, so we can't use something like groovy to create
better output display.
* There is a big and fancy artifacts tab, but it only lets you download
artifacts, not view them. Also we need to check how it behaves when we have
many artifacts nested inside directories.
*Conclusions:*
# Blue Ocean requires Jenkins 2
# We should slowly move to pipeline jobs everywhere if we want to get any
improved logging.
# We should keep pipelines simple - not do complex stuff in parallel, instead
split pipelines into serial stages and only do 1-3 steps on parallel within the
stage boundaries.
# Blue Ocean cannot completely replace the Jenkins UI.
# I recommend we install Blue Ocean once we upgrade to Jenkins 2, so we can
start gaining real world experience with it.
# Over time I expect we will link to Blue Ocean from Gerrit instead of to the
old UI.
> check out blue ocean jenkins project
> ------------------------------------
>
> Key: OVIRT-853
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-853
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
> https://jenkins.io/projects/blueocean/
--
This message was sent by Atlassian JIRA
(v1000.670.2#100024)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
