Skip to content

Build and deploy from the devel branch once a week, preferably at the… #2486

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

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

Conversation

x1101
Copy link
Contributor

@x1101 x1101 commented Mar 28, 2025

… start of the week

Fixes #2049

@oraNod
Copy link
Contributor

oraNod commented Apr 8, 2025

@x1101 As mentioned in the DaWGs meeting today, could you adjust the schedule so devel builds at least once a day?

@samccann Should we maybe go for twice a day even?

@x1101
Copy link
Contributor Author

x1101 commented Apr 8, 2025

@oraNod until we do more digging on the integrated build matrix, I did push fixes for the other issues @gotmax23 mentioned on #2050 as well as the change to daily.

@x1101
Copy link
Contributor Author

x1101 commented Apr 21, 2025

@oraNod & @gotmax23 I think I have both of these sorted out now. I'm still not 100% confident that I have the deployment/package/repository vars set correctly for the individual builds. I might have gotten a little lost in the weeds trying to dig through the two different threads we had open for the builds.

Feel free to "just fix it" if I'm still off, or let me know and I can.

…mp this to fedora 40 (41 and 42 had other failures and would require additional investigation/modification)
@oraNod
Copy link
Contributor

oraNod commented Apr 22, 2025

@x1101 Thanks for continuing to work on this. I've noticed a few updates to the workflows. It looks like your branch needs to be rebased against devel. And there is also an unrelated commit to the EE base image version that needs to be dropped.

It would get messy if I tried to push all that directly to your branch. Could you please take a look and update?

I pushed the changes that I think we need to my own branch here: https://github.com/oraNod/ansible-documentation/commits/issue-2049/50/schedule-builds/

Please see the top three commits in that branch. You can make the changes directly or cherry pick them if you like.

If you would rather, we can close this PR and I can open a new one based on my branch. I cherry picked your commits so you'll still get attribution as a commit author.

…if we bump this to fedora 40 (41 and 42 had other failures and would require additional investigation/modification)"

This reverts commit a6b378c.
@x1101
Copy link
Contributor Author

x1101 commented Apr 22, 2025

@oraNod Thanks for all the help. I think this is (finally) in a state where it just has the two relevant files, named as we want, with the most current version of content.

At this point, we can poke at the details and determine if they're in-line with what we set out to achieve on #2049 and #2050

@oraNod oraNod added doc builds Relates to building the documentation no_backport This PR should not be backported. devel only. labels Apr 22, 2025
@oraNod
Copy link
Contributor

oraNod commented Apr 22, 2025

This looks pretty good to me @x1101 Thanks again for the work.

@samccann Can you please take a look and confirm the schedule / cronjob for each of the builds? I think we wanted devel on a daily basis and latest on once a week, right?

We could do devel twice a day. We want devel to be fairly up to date so I'm thinking about when merges are most likely to happen. I usually try to do reviews in the morning and merge so scheduling a build mid-day for me (early morning for EST) would make sense. And then another build scheduled for late afternoon EST could get any changes that folks in the US merge at the start of their day.

Can always monitor and adjust as we go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc builds Relates to building the documentation no_backport This PR should not be backported. devel only.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build and deploy from the devel branch once a week, preferably at the start of the week
2 participants