Nohup doesn't work when executing script from Jenkins












4














I have bash script which executes following



nohup ws --port 8080 &


when executing that script directly on remote server and closing connection - process still exists. But when i am using Jenkins "SSH plugin" - process stops after Jenkins closes connection. To execute that script i am using simple command sh scriptName.sh










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1




    I have managed to resolve issue by redirecting nohup output like: nohup ws --port 8080 >/dev/null 2>&1 &
    – user454546
    Jun 2 '15 at 17:30


















4














I have bash script which executes following



nohup ws --port 8080 &


when executing that script directly on remote server and closing connection - process still exists. But when i am using Jenkins "SSH plugin" - process stops after Jenkins closes connection. To execute that script i am using simple command sh scriptName.sh










share|improve this question
















bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.











  • 1




    I have managed to resolve issue by redirecting nohup output like: nohup ws --port 8080 >/dev/null 2>&1 &
    – user454546
    Jun 2 '15 at 17:30
















4












4








4


1





I have bash script which executes following



nohup ws --port 8080 &


when executing that script directly on remote server and closing connection - process still exists. But when i am using Jenkins "SSH plugin" - process stops after Jenkins closes connection. To execute that script i am using simple command sh scriptName.sh










share|improve this question















I have bash script which executes following



nohup ws --port 8080 &


when executing that script directly on remote server and closing connection - process still exists. But when i am using Jenkins "SSH plugin" - process stops after Jenkins closes connection. To execute that script i am using simple command sh scriptName.sh







linux command-line jenkins nohup






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 2 '15 at 17:36









Dave M

12.7k92838




12.7k92838










asked Jun 2 '15 at 17:17









user454546

2112




2112





bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 2 days ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.










  • 1




    I have managed to resolve issue by redirecting nohup output like: nohup ws --port 8080 >/dev/null 2>&1 &
    – user454546
    Jun 2 '15 at 17:30
















  • 1




    I have managed to resolve issue by redirecting nohup output like: nohup ws --port 8080 >/dev/null 2>&1 &
    – user454546
    Jun 2 '15 at 17:30










1




1




I have managed to resolve issue by redirecting nohup output like: nohup ws --port 8080 >/dev/null 2>&1 &
– user454546
Jun 2 '15 at 17:30






I have managed to resolve issue by redirecting nohup output like: nohup ws --port 8080 >/dev/null 2>&1 &
– user454546
Jun 2 '15 at 17:30












1 Answer
1






active

oldest

votes


















0














Best simple solution is to use "at now" instead of "nohup"



In your job jenkins (execute shell) put :



set +e #so "at now" will run even if java -jar fails
#Run java app in background
echo "java -jar $(ls | grep *.jar | head -n 1)" | at now + 1 min





share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f922841%2fnohup-doesnt-work-when-executing-script-from-jenkins%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Best simple solution is to use "at now" instead of "nohup"



    In your job jenkins (execute shell) put :



    set +e #so "at now" will run even if java -jar fails
    #Run java app in background
    echo "java -jar $(ls | grep *.jar | head -n 1)" | at now + 1 min





    share|improve this answer




























      0














      Best simple solution is to use "at now" instead of "nohup"



      In your job jenkins (execute shell) put :



      set +e #so "at now" will run even if java -jar fails
      #Run java app in background
      echo "java -jar $(ls | grep *.jar | head -n 1)" | at now + 1 min





      share|improve this answer


























        0












        0








        0






        Best simple solution is to use "at now" instead of "nohup"



        In your job jenkins (execute shell) put :



        set +e #so "at now" will run even if java -jar fails
        #Run java app in background
        echo "java -jar $(ls | grep *.jar | head -n 1)" | at now + 1 min





        share|improve this answer














        Best simple solution is to use "at now" instead of "nohup"



        In your job jenkins (execute shell) put :



        set +e #so "at now" will run even if java -jar fails
        #Run java app in background
        echo "java -jar $(ls | grep *.jar | head -n 1)" | at now + 1 min






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 5 '18 at 16:11

























        answered Dec 5 '18 at 7:57









        Walid

        12




        12






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f922841%2fnohup-doesnt-work-when-executing-script-from-jenkins%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀