-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run multiple batch-enabled instances on separate target branches #267
Comments
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Oct 1, 2021
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 30, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 30, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 30, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 30, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 30, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 31, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 31, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 31, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
sg70
added a commit
to sg70/marge-bot
that referenced
this issue
Mar 31, 2022
In order to support batch jobs in parallel, the batch branches need to be tied to the target branch name. Signed-off-by: Sascha Binckly <sascha.binckly@mbition.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a project we use a marge bot instance per release branch so that we can run merges in parallel. However in that configuration, only one instance can do batches. This is because the branch name used for the batch is constant:
marge_bot_batch_merge_job
.Instead it should be using a name that depends on the target branch. So for example for target branch
release/20.08
, it should usemarge_bot_batch_merge_job/release/20.08
.However there is no way to configure the name of the batch branch.
The text was updated successfully, but these errors were encountered: