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

Build Package automation #592

Closed
ssorenso opened this issue Feb 21, 2017 · 1 comment
Closed

Build Package automation #592

ssorenso opened this issue Feb 21, 2017 · 1 comment
Assignees

Comments

@ssorenso
Copy link

  • Title: Build package automation
  • Attachments: None
  • Details: This is an enhancement

OpenStack Release

WIP

Description

In order to handle the:

  • Detection of issues with Linux package building
  • Detect discrepancies in dependencies.
    • The automation around generalizing build requirements and make the package building process more future proof

Agent Version

Not set

Operating System

Both Ubuntu 14.04 (trusty) and CentOS 7

OpenStack Release

Not set

Description

This is not to handle a bug; however, it does expand up what the bug #494 fixed.

Deployment

This is not relevant.

@ssorenso ssorenso self-assigned this Feb 21, 2017
ssorenso pushed a commit to ssorenso/f5-openstack-agent that referenced this issue Feb 21, 2017
Fixes F5Networks#592

Problem:
The issue of the RPM and DEB build packages not being flagged as broken
if/when an issue occurs while building them as well as having multiple
places where dependencies are listed.

Analysis:
This change introduces automation around building the packages and
performing automated testing.  This also flat-lines the code into
python for greater usability as well as supportability.

Tests:
This code is, in and of itself, a test.  This code will first build the
packages, and then perform an install test against those packages.
ssorenso pushed a commit to ssorenso/f5-openstack-agent that referenced this issue May 23, 2017
Fixes F5Networks#592

Problem:
The issue of the RPM and DEB build packages not being flagged as broken
if/when an issue occurs while building them as well as having multiple
places where dependencies are listed.

Analysis:
This change introduces automation around building the packages and
performing automated testing.  This also flat-lines the code into
python for greater usability as well as supportability.

Tests:
This code is, in and of itself, a test.  This code will first build the
packages, and then perform an install test against those packages.
@richbrowne
Copy link
Contributor

Done.

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

No branches or pull requests

2 participants