assembly plugin: moduleSets & binary dependencies
Hi, I recently posted to the users mailing list about an issue with moduleSets & binary's dependencies, where it appears dependencies are based on the maven project's dependencies, whilst my //expectation// (perhaps wrong) was that they would be based on the module being processed by the assembly. The original thread is https://lists.apache.org/thread.html/r131e0699cb3d60763d0904425491924097168bb2de68da24bb5ddcb5%40%3Cusers.maven.apache.org%3E I also opened up https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-940 as it seemed as if the intent was to do this, though it could be my misreading of the docs, or something that could be improved. Would very much appreciate any tips Thanks! Nigel (planetf1) - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] elharo merged pull request #180: grammar nit: an -> a
elharo merged pull request #180: URL: https://github.com/apache/maven-site/pull/180 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] elharo merged pull request #181: grammar nit subject verb agreement
elharo merged pull request #181: URL: https://github.com/apache/maven-site/pull/181 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] elharo opened a new pull request #181: grammar nit subject verb agreement
elharo opened a new pull request #181: URL: https://github.com/apache/maven-site/pull/181 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
[GitHub] [maven-site] elharo opened a new pull request #180: grammar nit: an -> a
elharo opened a new pull request #180: URL: https://github.com/apache/maven-site/pull/180 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Excluding builds of certain git branches on ASF Jenkins
On 22/07/2020 11:49, Elliotte Rusty Harold wrote: On Wed, Jul 22, 2020 at 8:36 AM Maarten Mulders wrote: In the Jenkins user interface, I see there's an option to build only specific branches. I'm thinking of excluding everything that starts with dependabot/ there, just to be sure. Before I continue, does anyone know if it's possible to configure this with a Jenkinsfile? Without Jenkins running on Dependabot, we'd probably be safer just turning off Dependabot, unless maybe there's a way to manually trigger a build on a branch? I was thinking Dependabot could _tell_ us there's a newer version of a dependency. Those branches could be built with Github actions (they are already in use on some repositories). If that succeeds, and after inspection of the pull request by a committer, it could be built on Jenkins, too. We just don't want Jenkins to build those branches automatically, without human inspection. Thanks, Maarten - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Excluding builds of certain git branches on ASF Jenkins
On Wed, Jul 22, 2020 at 8:36 AM Maarten Mulders wrote: > In the Jenkins user interface, I see there's an option to build only > specific branches. I'm thinking of excluding everything that starts with > dependabot/ there, just to be sure. Before I continue, does anyone know > if it's possible to configure this with a Jenkinsfile? Without Jenkins running on Dependabot, we'd probably be safer just turning off Dependabot, unless maybe there's a way to manually trigger a build on a branch? -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Excluding builds of certain git branches on ASF Jenkins
Hi Maarten, you can add 'when' to a 'stage' but that would not prevent the job from being triggered. AFAICS, nothing that you can put in Jenkinsfile will prevent the job from being triggered. Cheers, Falko - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Maven builds out of control
Hi! On Wed, Jul 22, 2020 at 10:29 AM Robert Scholte wrote: > > > *Robert Scholte:* > That's very unlikely. I expect that Jenkins itself got an update of that > plugin and that our MultiBranch setup picked up that change. > hm, we don't normally do out of band plugin upgrades unless its' necessary , I'll investigate this end, I have added a plugin or two recently, and this may have come in as a dependant upgrade, but fairly sure I did not do any plugins on the 21st. Gav... > > > > > > > > > This caused new configuration for *all* our branches and triggered new > > builds. > > The Ubuntu builds were often ready, but a lot were still waiting for > > Windows Executors. > > > > Ack > > > > > > Most of these builds are quite short so under normal circumstances there > > shouldn't be any issues. > > However, I already noticed we're having way too much branches, so either > > we'll clean these up or remove/disable its JenkinsFile, so it won't be > > triggered anymore. > > > > That would be awesome, things are looking good at the moment, thanks for > looking into it > > Gav... > > > > > > thanks, > > Robert > > > > On 21-7-2020 19:49:13, Robert Scholte wrote: > > Looking at it. > > It seems like most are waiting for a Windows executor, but these are all > > taken too. > > Need to investigate a bit more, but it looks like all branches are > > triggered for some reason. > > That's weird, because we didn't touch are shared Jenkins scripts > > > > Robert > > > > On 21-7-2020 18:22:12, Gavin McDonald wrote: > > Hi Maven folks, > > > > Over 800 builds in the Jenkins queue right now, most of them Maven - and > > its been above 500 , mostly Maven for over 12 hours now - Please take a > > look and see what is going on ASAP, or I might have to cancel all Maven > > jobs to allow other projects to proceed > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > > > > > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Excluding builds of certain git branches on ASF Jenkins
Hi all, As you may have noticed, yesterday we had a situation on Jenkins where around 500 jobs where queuing up. Many of them of them where building Dependabot branches from our Github mirrors. The way Dependabot works is they do *not* create a fork of our repo's. Instead they create a branch in our repo's and push one commit that updates a particular dependency. Because of sync between Github and the ASF Gitbox, that branch also exists in the ASF Gitbox. And because of that, Jenkins may decide to start building it (as happened yesterday). This means we pull in changes from others that get executed on ASF infrastructure without any Maven committer reviewing or approving those changes. In the Jenkins user interface, I see there's an option to build only specific branches. I'm thinking of excluding everything that starts with dependabot/ there, just to be sure. Before I continue, does anyone know if it's possible to configure this with a Jenkinsfile? Thanks, Maarten OpenPGP_0x13D979595E6D01E1.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
Re: Maven builds out of control
On 22-7-2020 09:56:16, Gavin McDonald wrote: Hi Robert, On Tue, Jul 21, 2020 at 8:26 PM Robert Scholte wrote: > 2020-07-09_20-33-20 > > > 2020-07-21_11-38-13 > > Ok so that implies someone on your end made a config change? Robert Scholte: That's very unlikely. I expect that Jenkins itself got an update of that plugin and that our MultiBranch setup picked up that change. > > > This caused new configuration for *all* our branches and triggered new > builds. > The Ubuntu builds were often ready, but a lot were still waiting for > Windows Executors. > Ack > > Most of these builds are quite short so under normal circumstances there > shouldn't be any issues. > However, I already noticed we're having way too much branches, so either > we'll clean these up or remove/disable its JenkinsFile, so it won't be > triggered anymore. > That would be awesome, things are looking good at the moment, thanks for looking into it Gav... > > thanks, > Robert > > On 21-7-2020 19:49:13, Robert Scholte wrote: > Looking at it. > It seems like most are waiting for a Windows executor, but these are all > taken too. > Need to investigate a bit more, but it looks like all branches are > triggered for some reason. > That's weird, because we didn't touch are shared Jenkins scripts > > Robert > > On 21-7-2020 18:22:12, Gavin McDonald wrote: > Hi Maven folks, > > Over 800 builds in the Jenkins queue right now, most of them Maven - and > its been above 500 , mostly Maven for over 12 hours now - Please take a > look and see what is going on ASAP, or I might have to cancel all Maven > jobs to allow other projects to proceed > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [RESULT] [VOTE] Release Maven Resolver version 1.5.0
Hervé, Michael - missed the email about the vote earlier, just went hunting for the repo details to try it out on our internal range resolver/locking tool. +1 NON Binding here - passes my unit tests on my library, and the maven mojo that uses it runs fine as works as expected. Mark On 22 July 2020 at 6:05:39 PM, Hervé BOUTEMY (herve.bout...@free.fr) wrote: hey, keep cool, take time: 72h is the minimum, not the period after which the vote stops there was some discussions, people are on vacation, it takes more time than usual, nothing that a little bit of time won't solve Regards, Hervé Le mardi 21 juillet 2020, 20:32:49 CEST Michael Osipov a écrit : > Hi, > > The vote has passed and failed to reach a quorum. Only one, non-binding > vote has been cast. Therefore, I cancel the release and will drop the > staging repo tomorrow. > > Michael
Re: Maven builds out of control
Hi Robert, On Tue, Jul 21, 2020 at 8:26 PM Robert Scholte wrote: > 2020-07-09_20-33-20 > > > 2020-07-21_11-38-13 > > Ok so that implies someone on your end made a config change? > > > This caused new configuration for *all* our branches and triggered new > builds. > The Ubuntu builds were often ready, but a lot were still waiting for > Windows Executors. > Ack > > Most of these builds are quite short so under normal circumstances there > shouldn't be any issues. > However, I already noticed we're having way too much branches, so either > we'll clean these up or remove/disable its JenkinsFile, so it won't be > triggered anymore. > That would be awesome, things are looking good at the moment, thanks for looking into it Gav... > > thanks, > Robert > > On 21-7-2020 19:49:13, Robert Scholte wrote: > Looking at it. > It seems like most are waiting for a Windows executor, but these are all > taken too. > Need to investigate a bit more, but it looks like all branches are > triggered for some reason. > That's weird, because we didn't touch are shared Jenkins scripts > > Robert > > On 21-7-2020 18:22:12, Gavin McDonald wrote: > Hi Maven folks, > > Over 800 builds in the Jenkins queue right now, most of them Maven - and > its been above 500 , mostly Maven for over 12 hours now - Please take a > look and see what is going on ASAP, or I might have to cancel all Maven > jobs to allow other projects to proceed > > -- > > *Gavin McDonald* > Systems Administrator > ASF Infrastructure Team > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: [RESULT] [VOTE] Release Maven Resolver version 1.5.0
hey, keep cool, take time: 72h is the minimum, not the period after which the vote stops there was some discussions, people are on vacation, it takes more time than usual, nothing that a little bit of time won't solve Regards, Hervé Le mardi 21 juillet 2020, 20:32:49 CEST Michael Osipov a écrit : > Hi, > > The vote has passed and failed to reach a quorum. Only one, non-binding > vote has been cast. Therefore, I cancel the release and will drop the > staging repo tomorrow. > > Michael > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
