You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Kenneth Knowles <ke...@apache.org> on 2018/12/18 20:05:41 UTC
[RFC] I made a new tabbed Beam view in Jenkins
Hi all,
I made a new view to split Beam builds into tabs:
https://builds.apache.org/view/A-D/view/Beam%20Nested/
- PostCommit tab includes PostCommit and "PreCommit_.*_Cron" because these
are actually post-commit jobs; it is a feature not a bug.
- PreCommit tab includes jobs that have no meaningful history because they
are just against PRs, commits, phrase triggering
- Inventory self-explanatory
- PerformanceTests self-explanatory
- All; I didn't want to keep making categories but just send this for
feedback
WDYT about making this the top-level Beam view? (vs
https://builds.apache.org/view/A-D/view/Beam/)
After that, maybe we could clean the categories so they fit into the tabs
more easily with fewer regexes (to make sure things don't get missed). I
have read also that if you use / instead of _ as a separator in a name then
Jenkins will display jobs as nested in folders automatically. Not sure it
actually results in a better view; haven't tried it.
Kenn
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Ankur Goenka <go...@google.com>.
This is really cool.
Another request for cleaning the old build history from the list :)
On Thu, Dec 20, 2018 at 2:22 AM Łukasz Gajowy <lg...@apache.org> wrote:
> Looks great. +1 for making this a top level view.
>
>
>> After that, maybe we could clean the categories so they fit into the tabs
>> more easily with fewer regexes (to make sure things don't get missed). I
>> have read also that if you use / instead of _ as a separator in a name then
>> Jenkins will display jobs as nested in folders automatically. Not sure it
>> actually results in a better view; haven't tried it.
>>
>
> FWIW, I think we can easily test all this using the dockerized Jenkins[1]
> to have a quicker feedback loop. It proved very useful in refactoring
> Nexmark jobs and some other Jenkins related work. From my perspective such
> directories could be handy (different kinds of performance tests/load tests
> comming up next soon).
>
> [1]
> https://github.com/apache/beam/tree/master/.test-infra/dockerized-jenkins
>
> Łukasz
>
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Łukasz Gajowy <lg...@apache.org>.
Looks great. +1 for making this a top level view.
> After that, maybe we could clean the categories so they fit into the tabs
> more easily with fewer regexes (to make sure things don't get missed). I
> have read also that if you use / instead of _ as a separator in a name then
> Jenkins will display jobs as nested in folders automatically. Not sure it
> actually results in a better view; haven't tried it.
>
FWIW, I think we can easily test all this using the dockerized Jenkins[1]
to have a quicker feedback loop. It proved very useful in refactoring
Nexmark jobs and some other Jenkins related work. From my perspective such
directories could be handy (different kinds of performance tests/load tests
comming up next soon).
[1]
https://github.com/apache/beam/tree/master/.test-infra/dockerized-jenkins
Łukasz
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Maximilian Michels <mx...@apache.org>.
Thanks Kenn. Very useful. +1 for making it the default view!
-Max
On 18.12.18 23:12, Mark Liu wrote:
> That looks great. Thank you!
>
> Mark
>
> On Tue, Dec 18, 2018 at 1:53 PM Jason Kuster <jasonkuster@google.com
> <ma...@google.com>> wrote:
>
> Oh, a good fact! Thanks for the info. :)
>
> On Tue, Dec 18, 2018 at 1:48 PM Alan Myrvold <amyrvold@google.com
> <ma...@google.com>> wrote:
>
> The _Cron variants of pre-commits are run post-commit, to make it easier
> to tell if the pre-commit is flaky or broken.
>
> On Tue, Dec 18, 2018 at 1:40 PM Jason Kuster <jasonkuster@google.com
> <ma...@google.com>> wrote:
>
> This looks great! (also it looks like some precommits snuck into the
> postcommit view)
>
> On Tue, Dec 18, 2018 at 1:25 PM Alan Myrvold <amyrvold@google.com
> <ma...@google.com>> wrote:
>
> It does look much better!
>
> On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay <altay@google.com
> <ma...@google.com>> wrote:
>
> I like this version, it looks cleaner than the current
> combined view.
>
> On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner
> <swegner@google.com <ma...@google.com>> wrote:
>
> Very cool. I also didn't realize we had control over the
> Jenkins "views".
>
> We currently lack a decent dashboard to monitor the
> build health across Beam jenkins jobs and triage
> failures; this is a step in the right direction.
>
> I haven't played with Jenkins views before, but it
> appears they can be managed via the Job DSL similar to
> our job definitions [1]:
>
> > The DSL execution engine exposes several methods to
> create Jenkins jobs, views, folders and config files. [..]
>
> It would be cool to integrate this into our job config
> in such a way that we could automatically keep the views
> up-to-date as jobs are added or renamed.
>
> [1]
> https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
>
> On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin
> <kedin@google.com <ma...@google.com>> wrote:
>
> This is really helpful, didn't realize it was
> possible. Categories and contents look reasonable. I
> think something like this definitely should be the
> top-level Beam view.
>
> Regards,
> Anton
>
> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles
> <kenn@apache.org <ma...@apache.org>> wrote:
>
> Hi all,
>
> I made a new view to split Beam builds into
> tabs:
> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>
> - PostCommit tab includes PostCommit and
> "PreCommit_.*_Cron" because these are actually
> post-commit jobs; it is a feature not a bug.
> - PreCommit tab includes jobs that have no
> meaningful history because they are just against
> PRs, commits, phrase triggering
> - Inventory self-explanatory
> - PerformanceTests self-explanatory
> - All; I didn't want to keep making categories
> but just send this for feedback
>
> WDYT about making this the top-level Beam view?
> (vs https://builds.apache.org/view/A-D/view/Beam/)
>
> After that, maybe we could clean the categories
> so they fit into the tabs more easily with fewer
> regexes (to make sure things don't get missed).
> I have read also that if you use / instead of _
> as a separator in a name then Jenkins will
> display jobs as nested in folders automatically.
> Not sure it actually results in a better view;
> haven't tried it.
>
> Kenn
>
>
>
> --
>
>
>
>
> Got feedback? tinyurl.com/swegner-feedback
> <https://tinyurl.com/swegner-feedback>
>
>
>
> --
> -------
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>
> See something? Say something. go/jasonkuster-feedback
> <https://goto.google.com/jasonkuster-feedback>
>
>
>
> --
> -------
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>
> See something? Say something. go/jasonkuster-feedback
> <https://goto.google.com/jasonkuster-feedback>
>
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Mark Liu <ma...@google.com>.
That looks great. Thank you!
Mark
On Tue, Dec 18, 2018 at 1:53 PM Jason Kuster <ja...@google.com> wrote:
> Oh, a good fact! Thanks for the info. :)
>
> On Tue, Dec 18, 2018 at 1:48 PM Alan Myrvold <am...@google.com> wrote:
>
>> The _Cron variants of pre-commits are run post-commit, to make it easier
>> to tell if the pre-commit is flaky or broken.
>>
>> On Tue, Dec 18, 2018 at 1:40 PM Jason Kuster <ja...@google.com>
>> wrote:
>>
>>> This looks great! (also it looks like some precommits snuck into the
>>> postcommit view)
>>>
>>> On Tue, Dec 18, 2018 at 1:25 PM Alan Myrvold <am...@google.com>
>>> wrote:
>>>
>>>> It does look much better!
>>>>
>>>> On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> I like this version, it looks cleaner than the current combined view.
>>>>>
>>>>> On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner <sw...@google.com>
>>>>> wrote:
>>>>>
>>>>>> Very cool. I also didn't realize we had control over the Jenkins
>>>>>> "views".
>>>>>>
>>>>>> We currently lack a decent dashboard to monitor the build health
>>>>>> across Beam jenkins jobs and triage failures; this is a step in the right
>>>>>> direction.
>>>>>>
>>>>>> I haven't played with Jenkins views before, but it appears they can
>>>>>> be managed via the Job DSL similar to our job definitions [1]:
>>>>>>
>>>>>> > The DSL execution engine exposes several methods to create Jenkins
>>>>>> jobs, views, folders and config files. [..]
>>>>>>
>>>>>> It would be cool to integrate this into our job config in such a way
>>>>>> that we could automatically keep the views up-to-date as jobs are added or
>>>>>> renamed.
>>>>>>
>>>>>> [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
>>>>>>
>>>>>> On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin <ke...@google.com>
>>>>>> wrote:
>>>>>>
>>>>>>> This is really helpful, didn't realize it was possible. Categories
>>>>>>> and contents look reasonable. I think something like this definitely should
>>>>>>> be the top-level Beam view.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Anton
>>>>>>>
>>>>>>> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I made a new view to split Beam builds into tabs:
>>>>>>>> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>>>>>>>>
>>>>>>>> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron"
>>>>>>>> because these are actually post-commit jobs; it is a feature not a bug.
>>>>>>>> - PreCommit tab includes jobs that have no meaningful history
>>>>>>>> because they are just against PRs, commits, phrase triggering
>>>>>>>> - Inventory self-explanatory
>>>>>>>> - PerformanceTests self-explanatory
>>>>>>>> - All; I didn't want to keep making categories but just send this
>>>>>>>> for feedback
>>>>>>>>
>>>>>>>> WDYT about making this the top-level Beam view? (vs
>>>>>>>> https://builds.apache.org/view/A-D/view/Beam/)
>>>>>>>>
>>>>>>>> After that, maybe we could clean the categories so they fit into
>>>>>>>> the tabs more easily with fewer regexes (to make sure things don't get
>>>>>>>> missed). I have read also that if you use / instead of _ as a separator in
>>>>>>>> a name then Jenkins will display jobs as nested in folders automatically.
>>>>>>>> Not sure it actually results in a better view; haven't tried it.
>>>>>>>>
>>>>>>>> Kenn
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Got feedback? tinyurl.com/swegner-feedback
>>>>>>
>>>>>
>>>
>>> --
>>> -------
>>> Jason Kuster
>>> Apache Beam / Google Cloud Dataflow
>>>
>>> See something? Say something. go/jasonkuster-feedback
>>> <https://goto.google.com/jasonkuster-feedback>
>>>
>>
>
> --
> -------
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>
> See something? Say something. go/jasonkuster-feedback
> <https://goto.google.com/jasonkuster-feedback>
>
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Jason Kuster <ja...@google.com>.
Oh, a good fact! Thanks for the info. :)
On Tue, Dec 18, 2018 at 1:48 PM Alan Myrvold <am...@google.com> wrote:
> The _Cron variants of pre-commits are run post-commit, to make it easier
> to tell if the pre-commit is flaky or broken.
>
> On Tue, Dec 18, 2018 at 1:40 PM Jason Kuster <ja...@google.com>
> wrote:
>
>> This looks great! (also it looks like some precommits snuck into the
>> postcommit view)
>>
>> On Tue, Dec 18, 2018 at 1:25 PM Alan Myrvold <am...@google.com> wrote:
>>
>>> It does look much better!
>>>
>>> On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> I like this version, it looks cleaner than the current combined view.
>>>>
>>>> On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner <sw...@google.com>
>>>> wrote:
>>>>
>>>>> Very cool. I also didn't realize we had control over the Jenkins
>>>>> "views".
>>>>>
>>>>> We currently lack a decent dashboard to monitor the build health
>>>>> across Beam jenkins jobs and triage failures; this is a step in the right
>>>>> direction.
>>>>>
>>>>> I haven't played with Jenkins views before, but it appears they can be
>>>>> managed via the Job DSL similar to our job definitions [1]:
>>>>>
>>>>> > The DSL execution engine exposes several methods to create Jenkins
>>>>> jobs, views, folders and config files. [..]
>>>>>
>>>>> It would be cool to integrate this into our job config in such a way
>>>>> that we could automatically keep the views up-to-date as jobs are added or
>>>>> renamed.
>>>>>
>>>>> [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
>>>>>
>>>>> On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin <ke...@google.com> wrote:
>>>>>
>>>>>> This is really helpful, didn't realize it was possible. Categories
>>>>>> and contents look reasonable. I think something like this definitely should
>>>>>> be the top-level Beam view.
>>>>>>
>>>>>> Regards,
>>>>>> Anton
>>>>>>
>>>>>> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I made a new view to split Beam builds into tabs:
>>>>>>> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>>>>>>>
>>>>>>> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron"
>>>>>>> because these are actually post-commit jobs; it is a feature not a bug.
>>>>>>> - PreCommit tab includes jobs that have no meaningful history
>>>>>>> because they are just against PRs, commits, phrase triggering
>>>>>>> - Inventory self-explanatory
>>>>>>> - PerformanceTests self-explanatory
>>>>>>> - All; I didn't want to keep making categories but just send this
>>>>>>> for feedback
>>>>>>>
>>>>>>> WDYT about making this the top-level Beam view? (vs
>>>>>>> https://builds.apache.org/view/A-D/view/Beam/)
>>>>>>>
>>>>>>> After that, maybe we could clean the categories so they fit into the
>>>>>>> tabs more easily with fewer regexes (to make sure things don't get missed).
>>>>>>> I have read also that if you use / instead of _ as a separator in a name
>>>>>>> then Jenkins will display jobs as nested in folders automatically. Not sure
>>>>>>> it actually results in a better view; haven't tried it.
>>>>>>>
>>>>>>> Kenn
>>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Got feedback? tinyurl.com/swegner-feedback
>>>>>
>>>>
>>
>> --
>> -------
>> Jason Kuster
>> Apache Beam / Google Cloud Dataflow
>>
>> See something? Say something. go/jasonkuster-feedback
>> <https://goto.google.com/jasonkuster-feedback>
>>
>
--
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow
See something? Say something. go/jasonkuster-feedback
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Alan Myrvold <am...@google.com>.
The _Cron variants of pre-commits are run post-commit, to make it easier to
tell if the pre-commit is flaky or broken.
On Tue, Dec 18, 2018 at 1:40 PM Jason Kuster <ja...@google.com> wrote:
> This looks great! (also it looks like some precommits snuck into the
> postcommit view)
>
> On Tue, Dec 18, 2018 at 1:25 PM Alan Myrvold <am...@google.com> wrote:
>
>> It does look much better!
>>
>> On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay <al...@google.com> wrote:
>>
>>> I like this version, it looks cleaner than the current combined view.
>>>
>>> On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner <sw...@google.com>
>>> wrote:
>>>
>>>> Very cool. I also didn't realize we had control over the Jenkins
>>>> "views".
>>>>
>>>> We currently lack a decent dashboard to monitor the build health across
>>>> Beam jenkins jobs and triage failures; this is a step in the right
>>>> direction.
>>>>
>>>> I haven't played with Jenkins views before, but it appears they can be
>>>> managed via the Job DSL similar to our job definitions [1]:
>>>>
>>>> > The DSL execution engine exposes several methods to create Jenkins
>>>> jobs, views, folders and config files. [..]
>>>>
>>>> It would be cool to integrate this into our job config in such a way
>>>> that we could automatically keep the views up-to-date as jobs are added or
>>>> renamed.
>>>>
>>>> [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
>>>>
>>>> On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin <ke...@google.com> wrote:
>>>>
>>>>> This is really helpful, didn't realize it was possible. Categories and
>>>>> contents look reasonable. I think something like this definitely should be
>>>>> the top-level Beam view.
>>>>>
>>>>> Regards,
>>>>> Anton
>>>>>
>>>>> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I made a new view to split Beam builds into tabs:
>>>>>> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>>>>>>
>>>>>> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron" because
>>>>>> these are actually post-commit jobs; it is a feature not a bug.
>>>>>> - PreCommit tab includes jobs that have no meaningful history
>>>>>> because they are just against PRs, commits, phrase triggering
>>>>>> - Inventory self-explanatory
>>>>>> - PerformanceTests self-explanatory
>>>>>> - All; I didn't want to keep making categories but just send this
>>>>>> for feedback
>>>>>>
>>>>>> WDYT about making this the top-level Beam view? (vs
>>>>>> https://builds.apache.org/view/A-D/view/Beam/)
>>>>>>
>>>>>> After that, maybe we could clean the categories so they fit into the
>>>>>> tabs more easily with fewer regexes (to make sure things don't get missed).
>>>>>> I have read also that if you use / instead of _ as a separator in a name
>>>>>> then Jenkins will display jobs as nested in folders automatically. Not sure
>>>>>> it actually results in a better view; haven't tried it.
>>>>>>
>>>>>> Kenn
>>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>>
>>>>
>>>>
>>>> Got feedback? tinyurl.com/swegner-feedback
>>>>
>>>
>
> --
> -------
> Jason Kuster
> Apache Beam / Google Cloud Dataflow
>
> See something? Say something. go/jasonkuster-feedback
> <https://goto.google.com/jasonkuster-feedback>
>
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Jason Kuster <ja...@google.com>.
This looks great! (also it looks like some precommits snuck into the
postcommit view)
On Tue, Dec 18, 2018 at 1:25 PM Alan Myrvold <am...@google.com> wrote:
> It does look much better!
>
> On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay <al...@google.com> wrote:
>
>> I like this version, it looks cleaner than the current combined view.
>>
>> On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner <sw...@google.com> wrote:
>>
>>> Very cool. I also didn't realize we had control over the Jenkins "views".
>>>
>>> We currently lack a decent dashboard to monitor the build health across
>>> Beam jenkins jobs and triage failures; this is a step in the right
>>> direction.
>>>
>>> I haven't played with Jenkins views before, but it appears they can be
>>> managed via the Job DSL similar to our job definitions [1]:
>>>
>>> > The DSL execution engine exposes several methods to create Jenkins
>>> jobs, views, folders and config files. [..]
>>>
>>> It would be cool to integrate this into our job config in such a way
>>> that we could automatically keep the views up-to-date as jobs are added or
>>> renamed.
>>>
>>> [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
>>>
>>> On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin <ke...@google.com> wrote:
>>>
>>>> This is really helpful, didn't realize it was possible. Categories and
>>>> contents look reasonable. I think something like this definitely should be
>>>> the top-level Beam view.
>>>>
>>>> Regards,
>>>> Anton
>>>>
>>>> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I made a new view to split Beam builds into tabs:
>>>>> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>>>>>
>>>>> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron" because
>>>>> these are actually post-commit jobs; it is a feature not a bug.
>>>>> - PreCommit tab includes jobs that have no meaningful history because
>>>>> they are just against PRs, commits, phrase triggering
>>>>> - Inventory self-explanatory
>>>>> - PerformanceTests self-explanatory
>>>>> - All; I didn't want to keep making categories but just send this for
>>>>> feedback
>>>>>
>>>>> WDYT about making this the top-level Beam view? (vs
>>>>> https://builds.apache.org/view/A-D/view/Beam/)
>>>>>
>>>>> After that, maybe we could clean the categories so they fit into the
>>>>> tabs more easily with fewer regexes (to make sure things don't get missed).
>>>>> I have read also that if you use / instead of _ as a separator in a name
>>>>> then Jenkins will display jobs as nested in folders automatically. Not sure
>>>>> it actually results in a better view; haven't tried it.
>>>>>
>>>>> Kenn
>>>>>
>>>>
>>>
>>> --
>>>
>>>
>>>
>>>
>>> Got feedback? tinyurl.com/swegner-feedback
>>>
>>
--
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow
See something? Say something. go/jasonkuster-feedback
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Alan Myrvold <am...@google.com>.
It does look much better!
On Tue, Dec 18, 2018 at 1:10 PM Ahmet Altay <al...@google.com> wrote:
> I like this version, it looks cleaner than the current combined view.
>
> On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner <sw...@google.com> wrote:
>
>> Very cool. I also didn't realize we had control over the Jenkins "views".
>>
>> We currently lack a decent dashboard to monitor the build health across
>> Beam jenkins jobs and triage failures; this is a step in the right
>> direction.
>>
>> I haven't played with Jenkins views before, but it appears they can be
>> managed via the Job DSL similar to our job definitions [1]:
>>
>> > The DSL execution engine exposes several methods to create Jenkins
>> jobs, views, folders and config files. [..]
>>
>> It would be cool to integrate this into our job config in such a way that
>> we could automatically keep the views up-to-date as jobs are added or
>> renamed.
>>
>> [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
>>
>> On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin <ke...@google.com> wrote:
>>
>>> This is really helpful, didn't realize it was possible. Categories and
>>> contents look reasonable. I think something like this definitely should be
>>> the top-level Beam view.
>>>
>>> Regards,
>>> Anton
>>>
>>> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I made a new view to split Beam builds into tabs:
>>>> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>>>>
>>>> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron" because
>>>> these are actually post-commit jobs; it is a feature not a bug.
>>>> - PreCommit tab includes jobs that have no meaningful history because
>>>> they are just against PRs, commits, phrase triggering
>>>> - Inventory self-explanatory
>>>> - PerformanceTests self-explanatory
>>>> - All; I didn't want to keep making categories but just send this for
>>>> feedback
>>>>
>>>> WDYT about making this the top-level Beam view? (vs
>>>> https://builds.apache.org/view/A-D/view/Beam/)
>>>>
>>>> After that, maybe we could clean the categories so they fit into the
>>>> tabs more easily with fewer regexes (to make sure things don't get missed).
>>>> I have read also that if you use / instead of _ as a separator in a name
>>>> then Jenkins will display jobs as nested in folders automatically. Not sure
>>>> it actually results in a better view; haven't tried it.
>>>>
>>>> Kenn
>>>>
>>>
>>
>> --
>>
>>
>>
>>
>> Got feedback? tinyurl.com/swegner-feedback
>>
>
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Ahmet Altay <al...@google.com>.
I like this version, it looks cleaner than the current combined view.
On Tue, Dec 18, 2018 at 12:53 PM Scott Wegner <sw...@google.com> wrote:
> Very cool. I also didn't realize we had control over the Jenkins "views".
>
> We currently lack a decent dashboard to monitor the build health across
> Beam jenkins jobs and triage failures; this is a step in the right
> direction.
>
> I haven't played with Jenkins views before, but it appears they can be
> managed via the Job DSL similar to our job definitions [1]:
>
> > The DSL execution engine exposes several methods to create Jenkins jobs,
> views, folders and config files. [..]
>
> It would be cool to integrate this into our job config in such a way that
> we could automatically keep the views up-to-date as jobs are added or
> renamed.
>
> [1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
>
> On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin <ke...@google.com> wrote:
>
>> This is really helpful, didn't realize it was possible. Categories and
>> contents look reasonable. I think something like this definitely should be
>> the top-level Beam view.
>>
>> Regards,
>> Anton
>>
>> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> I made a new view to split Beam builds into tabs:
>>> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>>>
>>> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron" because
>>> these are actually post-commit jobs; it is a feature not a bug.
>>> - PreCommit tab includes jobs that have no meaningful history because
>>> they are just against PRs, commits, phrase triggering
>>> - Inventory self-explanatory
>>> - PerformanceTests self-explanatory
>>> - All; I didn't want to keep making categories but just send this for
>>> feedback
>>>
>>> WDYT about making this the top-level Beam view? (vs
>>> https://builds.apache.org/view/A-D/view/Beam/)
>>>
>>> After that, maybe we could clean the categories so they fit into the
>>> tabs more easily with fewer regexes (to make sure things don't get missed).
>>> I have read also that if you use / instead of _ as a separator in a name
>>> then Jenkins will display jobs as nested in folders automatically. Not sure
>>> it actually results in a better view; haven't tried it.
>>>
>>> Kenn
>>>
>>
>
> --
>
>
>
>
> Got feedback? tinyurl.com/swegner-feedback
>
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Scott Wegner <sw...@google.com>.
Very cool. I also didn't realize we had control over the Jenkins "views".
We currently lack a decent dashboard to monitor the build health across
Beam jenkins jobs and triage failures; this is a step in the right
direction.
I haven't played with Jenkins views before, but it appears they can be
managed via the Job DSL similar to our job definitions [1]:
> The DSL execution engine exposes several methods to create Jenkins jobs,
views, folders and config files. [..]
It would be cool to integrate this into our job config in such a way that
we could automatically keep the views up-to-date as jobs are added or
renamed.
[1] https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands
On Tue, Dec 18, 2018 at 12:35 PM Anton Kedin <ke...@google.com> wrote:
> This is really helpful, didn't realize it was possible. Categories and
> contents look reasonable. I think something like this definitely should be
> the top-level Beam view.
>
> Regards,
> Anton
>
> On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org> wrote:
>
>> Hi all,
>>
>> I made a new view to split Beam builds into tabs:
>> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>>
>> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron" because
>> these are actually post-commit jobs; it is a feature not a bug.
>> - PreCommit tab includes jobs that have no meaningful history because
>> they are just against PRs, commits, phrase triggering
>> - Inventory self-explanatory
>> - PerformanceTests self-explanatory
>> - All; I didn't want to keep making categories but just send this for
>> feedback
>>
>> WDYT about making this the top-level Beam view? (vs
>> https://builds.apache.org/view/A-D/view/Beam/)
>>
>> After that, maybe we could clean the categories so they fit into the tabs
>> more easily with fewer regexes (to make sure things don't get missed). I
>> have read also that if you use / instead of _ as a separator in a name then
>> Jenkins will display jobs as nested in folders automatically. Not sure it
>> actually results in a better view; haven't tried it.
>>
>> Kenn
>>
>
--
Got feedback? tinyurl.com/swegner-feedback
Re: [RFC] I made a new tabbed Beam view in Jenkins
Posted by Anton Kedin <ke...@google.com>.
This is really helpful, didn't realize it was possible. Categories and
contents look reasonable. I think something like this definitely should be
the top-level Beam view.
Regards,
Anton
On Tue, Dec 18, 2018 at 12:05 PM Kenneth Knowles <ke...@apache.org> wrote:
> Hi all,
>
> I made a new view to split Beam builds into tabs:
> https://builds.apache.org/view/A-D/view/Beam%20Nested/
>
> - PostCommit tab includes PostCommit and "PreCommit_.*_Cron" because
> these are actually post-commit jobs; it is a feature not a bug.
> - PreCommit tab includes jobs that have no meaningful history because
> they are just against PRs, commits, phrase triggering
> - Inventory self-explanatory
> - PerformanceTests self-explanatory
> - All; I didn't want to keep making categories but just send this for
> feedback
>
> WDYT about making this the top-level Beam view? (vs
> https://builds.apache.org/view/A-D/view/Beam/)
>
> After that, maybe we could clean the categories so they fit into the tabs
> more easily with fewer regexes (to make sure things don't get missed). I
> have read also that if you use / instead of _ as a separator in a name then
> Jenkins will display jobs as nested in folders automatically. Not sure it
> actually results in a better view; haven't tried it.
>
> Kenn
>