• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      I don't know how difficult this would be to implement, but it would be handy to
      have a user-definable set of "default" project settings that cascade into the
      setting for real projects. Real project can override the cascaded properties as
      they see fit.

      For example, almost every one of my projects uses the Sventon repository
      browser. When it is enabled they all point to the same URL and the same
      repository instance. When I start a new project I have to set up Sventon with
      these properties (with out typos). It would be easier to have the project
      automatically aquire these setting from the cascade.

      If at some later date I was to move Sventon to a new location I would like to be
      able to change the settings in one place (the top of the cascade) and have all
      the projects pick up the change. Currently I would have to edit all of the
      projects individually (with out making mistakes).

      In the few cases where I do not need the cascaded setting I would like to be
      able to override them in the individual projects.

      I've used Sventon in my examples, but in practice I always publish JavaDocs and
      Junit reports to the same location (relative to the project). I always pick up
      the Cobertura coverage report from the same location. I poll the source
      repository at the same time schedule. I use the same project-based security for
      most of my projects (there are a couple of projects where I need to give
      people less access rights).

      More importantly I always want the "Trigger even if build is unstable" setting
      to be turned on for all projects (I want to see how unstable builds effect down
      stream projects). However, we only get this option when we assign the first down
      stream project and it's default is off. Since I'm usually concerned with
      configuring the down stream project at this point it's easy to forget to set
      this flag.

          [JENKINS-3157] Feature request: cascading project settings

          Bart Shappee added a comment -

          For the projects I'm working this feature would be exceptionally useful, for many different builds were there are just slight tweaks to the build & test cycle to cover all variants.

          Bart Shappee added a comment - For the projects I'm working this feature would be exceptionally useful, for many different builds were there are just slight tweaks to the build & test cycle to cover all variants.

          Torresz Daniel added a comment - - edited

          We should decide between Hudson and Jenkins and we extremely need this feature. So I'd like to ask that will this feature implemented in the near future in Jenkins? Thanks for your answer!

          Torresz Daniel added a comment - - edited We should decide between Hudson and Jenkins and we extremely need this feature. So I'd like to ask that will this feature implemented in the near future in Jenkins? Thanks for your answer!

          David Ishee added a comment -

          I rely on this in my Hudson installation. Looks like I can't upgrade to Jenkins as a "drop in replacement" for Hudson according to https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins

          David Ishee added a comment - I rely on this in my Hudson installation. Looks like I can't upgrade to Jenkins as a "drop in replacement" for Hudson according to https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins

          Phil Rumble added a comment -

          Is this ever going to be ported from Hudson to Jenkins?

          Phil Rumble added a comment - Is this ever going to be ported from Hudson to Jenkins?

          Zofren Kopat added a comment -

          I really need this feature. I have nearly 200 jobs and I can't manage to update specific cobertura threshold, defined at the company level and recently updated. And this is only an example of planned modifications.

          Zofren Kopat added a comment - I really need this feature. I have nearly 200 jobs and I can't manage to update specific cobertura threshold, defined at the company level and recently updated. And this is only an example of planned modifications.

          Mike Smith added a comment -

          Any updates on this one?

          Mike Smith added a comment - Any updates on this one?

          Do you plan to merge this feature from Hudson?

          Ireneusz Makowski added a comment - Do you plan to merge this feature from Hudson?

          Seeing this issue has been opened and unassigned for more than 4 years , I highly doubt that the cascading project feature added by Oracle in Hudson will ever be ported to the Jenkins core or as a free plugin.

          In fact, an equivalent feature has been available since 2011 as part of the Jenkins Enterprise offering by Cloudbees, and is known as the 'Jenkins Enterprise Templates plugin':
          See http://kohsuke.org/2011/11/15/introducing-template-plugin/

          This commercial offering also benefits from the complementary 'Folders' and 'Role based access security' plugins that greatly simplify the administration of large Jenkins installations with hundreds or more jobs.

          What really is a pity is that, although the 'Folders' plugin is now available with a free licence (see http://www.cloudbees.com/press-room/cloudbees-donates-five-plugins-jenkins-community.cb), the 'Templates' plugin is not.

          With a templating/cascading configuration feature being such a basic requirement of a CI server, IMHO it really should be included in the core Jenkins, along with the Folders plugin as well for that matter, and possibly the Role-based access plugin too ...

          I mean, if you look at good old Apache Continuum, it's been featuring Project groups, Build definitions and common build schedules, and project-based security from the beginning...

          Laurent Denanot added a comment - Seeing this issue has been opened and unassigned for more than 4 years , I highly doubt that the cascading project feature added by Oracle in Hudson will ever be ported to the Jenkins core or as a free plugin. In fact, an equivalent feature has been available since 2011 as part of the Jenkins Enterprise offering by Cloudbees, and is known as the 'Jenkins Enterprise Templates plugin': See http://kohsuke.org/2011/11/15/introducing-template-plugin/ This commercial offering also benefits from the complementary 'Folders' and 'Role based access security' plugins that greatly simplify the administration of large Jenkins installations with hundreds or more jobs. What really is a pity is that, although the 'Folders' plugin is now available with a free licence (see http://www.cloudbees.com/press-room/cloudbees-donates-five-plugins-jenkins-community.cb ), the 'Templates' plugin is not. With a templating/cascading configuration feature being such a basic requirement of a CI server, IMHO it really should be included in the core Jenkins, along with the Folders plugin as well for that matter, and possibly the Role-based access plugin too ... I mean, if you look at good old Apache Continuum, it's been featuring Project groups, Build definitions and common build schedules, and project-based security from the beginning...

          Ed Randall added a comment - - edited

          The "Inheritance Plugin" is not perfect but seems to mostly solve this problem.
          https://wiki.jenkins-ci.org/display/JENKINS/inheritance-plugin

          Ed Randall added a comment - - edited The "Inheritance Plugin" is not perfect but seems to mostly solve this problem. https://wiki.jenkins-ci.org/display/JENKINS/inheritance-plugin

          Aidan Gauland added a comment -

          The Inheritance plugin hasn't had a release since 2014, and does not work with SCM polling.

          Polling will only work for many SCM plug-ins, if the SCM property or its polling property is enabled is defined on a job itself, but not if it's inherited. We are investigating whether this can be fixed without having to alter the code of the SCM plug-ins themselves.

          So it is not a viable option for many users.

          Aidan Gauland added a comment - The Inheritance plugin hasn't had a release since 2014, and does not work with SCM polling. Polling will only work for many SCM plug-ins, if the SCM property or its polling property is enabled is defined on a job itself, but not if it's inherited. We are investigating whether this can be fixed without having to alter the code of the SCM plug-ins themselves. So it is not a viable option for many users.

            Unassigned Unassigned
            stormcloud stormcloud
            Votes:
            163 Vote for this issue
            Watchers:
            98 Start watching this issue

              Created:
              Updated: