Code changed in jenkins
User: Victor Martinez
Path:
.gitignore
src/main/java/org/jenkins/ci/plugins/jenkinslint/JenkinsLintAction.java
src/main/java/org/jenkins/ci/plugins/jenkinslint/model/AbstractCheck.java
src/main/java/org/jenkins/ci/plugins/jenkinslint/model/AbstractSlaveCheck.java
src/main/java/org/jenkins/ci/plugins/jenkinslint/model/InterfaceCheck.java
src/main/java/org/jenkins/ci/plugins/jenkinslint/model/InterfaceSlaveCheck.java
src/main/java/org/jenkins/ci/plugins/jenkinslint/model/Job.java
src/main/java/org/jenkins/ci/plugins/jenkinslint/model/Lint.java
src/main/java/org/jenkins/ci/plugins/jenkinslint/model/Slave.java
src/main/resources/org/jenkins/ci/plugins/jenkinslint/JenkinsLintAction/index.jelly
src/test/java/org/jenkins/ci/plugins/jenkinslint/JenkinsLintActionTestCase.java
http://jenkins-ci.org/commit/jenkinslint-plugin/88781f1dab7c4c9c08d3be54a3c414d943fe2f0e
Log:
JENKINS-41449 RestAPI feature (#1)
RestAPI feature: creating a list of elements with some hierarchy
RestAPI feature: refreshing data when quering through the api otherwise it will keep the previous run which means null when it hasn't been requested through the UI
RestAPI feature: fixing bug when creating a list of elements with some hierarchy
Deprecated public api and created an alternative one based on Hashes
Added some test api cases
Added Rest API test cases
Excluding evil macosx files
Removed wrong size method
Using the class name rather than the package+class name, then those data structures amp correctly
- TODO: Hashes caused issues when showing the matrix in the UI, since the ordering is not following the sequential declaration as expclicitly defined in the array section
- We cannot deprecate since we need to use that sorted arraylist to show the UI details since we don't use a specific Key identifier in the hasharray
- Better UI with big tables
- Added better api test case to check the exposed api
Fair point, I've been playing a bit with the RestAPI and it seems to be a pretty simple feature by adding some annotations,
There are a couple of interesting points though:
I'm tempted to use some Hashtable as I've already done with my first approach and have something like:
I'll ask some feedback to the community then
Cheers