ordina-jtech / fordintysa-ci Goto Github PK

This ISO will be distributed on USB sticks.
Based on Boot2Docker? Should include docker-compose and reasonable shell with working backspace.
Save it in a state where all Docker images are already pulled.
Probably 2 CPU cores & 4GB RAMwill be enough.

It should be accompanied with a .pdf containing instructions how to get it up & running, up to:

./open.sh

All content of readme,md in the Master branch is now placed in the Wiki.
Content of the readme should be rewritten to contain just basic info about the project.
So link to the wiki for 'getting started' instructions.

Maybe in the wiki make explicit instructions for 'native' Docker users.

This is in homepage/html/homepage.md, page GitBlit — Repository Browsing
Indented bullet lists of one item looks sloppy.

DBAD ??

Ideas:

• unpack to a prepared servlet container
• unpack to Jenkins/UserContent
• spin up a new Docker container

• install the Sonar plugin (see jenkins/Dockerfile)
• do some configuration in Jenkins
  • base url should be http://sonarqube:9000/sonarqube
  • use default admin credentials
• perform simple test with an existing project
• copy the working sonar plugin config out of the container into jenkins/data
  • /var/jenkins_home/*sonar*.xml ??
  • probably also updated /var/jenkins_home/credentials.xml

looks like the saved user/password combination doesn't survive persistence (which is a good thing)

• File jenkins/data/credentials.xml needs to be removed
• Users need to be instructed to create credentials when specifying GitBlit repo.

• payload:

docker-compose stop

• write instruction in open.sh to execute close.sh to stop the environment instead of press Ctrl-C.

• Introduction - in short
• create a simple Maven build

Simple Java web app:

• has some unit tests
• index.html lets you play Prince of Persia (ask me for html source)
• later make a branch that results in merge conflicts and unforseen failing unit tests
• includes pom.xml with version -SNAPSHOT

Jenkins complains about the reverse proxy is not all that well.
Maybe it needs an extra header in homepage/default.conf ?

Noticed the GitBlit container remembers it's state and survives docker-compose stop & up. Can be purged with docker-compose rm -f btw.
Can we do the same thing with Jenkins? Now it restarts completely blank...

Current command

ip=`ip route | awk '/eth1/ { print $9 }'`

returns nothing when running native.

Can we extract the correct ip addres with command ip route ?
ifconfig is known to report it, but extraction from multiple lines would be complex...

3.0.5 is what apt-get maven installs (part of jenkins/Dockerfile)
Can we install eg 3.3.9?

I've only included Artifactory in the docker-compose, no further testing done yet.

• Artifactory server needs to be configured (Beheer Jenkins - Configureer Systeem) and saved.
• in a Jenkins - Maven build item: Bouwomgeving - Resolve artifacts from Artifactory will download needed plugins & dependencies from Artifactory mirror instead of straight from Maven Central. You need to push button Refresh Repositories to get the list of repos.
• also in a build item add Acties na bouwpoging - Deploy artifacts to Artifactory. Unlike Nexus mvn deploy won't do, the Artifactory plugin knows where to deploy to

Formerly http://${ip}/ showed /index.html with reveal.js content.
Since Artifactory is added to docker-compose, it hijacks the / location and does a forward to it's own loading page. Somehow in homepage/default.conf (the nginx config) the first location is not first preferred. Puzzles me, since only location /artifactory should forward to Artifactory.

NB: http://${ip}/index.html still works...

slide 1/2 should only instruct to browse a repo.
On the next page ask some questions, like what is the first tag, how are the tags created, look in Maven Central what the first version was...