100 Days of Code

[100 Days of Code] Day 065: June 24, 2017

I haven’t published my progress in the last few days also I’ve been working on my Project. This is due to the fact that I have been working on getting I2C working on my STM32 and just didn’t get it. Today I started a last try and finally was able to talk to let my STM32 talk to my BME280 environment sensor. I will post my findings in a separate post.
Read more

[100 Days of Code] Day 064: June 20, 2017

Today’s Progress: Setup the project on a new board and rewired everything. This allows me to move the project around more easily. I’ve also been looking into more I2C code. Things I’ve learned: I’ve seen the interior of a breadboard :) Finally… Things I’ve planned for tomorrow: Continue on I2C code. Link(s) to work:

[100 Days of Code] Day 063: June 19, 2017

Today’s Progress: Started to write I2C code. Unfortunately it’s not running yet. Although the examples are working well, using these for an own project is not that easy. Things I’ve learned: How to configure I2C on an STM32. Specially when it comes to more modern STM32 like the L4 family some things are different compared to the more mature families like the F1 or F4. Things I’ve planned for tomorrow: Continue with I2C code.
Read more

[100 Days of Code] Day 062: June 18, 2017

After struggling with the security server integration tests the last days (or weeks?) and being sick for the last days I decided to continue on my second project wich aims at reading and processing environmental data with a STM32 MCU. Today I setup the circuit and got into the Digilent Analog Discovery 2. Today’s Progress: Setting up the circuit and testing an I2C display with an Arduino which I will use as a Hello World tool.
Read more

[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 058: June 10, 2017

Today’s Progress: I have not been able to work on the project as much as I’ve planned but have been able to publish the next artifact. Things I’ve learned: Repeated the steps necessary to publish an artifact. Things I’ve planned for tomorrow: Visiting the Maker Faire Berlin Link(s) to work: persistence-support

[100 Days of Code] Day 057: June 9, 2017

Today’s Progress: Published first snapshot version of a project to OSSRH maven repository. Things I’ve learned: How to setup an account with Sonatype and publish an artifact from a gradle build Things I’ve planned for tomorrow: Integrate publishing into CD pipeline. Link(s) to work: rule-jpa

[100 Days of Code] Day 056: June 7, 2017

Today’s Progress: I have been fighting with eclipse link the whole time. Suddenly my integration tests that where using JPA did stop working. Finally I decided to switch to Hibernate which solved my problems. Things I’ve learned: I will be using Hibernate from now on whenever possible. Things I’ve planned for tomorrow: Continue to publish the whole dependency chain so I can continue with my CD pipeline. Link(s) to work: rules-jpa