I have been inactive for some time now, but I would like to get back up to speed and start making some contributions. One thing I was hoping to do was help get rid of some of the nightly build errors so that we can get a stable base and hopefully make a release soon. I spent the time getting the docker container set up and understanding how the current CI system works. Thanks to those who have been putting in the effort on this.
I got the basics working and then looked to the nightly build log from last night so that I could try and replicate, then fix a bug. To my surprise, the build that failed last night built successfully. Of course a quick look at the recent commits shows that Xiang already fixed the issue. This brings up a point that I saw mentioned in one of the email threads - we should use the Jenkins build failure to create an issue for us. This will allow us to see what progress is being made on each issue, and know if it has been resolved or not. Of course there is still a race condition where two people decide to pick up the same task at once, but this could be solved by the contributor assigning the issue to themselves, or commenting on it stating they are going to look into it. It looks like there is a Jenkins plugin that allows the Github issue to be created relatively easily. I'd be happy to try and get this working if everyone agrees. https://plugins.jenkins.io/github-issues/ Justin, could you please give me admin access to Jenkins? Best, Anthony
