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!

    Promote Package if Build is promoted to new stage

    Scheduled Pinned Locked Moved Support
    2 Posts 2 Posters 8 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.
    • I Offline
      it_9582
      last edited by

      Hi there,

      are there any possibilities to promote a package (internal feed) to next feed if the build is promoted?

      The reason for this question is that my idea for a good workflow would be as followed:

      • Developer commit changes in VCS
      • CI-System builds and
        • upload package to feed universal-build
        • creates new build in proGet with previously uploaded package in state Build
      • If the package will be tested the test-engineer could promote the build to state Test
        • now it would be nice if the packages (possible configurable) also would be promoted to another feed

      Actually we should start a lookup for each package in the Package in the Build after promotion and should promote each Package manually (over Web-UI or pgutil-CLI) to another feed.

      Would this be a possible workflow solution or there any other suggestions to work with package/build/promotion?

      Best regards,
      Florian

      stevedennisS 1 Reply Last reply Reply Quote 0
      • stevedennisS Offline
        stevedennis inedo-engineer @it_9582
        last edited by

        Hi @it_9582,

        First and foremost, we don't recommend the "package promotion" feature as a means to indicate which "stage" (i.e. tested quality) a package is in relative to a CI/CD pipeline.

        Instead, repackaging should be used:
        https://docs.inedo.com/docs/proget/packages/repackaging

        Having multiple feeds is fine; we do that for Products and PreReleaseProducts on proget.inedo.com, but that's to make it "harder" for someone to accidently use a prerelease version. Otherwise, you can just use one feed and have retention policies cleanup the "-ci" builds.

        As for having the "build promotion" feature in ProGet be used as a workflow engine (i.e. to trigger actions upon promotion), I don't think we would consider that. At the most, we would do a webhook of sorts... though it doesn't make a ton of sense to be honest.

        The reason is that ProGet isn't intended as the "source of truth" for build status - the idea is that you would have something like a pipeline in BuildMaster) update the statuses in ProGet.

        The main benefit to having this status in ProGet is retention of builds/SBOMs.

        Hope that helps,
        Steve

        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