You do not pass any credentials around the script in the pipeline,So the command “git pull” failed because does not have a way to authenticate. Check the article and the video of my previous message, there is explained how to pass credentials to your script.El 12 oct 2022, a las 8:13, pooja pooja
If you issue is the memory, it is time to check the garbage collector you are
using, check that you are not using deprecated JVM flags, IIRC the garbage
collector used by JDK 11 is G1 and should perform better than default JDK8
defaults.
Regards
Ivan Fernandez Calvo
> El 11 jul 2022, a las 19:
63.1 to 2.303.1
>
> EXTERNAL EMAIL
>
> I use Amazon Linux 2 for agents with no issue. I've never heard of a problem
> that was specific to Amazon Linux 2.
>
>> On Tue, Oct 5, 2021, 3:23 PM Iván Fernández Calvo
>> wrote:
>> I do not think so the issue see
I do not think so the issue seems related to the upgrade not the OS.
> El 5 oct 2021, a las 21:09, Daniel Burns
> escribió:
>
> Thank you. I wanted to at least respond. This is in DEV so I can
> definitely try different things. Using what you stated, I can mimic PROD and
> create a new DE
>> Dec 04, 2020 3:33:58 PM org.eclipse.jgit.util.FS
>>>>>>>>>>>>>>>> discoverGitSystemConfig
>>>>>>>>>>>>>>>> WARNING: Exception caught during execution of command '[git,
>&
> El 16 feb 2020, a las 11:15, Georges Moulinier
> escribió:
>
> Do you think I could "hide" this syntax " kubernetes { ..." or this "docker {
> ..." behind a label ?
On both plugins you can configure templates , those templates can be triggered
by labels so you still can use the agent { la
> El 16 feb 2020, a las 14:15, Vincent Massol escribió:
>
> In both cases it"ll be reported as INFO in the logs too. Right?
It seems like, I didn’t noticed that the exception is also a INFO messages, so
the only difference is the stack trace of the exception, the log level is the
same.
--
I dunno if it is your case, but things like VMotion that changes the VM to a
less loaded rack, energy saving, any kind of power on network, and in general
every that suspends the VM will break the connection, Jenkins check on agents
every 4 min, if the agent does not respond on time Jenkins brea
This timeout, it is only for the connection stage, and it includes whole retry
reconnections, long history, the default value is 210 seconds, less than 30-60
seconds it is not a good value and only if you have reties to 0.
I do not know how many agents you spin at the same time, I would try to
On the “Known Hosts Key Validation" agents, where you imported the key on the
jenkins user ssh authorized keys folder or on the etc ssh authorized keys
folder? On etc does not work.
The other error seems related with the format of the host public key, it
should’ve something like the following
10 matches
Mail list logo
