Le mardi 16 octobre 2018 à 17:38 +0200, Michael Scherer a écrit : > Hi, > > so I added another VM to run bugzilla job, this time inside the lan. > If > you see any issue related to bugzilla job executed by jenkins, please > tell us, I will disable the existing node now (and revert if any > issue > happen).
So, after seeing that all was ok, I went to shutdown the server. Turn out that I was wrong, and since I did "copy that node" in jenkins interface, I did create a 2nd node going on the first server, and so job started to fail for 30 seconds. if you see that a bug haven't been commented or anything around 10 minutes ago, that's likely the root cause, sorry So now, the jenkins config is fixed, i will let the new builders for 24h to see if it work. -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-infra mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-infra
