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

Move from Travis to GitHub Actions #124

Open
JonathonReinhart opened this issue Feb 25, 2020 · 4 comments
Open

Move from Travis to GitHub Actions #124

JonathonReinhart opened this issue Feb 25, 2020 · 4 comments

Comments

@JonathonReinhart
Copy link
Owner

JonathonReinhart commented Feb 25, 2020

JonathonReinhart/scuba#152

Create PYPI_PASSWORD et al. and add new API tokens.

@JonathonReinhart
Copy link
Owner Author

JonathonReinhart commented Oct 4, 2021

https://app.travis-ci.com/github/JonathonReinhart/staticx/jobs/541021098

Job has been terminated due to insufficient credits balance

WTF happened to "100% free for open-source projects?"

I'm so glad I recently spent the effort getting travis-ci.com (not .org) to work again 🙄

Now I'm back to having no fucking CI again.

https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works

@JonathonReinhart
Copy link
Owner Author

I started to implement this in #194.

@andrewthetechie
Copy link
Contributor

andrewthetechie commented Apr 16, 2023

I might attempt to fix this.

Would you happen to have any concerns with running CI steps inside of docker containers? Then it can use the python-3.x-slim containers and shouldn't hit the DT_RUNPATH issue

@JonathonReinhart
Copy link
Owner Author

JonathonReinhart commented Apr 16, 2023

Would you happen to have any concerns with running CI steps inside of docker containers? Then it can use the python-3.x-slim containers and shouldn't hit the DT_RUNPATH issue

I'm general I have no concerns, but it should be noted that some tests already invoke Docker, e.g.:

I think nested docker should be avoided.

Also, note that there is already an attempt to fix this by switching to a different Python setup action: #224. I don't remember exactly where that stopped.

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

2 participants