Re: Backporting for LTS 2.462.2 started

-candidate ORDER BY summary ASC, resolved ASC On Thursday, August 15, 2024 at 3:19:53 PM UTC+1 James Nord wrote: > https://issues.jenkins.io/browse/JENKINS-73404 is missing from the > candidate query as it has no resolution? > > > On Thursday, August 15, 2024 at 3:04:59 PM UTC+1

Re: Backporting for LTS 2.462.2 started

https://issues.jenkins.io/browse/JENKINS-73404 is missing from the candidate query as it has no resolution? On Thursday, August 15, 2024 at 3:04:59 PM UTC+1 Mark Waite wrote: > On Wednesday, August 14, 2024 at 1:48:01 PM UTC-6 Alex Brandes wrote: > > Hey everyone, > > Backporting for 2.462.2 ha

Re: Windows-arm64 native support

> Java 9 introduced richer process control APIs which might suffice for the particular use cases in Jenkins Alas much of that is unimplemented on windows. Don't know why as it is available as winp prooved.. (Command line and arguments for one, ability to gracefully kill (aka ctrl-c?)) Given that

Re: Banned dependencies error compiling SAML plugin PR

All the supporting code for providing a warning about this has been removed from the update center and Jenkins IIRC. So you will have no warning when you try and install the plugin - but it will blow up at runtime if you try and use it. Which is probably not a good idea for a critical plugin li

Re: build-blocker-plugin pending PR

Hi Olivier, There is a process to adopt the plugin which is described in in https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/ (this would be an abandoned plugin) So you need to wait 2 weeks (normally) bit as this is the summer holiday period in the northern hemisphere it may

Re: JSON license

If you are obtaining the pom from the hpi, then as you have the hpi why not just see what version if any is in the plugin (WEB-INF/lib/)? Transitive or not if the jar is provided by another plugin then it really doesn't matter and as you said maven doesn't understand the Jenkins plugin dependent

Re: Cannot run Testcontainers on "ci.jenkins.io / Tests / windows-11 / Build (windows-11)"

Test containers should work, so that seems like a bug in test containers . At least there should be a valid container runtime on the non containerised agents. However... The containers on the windows agent are currently set to Windows containers not Linux ones, so even if they worked it could be

Re: Delay while agent launching

You need to keep track of what provisioning requests you have in flight (that have not failed) and then act accordingly when called by looking at the CloudState https://javadoc.jenkins.io/hudson/slaves/Cloud.html#provision(hudson.slaves.Cloud.CloudState,int) By single shot I am taking it you mean

minimum / required maven version

Hi all, What are peoples thoughts on being more (obviously) aggressive on the required maven version for plugins? Currently we set a requirement in the plugin-pom on 3.8.1 so we do not allow http repositories but nothing else is "enforced". I say enforced as we actually have implied but not resp

Re: Next baseline shift

unlucky /James On Wed, 30 Nov 2022, 03:47 Basil Crow, wrote: > On Tue, Nov 29, 2022 at 3:19 PM James Nord wrote: > > > > This bytecode difference trips up spotbugs (causing several new false > positives) that have no option other than to be suppressed, so this change > will lik

Re: Servlet container support (was: Nov 28, 2022 Governance Board Agenda)

> Not sure if there was a thread somewhere in which this topic was discussed in writing, but my personal recommendation would be to formally drop support for running in a general servlet container, so that you could only use the bundled Winstone/Jetty via `java -jar jenkins.war` (we could even drop

Re: Next baseline shift

> Independently of that, we can consider switching the default JDK for ci.jenkins.io `buildPlugin` from 8 to 11. Even if your plugin supports older baselines and Java 8, running the build on JDK 11 is typically fine, since `-release 8` will ensure the right bytecode and even prevent the infamous `B

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

+1 On Thu, 13 Oct 2022 at 20:16, Pedro Amaral wrote: > +1 > > On Thu, Oct 13, 2022 at 10:12 AM 'Kevin Martens' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > >> +1 from me too! >> >> On Thu, Oct 13, 2022 at 5:52 AM 'Olblak' via Jenkins Developers < >> jenkinsci-dev@googlegro

winp maintainer

Hi all, Jenkins has a dependency on https://github.com/kohsuke/winp but it now seems like there is no one active in the project that can release it. ( https://github.com/kohsuke/winp/pull/69#pullrequestreview-867992611). Has anyone got the inclination and time and environment to want to step up

Re: Question regarding transitive plugin dependencies and security advisories

Hi Adam You don't have to do anything. Mostly as a security release of a plugin should not break API compatability. If someone installs your plugin then Jenkins will if the mailer plugin is not installed install the latest from the update center that it knows about You can choose to update th

Re: Dropping support for IE 11

Given Edge is Chromium based would it make sense to promote that to tier 1 at the same time to leave a platform default browser with T1 comparability / support? It's much less likely to be broken than Safari based on comparability charts. As such I would have no issue dropping IE support should

Re: Annotation versions

Iirc configuration-as-code plugin blew up when core no longer shipped the spotbugs annotations. The plugin pom probably needs to remove a lot of cruft that makes it work with older release now. The spotbugs annotations are source retention not runtime so unclear if that could cause tools issue

Re: Enabling Continuous Delivery / automated release process for Gradle project

But my point is the flatten plugin confuses tools and is awkward for many. Using MRP as I described would not confuse any tool as it would reqrite a pom as happens today. I'm also confused now as you are using MRP which the referenced comment is about. On Tuesday, 14 December 2021 at 18:57

Re: Getting 409 Conflict for CD GHA

Your project also contains SNAPSHOT dependencies so that should not be deployed as a release either. It should fail the build (not sure if it actually does right now though, but if not you should expect it to in the future. https://github.com/jenkinsci/keeper-secrets-manager-plugin/blob/main/po

Re: Hacktoberfest CI Load

Many thanks Damien! /James On Tue, 12 Oct 2021, 09:39 Damien Duportal, wrote: > Hello James! > > Thanks for the reminder and the bump. > > We saw the peak this morning: The ATH is not using container agents (Is it > because it uses Docker, a bunch of memory or both?) but VMs of kind > "higmem".

Re: How to deal with class update and serialization of Jenkins configurations

PR 229 only seemed to change the jelly - the persisted data (if no one saved it) is still looking like it is using the old projectId so existing things should still work, but newly saved configuration would likely not persist correctly. Change the Jelly option back to projectId and also change the

Re: Coverage reporting stops with plugin parent pom 4.27?

I've just take a look at 4.27 and yes it's broken. It shouldn't be setting the Argeline to surefire without including any other argkine ('@{argLine} newopts' iirc. Currently this will break a few different things, including din setting the surefire JVM args from a repository .mvn file.l as well a

Re: Plugins using removed Guava APIs

Thanks Basil, The operations center ones are released in lock step with a new LTS version, so I wouldn't worry too much about regressions there. We have internal tickets to track all the work (we had previously focused on the OSS part as we knew it would take longer due to not being maintainers

Re: ASM in core

Thanks for investigating further on this Basil! /James On Fri, 11 Jun 2021 at 16:00, Basil Crow wrote: > On Fri, Jun 11, 2021 at 2:19 AM Robert Sandell > wrote: > > > > Some historical context to know where we "old timers" are coming from :) > > https://kohsuke.org/2012/03/03/potd-package-rena

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

I am against a digester API plugin as it is not really something that should be used and by making a plugin-api we make that somewhat offical. We took a quicker path of bumping the digester usage to support 3 than remove / replace it entirely. as there are only a few plugins using this I think inl

Re: Plugins using removed Guava APIs

> > I merged usage in plugins this morning, so unless you need it released in > some way you shouldn't need that > Many thanks Tim! On Fri, 7 May 2021 at 16:08, Tim Jacomb wrote: > > remember is uses a PR not master of usage in plugins so it will find > usage in libraries too! > > I merged usa

Re: Jenkins 3.x

> We do not have a fresh new massive story to share. At the same time there could be a few changes to highlight: - Adoption of Configuration-as-Code as a recommended way to manage Jenkins. - Making emphasis on Jenkins-in-the-cloud applications and packaging, with making Docker/Helm/etc

Re: Core Baseline Java8 -> Java11?

> and it also natively supports TLS 1.3 which is fairly important for HTTPS as well as for securing inbound remoting agents. FTR that should be available in recent OpenJDK releases. https://bugs.openjdk.java.net/browse/JDK-8245466 On Fri, 4 Dec 2020 at 16:35, Matt Sicker wrote: > It may be i

Re: Jenkins 3.x

> if we go for 3.x, should we also change the versioning scheme? Can this come later? I think any discussions regarding versioning schemes should go together with a proper deprecation & removal policy. We could use this chance, for example, to say "we're removing prototypejs in 2 years, by version

Jenkins 3.x

Hi all, with the recent weeklies we have a couple of changes (Acegi upgrade/table-to-div) that break compatibility in plugins. Whilst many open source plugins have been updated and made compatible with the old and new version by the people making the changes (and compatability layers have been

Re: Plugin adoption request: bitbucket-branch-source

> Starting 2021 Atlassian will not sell any new Lizences for Bitbucket Server and EOL is February 2024 ( https://www.atlassian.com/de/software/bitbucket/download). AFAICT BitBucket DataCenter edition will still exist but you will require a DataCenter licence (and have to cough up more $$$) and

Re: sqlplus-script-runner help - MS Windows issue

are you using the ArgumentListBuilder and addMasked https://javadoc.jenkins-ci.org/hudson/util/ArgumentListBuilder.html#addMasked-java.lang.String- as per https://javadoc.jenkins-ci.org/hudson/Launcher.html#launch-- if not you need to tell Jenkins that the nth argument should be masked (but you

Re: Availability of Oliver Gondža in late 2020 and onward

Thank you for your contributions over the years and congratulations on the impending arrivals to your family! /James On Thursday, 22 October 2020 at 16:45:22 UTC+1 alytong13 wrote: > Congratulations on the arrival of the twins, Oliver. I'm so excited for > you and your family! > Thank you so m

Re: API to render links with RepositoryBrowser

there is also the link for the URL in the changeling which is controlled by the RepositoryBrowser implementation. https://javadoc.jenkins.io/hudson/scm/RepositoryBrowser.html. On Wednesday, 16 September 2020 at 06:28:45 UTC+1 timja...@gmail.com wrote: > I think it’s this: > > https://javadoc

Re: unable to transition Jira issue(s)

ssue that isn’t broken, and then file an >> INFRA ticket asking admins to delete all of the duplicates. See >> https://issues.jenkins-ci.org/browse/INFRA-2581 as an example. >> >> On Jul 6, 2020, at 10:26, James Nord > >> wrote: >> >> Hi all, >> >

unable to transition Jira issue(s)

Hi all, for some reason I can not close some specific Jira issues (other issues are fine)? anything in the following query seems like it can not change state : https://issues.jenkins-ci.org/browse/JENKINS-61646?jql=summary%20~%20%22attempt%20reconnect%22%20and%20component%20%3D%20kubernetes-cred

Re: Terminology Updates

how about monolith 🤔 for the 'master' it may be modular in terms of plugins and architecture but it's not micro services. whilst some parts (fingerprint storage, artifact storage) are pluggable we still have the one big thing. other equally bizarre / useful suggestions include: * comptroller *

Re: GitHub issues option in HOSTING

> am I missing something in this thread security reports? currently they are all triaged by the security team so the team can track disclosure deadlines etc. how would that worknif the plugin is usimg GH issues? (yes I know gh issues can now handle security reports but does that mean the secu

Re: Terminology Updates

you correctly Pou ted out my examples where rubbish. but you can not talk about the Jenkins server and know what the other is talking about without saying, you mean Linux or the java process thing it's a recepie for disaster or turning 2 words into 6 every time you want to use it. today sure we

Re: Terminology Updates

Jenkins server is ambiguous it has as many minus votes as I can put (limited to one) login to the Jenkins server and run service start Jenkins. login to the Jenkins server and create a new job whatever we choose it can not be confused with the host/is/server/machine that the is process run

Re: GitHub issues option in HOSTING

I agree with Ulli's statements. There seems to be comments that our hosted Jira is sluggish or hard to maintain. I've asked before but why can,t the cloud version be an option? we should be able to spin up a stateless SAML to LDAP integration for Jira Cloud with much less effort than continuing

Re: Proposal: Windows support policy for Jenkins

I'm not sure it's just a technical issue. last I was working in this area there where licensing issues around running Windows 10 in VMs (when you run the windows Amis in Aws you also pay the license for the software, same for GCP Azure etc). Thus we would need to have our own licenses for all

Re: Plugin Licenses

ugin with > severe license violations. > > BR, Oleg > > > On Mon, Apr 27, 2020 at 10:32 AM James Nord > wrote: > >> the license in the pom only refers to source code in that repo, not the >> plugin. >> >> the plugin can include many dependencies that

Re: best ide

eclipse is generally ok - but sometimes it doesn't run the annotation processor so Extensions don't get the correct information generated and then they don't show up when debugging... dropping to the command line to run mvn clean package -DskipTests works for me. I've had issues with IntelliJ

undeprecate Run.getAbsoluteUrl()

As per title... its unclear to me why AbstractItem.getAbsoluteUrl would be ok but Run.getAbsoluteUrl would not, now would Item.getAbsoluteUrl() Either they should all be deprecated or none should be. When sending links to external services (mail / slack / Irc etc) it is a requirement to have t

Re: Plugin Licenses

the license in the pom only refers to source code in that repo, not the plugin. the plugin can include many dependencies that are licensed differently (which is why the about page for a plugin shows much more than the top level license for a plugin). Also i hate to say it but those pesky JavaSc

Re: plugin parent 4.0

> What I do not understand yet: do I still need to set the profile > -Duse-jenkins-bom no. is that still documented somewhere? if so I need to remove it -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and s

Re: plugin parent 4.0

my experience is the same as Ulli. never had an issue with linkage or class not found, and spend a lot of time fixing upper bounds to keep the enforcer rule happy (probably wrongly but if it keeps it happy) (hence the introduction of the jenkins BOM) -- You received this message because you

Re: plugin parent 4.0

many thanks Tim /James -- 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 visi

Re: Prevent building branches/PRs existing before the first branch indexing (Branch API plugin)

> > I fixed this by adding the only build matching branches to be 'master > > Stable-* PR-*' > > Regexes can’t always help with this. > This doesn't prevent building branches after the job creation. correct but it will build interesting branches not dangling ones. > If I inform developers that

Re: Prevent building branches/PRs existing before the first branch indexing (Branch API plugin)

what scm prilovider are you using? I fixed this by adding the only build matching branches to be 'master Stable-* PR-*' this builds only the branches matching any one of those. the PR-* matches pull requests in GitHub (even if they are from a branch called wibble). obviously you should tune

Re: Move the LTS baseline selection to take place 2 weeks earlier in the cycle

👍 from me -- 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://gro

Re: JSR-305

missing annotation classes do not cause a class loading issue and so the class referencing them should load fine. when someone bumps core in their plugin they will still (today) have the annotations via transitive dependency however they /may/ need to update their own plugins where they overrid

Re: JSR-305

On Thursday, 26 March 2020 21:27:59 UTC, Jesse Glick wrote: > > The main obstacle was that the available annotations in the > `edu.umd.cs.findbugs.annotations` package were all `@Deprecated` and > told you to use `javax.annotation`, so we would be peppering the > source code with deprecation w

How to Change Plugin Name - Remote File Plugin

change the 'name' element in pom.xml. you will also need to change any references you have in the plugin (index.jelly for example). just don't change the artifactId as this will make it a new plugin. -- You received this message because you are subscribed to the Google Groups "Jenkins Develop

windows builds of core

I'm trying to test a patch locally and well lets just say it does not look like Jenkins is healthy - even on master... Can we please add a windows stage back into the core CI build? If you need help with this I am happy to help out. /James -- You received this message because you are subscrib

Re: JSR-305

the 3 Nonnegative annotations - I'm going to remove them - let's have some conversation in the soon to be submitted PR :) /James On Thursday, 26 March 2020 11:38:48 UTC, James Nord wrote: > > Hi all, > > its been on my TODO list for a while to remove JSR-305 annotations from &

Git plugin 5.0 require Jenkins 2.190.3

> Are there pitfalls or problems that I have not considered in making the > Jenkins version required by git plugin 5.0 be Jenkins 2.190.3? did you think of potential security issues and the need to to backport to the 4.x line so that older (commercially supported) LTS lines can upgrade? -- You

JSR-305

Hi all, its been on my TODO list for a while to remove JSR-305 annotations from core. the reason behind this is 1) the framework is deader than a dodo 2) the annotations have a questionable licence 3) the annotations are in the reserved javax namespace and there is no public release of the spe

plugin patent 4.0

Hi Oleg et al. is it time to move the plugin parent out of beta? have not seen any negative feedback (or positive door that matter) but I've been using it for numerous proprietary plugins with no issue. /James -- You received this message because you are subscribed to the Google Groups "Jenk

Re: findsecbugs in spotbugs

> James, you're talking about the plugin parent pom, right? The current PR is > for the Jenkins pom, which is currently at 1.55-SNAPSHOT. yes you are completely correct, my apologies. > Any idea when we'll move forward to the 4.0 release of the plugin pom? -- You received this message because

Re: findsecbugs in spotbugs

I would rather this did not get merged until after the 4.0 release of pom and have left further comment in the pr about the lack of reasonable opt out. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and sto

regression in hpi:run?

Hi all, Has anyone else seen or aware of an issue with context reloading in `hpi:run` in the latest (3.13) hpi plugin version? basically pressing enter in the console to reload caused the following: INFO: Starting the installation of jackson2-api on behalf of anonymous Mar 16, 2020 11:19:20 AM

Re: Assigning Labels to Plugins

> Skip labels provided by parents - When a plugin depends on another plugin, > the dependency will be installed automatically. A label is not required on > the dependency if the consuming plugin has the label but if the parent can be used without the child (extension) then how does that parent

Re: Heads-up: Jenkins 2.221 weekly release delay

o think it would be a shame to buy have these (disabled by default) improvements available for experimenting with in the next LTS so I am plus one for a mid week release. that said and switching topic slightly should we start releasing every change from master as a new version? -- You received

Re: GitHub issues option in HOSTING

>With jira, I'm either auto assigned the issue due to whatever component was >first picked, or nothing at all. Groups of maintainers can't be notified. >Un-assigned tickets don't get notified create a filter that matches things you want to be notified for. subscribe to that filter in https://is

Re: GitHub issues option in HOSTING

I generally agree with Ulli's comments. so far we are all talking about the developer experience when interacting with issues. we need to also think of the user experience to Jenkins users too. it kills me every time I need to file an issue and try and work out where it is to be reported and

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

On Wednesday, January 22, 2020 at 1:24:05 AM UTC, Michael Cirioli wrote: > > (moving this discussion from https://github.com/jenkinsci/jep/pull/261 in > order to have more visibility) > > JEP-223 : "Limited Administer" permission > and JEP-

Re: Jenkins Plugin pom (future of)

know and I will file an INFRA ticket and try and get them cleaned up). /James On Tuesday, January 21, 2020 at 2:42:23 PM UTC, James Nord wrote: > > Never mind, several of the retrospective BOMs are garbage because I used a > non local parent and the resolved parent is flattened so the p

Re: Jenkins Plugin pom (future of)

good solutions. /James On Tuesday, January 21, 2020 at 2:32:38 PM UTC, James Nord wrote: > > do you have a PR I can checkout locally? > > > On Monday, January 20, 2020 at 10:13:54 PM UTC, Ullrich Hafner wrote: >> >> Ok, thanks. 2.164 would be ok for me. >> >

Re: Jenkins Plugin pom (future of)

t; [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, > please read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingExcepti

Re: Beta releases of new UI modules available

hides the orginal JUnit chart but that would be kind of hack...) > > > > Am 16.01.2020 um 22:36 schrieb James Nord >: > > > > I was looking at how old and outdated the junit test result charts > looked next to you new charts. > > ild love to try and update jun

Re: Jenkins Plugin pom (future of)

On Friday, January 17, 2020 at 1:28:09 PM UTC, James Nord wrote: > > > On Friday, January 17, 2020 at 12:46:15 PM UTC, Ullrich Hafner wrote: >> >> Would its make sense to remove that part from the pom until we have older >> Jenkins versions supported? Otherwise we wi

Re: Jenkins Plugin pom (future of)

s one has not been implemented yet IIUC. +1 for doing so >> >> BR, Oleg >> >> >> On Friday, December 27, 2019 at 2:23:15 PM UTC+1, Oleg Nenashev wrote: >>> >>> 4.0-beta-1 is here: >>> https://github.com/jenkinsci/plugin-pom/releases/tag/p

Beta releases of new UI modules available

I was looking at how old and outdated the junit test result charts looked next to you new charts. ild love to try and update junit charts but that you is in the core so I feel this would be a step to far for my lack of frontend skills. but amazing results! -- You received this message because

Re: retrospecitvly publishing the jenkins bom

gt; > Fine with me. > Probably we should think about renaming components to "core-bom" and > "plugin-bom" to stop creating confusion > > On Monday, December 23, 2019 at 1:50:19 PM UTC+1, James Nord wrote: >> >> Created >> https://github.com/jenkins-infra/r

Re: retrospecitvly publishing the jenkins bom

ly available core BOM's > > On Wed, Oct 30, 2019 at 4:35 PM James Nord > wrote: > >> So I shall take silence as create a PR and be damned :) >> >> On Monday, October 21, 2019 at 7:04:37 PM UTC+1, Jesse Glick wrote: >>> >>> On Mon, Oct 21, 2019

Re: Jenkins Plugin pom (future of)

opic . It is a pretty big change inside the > core, and Parent POM > > I wonder if it would make sense to integrate SpotBugs (and CheckStyle) >> into the verify phase as well. So plugin developers will get the results >> automatically by running mvn verify (or

Re: Jenkins Plugin pom (future of)

jenkinsci/maven/plugins/hpi/RunMojo.java#L775-L780>) or am I missing something? /James On Thursday, December 12, 2019 at 9:23:55 PM UTC, James Nord wrote: > > Hi all, > > firstly apologies about the recent messiness with consuming the jenkins > bom <https://github.com/jenki

Re: Jenkins Plugin pom (future of)

On Friday, December 13, 2019 at 3:34:05 PM UTC, Jesse Glick wrote: > > On Thu, Dec 12, 2019 at 4:24 PM James Nord > wrote: > > There is also the support for javascript builds, but a quick search of > repos showed only 29 repositories … that use this … so I would argue

Re: findsecbugs in spotbugs

On Thursday, December 12, 2019 at 6:28:21 PM UTC, Jeff Thompson wrote: > > On 12/12/19 7:10 AM, Jesse Glick wrote: > > On Wed, Dec 11, 2019 at 2:06 PM Jeff Thompson > wrote: > > As I was analyzing one findsecbugs finding, I immediately recognized it as > SECURITY-1322 […] > If someone had run

Jenkins Plugin pom (future of)

Hi all, firstly apologies about the recent messiness with consuming the jenkins bom in the plugin-pom . For those of you that are not aware the jenkins bom is trying to solve to problem of not consu

Re: findsecbugs in spotbugs

I had a quick peek at the 2 PRs and my main concern is that this found no security issues and forced annotations on a lot of places, that is it found no issues according to the PRs. Whilst it could prevent issues being introduced in the future I am concerned it will cause 99% `@SuppressFBWarnin

Do not use the new plugin-pom with the BOM profile.

Hi all, There are issues using the jenkins-bom for dependency versioning in the plugin pom. Whilst it works for a single plugin, any plugins that are deployed using this also force any plugins that depend on them to enable the profile (as it can not be enabled per module). likewise the other

Re: Possible LTS regression in commons-compress

g/String.html?is-external=true> >> name, >> boolean preserveAbsolutePath) >> (less likely that is the cause). >> >> Björn >> >> Am Mittwoch, 27. November 2019 01:03:40 UTC+1 schrieb James Nord: >>> >>> Hi all, >>> >>&g

Possible LTS regression in commons-compress

Hi all, just a quick note, I *think *I have discovered a regression in 2.204 upcoming LTS due to commons-compress library bump. One of our plugins was using TarInputStream fo

Re: Next LTS baseline selection

just following up the workaound for Config as Code plugin was tested by 夏润泽 and shown to work. it has also been merged. http://github.com/jenkinsci/configuration-as-code-plugin/pull/1204 On Thursday, November 21, 2019 at 6:54:20 PM UTC, ogondza wrote: > > Alright, thanks for the inputs. Next LTS

Re: Proposal: Implementing sensible fine grained permissions to allow an administer to securely delegate some aspects of jenkins configuration

sorry hit send to soon > > At the same time just because you can configure the system message does > not mean that you should be able to install new plugins. > `CONFIGURE` means a lot more than setting the system message, I hope. > And if you have this curated update center then what is the ha

Re: Proposal: Implementing sensible fine grained permissions to allow an administer to securely delegate some aspects of jenkins configuration

On Monday, November 25, 2019 at 8:43:07 PM UTC, Jesse Glick wrote: > > On Mon, Nov 25, 2019 at 2:03 PM James Nord > wrote: > > IMO [installing plugins] should be another Permission > > Just seems like permission bloat. I would expect `CONFIGURE` to imply > the abil

Re: How to consume incrementals?

> Ok, then IntelliJ simply does not read ‚maven.config‘. That's a shame. I was planning on using that to activate the jenkins-bom profile but I have also found issues in large agregator projects where some modules want it enabled and some do not. I'm wondering if we should generically switch

Re: Proposal: Implementing sensible fine grained permissions to allow an administer to securely delegate some aspects of jenkins configuration

> I wonder whether it would make sense to (optionally) allow use of the > plugin manager. With an admin-configured update site only offering curated > plugins, it could make sense to allow Configurers to update or install > plugins themselves. (Basically retaining the legacy distinction betwee

Re: How to consume incrementals?

You should just need to enable the "consume-incrementals" profile, rather than adding extras to the pom https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml#L1348-L1369 If you are not using a mirror in your settings.xml then yes, I have always had to bootstrap the repositories section fo

Re: Next LTS baseline selection

> My point being we ware shipping a core with > this flaw for years (correct me if I wrong) Correct there ware no documentation > plugins should not save before EXTENSIONS_AUGMENTED is completed and > people ware not bitten severely enough to file an issue until recently > (again, correc

Re: Proposal: new initialization milestone for configuration-as-code-plugin

Thanks RunZeXia, Please let me know how you get on with this as it being discussed in the next LTS selection thread. ( https://groups.google.com/forum/#!topic/jenkinsci-dev/2hPMwmZDZFg) /James On Thursday, November 21, 2019 at 3:07:36 AM UTC, 夏润泽 wrote: > > >> The whole point of the initial cod

Re: Proposal: new initialization milestone for configuration-as-code-plugin

Thanks RunZeXua, Please let me know how you get on with this as it being discussed in the next LTS selection thread. ( https://groups.google.com/forum/#!topic/jenkinsci-dev/2hPMwmZDZFg) /James On Thursday, November 21, 2019 at 3:07:36 AM UTC, 夏润泽 wrote: > > >> The whole point of the initial cod

Re: Next LTS baseline selection

I will state this again -* no level of dataloss is acceptable* - we should not back this change out or make it disabled by default. There is a drive by untested PR to Configuration As Code plugin if someone wants to look at it. https://github.com/jenkinsci/configuration-as-code-plugin/pull/12

Re: Next LTS baseline selection

I can not speak to Config As Code, but the issue I found that lead me to write the code in Jenkins in the first place was reported reliably by one of CloudBees' customers (they could hit it every single time). I also saw this on my internal issue sometimes (we randomly lost the cloud configurati

Re: Next LTS baseline selection

I will bite :) I would be -1 on that version. not having the fix in core is allowing silent corruption of configuration. knowing allowing silent corruption and doing nothing about it has no place to exist in code. It is not Jenkins that is blowing up but a plugin manipulating Jenkins state be

Re: Proposal: new initialization milestone for configuration-as-code-plugin

nd in LTS in one month unless we take > a baseline before 2.198 > > On Wednesday, November 20, 2019 at 6:24:38 PM UTC+1, James Nord wrote: >> >> If you (or someone) wants to try a quick and dirty quick fix (until the >> required milestones are available) then sle

Re: Proposal: new initialization milestone for configuration-as-code-plugin

If you (or someone) wants to try a quick and dirty quick fix (until the required milestones are available) then sleeping an amount of time if a system property is set would be a temporary hackish workaround. https://github.com/jenkinsci/configuration-as-code-plugin/blob/c7864838afa0c96b346974800

  1   2   3   4   >