Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[Jesse Glick]

On Thu, Dec 1, 2016 at 3:08 AM, ogondza  wrote:
> is JDK 7 support really blocking us somewhere? Bugs
> we cannot fix / need to awkwardly compensate, features we can not deliver on
> Java 7?

Of course not. It just slows down developers trying to work on new
things in the name of supporting an old system most users are not
running (or need not run) and which we do not really test on anyway.

> you can run agent on older Java version but it causes subtle
> problems.

It will not work at all—you will get `ClassFormatError`s. If you
really need to build some projects on obsolete operating systems, you
can run the Jenkins agent on a normal computer, then SSH into an old
box or use VirtualBox or Docker or whatever to do the actual build
steps.

> plugin manager offers plugin updates
> (perhaps even core ones) that require newer Java version than the one
> installed on master

Yes there is a long-filed RFE to include the minimum JRE requirement
in plugin metadata. In the meantime,

> there is no guarantee plugin that needs Java 8
> require core with same requirement.

plugin authors are strongly advised to build against the same Java
Platform version as that used as a minimum by their minimum core
dependency. Thus, for example, you may delete

6

in your POM (and so go to the default of 7) when you update your
baseline to 1.625.x or later.

-- 
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/CANfRfr3fjWf%2BLgxM4%3Dy5eFarNHxs26J5WB-AN%2BNJnZQyJ%2BHwnw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: PR and release pending. Reverse Proxy Auth. Plugin

[Baptiste Mathus]

Hello, this is not exactly how it works. Please make sure to show you've
tried to contact existing/previous maintainers. Adding her/them/him in CC
(better look at latest commits than at the wiki page, this last one is
almost always wrong...)

I've adjusted the documentation a bit here:
https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess
This is to reflect what we have actually been doing for at least one or two
years.

Thanks

2016-12-01 13:22 GMT+01:00 Emilio Escobar :

> Hello,
>
> There are two PR waiting for merge some weeks/month ago...
>
> https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/29
> https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/28
>
> I have asked to the maintainer at PR and here at the group for merging the
> code. As I had no replies, can anyone give me the permissions? I will
> maintain the plugin, my id is: escoem
>
> Thanks!
>
> On Monday, November 7, 2016 at 9:25:09 PM UTC+1, Jesse Glick wrote:
>>
>> On Wed, Nov 2, 2016 at 7:32 AM, Emilio Escobar  wrote:
>> > There is a PR https://github.com/jenkinsci/r
>> everse-proxy-auth-plugin/pull/28
>> > waiting for merge two weeks ago
>>
>> And my #29 may fix a gigantic performance problem.
>>
> --
> 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/5be0b836-068d-4c50-9699-4ad2bc6dae84%
> 40googlegroups.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/CANWgJS4544RcrT9aQBM1ZpOwZ3J-uk6gsD83qquLq-z4nDY6sw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to reload configuration of Folder property after Jenkins restart

[yairogen]

Izek, do you see your configuration in the files?
Anything in the log files?

On Thursday, December 1, 2016 at 2:12:59 PM UTC+2, Izek Greenfield wrote:
>
> When I save the configuration of the folder and reload it all is ok and it 
> loads the configuration 
>
> but if I restart the Jenknis instance it does not reload the configuration 
> I see the new configuration config.xml file.
>

-- 
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/3e6e3890-fea7-4f01-b01b-d748c366d967%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PR and release pending. Reverse Proxy Auth. Plugin

[Emilio Escobar]

Hello, 

There are two PR waiting for merge some weeks/month ago...

https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/29
https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/28

I have asked to the maintainer at PR and here at the group for merging the 
code. As I had no replies, can anyone give me the permissions? I will 
maintain the plugin, my id is: escoem

Thanks!

On Monday, November 7, 2016 at 9:25:09 PM UTC+1, Jesse Glick wrote:
>
> On Wed, Nov 2, 2016 at 7:32 AM, Emilio Escobar  > wrote: 
> > There is a PR 
> https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/28 
> > waiting for merge two weeks ago 
>
> And my #29 may fix a gigantic performance problem. 
>

-- 
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/5be0b836-068d-4c50-9699-4ad2bc6dae84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Failed to reload configuration of Folder property after Jenkins restart

[Izek Greenfield]

When I save the configuration of the folder and reload it all is ok and it 
loads the configuration 

but if I restart the Jenknis instance it does not reload the configuration 
I see the new configuration config.xml file.

-- 
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/247a84d7-9ef9-489b-90c3-520e32f5814a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Thanks for commit access and the information.

Nothing opposed to a fork so lets go with that route to simplify things. The 
people whom I will be sharing work with are colleagues so we can share a fork 
and keep things separate.

Really appreciate all the help.

> On 1 Dec 2016, at 13.19, Daniel Beck  wrote:
> 
> 
>> On 01.12.2016, at 12:13, Jacob Larfors  wrote:
>> 
>> Awesome - looks good. Can I also have commit access to this one, or how do 
>> we plan to do this?
>> 
>> My plan was to create an update branch on this repo and then file a pull 
>> request to get this into master and include the Jenkins reviewers as Oleg 
>> suggested.
>> 
>> GitHub user: jlarfors 
> 
> Granted you commit access.
> 
> Plan sounds reasonable if it's supposed to be a branch that multiple people 
> would work on (or if you're opposed to maintaining your own fork), but most 
> probably develop in their own fork first and base PRs on that. It also won't 
> confuse the JIRA bot as it thinks everything in the jenkinsci repos is on 
> master, and even resolves issues based on that :-)
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/U7SFVsjsHHQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/503C9858-35E9-4770-9913-2BCA949CF01C%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/8AA06AD0-4C02-4AD2-8A8F-98454CE177AD%40larfors.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Daniel Beck]

> On 01.12.2016, at 12:13, Jacob Larfors  wrote:
> 
> Awesome - looks good. Can I also have commit access to this one, or how do we 
> plan to do this?
> 
> My plan was to create an update branch on this repo and then file a pull 
> request to get this into master and include the Jenkins reviewers as Oleg 
> suggested.
> 
> GitHub user: jlarfors 

Granted you commit access.

Plan sounds reasonable if it's supposed to be a branch that multiple people 
would work on (or if you're opposed to maintaining your own fork), but most 
probably develop in their own fork first and base PRs on that. It also won't 
confuse the JIRA bot as it thinks everything in the jenkinsci repos is on 
master, and even resolves issues based on that :-)

-- 
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/503C9858-35E9-4770-9913-2BCA949CF01C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Awesome - looks good. Can I also have commit access to this one, or how do we 
plan to do this?

My plan was to create an update branch on this repo and then file a pull 
request to get this into master and include the Jenkins reviewers as Oleg 
suggested.

GitHub user: jlarfors 

Sent from my iPhone

> On 1 Dec 2016, at 13.02, Daniel Beck  wrote:
> 
> 
>> On 01.12.2016, at 11:34, Jacob Larfors  wrote:
>> 
>> All good to delete the jenkinsci/klocwork-plugin-fork repo as it was never 
>> used.
> 
> Done, and transferred the one with issues and PRs:
> 
> https://github.com/jenkinsci/klocwork-plugin
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/U7SFVsjsHHQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/FE1A646F-3671-4635-B1C0-480BB9E91F60%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/EFB2862A-CE2B-49C0-B530-F664ABBB498E%40larfors.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Daniel Beck]

> On 01.12.2016, at 11:34, Jacob Larfors  wrote:
> 
> All good to delete the jenkinsci/klocwork-plugin-fork repo as it was never 
> used.

Done, and transferred the one with issues and PRs:

https://github.com/jenkinsci/klocwork-plugin

-- 
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/FE1A646F-3671-4635-B1C0-480BB9E91F60%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

 

All good to delete the jenkinsci/klocwork-plugin-fork repo as it was never 
used.

On Thursday, 1 December 2016 12:32:59 UTC+2, Daniel Beck wrote:
>
>
> > On 01.12.2016, at 11:17, Jacob Larfors  
> wrote: 
> > 
> > Great, I acknowledge and sounds like a good idea - so please go ahead. 
>
> Hmmm that didn't work… 
>
> "jenkinsci already has a repository in the 
> jenkinsci-transfer/klocwork-plugin network" 
>
> It looks like I'll have to delete the repo we already have (now named 
> klocwork-plugin-fork) first. It doesn't look like it contains anything that 
> the original we're transferring doesn't, but can you please confirm? 
>
>

-- 
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/401b8ce3-8b1c-4f76-87c8-f489f46306cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Daniel Beck]

> On 01.12.2016, at 11:17, Jacob Larfors  wrote:
> 
> Great, I acknowledge and sounds like a good idea - so please go ahead.

Hmmm that didn't work…

"jenkinsci already has a repository in the jenkinsci-transfer/klocwork-plugin 
network"

It looks like I'll have to delete the repo we already have (now named 
klocwork-plugin-fork) first. It doesn't look like it contains anything that the 
original we're transferring doesn't, but can you please confirm?

-- 
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/EC3F0B71-FD7F-4D15-830A-EA048B6526DD%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Request ownership/action for a plugin (klocwork)

[Jacob Larfors]

Great, I acknowledge and sounds like a good idea - so please go ahead.

Thanks,
Jacob

On Wednesday, 30 November 2016 21:03:00 UTC+2, Daniel Beck wrote:
>
>
> > On 28.11.2016, at 17:44, Jacob Larfors  
> wrote: 
> > 
> > Awesome, and thanks Daniel & Gregory. 
>
> We have control over the klocwork plugin. It currently resides in 
>
> https://github.com/jenkinsci-transfer/klocwork-plugin 
>
> I'll rename the existing repo and move this one into jenkinsci as soon as 
> you acknowledge; as it'll be the same remote URL in Git and could cause 
> confusion when I do this unexpectedly. 
>
>

-- 
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/776b057a-b65f-4631-a959-aa850a948830%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[Oleg Nenashev]

The plan looks good to me.
I'm also thinking about dropping the .NET 2.0 support in Windows installer
and windows-slave-installer. If we drop Java 7, I would like to join the
party and to announce the .NET2 and 3.5 deprecation and selection of .NET4
as a baseline.

.NET 4 is 5 years old && available on Operating systems including the
latest Windows XP service pack. The situation with Embedded Windows
versions is a bit worse, so we may still impact a particular subset of
users.

If there is no strong -1s, I will start a standalone discussion of it.

P.S: Maybe we also want to discontinue support of Windows 32 bit systems
and other such stuff. But it's very debatable

2016-12-01 9:08 GMT+01:00 ogondza :

> I am undecided on the subject. There clearly always are reasons to use
> newer/better version but is JDK 7 support really blocking us somewhere?
> Bugs we cannot fix / need to awkwardly compensate, features we can not
> deliver on Java 7?
>
> I felt much stronger against dropping Java 6 as we identified several
> architecture/OS combinations with no Java 7+ vendor making the platforms
> (RHEL4, itanium architecture, Solaris 9 (IIRC)) not usable as Jenkins
> nodes. (Yes, you can run agent on older Java version but it causes subtle
> problems.) However, oracle does not seem to drop any of the platforms (at
> least those we care for) between 7 and 8.
>
> What we can do right now, to make this a bit less troublesome to users and
> easier to digest for community, is creating a general time plan for
> dropping support of JDKs (or other things) we would follow in specific
> cases. Something like:
>
> - Month 0: Announce the intention publicly, with this plan attached.
> - Month 3: Drop support for Jenkins weekly. Declare what LTS will be the
> last one to support the think we are dropping. Since we gave people time to
> get prepared, we do not have to try hard to prolong the support in LTS
> branch. IOW, I see no reason to do whole new LTS line after the support was
> dropped for weeklies.
> - Month 3-5: LTS.1 with support dropped is released.
> - Month 12?: In case of Java, encourage the use from plugins / use it as
> default. Extending the support in plugins allow people to consume plugin
> updates/fixes after upstream has dropped support without upgrading Java.
> This is especially subtle as IIRC plugin manager offers plugin updates
> (perhaps even core ones) that require newer Java version than the one
> installed on master, and there is no guarantee plugin that needs Java 8
> require core with same requirement.
>
> --
> oliver
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/fo5nKLhZK5U/unsubscribe.
> To unsubscribe from this group and all its topics, 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/503afa20-4e4d-4aad-91d4-e28439cf269c%
> 40googlegroups.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/CAPfivLDDGCuJoRbay_LifVP%3DEpxtJ0bMdMwCTUE88SL0ppG7Uw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[ogondza]

I am undecided on the subject. There clearly always are reasons to use 
newer/better version but is JDK 7 support really blocking us somewhere? 
Bugs we cannot fix / need to awkwardly compensate, features we can not 
deliver on Java 7?

I felt much stronger against dropping Java 6 as we identified several 
architecture/OS combinations with no Java 7+ vendor making the platforms 
(RHEL4, itanium architecture, Solaris 9 (IIRC)) not usable as Jenkins 
nodes. (Yes, you can run agent on older Java version but it causes subtle 
problems.) However, oracle does not seem to drop any of the platforms (at 
least those we care for) between 7 and 8.

What we can do right now, to make this a bit less troublesome to users and 
easier to digest for community, is creating a general time plan for 
dropping support of JDKs (or other things) we would follow in specific 
cases. Something like:

- Month 0: Announce the intention publicly, with this plan attached.
- Month 3: Drop support for Jenkins weekly. Declare what LTS will be the 
last one to support the think we are dropping. Since we gave people time to 
get prepared, we do not have to try hard to prolong the support in LTS 
branch. IOW, I see no reason to do whole new LTS line after the support was 
dropped for weeklies.
- Month 3-5: LTS.1 with support dropped is released.
- Month 12?: In case of Java, encourage the use from plugins / use it as 
default. Extending the support in plugins allow people to consume plugin 
updates/fixes after upstream has dropped support without upgrading Java. 
This is especially subtle as IIRC plugin manager offers plugin updates 
(perhaps even core ones) that require newer Java version than the one 
installed on master, and there is no guarantee plugin that needs Java 8 
require core with same requirement.

--
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/503afa20-4e4d-4aad-91d4-e28439cf269c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.