Skip to content

Travis now limiting OSS builds #3274

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

Closed
effigies opened this issue Nov 22, 2020 · 6 comments · Fixed by #3318
Closed

Travis now limiting OSS builds #3274

effigies opened this issue Nov 22, 2020 · 6 comments · Fixed by #3318

Comments

@effigies
Copy link
Member

Travis won't run until OSS credit builds for the nipy organization are replenished at some unknown time.

We may want to transition to GitHub actions.

@satra
Copy link
Member

satra commented Nov 22, 2020

i have requested additional credits. but github actions would be fine as well.

@effigies
Copy link
Member Author

I'm going to try to transition nibabel. Azure has been dissatisfying for Windows anyway, so I'm a bit motivated to abstract out the CI into shell scripts that just need to be invoked from whatever the next CI is.

@effigies
Copy link
Member Author

FWIW: nipy/nibabel#972

The unification of Linux/OSX/Windows is quite nice. The handling of environment variables less so.

@effigies
Copy link
Member Author

Looks like a couple daily cron jobs was enough to exhaust our extended supply. I cut nibabel way back, so either ARM jobs cost a TON or nipype is chewing through credits with the parameterized jobs.

@satra
Copy link
Member

satra commented Dec 10, 2020

they extended my credits. are they not being used for this? i'll try to look into it.

@effigies
Copy link
Member Author

We did get more. And it seems they're used up.

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 a pull request may close this issue.

2 participants