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!

  • 0 Votes
    2 Posts
    0 Views
    ?
    Anything with the suffix _Configuration can be deserialized, so for your example all you need is: return (ArtifactoryVersionVariable)Util.Persistence .DeserializeFromPersistedObjectXml(settings);
  • How do I get the Application Id from within a predicate editor?

    buildmaster
    2
    0 Votes
    2 Posts
    0 Views
    ?
    Predicates are not directly tied to applications anymore as of v4.3 because of global plans. However, if the plan is in a single application, you can use: int id = int.Parse(HttpContext.Current.Request.QueryString["planActionGroupId"]); int applicationId = StoredProcs.Plans_GetPlanActionGroup(id) .Execute() .ApplicationDeploymentPlans .First() .Application_Id; to get it.
  • Create Feed button unresponsive

    feeds proget
    6
    0 Votes
    6 Posts
    10 Views
    ?
    Actually I was able to repro this (only when LDAP is enabled however); thank you for the report - it will be fixed in the next maintenance release v3.6.2. As a workaround, just visit the /administration/feeds/select URL directly.
  • 0 Votes
    4 Posts
    1 Views
    ?
    That should be OK - just note that this will update all workflows in the system to have this behavior.
  • How Get Extension Configurer within Variable class?

    buildmaster
    2
    0 Votes
    2 Posts
    0 Views
    ?
    You can use: var configurer = Util.ExtensionConfigurers.GetExtensionConfigurer(this); from within the variable itself, or pass in an instance of the variable instead of this from the variable setter.
  • Frontend Package Version Bug

    proget
    4
    0 Votes
    4 Posts
    0 Views
    ?
    Thank you for the additional information, we were able to reproduce. The fix will be included in v3.6.2. If you want an immediate patch for v3.6.1, you can download the file at: http://44.inedo.com/proget/NuGetPackageVersionPage.js and save it into the WebApp directory of the ProGet installation under the following subdirectory: WebApp\Resources\mapped\Pages\NuGet\Feeds\ alongside the NuGetPackageVersionPage.js.gz file. You may have to clear your browser cache to see the change.
  • Generic .nuspec file

    nuget packages proget
    2
    0 Votes
    2 Posts
    4 Views
    ?
    You may be best asking this on NuGet forums, as this relates to behavior in the nuget.exe client. We do not use "nuget.exe pack" ourselves (instead, we opt to use the proget client tools) as it's more reliable and has defined behaviors.
  • Proget with npm feed use massive a amounts of CPU/RAM

    proget npm
    4
    0 Votes
    4 Posts
    14 Views
    ?
    We have not had other users report this problem, nor have we seen it during testing. You can try running the service interactively (just stop the WIndows Service, then run the .exe file), and see what happens. Also worth noting, make sure that all the errors in the log are deleted before the packages start indexing again.
  • 0 Votes
    3 Posts
    2 Views
    ?
    It is also worth noting that strictly speaking, pushing packages does not require the View privilege, that is a result of the NuGet client sending a GET request (i.e. "list") first before sending the PUT request to push the package -- it's the first request that gets 401ed. You can use the following PowerShell script to perform just the package upload: $FeedUrl = 'http://proget/nuget/Default' $FileName = 'C:\tmp\ProGet\packages\Package.1.0\Package.1.0.nupkg' $APIKey = 'Admin:Admin' #params([string]$FeedUrl, [string]$FileName, [string]$APIKey) $req = [System.Net.WebRequest]::CreateHttp($FeedUrl) $req.Method = 'PUT' $req.ServicePoint.Expect100Continue = $false If ($APIKey) { $req.Headers.Add('X-NuGet-APIKey', $APIKey) } $boundary = '---------------------------' + [System.Guid]::NewGuid().ToString('n') $req.ContentType = "multipart/form-data; boundary=""$boundary""" $utf8 = New-Object -TypeName System.Text.UTF8Encoding -ArgumentList ($false) $reqWriter = New-Object -TypeName System.IO.StreamWriter -ArgumentList ($req.GetRequestStream(), $utf8) $reqWriter.WriteLine("--$boundary") $reqWriter.WriteLine("Content-Disposition: form-data; name=""package""; filename=""package""") $reqWriter.WriteLine("Content-Type: application/octet-stream") $reqWriter.WriteLine() $reqWriter.Flush() $fileStream = [System.IO.File]::OpenRead($FileName) $fileStream.CopyTo($reqWriter.BaseStream) $fileStream.Close() $reqWriter.WriteLine() $reqWriter.Write("--$boundary--") $reqWriter.Dispose() $response = $req.GetResponse() $response.Dispose()
  • 0 Votes
    3 Posts
    11 Views
    ?
    If "Multiple Active Builds" is enabled for the application, the builds will queue (i.e. the latest ones will stay "Pending" until the prior ones finish sequentially). Without that setting, newer builds will reject older builds for the same release. Beyond that, your workaround for the non-mulitple-active builds setting will work fine.
  • Build Variables not showing

    buildmaster
    2
    0 Votes
    2 Posts
    0 Views
    ?
    There shouldn't be anything else that needs to be passed in, are "hello" and "cause" the only 2 variables? It's possible there could be an issue with default variable values.
  • 0 Votes
    2 Posts
    7 Views
    ?
    This error means that the connection string in the installed product doesn't work for the user installing the software. Most likely, you don't have access to the database or server. I think the discussion here http://inedo.com/support/questions/3126 may be related as well.
  • Upgrading 3.3 -> 3.6.1 results with new issue

    proget
    3
    0 Votes
    3 Posts
    0 Views
    ?
    You will need to use Fiddler to determine the EXACT urls that are causing a problem during package restore; we can then investigate what query is causing the problem.
  • Support for nuget v3

    proget nuget
    2
    0 Votes
    2 Posts
    8 Views
    ?
    ProGet works great with NuGet client v3! As far as the "protocol" is concerned (i.e. ODATA vs JSON-LD) the "v3" protocol is intended only for use by nuget.org and nuget client. It's not documented by Microsoft, unstable, and they have no plans to document or support it. Since the "v2" protocol (ODATA) works just fine, we are not going to reverse engineer the "v3" protocol or otherwise use it.
  • Is there is any version of build master for mac os

    buildmaster
    2
    0 Votes
    2 Posts
    3 Views
    ?
    The BuildMaster (primary) server currently only runs on Windows, but it can connect with MacOs servers via SSH. It's a web application, so of course you can access it on a Mac no problem.
  • ProGet crashing

    proget service
    5
    0 Votes
    5 Posts
    23 Views
    ?
    I can't believe I missed that. I upgraded and that problem is gone but with new issues. Will open a separate question for that problem. Suggestion: How about adding a new tag npm? Thanks Niklas
  • IIS 8.5 Installation Error

    proget iis
    2
    0 Votes
    2 Posts
    7 Views
    ?
    If you're seeing this message, then you'll need to ensure ASP.NET4 is installed -- not just .NET4 and .NET4 Extensibility. It's a separate option (that's kinda hidden).
  • Agent - Incorrect keyboard layout

    agents buildmaster bug
    2
    0 Votes
    2 Posts
    12 Views
    ?
    Embarrassing, a Spanish colleague had been on the server and changed all the setting!
  • 0 Votes
    4 Posts
    235 Views
    ?
    Interestingly enough, disabling connection pooling for Buildmaster seems to have solved our issues. It's been five days and there hasn't been a single error in the event logs or Buildmaster itself. In app_appSettings.config we now have our connection string setting looking like this: <add key="Core.DbConnectionString" value="Data Source=localhost; Initial Catalog=BuildMaster; Integrated Security=SSPI;Pooling=no" /> Could this possibly be caused by a connection in Buildmaster not being disposed properly such that when it is pulled back out of the pool, it's in a broken state?
  • Moving proget server to other machine

    proget
    2
    0 Votes
    2 Posts
    19 Views
    ?
    The basic process is: Install the exact same version of ProGet on the new machine Backup the ProGet the database and restore it onto new machine over the new database that was created by the installer Set a bulk import path for each feed Copy the packages from each feed into the corresponding bulk import path of each feed Allow a minute or so for the indexer to pick up the new packages and add them to the feed
Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation