Skip to content
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

Setup mail configuration #33

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

CedricLevasseur
Copy link

A task to enable mail configuration for nexus, using the rest API

@CedricLevasseur
Copy link
Author

Please don't hesitate to let me know it had a chance to be merged.
If you whish some improvements in my code, let me know.
Thanks

@CedricLevasseur
Copy link
Author

CedricLevasseur commented Oct 24, 2017

Facepalm, i'm just seeing @dannyk81 made a pull request on exactly the same subject : the mail configuration. We used differents solutions : Rest Api for me. Groovy for him.

@zeitounator
Copy link
Contributor

Hi @CedricLevasseur

As you may have seen in #36 and #38, 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, 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

I already integrated the other submitted pull request regarding email configuration as well as many other things among which travis integration for CI and testing. You're more than welcome to join and contribute if you have time and other 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.

Copy link

@gbonnefille gbonnefille left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a consequence, and after waiting for a response of the authors and suggestions from other contributors, 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

Why this repository is not declared as a fork of @SavoirFaire's one? It would certainly help to understand the community around Nexus3 Ansible role.

args:
ldap_id: "{{ nexus_ldap_id }}"
role: "{{ nexus_role }}"
usernames: "{{ nexus_ldapadmin_username }}"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why LDAP related info for seting up mail parameters?

@zeitounator
Copy link
Contributor

@gbonnefille: the forked repository is a "hard" fork. The repos here has not moved for the last year and nobody was willing to answer our questions at the time the decision was taken.

Have a look at the new repo and you'll see a lot of work as been done since then that makes the 2 repos very different (and would make collaboration and pull requests between the 2 repos merely impossible now).

Feel free to use either repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants