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

Working with current Ansible (>= 1.9.x[.x]) and CentOS #2

Closed
tnt opened this issue Apr 10, 2015 · 3 comments
Closed

Working with current Ansible (>= 1.9.x[.x]) and CentOS #2

tnt opened this issue Apr 10, 2015 · 3 comments

Comments

@tnt
Copy link
Contributor

tnt commented Apr 10, 2015

I've put some crude changes for working with CentOS and current Ansible to this gist. This should be okay for quick testing here and now. But it's not good enough for a PR. And honestly said I would prefer to drop git-install.sh at all. The EPEL-/ppa-packages seem to be very up-to-date.


The previous way of installing Ansible with git does not work with the current version. Some considerations:

Until Vagrant 1.8.x the content of the VERSION file matched the version number in the respective branch name (1.8.4 -> release1.8.4). Currently (with version 1.9.0) there is only one stable-1.9 branch but several sub-versions. For each of these sub-versions (or sub-sub-versions) there is a tag and the respective commit has a VERSION-file with equivalent content as follows:

tag VERSION
v1.9.0-1 1.9.0 1
v1.9.0-2 1.9.0 2
v1.9.0.1-1 1.9.0.1 1
v1.9.1-0.1rc1 ?

So we could replace the --branch release$ANSIBLE_VERSION with something like --branch v$ANSIBLE_VERSION to install that version and at a later run compare it like [ "$(<${ANSIBLE_DIR}/VERSION)" != "${ANSIBLE_VERSION/-/ }" ]. But what really sucks is:

set +e
source ${ANSIBLE_DIR}/hacking/env-setup
set -e

which seems to fail more or less regularly.

With pip installs it would not work to compare a version (or only for minor versions - pip show ansible | grep -E "^Version: " | grep -Eo "[0-9.]+" yields 1.9).

@arBmind
Copy link
Member

arBmind commented Apr 11, 2015

You made some good points here... I would not drop the git-install. You can give it a branch and a version to compare to. Which works fine for trying out betas and master versions. But this is not the desired interface.

Adding pip-install would definitely be a huge improvement.

@arBmind
Copy link
Member

arBmind commented Apr 2, 2016

I added a mirror https://github.com/dresden-weekly/ansible that contains clean git branches that are usable with the git install.

Overall it's not ideal.
We continue to need git install support, to try out custom patches and ansible variations.
The branch names should be more customizable and possibly independent of the VERSION check. See #5

PIP installation option would still be very nice to have. See #4

@arBmind
Copy link
Member

arBmind commented Apr 2, 2016

I close this issue as no progress was made in the last year and we have more focussed follow up tickets.

@arBmind arBmind closed this as completed Apr 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants