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 assem
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
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
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
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
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 co
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
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
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' necessa
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 branc
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
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 2
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 o
13 matches
Mail list logo
