Optional Workspaces - Githubissues

Accenture / adop-platform-management

Apache License 2.0

60 stars 60 forks source link

Optional Workspaces #31

Open nickdgriffin opened 7 years ago

nickdgriffin commented 7 years ago

There are use cases where a workspace isn't necessary for users when using ADOP so it would be useful to "opt-out" of using them.

I think this could be achieved by generalising the "Generate_Workspace" job so that it allows creating either a workspace or a project directly, via a dropdown to pick the type.

michael-t-dukes commented 7 years ago

+1- I like the separation layers that workspace/project brings but do feel like being optional would be better in the following usecases:

1 client using a singular ADOP instance (with multiple projects)
1 project/studio having their own singular ADOP instance (with multiple-sub projects)

kramos commented 7 years ago

Sounds wise to me. Also +100 for retiring the name Workspace which is a reserved word in Jenkins referring to... the job Workspace. 😁