@dconnol1, @JasonWalker posted a repo with a custom plugin to download from GitHub (link), I’ve only ever spent 2-3 hours but couldn’t get it to work with Azure DevOps (probably issue on my side as I just didn’t have enough time). There was recently a discussion here of someone asking how to integrate git in the process and suggestion was to write a script that pulls content puts it in a folder and then schedule periodic “sync” but all manual, nothing integrated/automated.
Hi @Aram , I do have our documented in the RFE but as far as we are concerned there are need for two separate use cases:
-
The more-straight forward one is something along the lines of what Jason provided where support for “download latest” from a repo or folder in a repo, so when you run an action root server makes grabs the latest version of a script/binary/etc and performs the process around it. This will essentially open the door for content developers to store and track their stuff in GIT repos outside of BigFix (for example, if there is a bug in a new version I can track within the repo who did what where; it can be easily reversible; it opens the door for streamlining automation of custom content, especially repetitive ones - not every single software is patchable by BigFix out-of-box and when we create a manual fixlet for it the tedious bit is that every month/quarter/half-year/year we have to recreate that for their latest version where the only thing that changes is version number, which is built into relevance/success criteria, and the binary but everything else is copy/paste, so “automatic grab” of the file + version and having that dynamically referenced in actionscript solves it)
-
Bigger and a lot more involved use case is fully-fledged integration with GIT Repo.- the way I envision this is Git-based custom sites where the repo is the site and irregardless of where you make the change from (console, GIT client, GIT command-line tool, etc) all that is sync’ed into the repo and to root server respectively. Important aspect should be ability for BigFix to display the history from GIT and use it (for example, ability to view changes to a fixlet - what was changed; who changed it; when; and even run older version of that fixlet if you chose to; ability to “sync” baseline to specific version of a fixlet). The way I see it - this would truly add version control, auditing and compliance to content management side of the system that is currently lacking, not to mention external integrations for development processes (a ton of Agile/DevOps/etc tools integrate with GIT and provide the perfect combination of issue tracking & development-to-release tracking). It can also open the door of custom data fields around fixlets with the tagging/custom properties.
Happy to discuss further if required but to sum it up - this kind of integration would truly be a game-changer!