> Am 28.06.2021 um 23:51 schrieb Devin Foxhoven <[email protected]>: > > Hello, > > I was guided to this online group to direct my question. Specifically, myself > and several other students at a university are working on a research project > that will function as a plugin on Jenkins. Only just recently starting > however, we had several questions regarding the capabilities and limitations > of the plugins. > > These are as follows: > How can we design the plugin to trigger whenever a user commits to a GitHub > repository? > Can a Plugin access the current codebase in a GitHub repository, and by > extension extract the java files within? > Can a plugin run the test cases of a Repository, and then by extension save > the data to a csv file? > We haven't been the most successful in finding these answers in any previous > posts or on tutorials, so if anyone can assist us, that would be phenomenal. >
>From your descriptions it looks like that you are trying to adapt Jenkins to >work with your code. It would simpler if you would adapt your code to work >with Jenkins. Normally Jenkins handles for you: 1) Trigger from any repository 2) Checkout from any repository Then your plugin comes into place: it runs on the checked out sources and produces results (typically in the UI but CVS will be possible as well). Your plugin then can access the files in the workspace and run tests. -- 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/F99BBC2E-A587-4DE0-8246-9295165E85B9%40gmail.com.
