pimutils / pimutils/vdirsyncer
Testing google backend on travis
Open
Nobody has claimed this yet.
cat: server compat
cat: testing
mod: Google
ready
type: enhancement
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 185
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 1
Description
I'd like to see if it's possible to run CI with google's API.
My main idea is:
- Have a
client_idandclient_secretas encrypted travis variables. - Keep the refresh token in some place that lets us store stuff online*. I really wish we could have real long-lived tokens, but oh, well.
- Run tests like we do with other servers (well, actually, requires setting a token and stuff, so a bit of extra work involved).
I'm willing to work on this, since I have to use google's caldav auth for work stuff recently.
- Firebase DB? I recall Mozilla having a similar database (where you could store and retrieve arbitrary JSON), but I can't seem to find it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by reviewing the existing Travis CI configuration and server-integration tests, then determine secure handling for the Google credentials and refresh token; done means Google-backed tests run reliably in CI without exposing secrets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100