Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 23 12:09

    nrayapati on maven

    (compare)

  • Jan 23 12:09

    nrayapati on master

    Bump assertj-core from 3.24.1 t… (compare)

  • Jan 23 12:09
    nrayapati closed #85
  • Jan 23 12:08

    nrayapati on master

    Bump plugin from 4.53 to 4.54 (… (compare)

  • Jan 23 12:08

    nrayapati on maven

    (compare)

  • Jan 23 12:08
    nrayapati closed #84
  • Jan 23 07:08
    dependabot[bot] labeled #85
  • Jan 23 07:08
    dependabot[bot] labeled #85
  • Jan 23 07:08
    dependabot[bot] opened #85
  • Jan 23 07:08

    dependabot[bot] on maven

    Bump assertj-core from 3.24.1 t… (compare)

  • Jan 23 07:08
    dependabot[bot] labeled #84
  • Jan 23 07:08
    dependabot[bot] labeled #84
  • Jan 23 07:08
    dependabot[bot] opened #84
  • Jan 23 07:08

    dependabot[bot] on maven

    Bump plugin from 4.53 to 4.54 … (compare)

  • Jan 22 22:27

    github-actions[bot] on 2.0.65.vd26b_5b_9b_de4d

    (compare)

  • Jan 22 22:16

    nrayapati on master

    Bump jna-platform from 5.12.1 t… (compare)

  • Jan 22 22:16
    nrayapati closed #83
  • Jan 22 22:16

    nrayapati on maven

    (compare)

  • Jan 22 22:07
    nrayapati labeled #83
  • Jan 22 22:07
    nrayapati assigned #83
zdrescher
@zdrescher
Hi
I am using this plug in to orchestrate some processes on a remote server.
Using the sshScript step seems to time out for no apparent reason, reports an error to the jenkins server despite the process it kicks off continuing to run.
the only thing it returns is:

Failed command mlops-dev1#56 with status -1: /bin/bash

Command returned exit status -1: /bin/bash

zdrescher
@zdrescher
im noticing that its not displaying some telemetry to stout that i would expect to see
Naresh Rayapati
@nrayapati
It usually prints the return code from the actual command / script being executed, is this a new command did you try some test commands to see if that is working
zdrescher
@zdrescher
So the script has multiple commands and the issue seems to only appear on the last one.
zdrescher
@zdrescher
I am able to confirm that that the exit status isn't coming from the command, as i can confirm that the command continues running after the jenkins pipeline fails and shuts down.
Additionally, I am able to run the command outside the Jenkins context with no errors.
Naresh Rayapati
@nrayapati
sshScript is a bit special and it tries to stream the given script to the node, can you try the sshCommand and see if that is failing too
If this is a already in a file, probably you can try sshPut to place it on to the actual node and the sshCommand as it is local script.
zdrescher
@zdrescher
I see, let me try that
Thanks for the quick feedback!
zdrescher
@zdrescher
That worked! Thanks again!!
Naresh Rayapati
@nrayapati
Thank you for reporting!
zdrescher
@zdrescher
Hmmm actually, I may have spoke too soon...
i am getting a similar error:
Failed command mlops-dev1#69 with status -1: source helps/train.sh
when i run the same script as the same user on the remote
echo $?
returns 0
zdrescher
@zdrescher
So instead of running the command i've been trying i ran something along the lines of "for i in {1..10}; do echo -n \"Loop \$i \"; date ; sleep 1m; done"
the idea is to do something that takes as long as the command to see if it has a similar issue. it doesnt.
I think part of the problem is that the command i am running (a python process) isn't printing to stdout.
It should be but for whatever reason its not.