Is there a way to write a jenkins job that keeps state across runs?Jenkins slave job fails after successful jobHow to “modularize” my Jenkins jobsComplex and long single-job Jenkins Job Pipeline Builds: There yet?How to fix Jenkins job that is failing on git checkout when workspace is on network share, but not when workspace is on local drive?Continue Jenkins job after failed stage while marking stage as failedJenkins job status failing despite running correctlyRetry on Jenkins triggered by GitHub Pull Request BuilderLimit the number of pipeline jobs of a particular git repo in JenkinsHow to fail master Jenkins pipeline job if downstream jobs failsHow to checkout and run pipeline file from TFS on specific node in Jenkins?

Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?

Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?

Why do falling prices hurt debtors?

How to say job offer in Mandarin/Cantonese?

strToHex ( string to its hex representation as string)

Why are electrically insulating heatsinks so rare? Is it just cost?

Fencing style for blades that can attack from a distance

Did Shadowfax go to Valinor?

Have astronauts in space suits ever taken selfies? If so, how?

What does CI-V stand for?

can i play a electric guitar through a bass amp?

How much RAM could one put in a typical 80386 setup?

Languages that we cannot (dis)prove to be Context-Free

TGV timetables / schedules?

Is it important to consider tone, melody, and musical form while writing a song?

What are these boxed doors outside store fronts in New York?

How do I create uniquely male characters?

Today is the Center

How to test if a transaction is standard without spending real money?

Theorem, big Paralist and Amsart

Why was the small council so happy for Tyrion to become the Master of Coin?

How can I prevent hyper evolved versions of regular creatures from wiping out their cousins?

How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?

Is it tax fraud for an individual to declare non-taxable revenue as taxable income? (US tax laws)



Is there a way to write a jenkins job that keeps state across runs?


Jenkins slave job fails after successful jobHow to “modularize” my Jenkins jobsComplex and long single-job Jenkins Job Pipeline Builds: There yet?How to fix Jenkins job that is failing on git checkout when workspace is on network share, but not when workspace is on local drive?Continue Jenkins job after failed stage while marking stage as failedJenkins job status failing despite running correctlyRetry on Jenkins triggered by GitHub Pull Request BuilderLimit the number of pipeline jobs of a particular git repo in JenkinsHow to fail master Jenkins pipeline job if downstream jobs failsHow to checkout and run pipeline file from TFS on specific node in Jenkins?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















For testing a pipeline with a retry-option I'd like to create a Jenkins job that will pass or fail in some pattern across runs. For example:



run 1: failure
run 2: failure
run 3: pass


and then repeat the pattern.



I don't want to assume that the job will be using the same workspace or even the same node but I am ok preventing concurrent runs... so just marking a text file won't necessarily work.



I was thinking it could be done via artifacts but am not sure how to set that up... can a job load an artifact from the previous job?



Any suggestions on how I might put something like this together would be great!










share|improve this question






























    0















    For testing a pipeline with a retry-option I'd like to create a Jenkins job that will pass or fail in some pattern across runs. For example:



    run 1: failure
    run 2: failure
    run 3: pass


    and then repeat the pattern.



    I don't want to assume that the job will be using the same workspace or even the same node but I am ok preventing concurrent runs... so just marking a text file won't necessarily work.



    I was thinking it could be done via artifacts but am not sure how to set that up... can a job load an artifact from the previous job?



    Any suggestions on how I might put something like this together would be great!










    share|improve this question


























      0












      0








      0








      For testing a pipeline with a retry-option I'd like to create a Jenkins job that will pass or fail in some pattern across runs. For example:



      run 1: failure
      run 2: failure
      run 3: pass


      and then repeat the pattern.



      I don't want to assume that the job will be using the same workspace or even the same node but I am ok preventing concurrent runs... so just marking a text file won't necessarily work.



      I was thinking it could be done via artifacts but am not sure how to set that up... can a job load an artifact from the previous job?



      Any suggestions on how I might put something like this together would be great!










      share|improve this question
















      For testing a pipeline with a retry-option I'd like to create a Jenkins job that will pass or fail in some pattern across runs. For example:



      run 1: failure
      run 2: failure
      run 3: pass


      and then repeat the pattern.



      I don't want to assume that the job will be using the same workspace or even the same node but I am ok preventing concurrent runs... so just marking a text file won't necessarily work.



      I was thinking it could be done via artifacts but am not sure how to set that up... can a job load an artifact from the previous job?



      Any suggestions on how I might put something like this together would be great!







      jenkins






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 22 at 21:39







      TxAG98

















      asked Mar 22 at 0:00









      TxAG98TxAG98

      373214




      373214






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Figured it out... this is what I did in case it's useful for anyone else:



          I'm using a 'freestyle' job that does not allow concurrent builds.



          The job will use a text file named counter.txt that just contains a single line with the counter # in it as my 'state'. I'll save that as an artifact at the end of my job and load it at the start.



          $ cat counter.txt
          1


          First build step: load counter.txt from artifacts:



          enter image description here



          Second build step: bash script to pull the value and check against a threshold (in my case 3). Exit with status=1 unless counter >= 3. If counter.txt doesn't exist it's created and set to 1, otherwise we load the file and increment it, and check the value to determine if we meet the PASS condition.



          enter image description here



          I added two post-build conditions, first I archive counter.txt as an artifact and then delete the workspace. I doubt deleting the workspace is necessary but I added it to just make sure the counter.txt file I'm getting is the artifact in case Jenkins decided it didn't want to overwrite the file or something.



          enter image description here



          When I run this it's doing the right thing:



          enter image description here






          share|improve this answer























            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            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%2fstackoverflow.com%2fquestions%2f55290953%2fis-there-a-way-to-write-a-jenkins-job-that-keeps-state-across-runs%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














            Figured it out... this is what I did in case it's useful for anyone else:



            I'm using a 'freestyle' job that does not allow concurrent builds.



            The job will use a text file named counter.txt that just contains a single line with the counter # in it as my 'state'. I'll save that as an artifact at the end of my job and load it at the start.



            $ cat counter.txt
            1


            First build step: load counter.txt from artifacts:



            enter image description here



            Second build step: bash script to pull the value and check against a threshold (in my case 3). Exit with status=1 unless counter >= 3. If counter.txt doesn't exist it's created and set to 1, otherwise we load the file and increment it, and check the value to determine if we meet the PASS condition.



            enter image description here



            I added two post-build conditions, first I archive counter.txt as an artifact and then delete the workspace. I doubt deleting the workspace is necessary but I added it to just make sure the counter.txt file I'm getting is the artifact in case Jenkins decided it didn't want to overwrite the file or something.



            enter image description here



            When I run this it's doing the right thing:



            enter image description here






            share|improve this answer



























              0














              Figured it out... this is what I did in case it's useful for anyone else:



              I'm using a 'freestyle' job that does not allow concurrent builds.



              The job will use a text file named counter.txt that just contains a single line with the counter # in it as my 'state'. I'll save that as an artifact at the end of my job and load it at the start.



              $ cat counter.txt
              1


              First build step: load counter.txt from artifacts:



              enter image description here



              Second build step: bash script to pull the value and check against a threshold (in my case 3). Exit with status=1 unless counter >= 3. If counter.txt doesn't exist it's created and set to 1, otherwise we load the file and increment it, and check the value to determine if we meet the PASS condition.



              enter image description here



              I added two post-build conditions, first I archive counter.txt as an artifact and then delete the workspace. I doubt deleting the workspace is necessary but I added it to just make sure the counter.txt file I'm getting is the artifact in case Jenkins decided it didn't want to overwrite the file or something.



              enter image description here



              When I run this it's doing the right thing:



              enter image description here






              share|improve this answer

























                0












                0








                0







                Figured it out... this is what I did in case it's useful for anyone else:



                I'm using a 'freestyle' job that does not allow concurrent builds.



                The job will use a text file named counter.txt that just contains a single line with the counter # in it as my 'state'. I'll save that as an artifact at the end of my job and load it at the start.



                $ cat counter.txt
                1


                First build step: load counter.txt from artifacts:



                enter image description here



                Second build step: bash script to pull the value and check against a threshold (in my case 3). Exit with status=1 unless counter >= 3. If counter.txt doesn't exist it's created and set to 1, otherwise we load the file and increment it, and check the value to determine if we meet the PASS condition.



                enter image description here



                I added two post-build conditions, first I archive counter.txt as an artifact and then delete the workspace. I doubt deleting the workspace is necessary but I added it to just make sure the counter.txt file I'm getting is the artifact in case Jenkins decided it didn't want to overwrite the file or something.



                enter image description here



                When I run this it's doing the right thing:



                enter image description here






                share|improve this answer













                Figured it out... this is what I did in case it's useful for anyone else:



                I'm using a 'freestyle' job that does not allow concurrent builds.



                The job will use a text file named counter.txt that just contains a single line with the counter # in it as my 'state'. I'll save that as an artifact at the end of my job and load it at the start.



                $ cat counter.txt
                1


                First build step: load counter.txt from artifacts:



                enter image description here



                Second build step: bash script to pull the value and check against a threshold (in my case 3). Exit with status=1 unless counter >= 3. If counter.txt doesn't exist it's created and set to 1, otherwise we load the file and increment it, and check the value to determine if we meet the PASS condition.



                enter image description here



                I added two post-build conditions, first I archive counter.txt as an artifact and then delete the workspace. I doubt deleting the workspace is necessary but I added it to just make sure the counter.txt file I'm getting is the artifact in case Jenkins decided it didn't want to overwrite the file or something.



                enter image description here



                When I run this it's doing the right thing:



                enter image description here







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 22 at 22:32









                TxAG98TxAG98

                373214




                373214





























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • 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%2fstackoverflow.com%2fquestions%2f55290953%2fis-there-a-way-to-write-a-jenkins-job-that-keeps-state-across-runs%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

                    Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

                    SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

                    은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현