Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-1162

Non-repository based builds

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.1
    • Builds, Triggers
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      One of the points made with Bamboo is the ability to use the CI process to control things other that the standard build stuff like backups and publishing to web sites, etc... This makes Bamboo more valuable to manage and control these other processes in a consistent way with all the metrics and notification support that Bamboo provides. However, many of those processes are schedule based and not based on repository changes. Specifically, there is no need to specify a repository at all. The request is to provide an option to specify repository of none or similar way to specify in a build plan that the repository checkout phase is not required. The build in this case is just a script.
      I guess the workaround with current bamboo is configure some unimportant repository checkout

            [BAM-1162] Non-repository based builds

            MarkC added a comment -

            This is now available in Bamboo 3.1

            MarkC added a comment - This is now available in Bamboo 3.1

            Bob Swift added a comment -

            Dummy Repository Plugin might help here, but haven't had time to try it out.

            Bob Swift added a comment - Dummy Repository Plugin might help here, but haven't had time to try it out.

            David A. Riggs added a comment -

            We have dependent processes that need kicked off after a parent build, and those processes have nothing to do with checking out source code. I have currently configured them to do an `svn co` of some tiny, unrelated code just to appease Bamboo. This is a big sore spot that many other Continuous Integration servers allow and Bamboo does not.

            David A. Riggs added a comment - We have dependent processes that need kicked off after a parent build, and those processes have nothing to do with checking out source code. I have currently configured them to do an `svn co` of some tiny, unrelated code just to appease Bamboo. This is a big sore spot that many other Continuous Integration servers allow and Bamboo does not.

            maplemuse added a comment -

            Defining this would allow a Nightly Build plan to be created as cron based, and have other, polling plans as dependent builds, adding a nightly build capability.

            Or is there another way to combine nightly build and polling of a single build plan?

            maplemuse added a comment - Defining this would allow a Nightly Build plan to be created as cron based, and have other, polling plans as dependent builds, adding a nightly build capability. Or is there another way to combine nightly build and polling of a single build plan?

              mgardias Marcin Gardias
              bob.swift Bob Swift
              Votes:
              6 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: