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!

    Unique Source Control Actions

    Scheduled Pinned Locked Moved Support
    source-controlbuildmaster
    2 Posts 1 Posters 6 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

      Do you have a sample action that requests the build's current source control provider?

      Apologies if this is a "lazy" question, I'm only thinking about it for a "nice-to-have" "icing-on-the-cake" feature idea.

      Essentially I've taken our customized version of the GitHub extension (I've been very slowly working through the legal details on what it might take to send a pull request or three) and made it so that for ApplyLabel instead of adding a git tag to the repository on the agent it instead uses the GitHub API to create a Release in "Prerelease" status. This is actually pretty nifty as it cleans up the Releases page in GitHub considerably. It's also nice because I have it check for an existing tag/release, rather than erroring on tag/release creation. The "icing-on-the-cake" would be a deployment action for Production deploys to mark the promoted build as "Stable" and probably remove the build number from the GitHub release title (change the semver-based release name from "v1.0+89" to just "v1.0").

      Product: BuildMaster
      Version: 4.1.3

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

        Hi Max,

        That sounds like a great idea.

        Unfortunately, there is no SC Provider that is associated with a particular build; that is, there'd be no way (aside from looking at logs) to know which ProviderIds were used in deployment plans executed over a build's lifecycle.

        You could capture this as a variable, however.

        If you haven't already, make sure to see how the SourceControlProviderActionBase actions work; you can find their code thru a decompiler (BuildMasterExtensions assembly), or just ask for it and we'll email you.

        Hope that helps,

        Alex

        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