mrueegg
commented
6 years ago Hi,
Please excuse my late response.
Unfortunately, I was not yet able to reproduce this with Bamboo 6.1.
1) I ran the seed task with the following example DSL and "Action for not-referenced Bamboo objects" = DELETE:
project(key: 'PROJECTKEY', name: 'my project') {
plan(key: 'SIMPLEPLAN', name: 'my simple plan') {
deploymentProject(name: 'DP1') {
description 'my deployment project'
environment(name: 'staging') {
description 'Staging env'
notifications {
custom(event: NotificationEvent.DEPLOYMENT_FINISHED,
pluginKey: 'com.atlassian.bamboo.plugins.bamboo-slack:recipient.slack') {
configure(
webhookUrl: "x",
channel: "y",
botName: "z"
)
}
custom(event: NotificationEvent.DEPLOYMENT_FINISHED,
pluginKey: 'com.atlassian.bamboo.plugins.bamboo-slack:recipient.slack') {
configure(
webhookUrl: "x",
channel: "y",
botName: "z"
)
}
}
}
}
}
}- I removed the complete
notificationsblock and re-run the seed task. - The seed task was successful.
Do you see any differences compared to your example?
Thanks, Michael
Version 1.9.7 Bamboo Version: 6.1.0
We're seeing a
ConcurrentModificationExceptionwhen it tries to update/delete deployment environment custom notifications.Steps to reproduce
Add a Custom Environment Notification to a Deployment Plan
notificationsand run the seed again.Not sure if this is just specific to custom environment notifications.
EDIT: It only seems to happen when there's two environment notifications that exist. Haven't tried it with plan notifications.