Support

• ?

  Un-Deploying a Release
  buildmaster releases imported-deployables • • Michael  

  2
  0
  Votes
  2
  Posts
  4
  Views

  ?

  It sounds like this is a bit of a hack; when an application component is deployed to a production environment, it's status should be represented as "Deployed". You can purge releases if needed using the Releases_PurgeReleaseData API/Sproc method.
• ?

  Passing build master parameters via a URL Triggered Build from TeamCity
  buildmaster variables triggered-builds • • Michael  

  2
  0
  Votes
  2
  Posts
  67
  Views

  ?

  Currently this is supported through the API, but not via the triggered builds. We will add the ability to specify a build number for URL triggered builds in the final version of 4.3 due out end of next week. You can already specify variables for URL triggered builds by including them as part of the query string, e.g. http://buildmaster-server/trigger-build?id=1000&myVar1=value1&myVar2=value2
• ?

  Backup ProGet
  proget • • Michael  

  2
  0
  Votes
  2
  Posts
  0
  Views

  ?

  Yes, although you may get some file read errors if someone happens to be downloading the exact package that's being backed-up or copied. Many back-up processes/tools will do things like shadow copy and limited read handles to prevent this from happening.
• ?

  ProGet fail to index symbol on a CPP DLL/PDB
  proget symbols • • Michael  

  4
  0
  Votes
  4
  Posts
  29
  Views

  ?

  Thanks so much! This has been logged as PG-208, and we plan to fix in the upcoming maintnence release (3.0.4)
• ?

  Handling multiple websites
  buildmaster net tfs • • Michael  

  2
  0
  Votes
  2
  Posts
  5
  Views

  ?

  The main strategy is to have one application per website, and then either: Pull the core 30 projects and build them as part of each website application, you can use shared/linked action groups for this to make it a little easier. -or- Build the web core files in their own application as you've started to do it seems, and store the build output as an artifact, then import that deployable in each of your website applications. This allows you to deploy the artifact with the core files in it before you build one of your web applications. We've named this option the "Core Version" pattern, and you can find a specific example of it here: http://inedo.com/specifics/buildmaster-extensions I will also note that deployment plans are getting a nice overhaul in the upcoming BuildMaster v4.3, it will be much simpler to share deployment plans across applications so managing plans for this scenario will be even easier.
• ?

  Delete a Package
  proget packages • • Michael  

  2
  0
  Votes
  2
  Posts
  2
  Views

  ?

  Thanks for the report - we are able to repro and will fix it in the next maintenance release.
• ?

  Can't install 2.1.4 ProGet to update to newest version
  proget • • Michael  

  4
  0
  Votes
  4
  Posts
  4
  Views

  ?

  Hmm, not sure, but it sounds like the problem is a corrupt install package? That's a error thrown from within MSI extraction. Maybe try downloading the file again.
• ?

  ProGet Settings Documentation
  proget • • Michael  

  4
  0
  Votes
  4
  Posts
  9
  Views

  ?

  We will add the descriptions at some point (we have them in BuildMaster). The HTML should probably be in a div, as it renders the value as a literal string. You can try it with something like: <div class="white-box padded-box"><h2>{Company} ProGet Repository</h2><p>Welcome to our collection of ProGet feeds.</p></div>
• ?

  Issue uploading packages
  proget • • Michael  

  2
  0
  Votes
  2
  Posts
  0
  Views

  ?

  This sounds like it's related to package indexing. Please see this StackOverflow answer for troubleshooting steps: http://stackoverflow.com/questions/23812344/publishing-to-proget-and-i-cant-see-any-packages
• ?

  Artifacts cleanup
  buildmaster • • Michael  

  2
  0
  Votes
  2
  Posts
  1
  Views

  ?

  There is a "purge artifacts trigger" that you can set-up that will delete artifacts from Rejected Builds, either immediately or once the release is deployed. We do have it on our roadmap to have artifact retention and clean-up policies as a more advanced feature.
• ?

  Deleting old database records
  buildmaster databases cleanup • • Michael  

  2
  0
  Votes
  2
  Posts
  9
  Views

  ?

  NOTE : BuildMaster has Retention Policies which are strongly recommended, rather than manually purging data That being said, you can use the same strategy to delete from that table that you used for log entries: BuildMaster 4.2 and earlier: SELECT TOP 100 * FROM BuildExecution_PlanActionVariableValues --DELETE BuildExecution_PlanActionVariableValues WHERE BuildExecution_PlanAction_Id IN (SELECT BuildExecution_PlanAction_Id FROM BuildExecution_PlanActions BEPA INNER JOIN BuildExecutions BE ON BE.Execution_Id = BEPA.Execution_Id INNER JOIN Builds B ON BE.Application_Id = B.Application_Id AND BE.Release_Number = B.Release_Number AND BE.Build_Number = B.Build_Number WHERE B.BuildStatus_Name = 'Rejected') BuildMaster 4.3 through 4.9: SELECT TOP 100 * FROM BuildExecution_ActionGroupActionVariableValues --DELETE BuildExecution_ActionGroupActionVariableValues WHERE BuildExecution_ActionGroupAction_Id IN (SELECT BuildExecution_ActionGroupAction_Id FROM BuildExecution_ActionGroupActions BEAGA INNER JOIN BuildExecution_DeploymentPlans BDP ON BEAGA.BuildExecution_DeploymentPlan_Id = BDP.BuildExecution_DeploymentPlan_Id INNER JOIN BuildExecutions BE ON BE.Execution_Id = BDP.Execution_Id INNER JOIN Builds B ON BE.Application_Id = B.Application_Id AND BE.Release_Number = B.Release_Number AND BE.Build_Number = B.Build_Number WHERE B.BuildStatus_Name = 'Rejected')
• ?

  Problems with the FTP action
  buildmaster ftp • • Michael  

  5
  0
  Votes
  5
  Posts
  2
  Views

  ?

  Wow, what an incredibly fast response. Thanks
• ?

  ProGet will not upload Nuget Package
  proget • • Michael  

  2
  0
  Votes
  2
  Posts
  3
  Views

  ?

  This sounds like it's related to package indexing. Please see this StackOverflow answer for troubleshooting steps: http://stackoverflow.com/questions/23812344/publishing-to-proget-and-i-cant-see-any-packages
• ?

  User Tracking Feature
  proget • • Michael  

  3
  0
  Votes
  3
  Posts
  0
  Views

  ?

  To expand on this story what we are thinking about doing is creating a wide open pass through feed to Nuget that would allow users to discover new open source software to use. By forcing users through Proget we can get user info to send them reminder emails about OSS that we have not yet cleared for use in our products. Then the devs can get it cleared etc.
• ?

  Publishing from our build server fails intermittently
  proget • • Michael  

  2
  0
  Votes
  2
  Posts
  4
  Views

  ?

  Are you overwriting an existing package when this happens, or are these fresh packages that are getting uploaded? Either way, if you could send that Process Monitor output to support@inedo and reference this post that would be very helpful, thank you!
• ?

  Missing ~\xxxx directory
  buildmaster actions • • Michael  

  2
  0
  Votes
  2
  Posts
  10
  Views

  ?

  We believe that it should not because it's most likely a mistake to specify a directory that doesn't exist as the working directory since presumably there could be files to work with, etc. in that directory. As you mentioned, the workaround is to create the directory before this step. I would just use mkdir in a PowerShell or Bash script.
• ?

  Atlassian Crowd Integration
  proget atlassian • • Michael  

  2
  0
  Votes
  2
  Posts
  14
  Views

  ?

  At this point in time, it is unlikely. However, Atlassian does mention on their site that plugins could be created to integrate with third-party tools, and the JSON ProGet API could be used for this.
• ?

  Exporting application variables and triggers
  buildmaster actions • • Michael  

  2
  0
  Votes
  2
  Posts
  7
  Views

  ?

  We don't have export capability for those other items just yet. Does purging the logs as per http://inedo.com/support/questions/1826 not help clean out 90%+ of the space? The log table is the one that typically fills the BuildMaster database. There are some other tables that could also contain a lot of data depending on usage, those being: BuildOutputs (if you generate and store reports with every build) BuildTestResults (if you run unit tests during builds) EventOccurenceDetails & EventOccurences (if many users are constantly using the software) The first 2 can be purged for rejected builds, and the event occurences can be purged entirely if that data is meaningless.
• ?

  ProGet does not support the FindPackagesById() service
  proget • • Michael  

  4
  0
  Votes
  4
  Posts
  5
  Views

  ?

  Tod, I justed tested it and it works perfectly. You can see this API being used in Fiddler when you use the "Show all versions" link for a package in NPE. Previously doing that didn't work against a ProGet feed. Thank you for the fast turn-around! That was impressive... Riko
• ?

  Keeping pdb files in non-symbol packages
  proget symbols • • Michael  

  5
  0
  Votes
  5
  Posts
  4
  Views

  ?

  Apologies for the delay, but as of v3.0.3, you can configure your feed so that the PDBs are not stripped out.