Support

• ?

  Agents set to use Agent.SecurityToken show error status
  buildmaster agents • 30 Jan 2014, 15:02 • Dalmiro   1 Feb 2014, 17:37

  2
  0
  Votes
  2
  Posts
  1
  Views

  ? 1 Feb 2014, 17:37

  You may want to check v4.1; there is some improved diagnosis/debugging with agents that might give a better error message as to the issue.
• ?

  Fortify SCA
  buildmaster • 31 Jan 2014, 17:46 • Dalmiro   1 Feb 2014, 17:09

  2
  0
  Votes
  2
  Posts
  3
  Views

  ? 1 Feb 2014, 17:09

  This sounds like a good candidate for a Reporting Action, but with the ZippedHtml option. Although the report outputs a binary file, you could write an html file to disk with a hyperlink to the file, and use that as the index. Both would be included in the zip file, and present in the report. If the FPR file is large, it might be better to save these on disk so it's not saved in the database. There are some additional built-in reporting actions that are not on GitHub; you can find those thru Reflector or something or fill out the Source Code Request Form. There are no background actions of course, but one option could be... Trigger that watches Promotion Completed event Runs report in background; adds report to the Build using the BuildOutputs_AddOutput action Add a Promotion Requirement to verify report has completed hope that helps. I'd be curious to see what you come up with.
• ?

  2nd workflow
  buildmaster workflows • 30 Jan 2014, 12:53 • Dalmiro   31 Jan 2014, 12:59

  7
  0
  Votes
  7
  Posts
  8
  Views

  ? 31 Jan 2014, 12:59

  OK they are now triggering. Thanks. Please can you advise on how to manage the release numbers For the regression test I entered a release number one higher than the current release on the standard. In reality my regression release will never go into production. The regression Test workflow is set to a loose Automatic Release Close-Out and disabled Release Cancellation. But the standard workflow is set to strict on all these. When the standard workflow is released into production, will it cancel my regression release. Should I set the regression release to a much high number or will this screw up the standard release numbering?
• ?

  Is there an easy way to delete ALL files/folders in the working directories?
  buildmaster actions • 30 Jan 2014, 11:11 • Dalmiro   31 Jan 2014, 01:33

  2
  0
  Votes
  2
  Posts
  7
  Views

  ? 31 Jan 2014, 01:33

  Your best bet would be to do a "Delete Files (*) From ~/Src" Action.
• ?

  Different context path
  proget http • 30 Jan 2014, 03:38 • Dalmiro   30 Jan 2014, 10:38

  2
  0
  Votes
  2
  Posts
  5
  Views

  ? 30 Jan 2014, 10:38

  ProGet does not support being installed in a virtual directory; it must be at the site root.
• ?

  Send email if a build fails
  buildmaster actions • 28 Jan 2014, 21:11 • Dalmiro   29 Jan 2014, 20:24

  4
  0
  Votes
  4
  Posts
  2
  Views

  ? 29 Jan 2014, 20:24

  We have upgraded to Buildmaster 4.0.9 (B31) and the "Execution Status" == succeeded work better but still not correctly. The predicate test is on the Action Group which contains 2 separate actions. The first action fails (and shows as failed in the log) then the next action succeeds and this marks the Execution Status as succeeded again to the remaining predicate tests pass. It would seem that the Execution Status should not be set the succeeded after it has been set to Failed.
• ?

  When my build action runs, the web.config transforms only partially work
  buildmaster actions configuration-files • 29 Jan 2014, 14:35 • Dalmiro   29 Jan 2014, 15:11

  3
  0
  Votes
  3
  Posts
  61
  Views

  ? 29 Jan 2014, 15:11

  Additionally, if you have publish profiles saved in your solution, you can add the following additional argument that will exhibit the same behavior as AutoParameterizationWebConfigConnectionStrings=false for the chosen ProfileName: /p:PublishProfile=ProfileName
• ?

  LDAP: Assign Privilages, Enable LDAP Authentication - Broken WebSite
  proget proget-installation authentication ldap • 29 Jan 2014, 11:49 • Dalmiro   29 Jan 2014, 11:49

  1
  0
  Votes
  1
  Posts
  7
  Views

  No one has replied

• ?

  How does "default" folder work for different users, builds and releases?
  buildmaster actions • 29 Jan 2014, 11:18 • Dalmiro   29 Jan 2014, 11:29

  2
  0
  Votes
  2
  Posts
  2
  Views

  ? 29 Jan 2014, 11:29

  The "default" folder (usually the SRC subfolder) is unique to applications and deployables, and is housed under the <bmas-tmp>\A<appid>\S<depid> folders. It is cleared during the "preparing agents" step at the start of every action, unless it's a re-execution of a failed deployment. Only one execution within an application is permitted at the same time, so the second one created will be queued until the first completes.
• ?

  If an action group is not related to a deployable, do I still have to put a ~ in my target/source path to get to the root of the application?
  buildmaster actions • 29 Jan 2014, 11:22 • Dalmiro   29 Jan 2014, 11:24

  2
  0
  Votes
  2
  Posts
  4
  Views

  ? 29 Jan 2014, 11:24

  Yes; if there is no deployable, then "0" is used as part of the path (e.g. <tmp>\A12\S0\WRK\my-path)
• ?

  Parallel Actions
  buildmaster • 28 Jan 2014, 18:52 • Dalmiro   28 Jan 2014, 18:54

  2
  0
  Votes
  2
  Posts
  3
  Views

  ? 28 Jan 2014, 18:54

  It's not available now, but we are strongly considering targeting that (and some related features) in v4.2, which should ship in March.
• ?

  Unable to install extensions on Windows Server 2012
  buildmaster • 28 Jan 2014, 09:01 • Dalmiro   28 Jan 2014, 10:37

  2
  0
  Votes
  2
  Posts
  1
  Views

  ? 28 Jan 2014, 10:37

  It appears the user that is running the web application does not have the needed permissions to restart the BuildMaster service. If you either 1) change the user account to one that has permissions to do so, or 2) manually restart the BuildMaster service, you should see the extensions.
• ?

  Custom extension doesn't show up
  15 Jan 2014, 16:10 • Dalmiro   25 Jan 2014, 06:45

  3
  0
  Votes
  3
  Posts
  2
  Views

  ? 25 Jan 2014, 06:45

  Hi Tod, I was aware of this extension but it didn't work for me (gave me all sorts of build errors). I took a closer look and you did help me on my way. I am now creating an artifact from a TFS build, make a temporary deployment and zip up this deployment into a new artifact. Everything works now, thanks!
• ?

  MsBuild failes with Error code -1
  22 Jan 2014, 11:47 • Dalmiro   23 Jan 2014, 16:33

  5
  0
  Votes
  5
  Posts
  23
  Views

  ? 23 Jan 2014, 16:33

  Command line works just fine..
• ?

  This machine cannot be uniquely identified error
  buildmaster error activation • 23 Jan 2014, 14:09 • Dalmiro   23 Jan 2014, 14:12

  2
  0
  Votes
  2
  Posts
  5
  Views

  ? 23 Jan 2014, 14:12

  This is caused when BuildMaster cannot determine the CPU ID or MAC address of the server it is installed on. Here is a detailed description: http://inedo.com/support/kb/1005/this-machine-cannot-be-uniquely-identified Typically, restarting the server fixes this problem. If that still doesn't work, you can also try the following steps to resolve: Stop the Windows Management Instrumentation service. Go to the %SystemRoot%\System32\Wbem\Repository folder. Delete all of the files that are in the %SystemRoot%\System32\Wbem\Repository folder. Restart the computer. The files that were deleted are recreated when the computer restarts. The Windows Management Instrumentation service will start automatically when you restart the computer. (These steps were taken from: http://minasi.com/forum/topic.asp?TOPIC_ID=5772)
• ?

  Desktop Notifier
  buildmaster • 23 Jan 2014, 12:43 • Dalmiro   23 Jan 2014, 13:27

  2
  0
  Votes
  2
  Posts
  14
  Views

  ? 23 Jan 2014, 13:27

  There is no officially supported desktop client; however, one of our VIPs at Leaping Gorilla built a custom one. The repository is at: https://leapinggorilla.kilnhg.com/Code/Open-Source/Group/Buildmaster-Tray
• ?

  BuildMaster + ProGet on Same Server
  proget buildmaster • 23 Jan 2014, 10:07 • Dalmiro   23 Jan 2014, 12:07

  2
  0
  Votes
  2
  Posts
  0
  Views

  ? 23 Jan 2014, 12:07

  I can't think of any tangible benefits to doing so, and can't think of any real drawbacks either. The only possible issue I could think of would be cookie related -- e.g. if you have the same hostname for both products differing only by port, there could possibly be conflicts with the cookie names. Using different hostnames would solve that, however.
• ?

  Would like to give you some money!
  20 Jan 2014, 12:52 • Dalmiro   20 Jan 2014, 13:44

  2
  0
  Votes
  2
  Posts
  2
  Views

  ? 20 Jan 2014, 13:44

  Hi Tim, Multiple Active Builds will not auto-reject builds when another one in the same release is deployed to the environment. It's mostly used when testers need to consider which build (of many) will be promoted to the next environment. There is a limit of "one connection per deployable" in the Express Edition and yes, the packager uses the same metadata table. Also... as an FYI, Express Edition Upgrades do not include support/maintenance, and we are planning to phase them out soon.
• ?

  Proget: No packages found. after renaming feed
  17 Jan 2014, 13:52 • Dalmiro   17 Jan 2014, 14:03

  2
  0
  Votes
  2
  Posts
  8
  Views

  ? 17 Jan 2014, 14:03

  Thanks for the report. This happens because the default package storage path for a feed uses the feed name, but doesn't rename the directory when you edit the feed name. You can fix this either by specifying a storage path for the feed, or renaming the existing storage path to match the new feed name.
• ?

  Cannot login after update from 2.2.5 to 2.2.9
  15 Jan 2014, 14:58 • Dalmiro   16 Jan 2014, 11:47

  2
  0
  Votes
  2
  Posts
  2
  Views

  ? 16 Jan 2014, 11:47

  Were you able to resolve this? Can you try clearing cache & cookies, and try again? Also, if you're hosting in IIS, can you run "iisreset" from the command to restart IIS... or restart the ProGet service from the services management console?