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!

  • How to always execute Get-Asset in Role?

    2
    0 Votes
    2 Posts
    7 Views
    atrippA
    Great question! The answer is, unfortunately, buried in the Formal Specifications. But long story short, you'll want to wrap the Get-Asset operation in a with executionPolicy = always block. For more information, note that there are three modes of executions: Collect Only - only ICollectingOperation operations will run; if the operation is a IComparingOperation, then drift may be indicated. All ensure operations implement both interfaces. Collect then Execute - a collection pass is performed as described above; if any drift is indicated, an execution pass is performed that runs: operations that indicated drift IExecutingOperation operations in the same scope as a drift-indicating operation that do not implement - IComparingOperation; this is all execution actions operations with an execution policy of AlwaysExecute; this can only be set on a Context Setting Statement Execute Only- only IExecutingOperation operations will run; all ensure and execute operations implement this interface So what's happening is that Get-Asset will never run in a Collect pass, where as Ensure-DscResource will always run in a Collect pass (but only in Collection mode). By forcing Get-Asset to always execute, it will run even in the collect pass. By the way: I would love to find a way to properly document the answer to this, so users don't get frustrated; any suggestions on where to edit the contents?
  • Combine strings BuildMaster

    6
    0 Votes
    6 Posts
    19 Views
    atrippA
    Nice OtterScript :) This will work, the variables won't "leak over" or anything like that.
  • BuildMaster Artifact Retention Question

    2
    1 Votes
    2 Posts
    7 Views
    jraschJ
    Hi Ali, By default, an artifact retention policy operates on artifacts alone and does not consider builds/releases/etc. There is no current way to say "500MB of artifacts per release", however, you can combine 2 retention policies that should be close to what you want: Build retention policy: Only purge builds in deployed releases Only purge rejected builds Keep last (whatever you want) Artifact retention policy: Only purge artifacts in deployed releases Only purge artifacts in rejected builds Purge orphaned artifacts The key is "purge orphaned artifacts" which will only delete artifacts after its corresponding build is deleted. This allows you to provide the necessary granularity on the builds themselves, and let the artifact policy come in after and clean up the artifacts that no longer have an existing build. This can be extended to releases in a way, since any releases that get deleted will also have all their builds deleted. Hope this helps, -John
  • Publish npm package to Proget

    proget npm publishing
    17
    0 Votes
    17 Posts
    218 Views
    P
    Any updates on this? I encounter the same issue and none of your comments helped .
  • Can proget be upgraded using an account that doesnt have db access?

    2
    0 Votes
    2 Posts
    6 Views
    atrippA
    The user running the install/upgrade needs to have dbowner rights on the ProGet database. The installer will give a database access error.
  • Error during package Upload

    2
    0 Votes
    2 Posts
    3 Views
    atrippA
    The error message is "cvs.badguy does not have the Feeds_AddPackage privilege", which means that the api key you've configured does not have that privilege. Please add it.
  • 0 Votes
    6 Posts
    19 Views
    atrippA
    To simplify the import/export options, BuildMaster 6.2 only supports backing up / restoring to a "Package Source" (i.e. a ProGet feed); we may support for using a disk-based package source instead, but for now it's only a ProGet Universal feed. BuildMaster 6.1.5 lets you back-up to a feed URL. Note that BuildMaster 6.1.25 also has "Package Sources" (as a preview feature), which you can use to back-up all of your applications if you'd like.
  • Upgrade to Buildmaster 6.2 not possible :(

    5
    0 Votes
    5 Posts
    22 Views
    P
    Update is ok
  • Has anyone created a BuildMaster repository monitor for Azure (TFVC)?

    8
    0 Votes
    8 Posts
    41 Views
    jraschJ
    Hi Philip, The next TFS extension v1.4.0 now has a TFVC monitor included. It's a little rough around the edges i.e. it monitors separate paths instead of branches for the time being. Let me know if you run into any issues with it. Thanks, -John
  • Question about retention policies

    7
    0 Votes
    7 Posts
    19 Views
    A
    @jrasch I tried creating a retention policy, like my attached screenshot. However, it deleted all of the artifacts in BuildMaster, not just orphaned ones. Is there a way to delete just the orphaned ones? We are using Version 5.8.3 (Build 7) of BuildMaster. [image: 1580217495062-inedojpg.jpg]
  • Error attempting to set GitHub Build status

    3
    0 Votes
    3 Posts
    7 Views
    T
    Thank you
  • Polling Inedo Agents

    2
    0 Votes
    2 Posts
    12 Views
    atrippA
    Hello; the agents don't currently support this, though this is something that we've considered for a long time -- some of our key customers have requested this as well. However, we've developed some interesting technical alternatives that make the pull-based agents largely moot (at least according to the folks who requested it originally); for example Romp and universal packages allow the client to self-install, or at least have an in-house BuildMaster or Otter instance that can manage installations based on packages.
  • Adding functions in Otter

    otter
    11
    0 Votes
    11 Posts
    2k Views
    P
    Hello Jonathan, We use Proget to deploy our PSModules. The deployement is driven with an Otter PSEnsure fonction- check if module exist with a specific version, if not deploy - Each new server is linked to an Otter role and after remediation, the module is installed. To update the module, we change version number in a otter variable. Otter remediation make the job We call PS function from local script or from Otter plan directly or from module. Don't know if this your need but it is working fine for us.
  • Proget docker delete manifest api request fails

    3
    0 Votes
    3 Posts
    14 Views
    A
    Ok, thank you!
  • Proget filesystem access

    2
    0 Votes
    2 Posts
    8 Views
    atrippA
    HTTP should be about same speed as FTP; you'll most certainly need to use chunked uploads. But Asset directories don't support drop folders, and we don't have a reindexing function for asset directories. So unfortunately there's no supported way to handle this. You might be able to "hack" something by going to the database and filesystem directly, but we obviously can't recommend it.
  • PyPI package not shown in search results accessible via url

    6
    1
    1 Votes
    6 Posts
    18 Views
    atrippA
    Interesting; I know it's not ideal, but it works, and it may only be a slight inconvenience at best, since not many search for packages from the UI, I think. https://github.com/Inedo/inedo-docs/blob/master/ProGet/feeds/pypi.md If anyone finds more issues with this, please let us know and we can consider investing in a proper fix.
  • Error attempting to Tag a Docker Image

    7
    0 Votes
    7 Posts
    24 Views
    T
    @tdean_3904 said in Error attempting to Tag a Docker Image: NETWORK SERVICE Following line needs to be added to daemon.json under Programdata\docker\config { "group" : "Network Service" }
  • [ProGet] Error during package upload with SemVer2

    windows proget nuget
    2
    1
    0 Votes
    2 Posts
    23 Views
    gdivisG
    Hi, Thanks for letting us know. Looks like the error message is wrong - actually the problem is caused by build metadata being present in a version number that is not a semver2 version. We've filed this as PG-1655 to make parsing these versions more permissive - it will be fixed in the next ProGet release (5.2.23), currently scheduled for Jan-17.
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    12 Views
  • OCI support in Docker registry

    docker-registry proget oci
    2
    0 Votes
    2 Posts
    37 Views
    benB
    Hello @luminiscence_6236, It looks like ProGet is misinterpreting the auth token request helm sends during the second command as being anonymous. I've filed PG-1651 to address this.
Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation