Am 2021-02-06 um 14:32 schrieb Robert Scholte:
(I'm not sure if this has already been discussed on the dev-list, but I can't
find any related thread)
Plugins that depend on maven-core 2.x will pull in Wagon, which causes unwanted
behavior (it will superseed the one bundled with Maven for that
Robert shared with me that an issue we have is that when we update the
shared library we are rebuilding all projects/branches.
I understand how it can easily kill the instance.
We can disable this option
[image: Screenshot 2021-02-06 at 15.14.41.png]
I don't think we really want to rebuild everyt
Not sure if we are losing some events or if the shared controller has too
many events to process
We can ask to INFRA if they are aware of such issue.
If needed they can contact CloudBees' support to assist in the
troubleshooting.
I can be in the loop and assist if I can get more details from the sy
+1 for option 3
sob., 6 lut 2021, 14:43 użytkownik Tamás Cservenák
napisał:
> +1 fot option 3: we drag so much of legacy, that m4 really should accept
> maven 3.1+ plugins only (covers 14 years?).
>
> T
>
> On Sat, Feb 6, 2021, 14:32 Robert Scholte wrote:
>
> > (I'm not sure if this has already
Yes, because after pushing changes to master (or other branch) nothing has
happened, i manually requested to scan build. I also observe that
something happened recently.
Sylwester
sob., 6 lut 2021, 15:07 użytkownik Arnaud Héritier
napisał:
> I had a look at it and I am not sure if the comment
Because we have a lot of repos maybe we should have a dedicated CI infra.
I know that it's possible to use a dedicated Jenkins controller (and
associated agents) to avoid to use the shared resources of all other
projects.
On Sat, Feb 6, 2021 at 3:07 PM Arnaud Héritier wrote:
> I had a look at it
I had a look at it and I am not sure if the comment is recent or not
The job wasn't disabled and the comment not visible without editing the job
because the HTML was invalid
For sure something is not right and it seems that the repo events are
automatically triggering the builds (or add/remove bran
+1 fot option 3: we drag so much of legacy, that m4 really should accept
maven 3.1+ plugins only (covers 14 years?).
T
On Sat, Feb 6, 2021, 14:32 Robert Scholte wrote:
> (I'm not sure if this has already been discussed on the dev-list, but I
> can't find any related thread)
>
> Plugins that dep
(I'm not sure if this has already been discussed on the dev-list, but I can't
find any related thread)
Plugins that depend on maven-core 2.x will pull in Wagon, which causes unwanted
behavior (it will superseed the one bundled with Maven for that plugin).
MNG-7020 asks for removing this class,
+1
On 4-2-2021 16:40:08, Sylwester Lachiewicz wrote:
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344858&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHAR
slachiewicz opened a new pull request #56:
URL: https://github.com/apache/maven-doxia/pull/56
…su.plexus
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
I see this line in the description:
On 6-2-2021 12:38:21, Arnaud Héritier wrote:
I do not have enough privilege to do anything on this instance but the scan
is configured to be done every week even if nothing happens
Nothing happens means that we got no new event and effectively there is
nothing
I do not have enough privilege to do anything on this instance but the scan
is configured to be done every week even if nothing happens
Nothing happens means that we got no new event and effectively there is
nothing on this page after Feb 2nd which is suspicious :
https://builds.apache.org/job/Mave
Most likely there has been an update at INFRA, which causes that commits aren't
picked up automatically.
Last scan details[1]
[Thu Feb 04 20:27:32 UTC 2021] Finished organization scan. Scan took 1 min 31
sec
Finished: SUCCESS
Would be great if somebody could investigate this.
thanks,
Robert
[
+1
checked that the build is reproducible, built with JDK 11 on Windows
Regards,
Hervé
Le jeudi 4 février 2021, 16:39:51 CET Sylwester Lachiewicz a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&ve
> rsion=12344858&styleName=Te
15 matches
Mail list logo
