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

Manual execution of jobs even when jobs don't fail

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Stages
    • 0
    • 2
    • 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.

    Description

      There I uses the newer features like Stages and having many jobs inside of stages quite a lot.

      It works quite well when doing a complete production build. If something fails in between I can try to fix things and hit the "Rerun Failed Jobs".

      But I would need the functionality to run individual jobs on demand, not only the complete build or the "failed" jobs.

      Why would this be important:

      1) for testing purposes. When setting up/maintaining such a build it takes too long to restart the complete build for just seeing whether one special job is working well. In theory it would be possible to disable all jobs not needed for that testrun, but with that many jobs this is not a really practical solution.

      2) sometimes we only need special parts of the complete build.
      Doing a complete build takes lots of time (up to 24h in this example) and wastes lots of resources. Here it would be possible to duplicate those jobs that might be used alone, but this also is not very practical as one would have to maintain to many builds in parallel.

      So it would be very helpful to get the possibility to have a possibility to start individual jobs of a complex build.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              e816ea2f0644 rjsathome
              Votes:
              9 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: