aistomin / jenkins-sdk Goto Github PK

Take a look at FakeJenkins methods implementation. We need something similar here.

We have empty interface JobDetails. It needs to be designed.

1. Implement method(see Documentation).
2. Create integration test for it.

Take a look how FakeJenkins is implemented. Here we want to have something similar.

1. Implement method(see Documentation).
2. Create integration test for it.

1. Implement method(see Documentation).
2. Create integration test for it.

1. Implement method(see Documentation).
2. Create integration test for it.

Take a look at FakeJenkins methods implementation. We need something similar here.

Take a look how it is implemented in Jenkins.xml(). Something similar must be there.

We have empty interface Job. It needs to be designed.

Take a look at FakeJenkins methods implementation. We need something similar here.

Must be done after #32. Just implement some primitive search by list.

We have empty interface Jobs. It needs to be designed.

Take a look how it is implemented in Jenkins.xml(). Something similar must be there.

We have empty interface Builds. It needs to be designed.

1. Implement method(see Documentation).
2. Create integration test for it.

The idea behind this two packages fake/real may be not clear. We need to add some explanations to README.

Currently "Purpose" section doesn't look great. Let's try to improve it.

1. Implement method(see Documentation).
2. Create integration test for it.

1. Implement method(see Documentation).
2. Create integration test for it.

1. Implement method(see Documentation).
2. Create integration test for it.

1. Implement method(see Documentation).
2. Create integration test for it.

We have empty interface Users. It needs to be designed.

Take a look at FakeJenkins methods implementation. We need something similar here.

1. Create class.
2. Create puzzles for every method.
3. Create test class with a sample method.

Create class, test class and puzzles for every method.

https://cisdk-istomin.rhcloud.com/

Take a look at FakeJenkins methods implementation. We need something similar here.

1. Implement method(see Documentation).
2. Create integration test for it.

Take a look at FakeJenkins methods implementation. We need something similar here.

Create design of empty interface User. Keep in mind this request: https://cisdk-istomin.rhcloud.com/asynchPeople/api/xml?depth=3&xpath=people/user/user[id='integration'] It might help with designing.

There is instruction how to do that: http://www.qulice.com/
What should be done:

1. Configure project to use Qulice.
2. Add sample class and test for it.
3. Make sure that Qulice validation works correctly.
4. Add section to README file. In this section explain how to test the project with Qulice.

1. Implement method(see Documentation).
2. Create integration test for it.

We need:

1. Parameterless constructor that will create fake instance with all the default fake objects.
2. Constructors with one and only parameter. For example, user wants to set only users dependency and want others to be default.

Take a look at FakeJenkins methods implementation. Here we want to have something similar.

1. Implement method(see Documentation).
2. Create integration test for it.

Take a look at FakeJenkins methods implementation. We need something similar here.

1. Implement method(see Documentation).
2. Create integration test for it.

Implement method(see Documentation).
Create integration test for it.

1. Implement method(see Documentation).
2. Create integration test for it.

Create Java Maven project structure.

We need basic interfaces like Jenkins, Builds, Build etc. This interfaces will be a good start point and define the SDK's architecture.
We need to create empty implementation for real classes(let's call them with prefix Real, like RealJenkins) and fake classes(let's call them with prefix Fake like FakeJenkins).
We need to create issues for every empty/unimplemented method.

Create apache license file.

1. Implement method(see Documentation).
2. Create integration test for it.

Would be great to have automated merge process. This looks like a really good tool. If configuration will not take > 8h, we definitely want to have it.

Look at FakeJenkins class. We need to implement something similar. List that will be returned have to be configurable via ctor.

1. Configure project to use Travis CI.
2. Add nice travis label to README file.

We have empty interface JobParameter. It needs to be designed.

Take a look at FakeJenkins methods implementation. We need something similar here.