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!
BuildMaster : Legacy URL Trigger editing
-
We have just upgraded to 6.1.28 and still have some legacy URL triggers for builds knocking around. I can see that a trigger is still functioning for one application - i.e. the build was kicked off properly when the corresponding URL was hit, however for another it is not working.
I appreciate that we should start to use the Build and Deployment API in place of these, but is there a way in 6.1.28 to view and edit the legacy URL triggers? If so, I don't find it at the moment.
Perhaps someone can point me towards it.
-
There's no problem in using the legacy features in BuildMaster 6.1.28, though they are a bit hard to find. Our goal was that no new users would see them, but existing users could still access them.
You can directly navigate to the page where these are displayed with
/schedulesunder an application, so for examplehttp://buildmaster/applications/4/schedules. You should be able to also find this page on the Applications > MyApp4 > Settings > Legacy Build Triggers.The Legacy Build Triggers link will only display when
Legacy.ScmTriggersis checked (Admin > All Settings). This should be set if you have them (the legacy feature detector should have checked this, but it might not have).These are also directly the database, happy to give more insight if you want to look across all apps. I don't believe there was a way to do this globally (but you can for 6.2 / non-legacy).
-
Many thanks Steve. I had run the legacy feature detector but the setting was still unchecked. After setting that I can now see an additional tab you mention. Appreciate the help.
-
Ah, I see what happened. The logic to display that particular should be tab
BuildMasterConfig.Legacy.ScmTriggers || BuildMasterConfig.Legacy.UrlTriggers. I fixed it!FYI - we still ship new maintenance releases of BuildMaster 6.1, but no "new features". The main goal is to make sure we have everything to help transition the migration to 6.2/7.0, so if there's anything we can add please don't hesitate to ask.
