ProGet: Feature Request: native integration with GitHub to perform automated tasks

[MaxCascone]

We don't have this process fully designed yet, but i am hoping that a pattern will emerge that allows us to automate tagging a git commit when a package is promoted.
I know there are already Webhooks available, but then i have to figure out how to use that. If there was a more sophisticated way to talk to github, it would make this a lot less challenging.

thanks!

[stevedennis]

Hi @mcascone,

Thanks for the feature request; this type of orchestration is something that should happen by at the CI/CD Pipeline-level, in a tool like BuildMaster.

For example, consider our open-source Inedo.AssetDirectories .NET library (GitHub, Package).

In the corresponding Inedo.AssetDirectories BuildMaster application, when someone promotes the package to Release (see the Deployment Pipeline), the source code is tagged immediately after the promotion:

ProGet::Repack-Package
(
    PackageSource: NuGetLibraries,
    Name: Inedo.AssetDirectories,
    Version: $ReleaseNumber-rc.$BuildNumber,
    NewVersion: $ReleaseNumber
);

... snip ...

# Tag Source Code
# Tag the commit in source control using the id captured in the Build plan
{
    GitHub::Tag
    (
        From: GitHub,
        Tag: Inedo.AssetDirectories-$ReleaseNumber.$BuildNumber,
        Branch: $Branch,
        CommitHash: $CommitId
    );
}

You may be able to do this with ProGet's webhooks, but ultimately ProGet isn't an orchestrator (i.e. it doesn't have an execution/automation engine), and you won't get the level of reliability or flexibility needed.

[MaxCascone]

Thanks, I knew this one was a bit of a stretch. It'll be tough if not impossible to automate this in Jenkins, and is another tick on the "check out buildmaster" list.