-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Release #966
Comments
Currently the acceptance tests are failing. I've tried to take a look at it, but haven't had a lot of time for it. This is probably related to the CLI and there's a few PRs / issues around that as well. If the acceptance tests are green, I have no problem releasing a new version. |
I agree with this. I just upgraded to the latest released version 1.7.0 of the module for it to work on Puppet 5.5 but I still get the:
error. This seems to be fixed in Git master so I will try that one, but it would be really nice if we can get a new release of this module. |
#981 at least made the test suite green on Ubuntu in Travis. On a libvirt VM it was also green on CentOS for me. Can't quite explain why yet, but I'd like to have green tests before we release. I also started with going through some deprecations. However, I'm mostly working on it as a side project so progress is slow. Any help is appreciated. |
I've started to assign things to the 2.0.0 milestone. |
@ekohl shouldn't it be something higher than 2.0.0? 2.0.0 release exists :) Anyways, a new release would be really appreciated, as Jenkins changed their signing keys (see e.g. the announcement on https://pkg.jenkins.io/redhat/) to https://pkg.jenkins.io/redhat/jenkins.io.key and the currently released module deploys the old key and then fails to install Jenkins :( Changing just the key URL in the 2.0.0 release is sufficient to make this work, so maybe a 2.0.1 with that change only is a good intermediate solution? Or picking 67d219e into that release? |
Well, it looks like I should have checked more. Looks like I should create a 3.0.0 milestone instead. |
For any following along... #1000 is in progress (a rebase post-merge of other bits of the 3.0.0 milestone will still be needed). |
Maybe worth a bump? Could you release a newer version which has the |
Hi,
I see it's been a while since a new release from this module has been released.
Could you please release a new version with the new commits please ?
If a new release is being blocked by something, could you tell what is blocking to see if this is something I can work on, so that we can move forward ?
The text was updated successfully, but these errors were encountered: