Enhancement: Deploy job should by default publish data to Environment dashboard

[deors]

Deploy job should by default publish data to Environment dashboard. Currently it is not done. Investigate if this is a limitation of the DSL, and if not, enable the action with these settings:

Environment name = ${ENVIRONMENT_NAME}
Component name = Pet Clinic
Build number = ${B}
Build job = ${BUILD_NAME}

[anton-kasperovich]

@deors why do we need Component name as static value? We can make it dynamic, via ${PROJECT_NAME} . I think we should cover all 3 deploy. I will take care of this one.

[deors]

+1 for both suggestions. Re project name I didn't suggest because in this
case it would show as ExampleProject, but using the env var seems like the
logical way of doing it. If it shows as example project in dashboard will
not harm as it is the example project. Thanks!

El vie., 22 abr. 2016 10:26, Anton Kasperovich [email protected]
escribió:

@deors https://github.com/deors why do we need Component name as static
value? We can make it dynamic, via ${PROJECT_NAME} . I think we should
cover all 3 deploy. I will take care of this one.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#10 (comment)

[nickdgriffin]

I don't think the environment dashboard plugin is really fit for purpose at the moment. It doesn't account for the fact we have multiple workspaces and the dashboard contents is global wherever the view is created. If a column is an environment and a row is a component/project, there's nowhere to represent the workspace without it going in with the component/project name - and that means the table is going to get quite bloated if there are lots of workspaces or lots of differently named environments.

[anton-kasperovich]

@deors i implemented this in DSL, but after discussion with Nick looks like it can't be accepted on "ADOP Core level", if you still need it, feel free to copy source code from my external branch anton-kasperovich@c2540fa

[deors]

Ok, understood. Let's leave it as is for now until we can find a more elegant way of presenting the information, probably as suggested by enhancing the environment dashboard so it can be either local, or workspace aware.
Are you fine if we leave this open for now, so we don't completely forget about it?