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 cleanup #1477

Merged
merged 10 commits into from
Jan 11, 2017
Merged

Build cleanup #1477

merged 10 commits into from
Jan 11, 2017

Conversation

blink1073
Copy link
Contributor

Models our python build after nbdime and adds basic install check on appveyor.

# scripts that are called at very beginning, before repo cloning
init:
- ps: (new-object net.webclient).DownloadFile('https://github.com/git-for-windows/git/releases/download/v2.11.0.windows.1/Git-2.11.0-64-bit.exe', 'C:\\git-setup.exe')
- cmd: START /WAIT C:\\git-setup.exe /VERYSILENT
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless you have a specific need for a newer version of git you can remove this bit :)

# scripts to run before tests
before_test:
- git config --global user.email appveyor@fake.com
- git config --global user.name "AppVeyor CI"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also only relevant if you call out to git during your tests.

@blink1073
Copy link
Contributor Author

Thanks @vidartf, I removed the appveyor file altogether because I couldn't figure out how to get appveyor enabled for this org.

@blink1073
Copy link
Contributor Author

Figured it out.

@blink1073
Copy link
Contributor Author

Ugh, no I didn't... There is a granularity of permissions problem.

@blink1073
Copy link
Contributor Author

Found it!

@afshin afshin merged commit 59ed90a into jupyterlab:master Jan 11, 2017
@blink1073 blink1073 deleted the setup-cleanup branch January 18, 2017 18:23
@lock lock bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Aug 10, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Aug 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
maintenance status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. tag:Build System
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants