Fwd: [JENKINS] - Removal of top level views

[Davor Bonaci <da...@apache.org>]

We need to move our top-level view [1] into the A-D view [2].

Any volunteers willing to code this view in the Jenkins DSL?

Davor

[1] https://builds.apache.org/view/Beam/
[2] https://builds.apache.org/view/A-D/view/Beam/

---------- Forwarded message ----------
From: Gavin McDonald <ga...@16degrees.com.au>
Date: Sun, Apr 30, 2017 at 1:19 AM
Subject: [JENKINS] - Removal of top level views
To: builds@apache.org
Cc: users@infra.apache.org


Hi All,

We are starting to get complaints about the amount of top level views in
our Jenkins instance.

I believe it is time for cleanup of those views once more.

A few years ago, I cleaned up a heap of views and got quite some complaints
from projects
about doing so, without consultation, and the fact that this breaks links
some projects use.

Since that time however, projects have continued to create new Top Level
views and now
we are at a stage where again there are too many - there are currently 22
project type views.

There are many more projects and I’d hate for this trend to continue
upwards and clutter the
main Jenkins landing page even more.

I have created an INFRA ticket to track this at :

https://issues.apache.org/jira/browse/INFRA-14002

The views I propose to remove are :

Airavata, Apache Commons, Apex, Beam Brooklyn, Calciate, CarbonData, DL,
Groovy, Hawq, Infra Jobs Monitor View, Lucene, OWB, Olingo, OpenJPA, POI,
Shiro, Tamaya, Tika, XMLGraphics. cloudstack, directory

Also: All the single letter viewss from A to Z. They are not much used and
it is preferred to use 'A-D', 'E-G', 'H-L', 'M-R' and 'S-Z'

Two Views unsure what to do with are: 'Incubator Projects' and 'PreCommit
Builds'


Some views have already been removed, I removed one called ‘jobs I have
access to’ or something like that, the Maven project also removed their top
level views so my thanks to them.
The Infra jobs monitor view is one I created, my fault and Im going to move
it under H-L where it belongs.

ACTION NEEDED:- Please, could all project who are listed above as having a
top level view, please move it to a view under the appropriate letters
group, or remove it.

The two Im not sure about ‘Incubator Projects’ and ‘PreCommit Builds’ ,
‘Incubator Projects’ may be a benefit at top level if used correctly.
‘PreCommit Builds’ is not one owned by any one project, Im unsure whether
this could stay top level and be a benefit.

I’ll be moving the Infra views shortly.

If, after a week, there are still projects at the top level view, I’ll move
onto the next step of mailing the projects dev lists directly, though that
should not be required if they have the representation on this list.

Thanks in advance.

I’ll keep the INFRA-14002 ticket updated with progress.

Gav… (ASF Infra.)

Re: [JENKINS] - Removal of top level views

[Jason Kuster <ja...@google.com.INVALID>]

I'm happy to do it, or help out if someone else is interested.

On Sun, Apr 30, 2017 at 9:27 PM, Davor Bonaci <da...@apache.org> wrote:

> We need to move our top-level view [1] into the A-D view [2].
>
> Any volunteers willing to code this view in the Jenkins DSL?
>
> Davor
>
> [1] https://builds.apache.org/view/Beam/
> [2] https://builds.apache.org/view/A-D/view/Beam/
>
> ---------- Forwarded message ----------
> From: Gavin McDonald <ga...@16degrees.com.au>
> Date: Sun, Apr 30, 2017 at 1:19 AM
> Subject: [JENKINS] - Removal of top level views
> To: builds@apache.org
> Cc: users@infra.apache.org
>
>
> Hi All,
>
> We are starting to get complaints about the amount of top level views in
> our Jenkins instance.
>
> I believe it is time for cleanup of those views once more.
>
> A few years ago, I cleaned up a heap of views and got quite some complaints
> from projects
> about doing so, without consultation, and the fact that this breaks links
> some projects use.
>
> Since that time however, projects have continued to create new Top Level
> views and now
> we are at a stage where again there are too many - there are currently 22
> project type views.
>
> There are many more projects and I’d hate for this trend to continue
> upwards and clutter the
> main Jenkins landing page even more.
>
> I have created an INFRA ticket to track this at :
>
> https://issues.apache.org/jira/browse/INFRA-14002
>
> The views I propose to remove are :
>
> Airavata, Apache Commons, Apex, Beam Brooklyn, Calciate, CarbonData, DL,
> Groovy, Hawq, Infra Jobs Monitor View, Lucene, OWB, Olingo, OpenJPA, POI,
> Shiro, Tamaya, Tika, XMLGraphics. cloudstack, directory
>
> Also: All the single letter viewss from A to Z. They are not much used and
> it is preferred to use 'A-D', 'E-G', 'H-L', 'M-R' and 'S-Z'
>
> Two Views unsure what to do with are: 'Incubator Projects' and 'PreCommit
> Builds'
>
>
> Some views have already been removed, I removed one called ‘jobs I have
> access to’ or something like that, the Maven project also removed their top
> level views so my thanks to them.
> The Infra jobs monitor view is one I created, my fault and Im going to move
> it under H-L where it belongs.
>
> ACTION NEEDED:- Please, could all project who are listed above as having a
> top level view, please move it to a view under the appropriate letters
> group, or remove it.
>
> The two Im not sure about ‘Incubator Projects’ and ‘PreCommit Builds’ ,
> ‘Incubator Projects’ may be a benefit at top level if used correctly.
> ‘PreCommit Builds’ is not one owned by any one project, Im unsure whether
> this could stay top level and be a benefit.
>
> I’ll be moving the Infra views shortly.
>
> If, after a week, there are still projects at the top level view, I’ll move
> onto the next step of mailing the projects dev lists directly, though that
> should not be required if they have the representation on this list.
>
> Thanks in advance.
>
> I’ll keep the INFRA-14002 ticket updated with progress.
>
> Gav… (ASF Infra.)
>



-- 
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow