Skip to content

Continuous testing (part 2) / Automatic Building #44

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

Open
3 of 10 tasks
stonebig opened this issue Jan 25, 2015 · 3 comments
Open
3 of 10 tasks

Continuous testing (part 2) / Automatic Building #44

stonebig opened this issue Jan 25, 2015 · 3 comments

Comments

@stonebig
Copy link
Contributor

The Continuous testing / Automatic building idea is the next direction of Winpython.

This tries to summary what seems logical steps to go in that direction:

Continuous testing

  • relies on python 'wheel-type' packages only
  • for build process, move all whished packages in a 'my_wheels' directory,
  • simplify build process up to pip install --no-index --find-links=file://my_wheels -r requirements.txt
  • translate it on a CI infrastructure
  • add tests on pre-built Winpython
  • avoid time-limit wall (of 40' ? ) in CI Infrastructure

Automatic building

  • resolve the create icons problem
  • resolve the create installer problem
  • add tests on builded Winpython
  • avoid time-limit wall (of 40' ? ) in CI Infrastructure
@stonebig
Copy link
Contributor Author

a baby step success after Ogrisel pycon2015 talk: re-engineering, building and testing on Appveyor an existing package.

@stonebig
Copy link
Contributor Author

stonebig commented Oct 5, 2015

maybe this would solve the big/volumetric part of the Winpython in-the-cloud equation: https://github.com/blog/2069-git-large-file-storage-v1-0

did anyone try this ?

@stonebig
Copy link
Contributor Author

small moces:

  • this is automatically build and deployable (as a webapp)... maybe the future: https://github.com/stonebig/my-demo2
  • cgolke is now creating his wheels on github, so automatic download is more possible.

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

1 participant