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!

ProGet - Feature Suggestion - adding Universal Packages



  • It would be handy to have a way to access the UI to create a universal package via the package's page. The package group and package name could therefore be pre-filled, to avoid having to cut and paste it, or for a mistake to be made in the name of the group or package. (same workflow as using the create package UI from the feed page)

    7746c381-b316-45f2-81d1-2ef92b0230a1-image.png


  • inedo-engineer

    Hi @kc_2466 ,

    Can you share how / why you're create Universal Packages in the UI? And perhaps how you're using upacks in general?

    We added them as a way to introduce the format to new users, but didn't really anticipate it being used beyond that.

    Thanks,
    Alana



  • Hi @atripp,

    One of the uses for upacks for us, is for storing binary images for things that are subsequently included into other CI builds. These are usually things are are not updated particularly frequently, and are not built by our CI system, for example an FPGA image, or perhaps some binary image provided to us by a component manufacturer.

    So the process to update these packages is generally manual - we could use pgutil, but the UI seemed like a really nice feature. It's great for creating the first version of a package, but it just seems a bit awkward when adding a new version of an existing package, as you have to carefully re-enter the group and package name to match the existing package. So having a shortcut on the package page to add a new version of a package with the group and package name pre-filled would be really helpful.


  • inedo-engineer

    Hi @kc_2466 ,

    Thanks! We'll add this via PG-3066 in an upcoming maintenance release, hopefully later this week if it's as trivial as it seems :)

    Thanks,
    Steve


Log in to reply
 

Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation