The images below is a draft for our casc.praqma.cloud that will soon demonstrate how we would run Jenkins Configuration as Code in Praqma.
For now it is only about creating a publicly available demo instance for inspection and scrutiny of other, but after that we will migrate our existing jenkins.praqma.cloud to a test and prod instance using casc.
The overall goal is to make an opinionated demo of casc in a way we would run it in Praqma on our production server. Because it is a demo, we do also handle provision and deployment
There might be some future improvements
We can later split it up further in smaller components if we like.
We can drive provision and deployment using circleci or similar
The white whiteboard drawings shows
..basically our components we need.
jenkins4casc.git
A very simple Jenkins docker image, almost identical to the official one but with the Configuration as Code plugin installed and ready to use.
This is supposed to be our recommended way to spin-up Jenkins and consist basically of two things: 1. the docker image, 2. the configuration file we point to.
praqma-jenkins-casc.git
This is our instance that goes live on https:\casc.praqma.cloud at some point and it just used the above jenkins4casc docker image and point to our configuration.
Further it contain some AWS stuff, so we have a place to deploy our docker image, but that could also be somewhere else.
demo1.git and demo2.git
These are supposed to be two "real" development project, it could be any of our project on our github that have builds and ci defined.
_But to avoid problems with multiple jobs running on the same repo (we also have them on our Praqma production Jenkins) we can't use real project, and will create two demo projects.
buep
commented
6 years ago 
The images below is a draft for our casc.praqma.cloud that will soon demonstrate how we would run Jenkins Configuration as Code in Praqma.
For now it is only about creating a publicly available demo instance for inspection and scrutiny of other, but after that we will migrate our existing
jenkins.praqma.cloudto a test and prod instance using casc.The overall goal is to make an opinionated demo of casc in a way we would run it in Praqma on our production server. Because it is a demo, we do also handle provision and deployment
There might be some future improvements
The white whiteboard drawings shows
..basically our components we need.
jenkins4casc.git
A very simple Jenkins docker image, almost identical to the official one but with the Configuration as Code plugin installed and ready to use. This is supposed to be our recommended way to spin-up Jenkins and consist basically of two things: 1. the docker image, 2. the configuration file we point to.
praqma-jenkins-casc.git
This is our instance that goes live on https:\casc.praqma.cloud at some point and it just used the above jenkins4casc docker image and point to our configuration. Further it contain some AWS stuff, so we have a place to deploy our docker image, but that could also be somewhere else.
demo1.git and demo2.git
These are supposed to be two "real" development project, it could be any of our project on our github that have builds and ci defined.
_But to avoid problems with multiple jobs running on the same repo (we also have them on our Praqma production Jenkins) we can't use real project, and will create two demo projects.