Re: 2019 Elections: voting has begun

[Tracy Miranda]

Seems that will adding it additional registrants to the poll, the whole csv
list was added which resulted in resend of the votes.
Fortunately it does not mess up the votes for those who have already voted.

(Adding to list of things for the retro...)

Tracy

On Fri, Nov 15, 2019 at 3:46 PM Richard Bywater  wrote:

> Ah good to know. Didn't want to click on the links in case it messed
> things up :)
>
> Richard.
>
> On Sat, 16 Nov 2019, 9:42 AM Slide,  wrote:
>
>> I received the same thing, but when I clicked on the links, it said I had
>> already voted.
>>
>> On Fri, Nov 15, 2019, 13:37 Richard Bywater  wrote:
>>
>>> A few hours ago I received another three poll emails even though I
>>> previously had voted. Is that expected and/or should I revote?
>>>
>>> Richard.
>>>
>>> On Wed, 13 Nov 2019, 12:52 PM Kohsuke Kawaguchi,  wrote:
>>>
 The voting has begun! It'll remain open until Nov 24th 5pm PT.

 If you have already registered, you should see 3 email in your box for
 3 positions that are contended. Please follow the link in those emails to
 cast your vote. If you haven't registered, you should have already received
 emils to solicit your registration.


 --
 Kohsuke Kawaguchi

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Developers" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yxaxnLwXKC7TCDpCRheCc%3DgDEp3ciZJMfF%3De2yrR5tJQ%40mail.gmail.com
 
 .

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwev8vxNpxJ3fUpun7voie%3DJOkmRYDaF3ZrxZsqhqLuKJw%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVeTncy-q-tsWjKi0EV%2B2VWr0hKzYOoEjQSCTt2zdkvcqg%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwfO%3D0DwwSjR9-c5stW4CtWmRG5w%3DVCEQmYKDA0eu2artw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6r5ri-_%3DX63M1%3DrNd%2Bd4TTiBwiEFTmSjZ2FUD%2BJ5-ZNfg%40mail.gmail.com.

Re: 2019 Elections: voting has begun

[Richard Bywater]

Ah good to know. Didn't want to click on the links in case it messed things
up :)

Richard.

On Sat, 16 Nov 2019, 9:42 AM Slide,  wrote:

> I received the same thing, but when I clicked on the links, it said I had
> already voted.
>
> On Fri, Nov 15, 2019, 13:37 Richard Bywater  wrote:
>
>> A few hours ago I received another three poll emails even though I
>> previously had voted. Is that expected and/or should I revote?
>>
>> Richard.
>>
>> On Wed, 13 Nov 2019, 12:52 PM Kohsuke Kawaguchi,  wrote:
>>
>>> The voting has begun! It'll remain open until Nov 24th 5pm PT.
>>>
>>> If you have already registered, you should see 3 email in your box for 3
>>> positions that are contended. Please follow the link in those emails to
>>> cast your vote. If you haven't registered, you should have already received
>>> emils to solicit your registration.
>>>
>>>
>>> --
>>> Kohsuke Kawaguchi
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yxaxnLwXKC7TCDpCRheCc%3DgDEp3ciZJMfF%3De2yrR5tJQ%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwev8vxNpxJ3fUpun7voie%3DJOkmRYDaF3ZrxZsqhqLuKJw%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVeTncy-q-tsWjKi0EV%2B2VWr0hKzYOoEjQSCTt2zdkvcqg%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwfO%3D0DwwSjR9-c5stW4CtWmRG5w%3DVCEQmYKDA0eu2artw%40mail.gmail.com.

Re: 2019 Elections: voting has begun

[Slide]

I received the same thing, but when I clicked on the links, it said I had
already voted.

On Fri, Nov 15, 2019, 13:37 Richard Bywater  wrote:

> A few hours ago I received another three poll emails even though I
> previously had voted. Is that expected and/or should I revote?
>
> Richard.
>
> On Wed, 13 Nov 2019, 12:52 PM Kohsuke Kawaguchi,  wrote:
>
>> The voting has begun! It'll remain open until Nov 24th 5pm PT.
>>
>> If you have already registered, you should see 3 email in your box for 3
>> positions that are contended. Please follow the link in those emails to
>> cast your vote. If you haven't registered, you should have already received
>> emils to solicit your registration.
>>
>>
>> --
>> Kohsuke Kawaguchi
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yxaxnLwXKC7TCDpCRheCc%3DgDEp3ciZJMfF%3De2yrR5tJQ%40mail.gmail.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwev8vxNpxJ3fUpun7voie%3DJOkmRYDaF3ZrxZsqhqLuKJw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVeTncy-q-tsWjKi0EV%2B2VWr0hKzYOoEjQSCTt2zdkvcqg%40mail.gmail.com.

Re: Where to place utility code used in several plugins?

[Jesse Glick]

On Fri, Nov 15, 2019 at 12:57 PM Ullrich Hafner
 wrote:
> What is the preferred way of handling theses classes? Should I create two new 
> modules (util and plugin-utill) that will host theses classes?

Keep it simple. The latter should be a plugin
(`hpi`), and both should be hosted in
@jenkinsci.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3GdcF9ocUKf4Kx81ZjbzVHWDxsQVaG9-CCAqEStMFXEw%40mail.gmail.com.

Re: 2019 Elections: voting has begun

[Richard Bywater]

A few hours ago I received another three poll emails even though I
previously had voted. Is that expected and/or should I revote?

Richard.

On Wed, 13 Nov 2019, 12:52 PM Kohsuke Kawaguchi,  wrote:

> The voting has begun! It'll remain open until Nov 24th 5pm PT.
>
> If you have already registered, you should see 3 email in your box for 3
> positions that are contended. Please follow the link in those emails to
> cast your vote. If you haven't registered, you should have already received
> emils to solicit your registration.
>
>
> --
> Kohsuke Kawaguchi
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yxaxnLwXKC7TCDpCRheCc%3DgDEp3ciZJMfF%3De2yrR5tJQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwev8vxNpxJ3fUpun7voie%3DJOkmRYDaF3ZrxZsqhqLuKJw%40mail.gmail.com.

Where to place utility code used in several plugins?

[Ullrich Hafner]

I have some classes that I would like to use in several of my Jenkins plugins. 
Some classes are depending on Jenkins core, some classes only use JRE 
dependencies. Up to now I duplicated these classes by copying them into the 
corresponding plugins -  but this is ugly and error prone.

What is the preferred way of handling theses classes? Should I create two new 
modules (util and plugin-utill) that will host theses classes? Or is this just 
overkill? Or should I better host them in my GitHub account and publish them to 
Maven central (or any other hosting service) on my own?  




Legend:
- blue: my existing plugins
- yellow: my existing library (hosted in jenkisci)
- orange: my planned libraries (plugin-util has Jenkins dependency, util not)
 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/A979E227-9A95-451D-A9E8-AA8F34CDD22F%40gmail.com.

Re: Modularization of UI modules

[Ullrich Hafner]

I just to report back here on how I finally implemented the modularization of 
the JS modules: for each JS dependency I created a new api plugin that contains 
the WebJar of the JS library and some utility classes. So other plugins can use 
these dependencies as well now. The resulting plugin dependencies are given in 
the following UML diagram: 




Legend: 
- blue: my plugins
- green: API plugins for JS libraries 
- yellow: standard Java library

I’m currently beta testing these new libraries, an example implementation is 
available in PR https://github.com/jenkinsci/warnings-ng-plugin/pull/252 

> Am 08.07.2019 um 07:24 schrieb 'Gavin Mogan' via Jenkins Developers 
> :
> 
> https://github.com/jenkinsci/graphql-server-plugin/pull/4 
>  is doing a 
> wishlist item with parceljs
> 
> On Sun, Jul 7, 2019 at 4:10 PM Gavin Mogan  > wrote:
> I don't have fond memories of js-builder from working on blueocean.
> 
> Personally I still think larger bundle sizes for an app like this is fine, so 
> using webpack or parcel or something to embed all the libraries you need 
> directly will take care of the version problem.
> 
> If you have a simple web app, I can submit a PR or try to setup a sample 
> plugin at some point.
> 
> https://parceljs.org/recipes.html  will 
> let you use commonjs, so its just requiring, no worrying about what other 
> plugins are doing.
> 
> Gavin
> 
> On Sun, Jul 7, 2019 at 2:20 PM Ullrich Hafner  > wrote:
> Yes, I tried that last year. But I got stuck somewhere in between (see 
> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/jenkinsci-dev/1nb5UDiUjeI/h6f38kTiBgAJ
>  
> ).
>  So I finally gave up since nobody was there to help. Also, looking at the 
> commit history, it indicates that this approach is dead as well :-(
> 
> 
>> Am 07.07.2019 um 20:32 schrieb Daniel Beck > >:
>> 
>> 
>> 
>>> On 2. Jul 2019, at 16:12, Jesse Glick >> > wrote:
>>> 
>>> Read
>>> 
>>> https://github.com/jenkinsci/js-libs 
>>> 
>>> and you will know more than I.
>> 
>> There's also https://github.com/jenkinsci/js-samples 
>>  which looks like it might be 
>> useful?
>> 
>> Step 4 looks potentially relevant?
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-dev+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/382F79BF-6618-4E97-8E1E-CA892BB0A381%40beckweb.net
>>  
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/3B172B21-751B-4660-8561-966B8C2CB15C%40gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvnS%3DaNwvqYCpAXL1EaaS9CrTvFQKR2Xq3hXviGS2-Cfg%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: 2019 Elections: voting is delayed

[Jakub Bocheński]

Found https://issues.jenkins-ci.org/browse/INFRA-2319

On Friday, November 15, 2019 at 5:26:56 PM UTC+1, Jakub Bocheński wrote:
>
> Hi, I tried to register
> After recovering the email from my spam folder I clicked "I want to 
> participate" but I get an error
>
> > Your participation can't be confirmed, please contact a Jenkins 
> administrator
>
> Is this the right place to "contact a Jenkins administrator"?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7a3d8496-3d06-4684-b20d-e2610d1544a6%40googlegroups.com.

Re: 2019 Elections: voting is delayed

[Jakub Bocheński]

Hi, I tried to register
After recovering the email from my spam folder I clicked "I want to 
participate" but I get an error

> Your participation can't be confirmed, please contact a Jenkins 
administrator

Is this the right place to "contact a Jenkins administrator"?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3a60df4f-91c0-4c05-b23e-01652b96e93a%40googlegroups.com.

Re: Proposal: Jenkins Browser Support policy updates

[Matt Sicker]

FWIW, I've written any new JS/HTML/CSS according to caniuse.com and their
base line supported level, though that might be fairly conservative (not as
conservative as the current Jenkins wiki, though!)

On Fri, Nov 15, 2019 at 8:15 AM Daniel Beck  wrote:

> I think Firefox ESR would make sense to support as well. Its baseline is
> never older than a year IIUC, so should be feasible to have it be
> considered supported.
>
> Showing warnings on the UI when using an unsupported browser would
> probably be fairly straightforward as well, and help to inform users.
> Perhaps we even distinguish between "outdated based on policy" and
> "outdated based on features actually used in core or popular plugins", but
> that may end up being too much effort to maintain.
>
>
> Does it actually make sense to still support IE?
>
> On Fri, Nov 15, 2019 at 10:17 AM Oleg Nenashev 
> wrote:
>
>> Hi all,
>>
>> There was recently a question about Jenkins browser support policy raised
>> in the chats. Currently the policy is hosted on Wiki (here
>> ),
>> and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully
>> supported, ouch. It does not look like we had any major changes since the
>> inception of the policy in 2014. I have created a pull reques
>> t to move the
>> policy to jenkins.io, and I would like to make some changes to actualize
>> it.
>>
>> What do I propose?
>>
>>- Chrome, Firefox, IE, Safari
>>   - Level 1:
>>  - "Latest regular release, latest minor release / patch level"
>>   - Level 2:
>>  - Previous patches of the latest regular release
>>  - Latest minor release / patch level  for the "Version -1"
>>   - Level 3:
>>  - All other versions
>>   - Other browsers, including mobile versions, Chromium, Microsoft
>>EDGE, etc.:
>>   - Level 2: Latest regular release, latest minor release / patch
>>   level
>>   - Level 3: All other versions
>>
>>
>> This policy should be somewhat aligned with the current ATH state. IIUC
>> we test only Firefox now, and there is a PR by Oliver Gondza to run tests
>> on Chrome instead (here
>> )
>>
>> WDYT?
>>
>> Best regards,
>> Oleg
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com
>> 
>> .
>>
>
>
> --
>
> Daniel Beck
> Senior Software Engineer
> CloudBees, Inc.
>
> [image: CloudBees-Logo.png]
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKGPEqv9gaVT%2BX%3DoXT%2Busp3RhA%3DfBgcHaWD0hrt8MPdaQ%40mail.gmail.com
> 
> .
>


-- 
Matt Sicker
Senior Software Engineer, CloudBees

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oyaa7gXJpdQ1aFh6Kd89cDQ8MMQJWDxhkmLdpkjH5J_Ew%40mail.gmail.com.

Re: Proposal: Jenkins Browser Support policy updates

[Daniel Beck]

I think Firefox ESR would make sense to support as well. Its baseline is
never older than a year IIUC, so should be feasible to have it be
considered supported.

Showing warnings on the UI when using an unsupported browser would probably
be fairly straightforward as well, and help to inform users. Perhaps we
even distinguish between "outdated based on policy" and "outdated based on
features actually used in core or popular plugins", but that may end up
being too much effort to maintain.


Does it actually make sense to still support IE?

On Fri, Nov 15, 2019 at 10:17 AM Oleg Nenashev 
wrote:

> Hi all,
>
> There was recently a question about Jenkins browser support policy raised
> in the chats. Currently the policy is hosted on Wiki (here
> ),
> and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully
> supported, ouch. It does not look like we had any major changes since the
> inception of the policy in 2014. I have created a pull reques
> t to move the
> policy to jenkins.io, and I would like to make some changes to actualize
> it.
>
> What do I propose?
>
>- Chrome, Firefox, IE, Safari
>   - Level 1:
>  - "Latest regular release, latest minor release / patch level"
>   - Level 2:
>  - Previous patches of the latest regular release
>  - Latest minor release / patch level  for the "Version -1"
>   - Level 3:
>  - All other versions
>   - Other browsers, including mobile versions, Chromium, Microsoft
>EDGE, etc.:
>   - Level 2: Latest regular release, latest minor release / patch
>   level
>   - Level 3: All other versions
>
>
> This policy should be somewhat aligned with the current ATH state. IIUC we
> test only Firefox now, and there is a PR by Oliver Gondza to run tests on
> Chrome instead (here
> )
>
> WDYT?
>
> Best regards,
> Oleg
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com
> 
> .
>


-- 

Daniel Beck
Senior Software Engineer
CloudBees, Inc.

[image: CloudBees-Logo.png]

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKGPEqv9gaVT%2BX%3DoXT%2Busp3RhA%3DfBgcHaWD0hrt8MPdaQ%40mail.gmail.com.

Re: Proposal: Jenkins Browser Support policy updates

[Baptiste Mathus]

+1 on the update of the policy. All for dropping explicit "support" for
older browsers. (support

I love the idea to actually have something like an Administrative warning
to tell users that they may see UI quirks given the browser they're using.
And that they should feel free to report them iff these quirks are also
present on latest browser versions.

+1 on supporting temporarily only the very latest version of IE, and maybe
have a blurb saying this is planned to be discontinued given MS plans
anyway to invest into Edge instead.

Le ven. 15 nov. 2019 à 11:44, 'Björn Pedersen' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Hi,
>
> sounds reasonable in general.
>
> What  another project (https://github.com/indico/indico/releases/tag/v2.2
> ):
>
>> *Drop support for Internet Explorer 11 and other outdated or discontinued
>> browser versions.* Indico shows a warning message when accessed using
>> such a browser. The latest list of supported browsers can be found in
>> the README , but
>> generally Indico now supports the last two versions of each major browser
>> (determined at release time), plus the current Firefox ESR.
>>
>
> So support one  version back at level 1 ( this means also that before
> using bleeding edge browser features they have settled for at least on
> release).
>
> I suggest to also add a js warning plugin (e.g.
> https://github.com/outdatedbrowser/outdated-browser) to jenkins to give
> the users a better feedback for unsupported browsers.
>
> Björn
>
>
> Am Freitag, 15. November 2019 10:17:10 UTC+1 schrieb Oleg Nenashev:
>>
>> Hi all,
>>
>> There was recently a question about Jenkins browser support policy raised
>> in the chats. Currently the policy is hosted on Wiki (here
>> ),
>> and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully
>> supported, ouch. It does not look like we had any major changes since the
>> inception of the policy in 2014. I have created a pull reques
>> t to move the
>> policy to jenkins.io, and I would like to make some changes to actualize
>> it.
>>
>> What do I propose?
>>
>>- Chrome, Firefox, IE, Safari
>>   - Level 1:
>>  - "Latest regular release, latest minor release / patch level"
>>   - Level 2:
>>  - Previous patches of the latest regular release
>>  - Latest minor release / patch level  for the "Version -1"
>>   - Level 3:
>>  - All other versions
>>   - Other browsers, including mobile versions, Chromium, Microsoft
>>EDGE, etc.:
>>   - Level 2: Latest regular release, latest minor release / patch
>>   level
>>   - Level 3: All other versions
>>
>>
>> This policy should be somewhat aligned with the current ATH state. IIUC
>> we test only Firefox now, and there is a PR by Oliver Gondza to run tests
>> on Chrome instead (here
>> )
>>
>> WDYT?
>>
>> Best regards,
>> Oleg
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/97fa0774-e4a3-4698-bfc4-94006dd51af2%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5vxUiUchuVyYkaoGQ9peM%3D8H%2BbRy7dZpUXziNMji1TKQ%40mail.gmail.com.

Re: speed your Jenkins by an adapter of Jenkins update center

[Rick]

What I'm talking about is not the internal mirror. The mirror is public. I
just set up one mirror on GitHub which is
https://github.com/jenkins-zh/update-center-mirror/tree/master/tsinghua.

On Fri, Nov 15, 2019 at 7:46 PM Oliver Gondža  wrote:

> I suspect few people would bother to report (accurate) numbers there.
> Setting up internal mirror is the part that needs to be done and this is
> the kind of bonus task that always gets outprioritized. IMO.
>
> On 15/11/2019 12.14, Rick wrote:
> > Hi Björn,
> >
> > It's true that those download statistics cannot be count. What about
> > building a third party statistic site. And we can publish this data
> > besides the official one as a reference. What do you think about this?
> >
> > Best,
> > Rick
> >
> > On Fri, Nov 15, 2019 at 6:52 PM 'Björn Pedersen' via Jenkins Developers
> > mailto:jenkinsci-dev@googlegroups.com>>
>
> > wrote:
> >
> > Hi,
> >
> > So the idea is to omit the round-trip to the main update center on
> > each download. Community-wise this has one downside: all those
> > downloads then do not show up in the download statistics.
> > But the same is true for all fully private mirrors behind firewalls
> > that serve updatecenter.json  with internal urls.
> >
> >
> > Björn
> >
> > Am Donnerstag, 14. November 2019 13:45:11 UTC+1 schrieb Rick:
> >
> > Hi Baptiste,
> >
> > Thanks for your response. Jenkins download the plugin by the URL
> > which comes from update-center.json. For example this plugin
> >
> http://updates.jenkins-ci.org/download/plugins/AnchorChain/1.0/AnchorChain.hpi
> .
> >
> > The problem is that it’s too slow for me. I hope jenkins can
> > download it from
> >
> https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins/AnchorChain/1.0/AnchorChain.hpi
> .
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to jenkinsci-dev+unsubscr...@googlegroups.com
> > .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/4e01b094-d310-448c-9706-6ed526a36e52%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/4e01b094-d310-448c-9706-6ed526a36e52%40googlegroups.com?utm_medium=email_source=footer
> >.
> >
> >
> >
> > --
> > Zhao Xiaojie (Rick)
> > Blog: https://github.com/LinuxSuRen
> > Twitter: https://twitter.com/suren69811254
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to jenkinsci-dev+unsubscr...@googlegroups.com
> > .
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF%3Ddk69exkvWN0Tv6rsdDa0cbcCLDSHaf8KxTsqKdgdRg%40mail.gmail.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF%3Ddk69exkvWN0Tv6rsdDa0cbcCLDSHaf8KxTsqKdgdRg%40mail.gmail.com?utm_medium=email_source=footer
> >.
>
>
> --
> oliver
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/2e072c53-8421-a371-f9d5-4e53e5c88cd3%40gmail.com
> .
>


-- 
Zhao Xiaojie (Rick)
Blog: https://github.com/LinuxSuRen
Twitter: https://twitter.com/suren69811254

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTGUKxgoWERq%2B1Cyx9bSUdiNDRwSskLc32h-FBt2W7%3DB%3DQ%40mail.gmail.com.

Re: speed your Jenkins by an adapter of Jenkins update center

[Oliver Gondža]

I suspect few people would bother to report (accurate) numbers there. 
Setting up internal mirror is the part that needs to be done and this is 
the kind of bonus task that always gets outprioritized. IMO.


On 15/11/2019 12.14, Rick wrote:

Hi Björn,

It's true that those download statistics cannot be count. What about 
building a third party statistic site. And we can publish this data 
besides the official one as a reference. What do you think about this?


Best,
Rick

On Fri, Nov 15, 2019 at 6:52 PM 'Björn Pedersen' via Jenkins Developers 
mailto:jenkinsci-dev@googlegroups.com>> 
wrote:


Hi,

So the idea is to omit the round-trip to the main update center on
each download. Community-wise this has one downside: all those
downloads then do not show up in the download statistics.
But the same is true for all fully private mirrors behind firewalls
that serve updatecenter.json  with internal urls.


Björn

Am Donnerstag, 14. November 2019 13:45:11 UTC+1 schrieb Rick:

Hi Baptiste,

Thanks for your response. Jenkins download the plugin by the URL
which comes from update-center.json. For example this plugin

http://updates.jenkins-ci.org/download/plugins/AnchorChain/1.0/AnchorChain.hpi.

The problem is that it’s too slow for me. I hope jenkins can
download it from

https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins/AnchorChain/1.0/AnchorChain.hpi.


-- 
You received this message because you are subscribed to the Google

Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/4e01b094-d310-448c-9706-6ed526a36e52%40googlegroups.com

.



--
Zhao Xiaojie (Rick)
Blog: https://github.com/LinuxSuRen
Twitter: https://twitter.com/suren69811254

--
You received this message because you are subscribed to the Google 
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-dev+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF%3Ddk69exkvWN0Tv6rsdDa0cbcCLDSHaf8KxTsqKdgdRg%40mail.gmail.com 
.



--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2e072c53-8421-a371-f9d5-4e53e5c88cd3%40gmail.com.

Re: speed your Jenkins by an adapter of Jenkins update center

[Rick]

Hi Björn,

It's true that those download statistics cannot be count. What about
building a third party statistic site. And we can publish this data besides
the official one as a reference. What do you think about this?

Best,
Rick

On Fri, Nov 15, 2019 at 6:52 PM 'Björn Pedersen' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi,
>
> So the idea is to omit the round-trip to the main update center on each
> download. Community-wise this has one downside: all those downloads then do
> not show up in the download statistics.
> But the same is true for all fully private mirrors behind firewalls that
> serve updatecenter.json  with internal urls.
>
>
> Björn
>
> Am Donnerstag, 14. November 2019 13:45:11 UTC+1 schrieb Rick:
>>
>> Hi Baptiste,
>>
>> Thanks for your response. Jenkins download the plugin by the URL which
>> comes from update-center.json. For example this plugin
>> http://updates.jenkins-ci.org/download/plugins/AnchorChain/1.0/AnchorChain.hpi
>> .
>>
>> The problem is that it’s too slow for me. I hope jenkins can download it
>> from
>> https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins/AnchorChain/1.0/AnchorChain.hpi
>> .
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/4e01b094-d310-448c-9706-6ed526a36e52%40googlegroups.com
> 
> .
>


-- 
Zhao Xiaojie (Rick)
Blog: https://github.com/LinuxSuRen
Twitter: https://twitter.com/suren69811254

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTF%3Ddk69exkvWN0Tv6rsdDa0cbcCLDSHaf8KxTsqKdgdRg%40mail.gmail.com.

Re: speed your Jenkins by an adapter of Jenkins update center

['Björn Pedersen' via Jenkins Developers]

Hi, 

So the idea is to omit the round-trip to the main update center on each 
download. Community-wise this has one downside: all those downloads then do 
not show up in the download statistics. 
But the same is true for all fully private mirrors behind firewalls that 
serve updatecenter.json  with internal urls.


Björn

Am Donnerstag, 14. November 2019 13:45:11 UTC+1 schrieb Rick:
>
> Hi Baptiste,
>
> Thanks for your response. Jenkins download the plugin by the URL which 
> comes from update-center.json. For example this plugin 
> http://updates.jenkins-ci.org/download/plugins/AnchorChain/1.0/AnchorChain.hpi
> .
>
> The problem is that it’s too slow for me. I hope jenkins can download it 
> from 
> https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins/AnchorChain/1.0/AnchorChain.hpi
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4e01b094-d310-448c-9706-6ed526a36e52%40googlegroups.com.

Re: Proposal: Jenkins Browser Support policy updates

['Björn Pedersen' via Jenkins Developers]

Hi, 

sounds reasonable in general. 

What  another project (https://github.com/indico/indico/releases/tag/v2.2):

> *Drop support for Internet Explorer 11 and other outdated or discontinued 
> browser versions.* Indico shows a warning message when accessed using 
> such a browser. The latest list of supported browsers can be found in the 
> README , but generally 
> Indico now supports the last two versions of each major browser (determined 
> at release time), plus the current Firefox ESR.
>

So support one  version back at level 1 ( this means also that before using 
bleeding edge browser features they have settled for at least on release).

I suggest to also add a js warning plugin (e.g. 
https://github.com/outdatedbrowser/outdated-browser) to jenkins to give the 
users a better feedback for unsupported browsers.

Björn


Am Freitag, 15. November 2019 10:17:10 UTC+1 schrieb Oleg Nenashev:
>
> Hi all,
>
> There was recently a question about Jenkins browser support policy raised 
> in the chats. Currently the policy is hosted on Wiki (here 
> ), 
> and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully 
> supported, ouch. It does not look like we had any major changes since the 
> inception of the policy in 2014. I have created a pull reques 
> t to move the 
> policy to jenkins.io, and I would like to make some changes to actualize 
> it.
>
> What do I propose?
>
>- Chrome, Firefox, IE, Safari
>   - Level 1: 
>  - "Latest regular release, latest minor release / patch level"
>   - Level 2: 
>  - Previous patches of the latest regular release
>  - Latest minor release / patch level  for the "Version -1" 
>   - Level 3:
>  - All other versions
>   - Other browsers, including mobile versions, Chromium, Microsoft 
>EDGE, etc.:
>   - Level 2: Latest regular release, latest minor release / patch 
>   level
>   - Level 3: All other versions
>
>
> This policy should be somewhat aligned with the current ATH state. IIUC we 
> test only Firefox now, and there is a PR by Oliver Gondza to run tests on 
> Chrome instead (here 
> )
>
> WDYT?
>
> Best regards,
> Oleg
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/97fa0774-e4a3-4698-bfc4-94006dd51af2%40googlegroups.com.

Re: Proposal: Jenkins Browser Support policy updates

[Oliver Gondža]

On 15/11/2019 10.17, Oleg Nenashev wrote:

Hi all,

There was recently a question about Jenkins browser support policy 
raised in the chats. Currently the policy is hosted on Wiki (here 
), 
and the policy looks to be REALLY old. E.g. we say that Safari 6+ are 
fully supported, ouch. It does not look like we had any major changes 
since the inception of the policy in 2014. I have created a pull reques 
t to move the 
policy to jenkins.io, and I would like to make some changes to actualize it.


What do I propose?

  * Chrome, Firefox, IE, Safari
  o Level 1:
  + "Latest regular release, latest minor release / patch level"
  o Level 2:
  + Previous patches of the latest regular release
  + Latest minor release / patch level  for the "Version -1" 
  o Level 3:

  + All other versions
  * Other browsers, including mobile versions, Chromium, Microsoft EDGE,
etc.:
  o Level 2: Latest regular release, latest minor release / patch level
  o Level 3: All other versions


This policy should be somewhat aligned with the current ATH state. IIUC 
we test only Firefox now, and there is a PR by Oliver Gondza to run 
tests on Chrome instead (here 
)


WDYT?


It makes sense to me up date it this way - especially getting rid of the 
explicit versions so this does not get outdated so easily.


Speaking of ATH, there is not enough hands to mirror the support matrix 
and test the UI on all supported browsers - not even those from level 1. 
We have started tentatively looking into replacing FF with chrome as the 
only browser we test with to (hopefully) improve the stability and 
(certainly) improve the test relevance.


--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6438b52c-9ac7-49d4-5056-ae1c6c921ac6%40gmail.com.

Re: Proposal: Jenkins Browser Support policy updates

[Richard Bywater]

Personally I think Microsoft Edge (Chromium) should be Level 1 as it will
be coming out in January and, as far as I know, will be the default browser
for Windows 10 (or at least be used quite a bit). I'd also say that given
its Chromium based I'd include that and Chromium together along with
Chrome.

I'd also suggest dropping IE although perhaps that's slightly too early?

Richard.

On Fri, 15 Nov 2019 at 22:17, Oleg Nenashev  wrote:

> Hi all,
>
> There was recently a question about Jenkins browser support policy raised
> in the chats. Currently the policy is hosted on Wiki (here
> ),
> and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully
> supported, ouch. It does not look like we had any major changes since the
> inception of the policy in 2014. I have created a pull reques
> t to move the
> policy to jenkins.io, and I would like to make some changes to actualize
> it.
>
> What do I propose?
>
>- Chrome, Firefox, IE, Safari
>   - Level 1:
>  - "Latest regular release, latest minor release / patch level"
>   - Level 2:
>  - Previous patches of the latest regular release
>  - Latest minor release / patch level  for the "Version -1"
>   - Level 3:
>  - All other versions
>   - Other browsers, including mobile versions, Chromium, Microsoft
>EDGE, etc.:
>   - Level 2: Latest regular release, latest minor release / patch
>   level
>   - Level 3: All other versions
>
>
> This policy should be somewhat aligned with the current ATH state. IIUC we
> test only Firefox now, and there is a PR by Oliver Gondza to run tests on
> Chrome instead (here
> )
>
> WDYT?
>
> Best regards,
> Oleg
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcsMWRvSQKs%3Dr4M8K2Dj-KL3NYNfYNOV4LaKO4QG4sFeA%40mail.gmail.com.

Proposal: Jenkins Browser Support policy updates

[Oleg Nenashev]

Hi all,

There was recently a question about Jenkins browser support policy raised 
in the chats. Currently the policy is hosted on Wiki (here 
), 
and the policy looks to be REALLY old. E.g. we say that Safari 6+ are fully 
supported, ouch. It does not look like we had any major changes since the 
inception of the policy in 2014. I have created a pull reques 
t to move the policy 
to jenkins.io, and I would like to make some changes to actualize it.

What do I propose?

   - Chrome, Firefox, IE, Safari
  - Level 1: 
 - "Latest regular release, latest minor release / patch level"
  - Level 2: 
 - Previous patches of the latest regular release
 - Latest minor release / patch level  for the "Version -1" 
  - Level 3:
 - All other versions
  - Other browsers, including mobile versions, Chromium, Microsoft 
   EDGE, etc.:
  - Level 2: Latest regular release, latest minor release / patch level
  - Level 3: All other versions
   

This policy should be somewhat aligned with the current ATH state. IIUC we 
test only Firefox now, and there is a PR by Oliver Gondza to run tests on 
Chrome instead (here 
)

WDYT?

Best regards,
Oleg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/976db98b-75be-4e29-9bd4-d5fe6676c674%40googlegroups.com.