How to run a build, when there is merge request from feature to master branch in GitLab before accepting the merge request










2















I have a created a Jenkins pipeline job and also added the webhook for the piepline in GitLab for the merge events and for the merge request my pipeline is executing.



But I am not able to get after raising the merge request, how can I test the requested merge code before accepting the merge request. (Can I create some temporary branch from gitlabTargetBranch? is it possible)



I am using the two variables gitlabSourceBranch and gitlabTargetBranch in the checkout stage.



Can anyone please suggest what should be added in checkout stage for the above?



Thanks!










share|improve this question






















  • Did you find a solution for this?

    – Vin Shahrdar
    Dec 14 '18 at 22:32











  • @VinShahrdar yes while doing checkout use PreBuildMerge option and please refer github.com/jenkinsci/gitlab-plugin/blob/master/…

    – user_9090
    Dec 17 '18 at 4:53















2















I have a created a Jenkins pipeline job and also added the webhook for the piepline in GitLab for the merge events and for the merge request my pipeline is executing.



But I am not able to get after raising the merge request, how can I test the requested merge code before accepting the merge request. (Can I create some temporary branch from gitlabTargetBranch? is it possible)



I am using the two variables gitlabSourceBranch and gitlabTargetBranch in the checkout stage.



Can anyone please suggest what should be added in checkout stage for the above?



Thanks!










share|improve this question






















  • Did you find a solution for this?

    – Vin Shahrdar
    Dec 14 '18 at 22:32











  • @VinShahrdar yes while doing checkout use PreBuildMerge option and please refer github.com/jenkinsci/gitlab-plugin/blob/master/…

    – user_9090
    Dec 17 '18 at 4:53













2












2








2


2






I have a created a Jenkins pipeline job and also added the webhook for the piepline in GitLab for the merge events and for the merge request my pipeline is executing.



But I am not able to get after raising the merge request, how can I test the requested merge code before accepting the merge request. (Can I create some temporary branch from gitlabTargetBranch? is it possible)



I am using the two variables gitlabSourceBranch and gitlabTargetBranch in the checkout stage.



Can anyone please suggest what should be added in checkout stage for the above?



Thanks!










share|improve this question














I have a created a Jenkins pipeline job and also added the webhook for the piepline in GitLab for the merge events and for the merge request my pipeline is executing.



But I am not able to get after raising the merge request, how can I test the requested merge code before accepting the merge request. (Can I create some temporary branch from gitlabTargetBranch? is it possible)



I am using the two variables gitlabSourceBranch and gitlabTargetBranch in the checkout stage.



Can anyone please suggest what should be added in checkout stage for the above?



Thanks!







jenkins gitlab jenkins-pipeline git-merge






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 16 '18 at 5:14









user_9090user_9090

336110




336110












  • Did you find a solution for this?

    – Vin Shahrdar
    Dec 14 '18 at 22:32











  • @VinShahrdar yes while doing checkout use PreBuildMerge option and please refer github.com/jenkinsci/gitlab-plugin/blob/master/…

    – user_9090
    Dec 17 '18 at 4:53

















  • Did you find a solution for this?

    – Vin Shahrdar
    Dec 14 '18 at 22:32











  • @VinShahrdar yes while doing checkout use PreBuildMerge option and please refer github.com/jenkinsci/gitlab-plugin/blob/master/…

    – user_9090
    Dec 17 '18 at 4:53
















Did you find a solution for this?

– Vin Shahrdar
Dec 14 '18 at 22:32





Did you find a solution for this?

– Vin Shahrdar
Dec 14 '18 at 22:32













@VinShahrdar yes while doing checkout use PreBuildMerge option and please refer github.com/jenkinsci/gitlab-plugin/blob/master/…

– user_9090
Dec 17 '18 at 4:53





@VinShahrdar yes while doing checkout use PreBuildMerge option and please refer github.com/jenkinsci/gitlab-plugin/blob/master/…

– user_9090
Dec 17 '18 at 4:53












1 Answer
1






active

oldest

votes


















0














One alternative would be to use a "gate" repo, a GitLab repo (fork of your first one) where your PR applies, and you run your test after accepting that PR.



If those tests pass, then that would trigger a new PR to the final actual target repo, which can then be automatically accepted.

That way, that final PR has been tested before being accepted.






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%2f53331824%2fhow-to-run-a-build-when-there-is-merge-request-from-feature-to-master-branch-in%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














    One alternative would be to use a "gate" repo, a GitLab repo (fork of your first one) where your PR applies, and you run your test after accepting that PR.



    If those tests pass, then that would trigger a new PR to the final actual target repo, which can then be automatically accepted.

    That way, that final PR has been tested before being accepted.






    share|improve this answer



























      0














      One alternative would be to use a "gate" repo, a GitLab repo (fork of your first one) where your PR applies, and you run your test after accepting that PR.



      If those tests pass, then that would trigger a new PR to the final actual target repo, which can then be automatically accepted.

      That way, that final PR has been tested before being accepted.






      share|improve this answer

























        0












        0








        0







        One alternative would be to use a "gate" repo, a GitLab repo (fork of your first one) where your PR applies, and you run your test after accepting that PR.



        If those tests pass, then that would trigger a new PR to the final actual target repo, which can then be automatically accepted.

        That way, that final PR has been tested before being accepted.






        share|improve this answer













        One alternative would be to use a "gate" repo, a GitLab repo (fork of your first one) where your PR applies, and you run your test after accepting that PR.



        If those tests pass, then that would trigger a new PR to the final actual target repo, which can then be automatically accepted.

        That way, that final PR has been tested before being accepted.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 16 '18 at 5:37









        VonCVonC

        850k30127063266




        850k30127063266





























            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%2f53331824%2fhow-to-run-a-build-when-there-is-merge-request-from-feature-to-master-branch-in%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

            Top Tejano songwriter Luis Silva dead of heart attack at 64

            ReactJS Fetched API data displays live - need Data displayed static

            Evgeni Malkin