Cd

[100 Days of Code] Day 061: June 15, 2017

Today’s Progress: Still no solution for the flickering integration tests. Things I’ve learned: Nothing new. Things I’ve planned for tomorrow: I will continue until I eventually find the reason. Link(s) to work: security-server

[100 Days of Code] Day 060: June 14, 2017

Unfortunately I had some important things to manage in the last days and therefore have not been able to work a lot on my projects. However since I’m doing this challenge to motivate myself and to have constant progress in my project I will continue where I left off a few days ago. Today’s Progress: Managed to get Jenkins collect all test results. Still don’t know why the integration tests are flickering.
Read more

[100 Days of Code] Day 059: June 11, 2017

Today’s Progress: Wrote all Jenkins pipelines and wired the security-server project to the snapshot libraries on the public maven repo. Unfortunately when the build of security-server is running in Jenkins it’s failing also a local build succeeds. Things I’ve learned: More about Jenkins pipelines. Things I’ve planned for tomorrow: Investigate on the issue why the build fails on Jenkins and why test reports of integration tests don’t get collected by Jenkins.
Read more

[100 Days of Code] Day 055: June 6, 2017

Today’s Progress: As I started to build my CD pipeline I noticed that I have some smaller “common” projects that have to be available in a repository in order to be used as a dependency during build. So I started to look into the different types of repositories that are available. Since my current project is publicly available I think that I also have to make the dependencies publicly available in a repository.
Read more

[100 Days of Code] Day 054: June 5, 2017

Today’s Progress: Setup a Jenkins 2 server for CI/CD and created a simple pipeline. Things I’ve learned: How to setup Jenkins 2 and how pipelines are working Things I’ve planned for tomorrow: Improve pipeline Link(s) to work: security-server