-
Notifications
You must be signed in to change notification settings - Fork 4k
(Updated) Adding a "source-bundle" target to the Makefile #13471
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
Conversation
…ist" target The main difference is that the "bundle" target does NOT exclude packaging and testing directories, which enables packaging and testing of the source archive. Signed-off-by: Kartik Ganesh <[email protected]>
This is done by introducing a generic function that holds the common code, which then creates these two targets. The differing properties (like rsync flags) are passed in as function arguments. Signed-off-by: Kartik Ganesh <[email protected]>
Test process detailsSetupFirst, I ran the Next, I switched to the feature branch and executed the source-dist verificationThe following commands produce no diff/output, verifying that the artifacts produced by the source-bundle compared to source-distThe following commands verify that the only difference between the output of |
|
I ran the commands that caused the prior PR to fail - #13385 (comment) - and verified that these pass now on the feature branch: I also ran these commands with |
|
@kartg thank you for sharing the steps you have taken to test these changes. |
michaelklishin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A generic binary build produced from a source bundle passes a set of client test suites I use (plus rabbitmqadmin v2 tests) and seems as complete and functional as a source-dist-based binary build.
Now lets see how the alpha package workflow runs.
|
All packages were built successfully so we can backport. |
|
@Mergifyio backport v4.1.x v4.0.x |
✅ Backports have been created
|
(Updated) Adding a "source-bundle" target to the Makefile (backport #13471)
(Updated) Adding a "source-bundle" target to the Makefile (backport #13471)
|
@michaelklishin thanks for merging this in! Also glad to see that I didn't break any of the packaging workflows this time 😅 Could this change be backported to |
(Updated) Adding a "source-bundle" target to the Makefile (cherry picked from commit 916b032) Conflicts: Makefile
|
@kartg since this is a non-functional change, I've backported manually to |
Proposed Changes
This change adds a
source-bundlebuild target to the RabbitMQ Makefile. This target is identical to the existingsource-disttarget but it also allows for packaging and testing of the source archive.Code duplication is avoided by moving the common code for both targets to a generic function, which is responsible for creating the actual Makefile targets. The differing properties (like
rsyncflags) are passed in as function arguments.This is a re-implementation of the change in #13385. Additional testing has been done to verify that existing targets do not change/break.
Types of Changes
What types of changes does your code introduce to this project?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply.You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
CONTRIBUTING.mddocumentFurther Comments
This PR consists of two commits - the earlier commit adds the
source-bundlein a straightforward manner by duplicating the logic forsource-distand simply modifying thersyncflags. The second commit refactors common code to a generic function, as described above.