Hundreds of branch with name origin/merge-requests/xxx












0














I enable the CI flow between Gitlab to Jenkins.



When I got to Gitlab Portal, only the branchs been created by me are listed there. But when I run the CI flow, from Jenkins console output, it will list extra hundreds branchs with name origin/merge-requests/xxx, xxx is the number from 1 to 156 in my case.



Any idea why and how can I delete these branches?










share|improve this question



























    0














    I enable the CI flow between Gitlab to Jenkins.



    When I got to Gitlab Portal, only the branchs been created by me are listed there. But when I run the CI flow, from Jenkins console output, it will list extra hundreds branchs with name origin/merge-requests/xxx, xxx is the number from 1 to 156 in my case.



    Any idea why and how can I delete these branches?










    share|improve this question

























      0












      0








      0







      I enable the CI flow between Gitlab to Jenkins.



      When I got to Gitlab Portal, only the branchs been created by me are listed there. But when I run the CI flow, from Jenkins console output, it will list extra hundreds branchs with name origin/merge-requests/xxx, xxx is the number from 1 to 156 in my case.



      Any idea why and how can I delete these branches?










      share|improve this question













      I enable the CI flow between Gitlab to Jenkins.



      When I got to Gitlab Portal, only the branchs been created by me are listed there. But when I run the CI flow, from Jenkins console output, it will list extra hundreds branchs with name origin/merge-requests/xxx, xxx is the number from 1 to 156 in my case.



      Any idea why and how can I delete these branches?







      gitlab branching-and-merging






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 22:16









      QiangQiang

      1




      1
























          1 Answer
          1






          active

          oldest

          votes


















          0














          It is because Jenkins never clean local Git repo which carry a lot of stale remote branch info. These branches already been auto deleted from Git repo.



          Inside Jenkins, after install Jenkins Git Plugin, we have two options to help us clean this legacy data:



          Source Code Management ==> Additional Behaviors:
          Wipe out repository & force clone
          Prune stale remote-tracking branches






          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%2f53421212%2fhundreds-of-branch-with-name-origin-merge-requests-xxx%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














            It is because Jenkins never clean local Git repo which carry a lot of stale remote branch info. These branches already been auto deleted from Git repo.



            Inside Jenkins, after install Jenkins Git Plugin, we have two options to help us clean this legacy data:



            Source Code Management ==> Additional Behaviors:
            Wipe out repository & force clone
            Prune stale remote-tracking branches






            share|improve this answer


























              0














              It is because Jenkins never clean local Git repo which carry a lot of stale remote branch info. These branches already been auto deleted from Git repo.



              Inside Jenkins, after install Jenkins Git Plugin, we have two options to help us clean this legacy data:



              Source Code Management ==> Additional Behaviors:
              Wipe out repository & force clone
              Prune stale remote-tracking branches






              share|improve this answer
























                0












                0








                0






                It is because Jenkins never clean local Git repo which carry a lot of stale remote branch info. These branches already been auto deleted from Git repo.



                Inside Jenkins, after install Jenkins Git Plugin, we have two options to help us clean this legacy data:



                Source Code Management ==> Additional Behaviors:
                Wipe out repository & force clone
                Prune stale remote-tracking branches






                share|improve this answer












                It is because Jenkins never clean local Git repo which carry a lot of stale remote branch info. These branches already been auto deleted from Git repo.



                Inside Jenkins, after install Jenkins Git Plugin, we have two options to help us clean this legacy data:



                Source Code Management ==> Additional Behaviors:
                Wipe out repository & force clone
                Prune stale remote-tracking branches







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 4 '18 at 18:23









                QiangQiang

                1




                1






























                    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%2f53421212%2fhundreds-of-branch-with-name-origin-merge-requests-xxx%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

                    404 Error Contact Form 7 ajax form submitting

                    How to know if a Active Directory user can login interactively

                    Refactoring coordinates for Minecraft Pi buildings written in Python