You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's common to have many repositories that follow the same structure, in a way that you could have a single general pipeline with multiple materials and figure out which one to build based on GO_MATERIAL_[MATERIAL_NAME]_HAS_CHANGED env variables.
Right now, if we do so, all pull requests in different materials will be updated no matter if they triggered the pipeline or not. It would be nice if a check is added here:
LOGGER.error(String.format("Error occurred. Could not update build status - URL: %s Revision: %s Build: %s Result: %s", url, revision, pipelineInstance, result), e);
}
}
}
to run updateStatus only if that material has changed. It makes sense to me to have that check unconditionally, but at least it can be a configuration if I'm missing something.
The text was updated successfully, but these errors were encountered:
alirezamirian
changed the title
update status only if material has changed
Update status only if material has changed
Dec 10, 2020
It's common to have many repositories that follow the same structure, in a way that you could have a single general pipeline with multiple materials and figure out which one to build based on
GO_MATERIAL_[MATERIAL_NAME]_HAS_CHANGED
env variables.Right now, if we do so, all pull requests in different materials will be updated no matter if they triggered the pipeline or not. It would be nice if a check is added here:
gocd-build-status-notifier/common/src/main/java/com/tw/go/plugin/BuildStatusNotifierPlugin.java
Lines 155 to 176 in d1bafa7
to run updateStatus only if that material has changed. It makes sense to me to have that check unconditionally, but at least it can be a configuration if I'm missing something.
The text was updated successfully, but these errors were encountered: