Where does Jenkins fit in the devops pipeline?












0














I don't know where could I fit the jenkins tool in the following devops pipeline:



code -> integrate -> test -> release -> deploy -> operate



Maybe it can be in every steps ?










share|improve this question






















  • Jenkins is a plugin manager, can use it for any stage of your pipeline, ex. GIT Plugin to checkout code, Ant Plugin to build, Ansible Plugin (ansible playbooks) for integration tests and packaging, Artifact Repository Plugin for deploying artifacts to a repository manager, etc.
    – masseyb
    Nov 13 '18 at 11:38










  • Correction: Jenkins is not a simple plugin manager. Jenkins is an open source implementation of a Continuous Integration Server written in Java.
    – JRichardsz
    Nov 13 '18 at 14:22












  • @JRichardsz thanks but no thanks? Jenkins is (among other things if you want) a plugin manager and “Plugins are the primary means of enhancing the functionality of a Jenkins environment to suit organization- or user-specific needs.”, ref. jenkins.io/doc/book/managing/plugins
    – masseyb
    Nov 13 '18 at 18:41










  • From jenkins.io: The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
    – JGK
    Nov 13 '18 at 18:45










  • @masseyb what is firefox for you? For me is a super cool browser based on multiples plugins and other functionalities over chrome u opera. With firefox, you can manage plugins (configure, install, delete, etc) but is not a plugin manager. Jenkins is a Continuous Integration Server or automation server based on a large number of integrated and comunity plugins. Check jenkins home page : jenkins.io
    – JRichardsz
    Nov 13 '18 at 20:08
















0














I don't know where could I fit the jenkins tool in the following devops pipeline:



code -> integrate -> test -> release -> deploy -> operate



Maybe it can be in every steps ?










share|improve this question






















  • Jenkins is a plugin manager, can use it for any stage of your pipeline, ex. GIT Plugin to checkout code, Ant Plugin to build, Ansible Plugin (ansible playbooks) for integration tests and packaging, Artifact Repository Plugin for deploying artifacts to a repository manager, etc.
    – masseyb
    Nov 13 '18 at 11:38










  • Correction: Jenkins is not a simple plugin manager. Jenkins is an open source implementation of a Continuous Integration Server written in Java.
    – JRichardsz
    Nov 13 '18 at 14:22












  • @JRichardsz thanks but no thanks? Jenkins is (among other things if you want) a plugin manager and “Plugins are the primary means of enhancing the functionality of a Jenkins environment to suit organization- or user-specific needs.”, ref. jenkins.io/doc/book/managing/plugins
    – masseyb
    Nov 13 '18 at 18:41










  • From jenkins.io: The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
    – JGK
    Nov 13 '18 at 18:45










  • @masseyb what is firefox for you? For me is a super cool browser based on multiples plugins and other functionalities over chrome u opera. With firefox, you can manage plugins (configure, install, delete, etc) but is not a plugin manager. Jenkins is a Continuous Integration Server or automation server based on a large number of integrated and comunity plugins. Check jenkins home page : jenkins.io
    – JRichardsz
    Nov 13 '18 at 20:08














0












0








0


2





I don't know where could I fit the jenkins tool in the following devops pipeline:



code -> integrate -> test -> release -> deploy -> operate



Maybe it can be in every steps ?










share|improve this question













I don't know where could I fit the jenkins tool in the following devops pipeline:



code -> integrate -> test -> release -> deploy -> operate



Maybe it can be in every steps ?







jenkins pipeline devops






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 13 '18 at 9:46









John DoeJohn Doe

336




336












  • Jenkins is a plugin manager, can use it for any stage of your pipeline, ex. GIT Plugin to checkout code, Ant Plugin to build, Ansible Plugin (ansible playbooks) for integration tests and packaging, Artifact Repository Plugin for deploying artifacts to a repository manager, etc.
    – masseyb
    Nov 13 '18 at 11:38










  • Correction: Jenkins is not a simple plugin manager. Jenkins is an open source implementation of a Continuous Integration Server written in Java.
    – JRichardsz
    Nov 13 '18 at 14:22












  • @JRichardsz thanks but no thanks? Jenkins is (among other things if you want) a plugin manager and “Plugins are the primary means of enhancing the functionality of a Jenkins environment to suit organization- or user-specific needs.”, ref. jenkins.io/doc/book/managing/plugins
    – masseyb
    Nov 13 '18 at 18:41










  • From jenkins.io: The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
    – JGK
    Nov 13 '18 at 18:45










  • @masseyb what is firefox for you? For me is a super cool browser based on multiples plugins and other functionalities over chrome u opera. With firefox, you can manage plugins (configure, install, delete, etc) but is not a plugin manager. Jenkins is a Continuous Integration Server or automation server based on a large number of integrated and comunity plugins. Check jenkins home page : jenkins.io
    – JRichardsz
    Nov 13 '18 at 20:08


















  • Jenkins is a plugin manager, can use it for any stage of your pipeline, ex. GIT Plugin to checkout code, Ant Plugin to build, Ansible Plugin (ansible playbooks) for integration tests and packaging, Artifact Repository Plugin for deploying artifacts to a repository manager, etc.
    – masseyb
    Nov 13 '18 at 11:38










  • Correction: Jenkins is not a simple plugin manager. Jenkins is an open source implementation of a Continuous Integration Server written in Java.
    – JRichardsz
    Nov 13 '18 at 14:22












  • @JRichardsz thanks but no thanks? Jenkins is (among other things if you want) a plugin manager and “Plugins are the primary means of enhancing the functionality of a Jenkins environment to suit organization- or user-specific needs.”, ref. jenkins.io/doc/book/managing/plugins
    – masseyb
    Nov 13 '18 at 18:41










  • From jenkins.io: The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
    – JGK
    Nov 13 '18 at 18:45










  • @masseyb what is firefox for you? For me is a super cool browser based on multiples plugins and other functionalities over chrome u opera. With firefox, you can manage plugins (configure, install, delete, etc) but is not a plugin manager. Jenkins is a Continuous Integration Server or automation server based on a large number of integrated and comunity plugins. Check jenkins home page : jenkins.io
    – JRichardsz
    Nov 13 '18 at 20:08
















Jenkins is a plugin manager, can use it for any stage of your pipeline, ex. GIT Plugin to checkout code, Ant Plugin to build, Ansible Plugin (ansible playbooks) for integration tests and packaging, Artifact Repository Plugin for deploying artifacts to a repository manager, etc.
– masseyb
Nov 13 '18 at 11:38




Jenkins is a plugin manager, can use it for any stage of your pipeline, ex. GIT Plugin to checkout code, Ant Plugin to build, Ansible Plugin (ansible playbooks) for integration tests and packaging, Artifact Repository Plugin for deploying artifacts to a repository manager, etc.
– masseyb
Nov 13 '18 at 11:38












Correction: Jenkins is not a simple plugin manager. Jenkins is an open source implementation of a Continuous Integration Server written in Java.
– JRichardsz
Nov 13 '18 at 14:22






Correction: Jenkins is not a simple plugin manager. Jenkins is an open source implementation of a Continuous Integration Server written in Java.
– JRichardsz
Nov 13 '18 at 14:22














@JRichardsz thanks but no thanks? Jenkins is (among other things if you want) a plugin manager and “Plugins are the primary means of enhancing the functionality of a Jenkins environment to suit organization- or user-specific needs.”, ref. jenkins.io/doc/book/managing/plugins
– masseyb
Nov 13 '18 at 18:41




@JRichardsz thanks but no thanks? Jenkins is (among other things if you want) a plugin manager and “Plugins are the primary means of enhancing the functionality of a Jenkins environment to suit organization- or user-specific needs.”, ref. jenkins.io/doc/book/managing/plugins
– masseyb
Nov 13 '18 at 18:41












From jenkins.io: The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
– JGK
Nov 13 '18 at 18:45




From jenkins.io: The leading open source automation server, Jenkins provides hundreds of plugins to support building, deploying and automating any project.
– JGK
Nov 13 '18 at 18:45












@masseyb what is firefox for you? For me is a super cool browser based on multiples plugins and other functionalities over chrome u opera. With firefox, you can manage plugins (configure, install, delete, etc) but is not a plugin manager. Jenkins is a Continuous Integration Server or automation server based on a large number of integrated and comunity plugins. Check jenkins home page : jenkins.io
– JRichardsz
Nov 13 '18 at 20:08




@masseyb what is firefox for you? For me is a super cool browser based on multiples plugins and other functionalities over chrome u opera. With firefox, you can manage plugins (configure, install, delete, etc) but is not a plugin manager. Jenkins is a Continuous Integration Server or automation server based on a large number of integrated and comunity plugins. Check jenkins home page : jenkins.io
– JRichardsz
Nov 13 '18 at 20:08












3 Answers
3






active

oldest

votes


















1














Jenkins is use for the Build, Test, and Deploy stages of the continuous delivery pipeline.






share|improve this answer





























    1














    You can have "n" number of stages in a pipeline that can be configured using Jenkins.



    Stages as follows (example) :-




    code -> integrate -> test -> release -> deploy -> operate







    share|improve this answer





























      1














      Jenkins is a build factory. In other words, its primary use is to run tasks that dedicated to build, integrate and deliver applications. It's a typical DEVOPS tool.



      Jenkins can be used to build pipelines (sequences of tasks) or to be called from a pipeline (to execute one of the pipeline's tasks).



      The great thing about Jenkins is that it integrates nicely with other devops tools:




      • SCM: SVN, Github, Gitlab

      • Build: maven, gradle

      • Test: Cucumber reports

      • Quality: SonarQube

      • Deployment: Octopus Deploy, XL Deploy, Run Deck...


      You name it!



      However, Jenkins is generally not used to "code" and "operated" applications.



      A typical pipeline would be:



      Try Pull Request => Build Release Candidate => Deploy RC on Integration => Deploy on Production


      This is a over simplified pipeline, just to give an idea of the scope of this tool. A production grade piepline should include security checks, and integrate nicely with human validation when needed.






      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%2f53278123%2fwhere-does-jenkins-fit-in-the-devops-pipeline%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        1














        Jenkins is use for the Build, Test, and Deploy stages of the continuous delivery pipeline.






        share|improve this answer


























          1














          Jenkins is use for the Build, Test, and Deploy stages of the continuous delivery pipeline.






          share|improve this answer
























            1












            1








            1






            Jenkins is use for the Build, Test, and Deploy stages of the continuous delivery pipeline.






            share|improve this answer












            Jenkins is use for the Build, Test, and Deploy stages of the continuous delivery pipeline.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Nov 13 '18 at 9:59









            FlokiFloki

            112




            112

























                1














                You can have "n" number of stages in a pipeline that can be configured using Jenkins.



                Stages as follows (example) :-




                code -> integrate -> test -> release -> deploy -> operate







                share|improve this answer


























                  1














                  You can have "n" number of stages in a pipeline that can be configured using Jenkins.



                  Stages as follows (example) :-




                  code -> integrate -> test -> release -> deploy -> operate







                  share|improve this answer
























                    1












                    1








                    1






                    You can have "n" number of stages in a pipeline that can be configured using Jenkins.



                    Stages as follows (example) :-




                    code -> integrate -> test -> release -> deploy -> operate







                    share|improve this answer












                    You can have "n" number of stages in a pipeline that can be configured using Jenkins.



                    Stages as follows (example) :-




                    code -> integrate -> test -> release -> deploy -> operate








                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 13 '18 at 10:51









                    user_9090user_9090

                    1669




                    1669























                        1














                        Jenkins is a build factory. In other words, its primary use is to run tasks that dedicated to build, integrate and deliver applications. It's a typical DEVOPS tool.



                        Jenkins can be used to build pipelines (sequences of tasks) or to be called from a pipeline (to execute one of the pipeline's tasks).



                        The great thing about Jenkins is that it integrates nicely with other devops tools:




                        • SCM: SVN, Github, Gitlab

                        • Build: maven, gradle

                        • Test: Cucumber reports

                        • Quality: SonarQube

                        • Deployment: Octopus Deploy, XL Deploy, Run Deck...


                        You name it!



                        However, Jenkins is generally not used to "code" and "operated" applications.



                        A typical pipeline would be:



                        Try Pull Request => Build Release Candidate => Deploy RC on Integration => Deploy on Production


                        This is a over simplified pipeline, just to give an idea of the scope of this tool. A production grade piepline should include security checks, and integrate nicely with human validation when needed.






                        share|improve this answer


























                          1














                          Jenkins is a build factory. In other words, its primary use is to run tasks that dedicated to build, integrate and deliver applications. It's a typical DEVOPS tool.



                          Jenkins can be used to build pipelines (sequences of tasks) or to be called from a pipeline (to execute one of the pipeline's tasks).



                          The great thing about Jenkins is that it integrates nicely with other devops tools:




                          • SCM: SVN, Github, Gitlab

                          • Build: maven, gradle

                          • Test: Cucumber reports

                          • Quality: SonarQube

                          • Deployment: Octopus Deploy, XL Deploy, Run Deck...


                          You name it!



                          However, Jenkins is generally not used to "code" and "operated" applications.



                          A typical pipeline would be:



                          Try Pull Request => Build Release Candidate => Deploy RC on Integration => Deploy on Production


                          This is a over simplified pipeline, just to give an idea of the scope of this tool. A production grade piepline should include security checks, and integrate nicely with human validation when needed.






                          share|improve this answer
























                            1












                            1








                            1






                            Jenkins is a build factory. In other words, its primary use is to run tasks that dedicated to build, integrate and deliver applications. It's a typical DEVOPS tool.



                            Jenkins can be used to build pipelines (sequences of tasks) or to be called from a pipeline (to execute one of the pipeline's tasks).



                            The great thing about Jenkins is that it integrates nicely with other devops tools:




                            • SCM: SVN, Github, Gitlab

                            • Build: maven, gradle

                            • Test: Cucumber reports

                            • Quality: SonarQube

                            • Deployment: Octopus Deploy, XL Deploy, Run Deck...


                            You name it!



                            However, Jenkins is generally not used to "code" and "operated" applications.



                            A typical pipeline would be:



                            Try Pull Request => Build Release Candidate => Deploy RC on Integration => Deploy on Production


                            This is a over simplified pipeline, just to give an idea of the scope of this tool. A production grade piepline should include security checks, and integrate nicely with human validation when needed.






                            share|improve this answer












                            Jenkins is a build factory. In other words, its primary use is to run tasks that dedicated to build, integrate and deliver applications. It's a typical DEVOPS tool.



                            Jenkins can be used to build pipelines (sequences of tasks) or to be called from a pipeline (to execute one of the pipeline's tasks).



                            The great thing about Jenkins is that it integrates nicely with other devops tools:




                            • SCM: SVN, Github, Gitlab

                            • Build: maven, gradle

                            • Test: Cucumber reports

                            • Quality: SonarQube

                            • Deployment: Octopus Deploy, XL Deploy, Run Deck...


                            You name it!



                            However, Jenkins is generally not used to "code" and "operated" applications.



                            A typical pipeline would be:



                            Try Pull Request => Build Release Candidate => Deploy RC on Integration => Deploy on Production


                            This is a over simplified pipeline, just to give an idea of the scope of this tool. A production grade piepline should include security checks, and integrate nicely with human validation when needed.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered yesterday









                            avi.elkharratavi.elkharrat

                            1,41411325




                            1,41411325






























                                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.





                                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%2fstackoverflow.com%2fquestions%2f53278123%2fwhere-does-jenkins-fit-in-the-devops-pipeline%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

                                Bressuire

                                Vorschmack

                                Quarantine