Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Cloning application and default release/pipeline
-
Under Buildmaster v5.6.9, I'm wondering if the following is expected behavior, and whether this can be changed in a future version of Buildmaster:
When cloning an application, visiting the new application shows that the operation created a release 0.0.0 with the progenitor application's original pipeline. In my Buildmaster configuration, there is no such pipeline, which causes confusion and build errors unless the application is modified. I'm wondering why the release is automatically created, when normally, this has to be done by a user who selects an appropriate pipeline.
Product: BuildMaster
Version: 5.6.9 -
Configuration file versions and database change scripts must be tied to a specific release number, so we create 0.0.0 to associate those. It might be best just to purge that release if you don't really use it.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login