I'm curious if you've had any progress in this area?
We currently have an automated deployment system for QlikView documents using a collection of scripts and git, but it still requires a user to manually initiate and remain logged in while it executes.
I'd like to fully automate the deployment through Jenkins, so any details on what you've found would be great.
We are currently working thought the process now and have yet to get it fully setup for unattended QlikView Reloads without the use of a QlikView Server.
Normally you would use QlikView Server to reload the .QVW on a schedule but it requires that the QlikView server have access to the source data that feeds the QVW. Because of security requirements we cannot grant the QlikView server access to the source data.
The current idea is to use BMC BladeLogic Server Automation to have the QlikView Application reload the source data into the .QVW. We are currently running into issue with Interact with Desktop and how BladeLogic RSCD agent can setup the QlikView Prompts during its first run under a user id.
I will post more as we work thought all the issues.
This a great topic, but this thread is stale. I am new to Qlik Sense and thinking that there must be a way to build a CI/CD pipeline and include some basic automated testing within the promotion workflow. I found the Qlik Deployment Framework and I have seen mention of a Deployment Console that is no longer supported.
Seems like I can use the QDF to structure my repositories, GIT to manage my source code, but how about automating the workflow, so that a check-in can trigger a rebuild, deployment and execute automated tests? After manual testing then a one click promotion of all artifacts to production?
The original post mentioned Jenkins, seems like a great starting point.
Can anyone chime in on current best practices and assets we can leverage in building a continuous deployment pipeline for Qlik Sense?
I've done this with QlikView...not sure if this works for Sense.
For command line build: Instead of qv.exe with /R, use QMSEDX (see Trigger QV Task using command line arguments)
For triggering rebuild based on check-in you could try to configure Jenkins to poll GIT repo.