Dear Jenkins Community,
in the context of a University project I have to evaluate the software architecture of the Jenkins software. Unfortunately I could not find any documentation regarding architectural decisions like the use of patterns, key drivers/quality attributes and architectural views. Do you know whether such documentation exists somewhere? Do you maybe know whether such considerations played and/or still play a role in the development of the core software? In return I will be happy to share my evaluation with the community which might help with structuring the software better and will hopefully offer a few recommendations for how to improve the software on its key quality attributes. All the best, Peter Ullrich -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ff2dbea8-2bb7-42e8-b79a-5d76f81842c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
