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

[WIP] Updates to support st2 packaging #1917

Merged
merged 61 commits into from
Sep 5, 2015
Merged

Conversation

Kami
Copy link
Member

@Kami Kami commented Aug 31, 2015

Another attempt based on #1677 and #1916.

This time more incremental and hopefully less breaking and more smooth.

TODO:

  • Make sure latest version of pip (7.0) is available on all the build servers

dennybaa and others added 30 commits June 17, 2015 21:36
… used by

current build workflows and st2_deploy.
Kami and others added 26 commits September 1, 2015 19:36
duplicating the code across setup.py files.

Note: This file is copied over from the common location to each component
directory during the build step.
Inferring it from the directory name only works inside the source check and
not anywhere else (e.g. setup.py doesn't work inside the dist tarball, etc).
duplicating the code across setup.py files.

Note: This file is copied over from the common location to each component
directory during the build step.
Inferring it from the directory name only works inside the source check and
not anywhere else (e.g. setup.py doesn't work inside the dist tarball, etc).
… into updates_for_st2_packaging_with_upstream_fixes
… into updates_for_st2_packaging_with_upstream_fixes
… into updates_for_st2_packaging_with_upstream_fixes
@Kami Kami merged commit 095d4b8 into master Sep 5, 2015
@Kami
Copy link
Member Author

Kami commented Sep 5, 2015

I finally managed to track down all the CI/CD pipeline issues and everything now passes so I went ahead and merged changes into master.

We still need to be a bit careful when rolling out a new "major" release (0.14.0 / 1.0.0) since some of the stuff has changed, but it should really only affect st2client if anything (I did fix and test all the st2client related issues locally, but it's also possible that our workflows do some weird stuff with it which I didn't catch :P)

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

Successfully merging this pull request may close these issues.

2 participants