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

ci: run-patch-release tries to run unexisting make target update-docs #13381

Closed
endorama opened this issue Jun 10, 2024 · 6 comments
Closed

ci: run-patch-release tries to run unexisting make target update-docs #13381

endorama opened this issue Jun 10, 2024 · 6 comments
Labels

Comments

@endorama
Copy link
Member

endorama commented Jun 10, 2024

RELEASE.md specified to run run-patch-release GitHub workflow when a new patch release should be cut from the release branch.

Trying to follow through for the next 7.17 release I run that workflow but it failed with No rule to make target 'update-docs'; see logs:

Run make patch-release
INFO: Create feature branch and update the versions. Target branch main.
create-branch update-7.17.23
  Switched to a new branch 'main'
  branch 'main' set up to track 'origin/main'.
  Switched to a new branch 'update-7.17.23'
go: downloading go1.22.1 (linux/amd64)
>> update-version
make[1]: *** No rule to make target 'update-docs'.  Stop.
make: *** [release.mk:140: patch-release] Error 2
Error: Process completed with exit code 2.

That target has been removed in c25abdd for releases >8.13, so I expect it to be available on 7.17 and I can grep for it locally:

❯ ag update-docs
release.mk
119:	$(MAKE) update-docs VERSION=$(RELEASE_VERSION)
140:	$(MAKE) update-docs VERSION=$(RELEASE_VERSION)
185:.PHONY: update-docs
186:update-docs: VERSION=$${VERSION}
187:update-docs: setup-yq
188:	@echo ">> update-docs"

The CI job did check out branch 7.17, so I'm not sure why this failure.
338260626-69da053d-b218-4860-be48-e9202e6eff86

As a workaround I've been able to run the command locally with:

❯ RELEASE_BRANCH=7.17 RELEASE_VERSION=7.17.22 make patch-release

to create this PR

@endorama endorama added the bug label Jun 10, 2024
@v1v
Copy link
Member

v1v commented Jun 10, 2024

PR:

I'm trying to recall how it worked in the past, and likely. it did when I tried locally but in the GitHub actions it didn't work.

Regardless, you can run using main always for minor and patch releases. The version is the important input parameter and will be used to switch to the specific branch (main, 7.17 or 8.14 ...)

@endorama
Copy link
Member Author

@v1v thanks for chiming in! So the issue here is that I run the workflow from branch 7.17 instead of main? I'll document this, as I guessed I needed to use the correct release branch.

@v1v
Copy link
Member

v1v commented Jun 10, 2024

The CI job did check out branch 7.17, so I'm not sure why this failure.

The problem is related to the RELEASE_TYPE?= minor therefore it uses main as the default branch and the makefile branches off from main.

image

Even though it initially used the 7.17 branch, as you pointed in the description with the screenshot.

Therefore the new makefile was the one from main and therefore the target update-docs is not available anymore in main or 8.14 .

So the issue here is that I run the workflow from branch 7.17 instead of main

It should behave similarly. The issue was that patch-release didn't set the variable RELEASE_TYPE=patch, then it won't use the main branch but the 7.17 or 8.14.

For simplicity, you don't need to change the branch when running the run-patch or run-minor but set the new version only.

image

@endorama
Copy link
Member Author

Thanks for the explanations and the fix! ❤️

@endorama endorama mentioned this issue Jun 10, 2024
2 tasks
@endorama
Copy link
Member Author

Improved docs around how to run the workflows in 97877ca (#13339)

@endorama
Copy link
Member Author

#13380 has been merged and I added some clarification to the RELEASE.md file in 97877ca (#13339). Closing

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

No branches or pull requests

2 participants