d_ need to update the Windows Nodes configs themselves to
match the Operations Center
Thanks for spotting that, hopefully all good now?
On Sun, Oct 18, 2020 at 1:45 PM Robert Scholte wrote:
> Hi Gavin,
>
> Well, it looks like the changes to Jenkins have impact on Windows nodes.
>
be updated for the Windows nodes too.
thanks,
Robert
On 17-10-2020 19:22:24, Gavin McDonald wrote:
Hi Robert,
Separate (I think known) issue, as I never touched the Windows configs,
will take a look
On Sat, Oct 17, 2020 at 7:04 PM Robert Scholte wrote:
> On all Windows Nodes I see
On all Windows Nodes I see the following exception (or similar):
Error: JAVA_HOME is set to an invalid directory.
JAVA_HOME = "/home/jenkins/tools/java/latest1.7"
Please set the JAVA_HOME variable in your environment to match the location of
your Java installation.
It looks like it is picking u
IIUC the issue here is that Jenkins doesn't make a difference between changed
to Global pipeline files and source repositories, so any change will directly
trigger builds of all branches of all ~100 Maven repos.
Ideally only the latter should be triggered immediately, and the first at any
random
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 exp
x27;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.
thanks,
Robert
On 21-7-2020 19:49:13, Robert Scholte wrote:
Looking at it.
It seems like mo
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 Mc
On Mon, 07 Oct 2019 21:49:44 +0200, Tilman Hausherr
wrote:
Am 07.10.2019 um 12:39 schrieb Gavin McDonald:
Please find below a summary of each; and links to their cwiki
documentation
page. Any questions please let me know.
Thanks
Gav...
[Maven]
3.0.4 (3.0.5 available)
3.2.1 (3.2.5 avail
: https://gitbox.apache.org/repos/asf?p=maven-jenkins-env.git
> [2]: https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git
>
>
> On Mon, Jun 17, 2019 at 7:16 PM Robert Scholte wrote:
>
>> Sure, will investigate.
>>
>> thanks,
>> Robert
>>
>>
Sure, will investigate.
thanks,
Robert
On Mon, 17 Jun 2019 15:21:30 +0200, Robert Munteanu
wrote:
Hi,
I noticed today that Jenkins is taking more time to start building
various jobs. Looking at the executors, I think there is a
misconfiguration/problem with some Maven-related jobs
-
http
maven-box[1] is actually our multibranch(?) job for all our ~100
repositories, which means the 18Gb is quite a good number.
With this in mind I believe maven-box should not be on the list for
cleanup.
thanks,
Robert
[1] https://builds.apache.org/job/maven-box/
On Thu, 27 Dec 2018 11:27:31
Hi,
Could someone fix https://builds.apache.org/job/maven-wagon-windows/
It is failing for quite some time. Reason:
The process cannot access the file because it is being used by another
process.
(I've disabled the job to stop it from spamming)
ErrorID=a47fb15e-561f-4ecd-af6f-36d0b1ecd8a9
I
Forwarding message to Apache Builds team
Robert
On Fri, 02 Dec 2016 08:28:32 +0100, Dan Tran wrote:
Looks like Jenkins does not like the provided maven
ERROR: Processing failed due to a bug in the code. Please report this
to jenkinsci-us...@googlegroups.comjava.lang.IllegalArgumentException
Yes, I've been using Jigsaw on my local system to implement its features
for Maven. I've started to create new jobs on Jenkins for the Maven
projects to confirm that it's all working well.
Robert
On Tue, 25 Oct 2016 09:28:45 +0200, Gavin McDonald
wrote:
Does anyone have a need for it?
14 matches
Mail list logo
