Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-30780

Natively support project embedded plugin, build, continuous delivery configuration

    Details

    • Similar Issues:

      Description

      Jenkin's is primarily configured via web ui. an evolved approach is to bundle the instructions/configurations with the project. Similar to:

      Once the build is configured, there should be an oportuntiy to supplement & override any functionality from the project embedded config file for additional features or for purposes of security.

      It would be great if the configuration could bring along plugins as well.

      Executing these builds should be in isolation so it doesn't bring down the server.

      The current strategy of it all being configured from the UI has several negatives:

      1. Encourages seperation between the developers on the build & release folks or the ops folks
      2. Doesn't allow uniform and simultaneous handling & tagging of the continuous delivery config as well as the project source code i.e. I should be able to say tag the release 2.0 and the build instructions as well as the code would be versioned together.
      3. makes it harder for others to understand the deployment processes

      Jenkin's could be configured at a server level, project level, and then embedded as part of the project. This is similar to Maven where you can configure at the server level ($M2_HOME/conf/settings.xml) and the user level (${user.home}/.m2/settings.xml) and at the project level with pom.xml (you could several numbers of poms that inherit from each other)

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          Is this a candidate for Jenkins 2.0? If so, why is it filed against Literate Plugin? Could you please clarify this?

          Show
          danielbeck Daniel Beck added a comment - Is this a candidate for Jenkins 2.0? If so, why is it filed against Literate Plugin? Could you please clarify this?
          Hide
          levonk Levon Karayan added a comment -

          Yes it is a candidate for 2.0, it's to make the philosophy of the literate plugin be tightly integrated with jenkins core (so overrides can happen from the server) workflows and all. If it's not the right place I can move it, if you don't want to.

          Show
          levonk Levon Karayan added a comment - Yes it is a candidate for 2.0, it's to make the philosophy of the literate plugin be tightly integrated with jenkins core (so overrides can happen from the server) workflows and all. If it's not the right place I can move it, if you don't want to.
          Hide
          danielbeck Daniel Beck added a comment -

          A note on the label change: This change is currently not planned for Jenkins 2.0, that's all it means. In a project like Jenkins it's very difficult to say something will not be done – but it will probably not be done by me or the other 2.0 contributors I know of. If you want to contribute it, let me know and I'll coordinate with you to get it in.

          Show
          danielbeck Daniel Beck added a comment - A note on the label change: This change is currently not planned for Jenkins 2.0, that's all it means. In a project like Jenkins it's very difficult to say something will not be done – but it will probably not be done by me or the other 2.0 contributors I know of. If you want to contribute it, let me know and I'll coordinate with you to get it in.
          Hide
          stephenconnolly Stephen Connolly added a comment -

          Pipeline is the successor for literate

          Show
          stephenconnolly Stephen Connolly added a comment - Pipeline is the successor for literate

            People

            • Assignee:
              stephenconnolly Stephen Connolly
              Reporter:
              levonk Levon Karayan
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: