swagger-api / swagger-api/swagger-codegen
Better CI/CD with travis-ci.org
Open
Nobody has claimed this yet.
Client: Android
Client: C-Sharp
Client: C++
Client: Dart
Client: Go
Client: Java
Client: JavaScript/Node.js
Client: Objc
Client: Perl
Client: PHP
Client: Python
Client: Retrofit
Client: Ruby
Client: Scala
Client: Swift
Client: TypeScript
Enhancement: Feature
help wanted
Server: Java
Server: Nodejs
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
The generator will automatically generate .travis.yml for API clients and server stubs so that the output will be ready for CI/CD with travis-ci.org.
If anyone has cycle to add travis.yml for a particular API client or server stub, please reply to let us know.
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
The issue concerns the generator's output for API clients and server stubs, specifically adding .travis.yml files. Start by locating the generator templates and existing generated-project CI configurations; done means the relevant outputs include working Travis CI configuration for the selected clients or stubs.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100