Jenkins scripted pipeline to trigger job only when commits happen in Github





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







0















We use CloudBees-2.138.2.2 Jenkins and have had lot of challenges to trigger jenkins jobs only based on commits in our Github repo. I am still looking for the exact working script for scripted pipeline and not declarative one.



so For example :- pipelineTriggers([cron('0-59/2 * * * *')]), works
but pipelineTriggers([pollSCM('0-59/2 * * * *')]), never works despite new commits










share|improve this question

























  • Did you consider such option as using 'Pipeline script from SCM' (via Jenkinsfile) with 'GitHub hook trigger for GITScm polling' enabled? E.g., see this example. It's a standard way of configuration and much easier to configure.

    – biruk1230
    Jan 3 at 16:09













  • Thanks for the response. I am aware of that but we want to establish entire pipeline using a single Jenkinsfile that uses scripted pipeline syntax. Hence the ask.

    – Ashley
    Jan 3 at 16:55


















0















We use CloudBees-2.138.2.2 Jenkins and have had lot of challenges to trigger jenkins jobs only based on commits in our Github repo. I am still looking for the exact working script for scripted pipeline and not declarative one.



so For example :- pipelineTriggers([cron('0-59/2 * * * *')]), works
but pipelineTriggers([pollSCM('0-59/2 * * * *')]), never works despite new commits










share|improve this question

























  • Did you consider such option as using 'Pipeline script from SCM' (via Jenkinsfile) with 'GitHub hook trigger for GITScm polling' enabled? E.g., see this example. It's a standard way of configuration and much easier to configure.

    – biruk1230
    Jan 3 at 16:09













  • Thanks for the response. I am aware of that but we want to establish entire pipeline using a single Jenkinsfile that uses scripted pipeline syntax. Hence the ask.

    – Ashley
    Jan 3 at 16:55














0












0








0








We use CloudBees-2.138.2.2 Jenkins and have had lot of challenges to trigger jenkins jobs only based on commits in our Github repo. I am still looking for the exact working script for scripted pipeline and not declarative one.



so For example :- pipelineTriggers([cron('0-59/2 * * * *')]), works
but pipelineTriggers([pollSCM('0-59/2 * * * *')]), never works despite new commits










share|improve this question
















We use CloudBees-2.138.2.2 Jenkins and have had lot of challenges to trigger jenkins jobs only based on commits in our Github repo. I am still looking for the exact working script for scripted pipeline and not declarative one.



so For example :- pipelineTriggers([cron('0-59/2 * * * *')]), works
but pipelineTriggers([pollSCM('0-59/2 * * * *')]), never works despite new commits







jenkins jenkins-pipeline cloudbees jenkins-groovy crontrigger






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 3 at 17:56







Ashley

















asked Jan 3 at 14:55









AshleyAshley

989




989













  • Did you consider such option as using 'Pipeline script from SCM' (via Jenkinsfile) with 'GitHub hook trigger for GITScm polling' enabled? E.g., see this example. It's a standard way of configuration and much easier to configure.

    – biruk1230
    Jan 3 at 16:09













  • Thanks for the response. I am aware of that but we want to establish entire pipeline using a single Jenkinsfile that uses scripted pipeline syntax. Hence the ask.

    – Ashley
    Jan 3 at 16:55



















  • Did you consider such option as using 'Pipeline script from SCM' (via Jenkinsfile) with 'GitHub hook trigger for GITScm polling' enabled? E.g., see this example. It's a standard way of configuration and much easier to configure.

    – biruk1230
    Jan 3 at 16:09













  • Thanks for the response. I am aware of that but we want to establish entire pipeline using a single Jenkinsfile that uses scripted pipeline syntax. Hence the ask.

    – Ashley
    Jan 3 at 16:55

















Did you consider such option as using 'Pipeline script from SCM' (via Jenkinsfile) with 'GitHub hook trigger for GITScm polling' enabled? E.g., see this example. It's a standard way of configuration and much easier to configure.

– biruk1230
Jan 3 at 16:09







Did you consider such option as using 'Pipeline script from SCM' (via Jenkinsfile) with 'GitHub hook trigger for GITScm polling' enabled? E.g., see this example. It's a standard way of configuration and much easier to configure.

– biruk1230
Jan 3 at 16:09















Thanks for the response. I am aware of that but we want to establish entire pipeline using a single Jenkinsfile that uses scripted pipeline syntax. Hence the ask.

– Ashley
Jan 3 at 16:55





Thanks for the response. I am aware of that but we want to establish entire pipeline using a single Jenkinsfile that uses scripted pipeline syntax. Hence the ask.

– Ashley
Jan 3 at 16:55












2 Answers
2






active

oldest

votes


















0














was able to make it work using :-



pipelineTriggers([pollSCM('* * * * *')]) under properties



This way the job polls the repo every minute and will trigger build only when it detects a new commit.






share|improve this answer































    0














    You can try adding the following in your scripted pipeline



    properties([pipelineTriggers([githubPush()])])





    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%2f54024726%2fjenkins-scripted-pipeline-to-trigger-job-only-when-commits-happen-in-github%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      was able to make it work using :-



      pipelineTriggers([pollSCM('* * * * *')]) under properties



      This way the job polls the repo every minute and will trigger build only when it detects a new commit.






      share|improve this answer




























        0














        was able to make it work using :-



        pipelineTriggers([pollSCM('* * * * *')]) under properties



        This way the job polls the repo every minute and will trigger build only when it detects a new commit.






        share|improve this answer


























          0












          0








          0







          was able to make it work using :-



          pipelineTriggers([pollSCM('* * * * *')]) under properties



          This way the job polls the repo every minute and will trigger build only when it detects a new commit.






          share|improve this answer













          was able to make it work using :-



          pipelineTriggers([pollSCM('* * * * *')]) under properties



          This way the job polls the repo every minute and will trigger build only when it detects a new commit.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 3 at 22:51









          AshleyAshley

          989




          989

























              0














              You can try adding the following in your scripted pipeline



              properties([pipelineTriggers([githubPush()])])





              share|improve this answer




























                0














                You can try adding the following in your scripted pipeline



                properties([pipelineTriggers([githubPush()])])





                share|improve this answer


























                  0












                  0








                  0







                  You can try adding the following in your scripted pipeline



                  properties([pipelineTriggers([githubPush()])])





                  share|improve this answer













                  You can try adding the following in your scripted pipeline



                  properties([pipelineTriggers([githubPush()])])






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 19 at 22:44









                  NicodemuzNicodemuz

                  1,38711424




                  1,38711424






























                      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%2f54024726%2fjenkins-scripted-pipeline-to-trigger-job-only-when-commits-happen-in-github%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

                      MongoDB - Not Authorized To Execute Command

                      How to fix TextFormField cause rebuild widget in Flutter

                      in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith