here you have some of the pod templates we use
https://github.com/elastic/apm-pipeline-library/pull/1614
El mié, 29 jun 2022 a las 12:33, Denis Mone ()
escribió:
> I have tried to provision the pod manually. It takes around 30 - 35
> seconds.
> We use GKE as well as the k8s provider.
>
> Do you
Does it happen only on one agent? if you disconnect the Agent and connect
the agent again, Do you see the same issue?
checking the version you are using has about a year, the Jenkins Core you
have can use the latest version. Checking the changes in 1.32 there is a
change in the library used to
Jenkins pipelines have two types of code, the steps and directives provided
by Jenkins, and the Groovy code.
All the Jenkins steps and directives are thread safe. On your Groovy you
must guarantee is thread-safe if it needs to be.
Unstash and archive are Jenkins steps you can use them in parallel
Did you test other commands in the Freestyle job? try this
#!/bin/bash
pwd
echo foo
date
El vie, 29 oct 2021 a las 7:21, Adharsha sri ()
escribió:
> Hi,
>
> In /etc/profile added the below bash environment variables
> export _CEE_RUNOPTS=“FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)”
> export
I have an example of Multibranch pipeline job with jobDSL
https://github.com/elastic/apm-pipeline-library/blob/master/.ci/jobDSL/jobs/apm-ci/apm-shared/oblt-test-env/test_mbp.groovy
it could help you to save some time.
El mar, 23 mar 2021 a las 11:15, Sverre Moe ()
escribió:
> I will check out
ildStepMonitor.java:20)
>>>> at
>>>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
>>>> at
>>>> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
>>>>
Yes, there is only one file to update the remoting.jar. If you install the
remoting process as a service the update is done by the service see
https://github.com/jenkinsci/windows-slave-installer-module and
https://github.com/winsw/winsw/blob/master/doc/installation.md#winsw-installation-guide
If
Module Descriptor
>
>
>
>> El mar, 9 feb 2021 a las 21:23, Jigar R ()
>> escribió:
>>
>>> Any recommendations on how should I go about this new error?
>>>
>>> On Thursday, February 4, 2021 at 5:26:13 PM UTC-5 Jigar R wrote:
>>>
>>>> On T
Hi,
We are trying to move to jobDSL our job definitions, at this point we have
hit an issue that I am not sure we can move forward.
To define the Multibranch Pipeline jobs everithing works fine except the
pull request discovery settings,
Because ForkPullRequestDiscoveryTrait and
, 10 feb 2021 a las 18:28, Eric Fetzer
escribió:
> My MACs line says:
>
> MACs hmac-ripemd160,hmac-sha2-256,hmac-sha2-512,hmac-ripemd...@openssh.com
>
> I believe this is hardened, isn't it?
>
> Thanks,
> Eric
>
> On Wed, Feb 10, 2021 at 9:40 AM kuisathaverat
&g
> something?
>
> Thanks,
> Eric
>
> On Tue, Feb 9, 2021 at 12:23 PM kuisathaverat
> wrote:
>
>> There is work in progress to bump the version of the library and convert
>> the sshd-module in a plugin to resolve this kind of issues quickly. For the
>> m
Thursday, February 4, 2021 at 5:26:13 PM UTC-5 Jigar R wrote:
>
>> On Thursday, February 4, 2021 at 12:20:21 PM UTC-5 Jigar R wrote:
>>
>>> On Thu, Feb 4, 2021 at 9:29 AM kuisathaverat
>>> wrote:
>>>
>>>> I see some serialization fails and this brea
There is work in progress to bump the version of the library and convert
the sshd-module in a plugin to resolve this kind of issues quickly. For the
moment you can configure your sshd servers on the Agents side to do not
allow weak ciphers, see https://www.ssh.com/ssh/sshd_config.
I see some serialization fails and this breaks the channel, the plugin that
causes the exception seems https://github.com/jenkinsci/tasks-plugin, and
the `[Deprecated] Scan workspace for open tasks` I think matters, this
plugins has been integrated into
Weird, Could you share a screencapture of what you configurate? Also the
whole exception those lines alone mean nothing. Know the version of Jenkins
and the version of the SSH build agents plugins you use can help, the
memory you have in your agents, if they are bare metal or cloud. In overall
if
then the only thing you can do it is to enable the debug on the sshd server
to see what happens with the connection (see
https://en.wikibooks.org/wiki/OpenSSH/Logging_and_Troubleshooting), then
open a regular ssh connection from the Jenkins instance to the Agent from
command line and see what
Hi,
We are facing some issues with a job that has about 100 stages in parallel,
we track down the issue and it happens when we storage artifacts on GCP in
parallel, the thing is that I am not sure it is related to the plugin
directly, Could someone take a look to this stack trace and confirm that
.
It is easy to check, run a Jenkins Docker container configured with
JCasC (e.g.
https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-63703)
then connect to the container and modify the JENKINS_HOME/jenkins.yaml file
and restart from UI or CLI, the JCasC changes will not apply if you stop
as I said your problem is the IO, if you enter en the Instance by ssh and
check the iostats you will see more than 5-10% of your operations waiting
for IO. NFS, EFS, and in general network filesystems works well with
big files but with small files and write concurrence is where the problems
start
arallelRefProcEnabled
> -XX:+DisableExplicitGC -XX:+UnlockDiagnosticVMOptions
> -XX:+UnlockExperimentalVMOptions -verbose:gc
> -Xlog:gc:/home/jenkins/.jenkins/support/gc-%t.log -XX:+PrintGC
> -XX:+PrintGCDetails -XX:ErrorFile=/hs_err_%p.log -XX:+LogVMOutput
> -XX:LogFile=/home/jenkin
El El dom, 16 feb 2020 a las 14:48, Vincent Massol
escribió:
> This is why I've been asking from the beginning if it's normal :) Usually
> when there's a stack trace it's not really normal. But it happens so
> frequently that the only explanation I can think of is that it's the normal
> behavior
I guess you make something like `ssh user@host echo "hello"`, if you want
to see the whole key interchange you have to enable the verbose mode `ssh
-vvv user@host echo "hello"` this give you all the data to troubleshooting
the issue
El jue., 6 feb. 2020 a las 15:52, Sanders, Sholom (<
You do not need to change anything there, you would need custom ECS AMIs
where you have pre-pull the Docker images that you will need, see
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html
El mar., 16 abr. 2019 a las 17:14, ZillaYT () escribió:
> So what values
the problem is that you are not running the code as Groovy script, you
include the code in your pipeline script, it is not the same.
save this as a Groovy script in your repo, something like
scripts/my-testlink.groovy
#!/usr/bin/env groovy
import testlink.api.java.client.TestLinkAPIResults.*
I will add it to the troubleshooting guide for future users, thx for sharing
El jue., 4 abr. 2019 a las 11:49, escribió:
> I fixed this problem through disable: "Manage Jenkins" > "Configure Global
> Security", and check "Enable Agent → Master Access Control" (as it's said
> in Jenkin
to discard things, Could you connect the agent as a regular ssh-agent and
run a silly job in it, something like the following pipeline ;), if it
works it is something in the selenium grid plugin
```
node('my-rebel-agent'){
sh(label: "the most complex thing in the world", script: "hello world")
Which versions of the selenium grid plugin do you use before and after?
maybe in the release notes, there is some change that affects you.
El mié., 3 abr. 2019 a las 13:08, escribió:
> *Hi* kuisathaverat,
>
> I upgraded the ssh slave plugin from 1.11 to 1.29 and now the error
>
Is nothing in the AGENT_WORKDIR/remoting folder logs? without more info, I
cannot help you too much, check the troubleshooting guide
https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md
there
you have details about what files are needed to check an issue.
El mié., 3
Multibranch pipeline with defaults
https://plugins.jenkins.io/pipeline-multibranch-defaults and Pipeline
Github plugin https://github.com/jenkinsci/pipeline-github-plugin the
first allow you to set a Jenkinsfile by default on Multibranch projects so
you can have the Jenkinsfile outside of the
Did you check if after the disconnection there is a remoting.jar process
running on the agents? you can try to fix the memory of the remoting
process by setting the JVM Options `--Xms=512m --Xmx=512m` on the node
configuration, I am not sure if it is crashing or not.
El mar., 12 mar. 2019 a las
yep, I use to recommend not share user too.
El jue., 21 feb. 2019 a las 15:22, 'Björn Pedersen' via Jenkins Users (<
jenkinsci-users@googlegroups.com>) escribió:
>
> We have setups with more than one agent on one host, but they do not share
> the root. Both agents hold a lock on
There is 4 min between the start of the connection and the termination, the
agent never opens the channel and is killed when the ping thread checks the
connection. It is an old version of ssh-slaves-plugin because the log,
Which version is it? also Which Jenkins Core? Which authentication do you
I think you can discard JVM versions issues and connectivity issues,
because the agent connects and copy the remoting.jar, How much time takes
between the agent connect and the channel is broken? Check you do not have
any configuration that kill idle connections, also try to assign memory to
the
33 matches
Mail list logo
