If you are unable to create a new account, please email support@bspsoftware.com



MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

CI/CD implementation in Cognos Analytics

Started by piyushbhadouriya, 13 Oct 2020 02:22:35 AM

Previous topic - Next topic


Hi All,
Does anyone in forum ever implemented CI/CD pipeline practice in Cognos using SDK or any other programming tool?I want to know what challenges you face while automating  version controlling, Testing and deployment. i am weighing the option to purchase software tool like MotioCI and building an in-house solution. Suggestions are welcome.


I know this is an old post and sorry nobody responded to it. Hopefully you're still around to share what solution you came up with and would like to share as I'm currently exploring a CI/CD solution.



That's not CI/CD.  It's just version history.

I suspect CI/CD will involve the Cognos Analytics SDK to allow the user to automatically identify changes in the Test environment, then build a deployment export, run the export, move the file(s), build a deployment import, run the import.

But CI/CD typically involves source code repository branching.  I can't imagine how that would be done in Cognos Analytics.

I haven't had a need for this because, while IT helps a lot, we push self-service.  The vast majority of the reports in my environment were created/managed/updated in production.  ...which is why I created a routine that would enable me to get an old version of a report without requiring a database restore and standing up a new Cognos environment.

While I'm pretty sure I put disclaimers all over my git repo, here's one more:  If you are going to use the SpecBackup stuff as an example, it's exactly that -- an example.  No two Cognos environments are the same.  Your mileage may vary.  And I don't think I have updated that in a long time.  The version on github may not work with current Cognos installs.  I could go on, but I think you get the idea.  Use at your own risk.