New deployment of prprocessor

Development
1

tl;dr: a heads up you might see issues with theforeman-bot

Soon I’ll deploy a new version of our PR processor (the code behind theforeman-bot on GH). One change is to use HTTPS to talk to Jenkins and Redmine. Last time we tried it, it didn’t work because the Ruby + OpenSSL versions we were using. Now we’re running on a newer Ruby version so I’m hopeful enough to try again. I’ll monitor the logs and revert if I see issues.

Of course I’d be happy to hear if you see odd things. Rather too much than too little reports so don’t hesitate.

2

The only issue I’ve seen is that the theforeman-bot user has insufficient permissions on the foreman_virt_who_configure repository but that’s unrelated :slight_smile: Still open to other bug reports of course.

3

Could it be related to the issue we see in foreman_discovery? We’re unable to kick off the test run.

4

I don’t see any errors in the log that could relate to this. Perhaps it has to with the refactoring @Adam_Price1 is doing.

5

Strange. That pull requests seems to have kicked off the job. The job finished (in a failed state) but the pull-request never got out of pending.

I have been refactoring lots of Jenkins jobs, but test_plugin_foreman_discovery_develop isn’t one where I’ve merged any changes yet.

I’ll have to investigate to see what’s going on.