Greetings Robert, The release-merge jobs are independent of branches therefore we have one job per-project. Having more number of jobs would not matter if they were not periodically run. I can update the default values for the jobs but still you would need to edit the build Params before running the job. Please open a helpdesk request, if this is required.
Cheers, Anil On Sat, 21 Nov 2020, 03:34 Robert Varga, <[email protected]> wrote: > Hello, > > I have been using infrautils-release-merge and its ilk for some time. > Overall they work just fine, but they are annoying to use. > > Everytime you need to release something, you have to fill out a bunch of > branch-related parameters -- like STREAM/GERRIT_BRANCH/GERRIT_REFSPEC > plus DISTRIBUTION_TYPE. This is very clunky with multiple branches, as > you just cannot use 'rebuild' and get correct readout of patches that > went into that release. > > This is in stark contrast to *-maven-stage jobs -- those are per-branch > and come with all this cruft pre-populated. > > Given maven-stage jobs are input to release-merge, I think release-merge > jobs need to be per-branch as well. > > Is there a way we can do that? Sorry my JJB-fu is not up to par. > > Thanks, > Robert > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1186): https://lists.opendaylight.org/g/infrastructure/message/1186 Mute This Topic: https://lists.opendaylight.org/mt/78403127/21656 Group Owner: [email protected] Unsubscribe: https://lists.opendaylight.org/g/infrastructure/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
