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

Cherry-pick: Publish artifacts from release branches separately (#8062) #8159

Merged
merged 1 commit into from
Jul 27, 2018

Commits on Jul 27, 2018

  1. Publish artifacts from release branches separately (vmware#8062)

    By default, the build-ova.sh script used by vic-product to create the
    unified OVA picks the most recent build uploaded to vic-engine-builds.
    
    Because builds from all branches are written to the same directory,
    this can lead to unexpected combinations of components being assembled
    into an OVA.
    
    To allow downstream jobs more reliably consume desired dependencies,
    publish artifacts from release branches into sub-directories of a
    releases directory.
    
    This alone will improve the behavior of downstream builds expecting to
    consume dependencies from master. With additional changes, this can be
    leveraged to allow push builds on release branches to behave more like
    push builds on master: consuming the most up-to-date build from the
    appropriate branch of the upstream.
    
    Update jenkins-nightly-run.sh to allow download of builds published to
    release branch directories.
    
    Additionally, publish artifacts from PR builds into separate bucket.
    
    (cherry picked from commit 00d377d)
    zjs committed Jul 27, 2018
    Configuration menu
    Copy the full SHA
    4b10b69 View commit details
    Browse the repository at this point in the history