Skip to content

Improvement to artifact delivery method #9633

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

Merged
merged 4 commits into from
Feb 11, 2019

Conversation

orenc17
Copy link
Contributor

@orenc17 orenc17 commented Feb 6, 2019

Description

A target can define a delivery directory instead of the default option

Pull request type

[ ] Fix
[ ] Refactor
[ ] Target update
[X] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

@theotherjimmy

Release notes

When a target declares a deliver_to_target in targets.json the output binary will be copied to DELIVERY directory in the root of mbed-os.
We now allow to declare a path to where the deliverables will be delivered to by declaring delivery_dir in the the target in targets.json
delivery_dir is a relative to where it was last changed.
so we have the following scenarios:

  1. delivery_dir not specified -> {mbed-os root}/DELIVERY/TARGET_{REQUESTED_TARGET}
  2. delivery_dir specified in targets.json -> the path will be relative to targets folder inside mbed-os.
  3. delivery_dir specified in mbed_app.json -> the path will be relative to that file's base folder.

A target can define a delivery directory instead of the default option
@ciarmcom ciarmcom requested review from theotherjimmy and a team February 6, 2019 14:00
@ciarmcom
Copy link
Member

ciarmcom commented Feb 6, 2019

@orenc17, thank you for your changes.
@theotherjimmy @ARMmbed/mbed-os-tools @ARMmbed/mbed-os-maintainers please review.

Copy link
Contributor

@theotherjimmy theotherjimmy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Back to where I started. Works for me.

@adbridge
Copy link
Contributor

adbridge commented Feb 6, 2019

CI started, but still needs maintainer review

@NirSonnenschein
Copy link
Contributor

NirSonnenschein commented Feb 7, 2019

@orenc17 please take a look at the CI failure - nevermind , unrelated CI issue

Copy link
Contributor

@mikisch81 mikisch81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we should change DELIVERY_DIR now to DEFAULT_DELIVERY_DIR?

@alekla01
Copy link
Contributor

alekla01 commented Feb 7, 2019

Restarted CI

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 7, 2019

Perhaps we should change DELIVERY_DIR now to DEFAULT_DELIVERY_DIR?

Why would you change it? I dont see anywhere in the config used DEFAULT_ ?

@mbed-ci
Copy link

mbed-ci commented Feb 7, 2019

Test run: SUCCESS

Summary: 12 of 12 test jobs passed
Build number : 5
Build artifacts

@mikisch81
Copy link
Contributor

@ARMmbed/mbed-os-maintainers does it really needs-work? eventually tests passed.

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 7, 2019

needs: work

Functionality change should contain release notes section , please add it (following ARMmbed/mbed-os-5-docs#933)

@mikisch81
Copy link
Contributor

Perhaps we should change DELIVERY_DIR now to DEFAULT_DELIVERY_DIR?

Why would you change it? I dont see anywhere in the config used DEFAULT_ ?

Not really important.. thats why I approved.

@orenc17
Copy link
Contributor Author

orenc17 commented Feb 7, 2019

@0xc0170 release notes added

@orenc17
Copy link
Contributor Author

orenc17 commented Feb 7, 2019

@ARMmbed/mbed-os-maintainers could you please run the CI again once travis is done?

@NirSonnenschein
Copy link
Contributor

starting CI

@mbed-ci
Copy link

mbed-ci commented Feb 7, 2019

Test run: FAILED

Summary: 1 of 12 test jobs failed
Build number : 6
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_dynamic-memory-usage

@mikisch81
Copy link
Contributor

LGTM
Did you check the scenario of building from inside/outside mbed-os folder?

@orenc17
Copy link
Contributor Author

orenc17 commented Feb 7, 2019

LGTM
Did you check the scenario of building from inside/outside mbed-os folder?

Yes, it works flawlessly

@mikisch81
Copy link
Contributor

@theotherjimmy, delivery for was changed as you requested.

Copy link
Contributor

@mikisch81 mikisch81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@0xc0170 Can we run CI?

We addressed @theotherjimmy remarks and waiting approval.

Co-Authored-By: orenc17 <oren.cohen@arm.com>
@NirSonnenschein
Copy link
Contributor

starting CI while we wait for technical writer review.

@mbed-ci
Copy link

mbed-ci commented Feb 10, 2019

Test run: SUCCESS

Summary: 12 of 12 test jobs passed
Build number : 7
Build artifacts

@mikisch81
Copy link
Contributor

@ARMmbed/mbed-os-maintainers No technical writer around?
Is it really necessary to postpone this PR like that?

@mikisch81
Copy link
Contributor

starting CI while we wait for technical writer review.

@AnotherButler

@0xc0170 0xc0170 merged commit 36df2aa into ARMmbed:master Feb 11, 2019
@cmonr
Copy link
Contributor

cmonr commented Feb 11, 2019

@mikisch81 Talking with other maintainers on the Release Notes review. Seems odd to me as well that we'd block a PR on a description update.

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

Successfully merging this pull request may close these issues.

10 participants