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

Move from Travis CI to GitHub Actions #50

Open
jpdillingham opened this issue Oct 2, 2022 · 3 comments
Open

Move from Travis CI to GitHub Actions #50

jpdillingham opened this issue Oct 2, 2022 · 3 comments
Assignees
@Udeozor
Labels
hacktoberfest

Comments

@jpdillingham
Copy link
Member

Travis CI discontinued their free product, which this relies (relied?) on. Either way, CI is broken and will remain that way.

We should use GitHub Actions for CI, instead.

I can help by adding whatever environment variables we need.
@Udeozor
Copy link

Udeozor commented Oct 2, 2022

Hello, I would like to take this up.

@jpdillingham
Copy link
Member Author

Thanks! I'll go ahead and generate new AWS credentials and put them in environment variables for you.

@jpdillingham
Copy link
Member Author

You can find the AWS creds in AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. These creds belong to the same user we were using for Travis CI, and permissions are unchanged (S3 full access) so there should be no issue uploading code or setting the ACL, but let me know if you encounter any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Udeozor Udeozor

Labels
hacktoberfest
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jpdillingham @Udeozor