Jenkins add px4fmu bloaty comparison with last successful master build #9142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dagar
changed the title
|
To see this follow the Jenkins link on a PR and drill down into the steps included under any of the px4fmu builds. Example removing mpu9250 from px4fmu-v2. http://ci.px4.io:8080/blue/organizations/jenkins/Firmware/detail/pr-jenkins_bloaty/4/pipeline/39 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This shows the code size changes compared to the last successful master build.
For example removing mpu9250 from the fmu-v2 configuration (not merging this).
@davids5 @bkueng @LorenzMeier FYI