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.

Sign up for GitHub

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

Jump to bottom

[appveyor] run testing and build artifacts #186

Open
iblislin opened this issue Sep 24, 2015 · 3 comments
Open

[appveyor] run testing and build artifacts #186

iblislin opened this issue Sep 24, 2015 · 3 comments

Comments

@iblislin
Copy link
Collaborator

Appveyor provides windows ci env.
Let's try it out and leverage the 'artifacts' feature to build the windows binary!
iblislin added a commit to iblislin/couchapp that referenced this issue Sep 24, 2015
@iblislin
[couchapp#186] Introduce appveyor testing script
ccf340c
@iblislin
Copy link
Collaborator Author

Got some dir access error

=====================================================================
ERROR: testClone (tests.test_cli.CliTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\projects\couchapp\tests\test_cli.py", line 39, in setUp
    self.tempdir = _tempdir()
  File "C:\projects\couchapp\tests\test_cli.py", line 30, in _tempdir
    os.unlink(fname)
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\users\\appveyor\\appdata\\local\\temp\\1\\tmpb1djax'
-------------------- >> begin captured logging << --------------------
couchapp.client: DEBUG: Resource uri: http://127.0.0.1:5984/couchapp-test

iblislin added a commit to iblislin/couchapp that referenced this issue Sep 24, 2015
@iblislin
[couchapp#186] Close fd properly to resolve the dir access issue
8a9a3e0
@iblislin
Copy link
Collaborator Author

OMG, lots of testing failed because i input unix style path as testing function args.

I decide to skip fixing testing on windows at first, and let standalone binary build ...

iblislin added a commit to iblislin/couchapp that referenced this issue Sep 26, 2015
@iblislin
[couchapp#186] Leverage appveyor to build windows standalone binary
abbda82 
1. So, we only need build with python27
2. python26 env matrix removed
3. Skip testing currently
4. Pack files generated via py2exe with InnoSetup
5. Let InnoSetup script output filename with following format:
   `couchapp-{version}-win{32/64}-py27-{commit hash}.exe`
6. Also, a wheel built, note that this wheel do not contain any depends
BigBlueHat added a commit that referenced this issue Nov 5, 2015
@BigBlueHat
Merge pull request #187 from iblis17/appveyor
f43e931 
[#186][appveyor] build standalone binary!
iblislin added a commit that referenced this issue Feb 12, 2016
@iblislin
Merge branch 'win-exe-test'
da374bf 
Now appveyor will run tests/test_cli.py with built
win standalone exe

ref #186
ref #224
@iblislin
Copy link
Collaborator Author

Now appveyor will run tests/test_cli.py after the standalone exe built. This will do blackbox testing for basic functions with the exe.

@BigBlueHat
Would you setup appveyor for us? I do not have the webhook permission...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iblislin