-
-
Notifications
You must be signed in to change notification settings - Fork 745
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
Conversation
… used by current build workflows and st2_deploy.
…nley into updates_for_st2_packaging
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
…nley into updates_for_st2_packaging
Conflicts: .travis.yml
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) |
Another attempt based on #1677 and #1916.
This time more incremental and hopefully less breaking and more smooth.
TODO: