If you know any more issues that should be in 1.16.2 please add them to this thread. You may also clone issues in Redmine supposed to be fixed in 1.17.2, set the Release field to 1.16.2 on the cloned version and link them. This is just a workaround as we don’t have the ability to have 2 release fields on Redmine issues.
If this post does not get any new issues by June 1st, I will start moving the release through the pipeline.
It’s after creation, it the post options menu. Here’s a shot.
Currently only Trust Level 3+ can make wikis, but we don’t have many of those yet (the requirements for TL3 are pretty harsh ). I’ve just dropped it to level 2 for now, so check again to see if you have the option.
The environment seems to have a Gemfile.lock for Foreman that’s forcing Rails 5.1 to be installed. This is not compatible with 1.16.2 which is supposed to be Rails 4.2, so it fails to bundle install and the tarball can’t be created.
@ehelms also made some changes to the job to run it just once with release_test. So in case anyone wants to run release_test, check the job changes history and roll it back to include ehelms change to find the Rails repo.
Nevertheless, http://ci.theforeman.org/job/release_test/212/ is failing (consistently) on CentOS. For some reason the proxy cannot be registered, however on Ubuntu/debs it’s able to register just fine…
). I’ve just dropped it to level 2 for now, so check again to see if you have the option.