Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    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!

    Silently ignore re-pushed packages?

    Scheduled Pinned Locked Moved Support
    teamcityproget
    2 Posts 1 Posters 19 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      We are doing .NET development of an in-house system. We’re using nuget packages to share modules between a set of Visual Studio solutions and ProGet has been working great so far.

      We are using TeamCity for CI, and it is building and pushing our nuget packages on each build. Since there are several independent packages in a solution we are manually controlling the package version by incrementing it when we make changes to a given package. This also means that all packages that are not changed will still be built as part of the solution and TeamCity will be re-pushing the same version of the packages every time. I have enabled the Feeds_OverwritePackage permission to avoid errors. The only problem we have with this is that if someone forgets to increment the version number when they make changes the package will be overwritten in the feed. And now there are differing packages in use with the exact same version number.

      My question is then, is there any way to have ProGet silently discard re-pushed packages instead of overwriting?

      Or even better, to fail in the case where the package has the same version and different content, and ignore the pushes where the content is the same except for file-dates and such since the package is re-built from the same source.

      Product: ProGet
      Version: 2.2.13

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        This is not a very common scenario, so I would suggest altering your workflow to not always update the packages if they don't change.

        Alternatively you'll need to add some custom steps such as deleting the package before pushing it, or using a custom package store.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation