Re: Changing LTS baseline in buildPlugin.recommendedConfigurations() on ci.jenkins.io

On Thu, Aug 29, 2019 at 11:24 AM Oleg Nenashev wrote: > Dependabot + pom.xml definition should be our target goal. Not quite sure what you are proposing here. Some kind of POM profile to test against newer stuff? I was actually proposing something completely different (but perhaps

Re: Changing LTS baseline in buildPlugin.recommendedConfigurations() on ci.jenkins.io

I agree with all points, Jesse. Dependabot + pom.xml definition should be our target goal. I am just not sure we ready to source versions in such way immediately. One of the major issues is lack of the node step where we can retrieve and process POM.xml >From the resources standpoint, it would

Re: Changing LTS baseline in buildPlugin.recommendedConfigurations() on ci.jenkins.io

On Thu, Aug 29, 2019 at 10:33 AM Gavin wrote: > it means a plugin doesn't work the same on newer versions Possibly, but much more commonly it just means some _test_ does not work the same on newer versions of Jenkins, sometimes for pretty minor technical reasons. Yes that ought to get fixed, but

Re: Changing LTS baseline in buildPlugin.recommendedConfigurations() on ci.jenkins.io

I'm okay breaking CI for plugins because it means a plugin doesn't work the same on newer versions and that seems bad to me. On Thu., Aug. 29, 2019, 6:34 a.m. Jesse Glick, wrote: > On Thu, Aug 29, 2019 at 5:42 AM Oleg Nenashev > wrote: > > Bump the version, potentially break CI for plugins

Re: Changing LTS baseline in buildPlugin.recommendedConfigurations() on ci.jenkins.io

On Thu, Aug 29, 2019 at 5:42 AM Oleg Nenashev wrote: > Bump the version, potentially break CI for plugins (Jesse's PR) > Pin the version, allow overriding it (Baptiste's PR) > Reject both PRs, keep status quo and old Jenkins core until a > plugin-repo-side suggestion is implemented by somebody

Re: Preparing your modules/library/plugin to be consumed by dependabot

Thanks for the investigation Gavin! I plan to document Dependabot usage guidelines eventually, and I will make sure to reflect it It can be also added to https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc somehow. BR, Oleg On Thursday, August 29, 2019 at 2:19:45 AM

Re: Hosting process

As long as the transfer process is automated, +100 for that. It should also help to avoid issues when contributor companies request hosting but then continue development in their own repos (no finger-pointing in this thread). On Wednesday, August 28, 2019 at 8:58:13 PM UTC+2, Gavin Mogan wrote:

Re: Next LTS line selection open. Due 2019-08-27

Hi Oliver, Could you please let us know what is your decision about the LTS baseline? Thanks in advance, Oleg On Wednesday, August 28, 2019 at 1:59:11 PM UTC+2, Mark Waite wrote: > > +1 from me to choose 2.190 as the baseline. > > On Wednesday, August 28, 2019 at 7:39:31 AM UTC-4, Oleg Nenashev

Changing LTS baseline in buildPlugin.recommendedConfigurations() on ci.jenkins.io

Hi all, I have a question about changing the Jenkins LTS versions in buildPlugin.recommendedConfigurations() which is a part of the Jenkins Pipeline Library . This is a utility method which provides a list of the recommended configurations for