-
Notifications
You must be signed in to change notification settings - Fork 729
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
The state of the galaxy release #269
Comments
Thanks for bringing up your concerns!
I wasn't aware of that. This sure sounds like a bug on galaxy side.
What situation do you mean? That galaxy shows the wrong readme?
Galaxy is the main distribution of roles and will probably stay that way, unless RedHat does something else.
If you mean why there is no newer release than 5.2.1: I haven't found the time, sadly.
Yes, absolutely. Right now doing releases is a manual process. For this I use the If you want to help automate this, let's talk! :) |
I'm happy to help with this also. I've done a lot of CI work in jenkins and buildkite. I'd love for a reason to play with github actions. |
Sounds great. Just writing down my ideas what is needed/how this should work.
|
Do you know semantic-release ? It can create a release by simply creating a commit with the |
What we're using right now on our internal projects is release-drafter. There is github action (https://github.com/marketplace/actions/release-drafter) for it that should be a good fit. I don't think it offers a way to update the CHANGELOG.md, but it neatly keeps releases up-to-date with PRs and reduces a release to a single click. What is the process to push the release to galaxy, or is that picked up automatically? @rndmh3ro |
Additionally I found this https://github.com/marketplace/actions/release-notifier-action that might be a good fit for the mailinglist message |
I know this. Since these roles rely on external contributors, I don't know if its a good idea to force specific commit-styles on them.
That's automatic. As soon as there is a new tag/release in Github, Galaxy pulls it.
This looks pretty great! I'd definetly use this, once this PR release-drafter/release-drafter#259 is merged. |
@7php I think Galaxy uses releases/tags, and there were no changes there:
|
@ivanovv is right. |
I uploaded a new version! I'm still looking for ways to automate this so if anyone wants to do this, tell me! |
Okay, I started experimenting. I can automatically update the changelog after closed PRs/issues. Here's the github action: https://github.com/dev-sec/ansible-os-hardening/runs/647446423 Now this is still missing:
For this maybe this works: https://github.com/marketplace/actions/ensure-release.
|
Next step: I have a workflow that runs on every merged PR and then does the following:
This works good so far in my personal repo. I'm going to put it into the hardening-roles next and do a little write-up. You can find the workflow here: https://github.com/rndmh3ro/ansible-os-hardening/blob/7.0.0/.github/workflows/release.yml: |
Removing 2fa
So, i've been struggling with both this and the ssh-hardening playbook for the past two days.
Most of my issues came from the fact that readme contents have diverged from the releases that are available in galaxy.
I know that it is entirely possible to run both playbooks easily from git directly, but keeping the releases available in galaxy combined with the fact that the readme on galaxy is apparently pulled from master is almost malicious.
The last release on galaxy was a year ago and current master is 33 commits ahead; the ssh-hardening repo looks very similar.
Is there any plan to fix this situation in the future? What is the intention towards galaxy?
Why are releases apparently not kept up-to-date?
Do you need support in automating anywhere?
The text was updated successfully, but these errors were encountered: