Topics created by dwynn_6489

This is handled by Release Package Variables within a Release Templates. They work basically the same, except now you can create multiple sets of required variables, depending on the template chosen at release time.

We had considered this as an option when designing templates, but decided against it because of the additional complexity required. The main challenge being, a user with Releases_Manage can already change the pipeline (or any other attribute) on an existing release. Making a "restrictive" template be a securable feature would require new permission attributes (and thus be more confusing/frustrating to use), and making it a convenience feature would give it the appearance of security (which is also bad).

David, great to hear! Aris, would you mind opening a new thread, or submitting a ticket (maybe easier to back and forth on email); I think I understand what you're suggesting. We'll definitely have to re-engineer something to support this sort of usecase, so any more details on how it should behave (from the UI, pipeline JSON, etc) would be helpful!

Thanks for the quick response. Yes, sooner would be great. I will start using the new feature as soon as you can release it, with or without documentation.

Yes, that's the directory used by the "local agent", for the buildmaster server.

The page was changed in v4.8.2 to only show the first 30 releases for perf reasons, so if you have more active releases than that, the list would be truncated to the first 30 ordered by when they were created. We're open to making this behavior configurable instead of a strict limit of 30.

Note this response will be handled via an email chain and will require either a new SVN extension or require a change to BuildMaster to resolve. Also see the following thread on GitHub: https://github.com/Inedo/bmx-subversion/issues/9