[2017-03-21 01:13:22] <teilo> @danielbeck: @rtyler is there something wrong with https://plugins.jenkins.io/? distfork is showing as the 1.4.1 release which was done ages ago - and not the 1.5.0 done 3 days ago or anything newer?
[2017-03-21 01:13:34] <teilo> it is up to date in the update-center.json
[2017-03-21 01:26:24] <@danielbeck> probably not updating properly, check recent release for how old it is
[2017-03-21 01:54:43] <@danielbeck> teilo right, so the problem is that a quirk of the plugin site is that the data is generated for the state that the master branch is in, while the deployed site may be behind
[2017-03-21 01:55:23] <@danielbeck> teilo since the docker images are built from master, no deployment without first changing the base for the data generator
[2017-03-21 01:55:39] <@danielbeck> teilo that was updated on Friday or Thursday, but no new deployment, so updates are broken
[2017-03-21 01:55:45] <@danielbeck> probably needs a different process
My suggestion: Revert the relationship between 'develop' and 'master', call them e.g. 'master' and 'active'. Generate data from what's on 'active'.
Whenever you open a PR to jenkins-infra to get a new build, sync 'active' from 'master'. This way, you can get docker builds and open infra PRs without having to break the updates in the mean time.
Alternatively, we can just merge 'master' (or 'active' in the above) into generate-data, so they're no longer separate. Could be easier that way, modulo the Jenkinsfile differences (always keep the 'generate-data' behavior).