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!

    Universal Package Versioning

    Scheduled Pinned Locked Moved Support
    4 Posts 3 Posters 23 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.
    • T Offline
      tyler_5201
      last edited by tyler_5201

      I like the setup of Universal Packages, however, the vendor installer packages I deal with (spread across .zip, .iso, .exe, and .msi) do not have friendly version names - certainly not semantic versioning.

      Their software is typically in the format of this: 2024 SP3 R2 P1, where the base version would be something like 2024, and then as the software is changed, but no major version is released, the service pack, revision, and patch numbers increase. I could account for this if the semantic versioning allowed 4 segments, but it only allows two. Is there a better way to store their files than using Universal packages (I could use the Asset feed, but the Universal looked cleaner)?

      I do like the Universal packages because I was going to bundle the PDFs with the installers.

      atrippA 1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer @tyler_5201
        last edited by

        hi @tyler_5201,

        For a case like this, I'd recommend using a custom metadata field like _vendorVersion or something like that? Of course, that's going to be relatively easy.

        The hart part is to "map" the vendor numbers to a SemVer. I would look at the data, and decide how you want to "pack" them into three segments.

        2024.3.201 might work, assuming there are less than 100 revisions per service pack. Or maybe 2024.302.1. The number is really just for you, so whatever makes sense to you :)

        Cheers,
        Alana

        1 Reply Last reply Reply Quote 0
        • T Offline
          tyler_5201
          last edited by

          Thanks Alana,

          I think I've developed a workable pattern for the vendor's versioning system. Are any of the fields searchable in the User Interface, whether pre-defined or custom?

          dean-houstonD 1 Reply Last reply Reply Quote 0
          • dean-houstonD Offline
            dean-houston inedo-engineer @tyler_5201
            last edited by

            Hi @tyler_5201,

            The UI package search is pretty basic, so it's not going to look through those metadata properties. They are something you could obviously search/find through the API.

            Depending on what you're trying to do, we do have a Whitelabel feature that makes the UI a lot easier to consume for end-users:

            • https://docs.inedo.com/docs/proget/administration/whitelabel
            • https://inedo.com/proget/case-studies/salient

            In particular, the "Tile View" on Universal Packages may help. But it's not very popular and is something we work closely with our users on, so let us know if that's of interest.

            -- Dean

            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