Remove maven-site-plugin:attach-descriptor from ASF Maven parent 42
Hi, I'm going to remove the goal maven-site-plugin:attach-descriptor from ASF Maven parent 42, It can cause problems with your project build if you need to deploy a site descriptor. In such cases you need to add it in your project after upgrading to ASF parent 42. Please look at MPOM-480 [1] issue for details. If someone will need an assist let me know. [1] https://issues.apache.org/jira/browse/MPOM-480 -- Sławomir Jaranowski
Re: ASF Maven parent pom and use properties to define the versions of plugins
Hi Currently we have two propositions: 1. Versions - like mavenCleanPluginVersion [1] 2. version. - like version.maven-clean-plugin [2] As I see from comments on PR more people is for option 2 [1] https://github.com/apache/maven-apache-parent/pull/155 [2] https://github.com/apache/maven-apache-parent/pull/158 wt., 6 cze 2023 o 00:28 Slawomir Jaranowski napisał(a): > Hi, > > I want to introduce properties to define versions of plugins. > I have prepared PR [1] and we have a discussion about properties schema > for such purposes. > > Because AFS Maven parent is used by other ASF projects, and such changes > can be difficult to change in the next release, I want to know other > opinions. > > [1] https://github.com/apache/maven-apache-parent/pull/155 > > > -- > Sławomir Jaranowski > -- Sławomir Jaranowski
ASF Maven parent pom and use properties to define the versions of plugins
Hi, I want to introduce properties to define versions of plugins. I have prepared PR [1] and we have a discussion about properties schema for such purposes. Because AFS Maven parent is used by other ASF projects, and such changes can be difficult to change in the next release, I want to know other opinions. [1] https://github.com/apache/maven-apache-parent/pull/155 -- Sławomir Jaranowski
Re: Broken Builds because of gradle-enterprise
pt., 9 gru 2022 o 15:48 Greg Stein napisał(a): > On Fri, Dec 9, 2022 at 5:41 AM Olivier Lamy wrote: > > > Hi > > Are we seriously activating this gradle enterprise to every build and > > so breaks a few builds without any notice? > > > > Apologies. We thought it would simply be an additional output, and would > not affect any builds. Gaven has turned it off, and we'll do some more > testing to find out why this happened. > > >... > > > [INFO] Publishing build scan... > > [INFO] https://ge.apache.org/s/mabitou3lbw2y > > > > we (Apache Maven) don’t want to use this > > > I see no discussion on dev@maven or private@maven to suggest the PMC does > not want this tool, once we get it debugged. > > There is no discussion on dev@maven, private@maven ... for a simple reason - nobody from the Maven team knows that you want to introduce such features. Please start a topic about it on Maven list with a description of what you want to introduce, why, what will be to do before change. Some of us were surprised due to the failed build. Regards, > Greg Stein > Infrastructure Administrator, ASF > -- Sławomir Jaranowski
Re: GitHub Actions runners
Thanks Richard, Mentioned page contains data which is one year old ... Can anyone update it? How does it look today? wt., 16 sie 2022 o 16:36 Zowalla, Richard napisał(a): > Hi, > > https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+status > > contains some performance details + background infos. > > Gruß > Richard > > ________ > Von: Slawomir Jaranowski > Gesendet: Dienstag, 16. August 2022 15:56:44 > An: builds@apache.org > Betreff: GitHub Actions runners > > Hi, > > Do we monitoring usage of GitHub action runners? > How many projects use GitHub actions? > How runners are utilized by each ASF project? > > Last time I see that Maven builds spent more time waiting for free runners > and builds took about 1 hour instead of a couple of minutes. > > Eg on https://github.com/apache/maven-remote-resources-plugin/actions > > Each job takes about 2 - 4 minutes but to complete the whole workflow we > need about 1 hour. > > If more projects will use GitHub actions it can be a problem. > > > -- > Sławomir Jaranowski > -- Sławomir Jaranowski
GitHub Actions runners
Hi, Do we monitoring usage of GitHub action runners? How many projects use GitHub actions? How runners are utilized by each ASF project? Last time I see that Maven builds spent more time waiting for free runners and builds took about 1 hour instead of a couple of minutes. Eg on https://github.com/apache/maven-remote-resources-plugin/actions Each job takes about 2 - 4 minutes but to complete the whole workflow we need about 1 hour. If more projects will use GitHub actions it can be a problem. -- Sławomir Jaranowski