Hi Janez,
1. Receive the job parameters from the Eclipse user (if I understand > correctly, this is already supported by Jenkins under the "File parameter" > utility). > 2. Run the build. These steps can be done using Jenkins APIs or CLI. No need in the plugin 3. Send the build and the parameters to the third-party tool. I need more details to provide an exact answer. There are dozens of potentially applicable plugins. E.g. https://wiki.jenkins-ci.org/display/JENKINS/Notification+Plugin 4. Receive the test results from the third-party tool and display them for > the Jenkins user (the results can be viewed in a web browser through the > Jenkins UI), including the results history for this job. Does not need a plugin if you want to display it in a separate job. Tests results can be uploaded as File parameters and displayed using xUnit plugin. среда, 14 октября 2015 г., 19:36:44 UTC+3 пользователь Janez Novak написал: > > Hi, > > so I'm working on a project that requires me to produce a Jenkins plugin. > My part of the project on the whole will look something like this: > > 1. An Eclipse user (a software engineer) will trigger a Jenkins job > through the Eclipse UI on his local machine. > 2. With action #1, a script (probably a bash script) will be sent to the > triggered job. This script will contain parameters for the job. > 3. The job will execute a build. The job will then send the build and the > parameters to a third-party tool (a testbed developed by the other guys on > the team). This third-party tool will execute tests based on the parameters. > 4. The third-party tool will then send the test results back to the > Jenkins job. Jenkins will then display the test results in some form > (graph, numbers, etc.). The results should represent some sort of history > (e.g. successful builds over time, etc.) > > So my Jenkins plugin should really do the following things: > > 1. Receive the job parameters from the Eclipse user (if I understand > correctly, this is already supported by Jenkins under the "File parameter" > utility). > 2. Run the build. > 3. Send the build and the parameters to the third-party tool. > 4. Receive the test results from the third-party tool and display them for > the Jenkins user (the results can be viewed in a web browser through the > Jenkins UI), including the results history for this job. > > I'm new to Jenkins and plugin development, so I'm not really sure whether > some of these functionalities are already implemented in Jenkins by > default. I am also not sure which of these functionalities are already > provided by existing plugins. I've chosen Java to write the whole thing > (not sure if other languages are even an option). > > The "results display" functionality is something I've found among existing > plugins, particulary in the "Warnings" plugin. Although the "Warnings" > plugin does not deal exactly with displaying results, it would at least > provide some kind of a blueprint to implement this functionality. > > As for the other functionalities, I haven't seen them in any of the > existing plugins. I have probably missed something, which is part of the > reason for this post. > > Could anyone point me towards existing plugins (or the ones in > development, code snippets, etc.) that I might've missed? Also, if anyone > has any general idea of the best way to go about this, that would be great. > Even a general discussion about how this could work would be good. > > If I've been unclear about anything, feel free to ask. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b32ea004-0b3d-4bc3-8c36-92444dc71ff1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
