ansible-nexus3-oss
ansible-nexus3-oss copied to clipboard
savoirfairelinux
Recent Releases
Hi,
I'm currently using this role to provision a Nexus instance on one of our servers, and it's working flawlessly, thanks for developing this! The only issue I'm finding so far is the purple bar stating the small amount of max file descriptors. The role defaults to 4096 whereas Sonatype recommends a minimum of 65536.
The latest commits to this role seem to have fixed the issue although the latest release does not include this fix. I was wondering when you're going to release v1.7.1, or v1.8.0? I could specify a commit hash in requirements.yml but it doesn't look right. At the moment I'm relying on the lineinfile module to specify the right amount of file descriptors.
Thanks in advance :)
Slow release cycles of this role are for me and my customers a problem, too. Forking and switching between the fork and this repo in the requirements.yml every time is a dangerous move and not the best solution.
@samherve: Can we discuss about a regular release cycle e.g. monthly? Can we help to get you there? If you have no time maybe you can delegate some rights for pull requests to a development branch?
I think a CD/CI pipeline can help to speed up the integration of pull requests too. Have a look at PR #24. It uses Travis CI, so you don't need additional infrastructure. You only have to merge the PR and register this repository to Travis.
This ansible role is great and big thanks to all contributors. I use it as an example for my Ansible training and consulting. Also I have more than 20 instances in production using this role.
Sorry to say this, but if this project doesn't speed up in the future, I see myself forced to hard fork this repo. I don't want to go so far. So please get in touch with us ;)
+100
We are too very dependant on this playbook and have been contributing various changes and enhancements that we require for our deployment, as a result we've had to fork and start using our own copy of this.
@samherve as mentioned above, we are willing to help and contribute!
Hi @balux , unfortunately I won't be able to continue working on this role, but maybe someone else at @savoirfairelinux will be able to ? If not, feel free to fork :)
cc @mgubaidullin
Hello @support-savoirfairelinux. Since @samherve announced above he would not be able to maintain this project anymore, is anyone in your organization willing to go on with this ? Of course, forking is an option but I don't think we (me or anybody) do it before you give us a clear response. Could you let us know your position before we take a decision ? Several users are interested in this role and actively using it. Thanks in advance.
Hello people. There is a discussion going on in #38 about how and where to fork the repo if @support-savoirfairelinux is not willing to take the maintenance over. Please let us know what you think and if you have time to devote to this.
Regards
Hi @justinsaliba ,
As announced here, the maintenance of this repo has been discontinued
As a consequence, and after waiting for a response of the authors and suggestions from other contributors here and in #38 , I decided to fork the repo to go on with maintenance. You can find the new repo there: https://github.com/ansible-ThoTeam/nexus3-oss
The last release integrated most of the current pull requests here among which travis integration and molecule testing on ubuntu and centos. You're more than welcome to join and contribute if you have time and contributions to propose. I'm also looking for good willing people for code reviews, writing more tests, documenting, preparing new releases/merges. Drop me an email (link on my github profile page) if you wish to get involved.
Cheers.
Thanks @zeitounator . Unfortunately I do not have much time to get involved, although i very much appreciate you and the rest of the authors taking this on and continuing with the development of this role.
I'll definitely follow any changes you make on that repository, and will ping you if time ever permits to devote some time to helping you with respect to maintenance tasks, or whatever is required :)
Cheers, Justin