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
This comes back to my question when I did the PR for additional Jenkins variables:
Do we really need to have them that deep?
Stuff like the Workspace could be in Build or in Node, Changes are also related to Build or Repository, Job is also related to Build and and and. All in all if you need something it's always a search until you found what you need.
I suggest having only one Environment class which directly contains all environment variables.
As the build system properties go pretty deep it would be really helpful if the properties had code samples i.e.
Jenkins BuildNumber
Not super obvious that it's accessed like this
BuildSystem.Jenkins.Environment.Build.BuildNumber
The text was updated successfully, but these errors were encountered: