Again: No offense - BUT ...

If your "use model" is to use Jenkins interactively, and believe that this is the intended way to use Jenkins then you must have got it wrong.

JENKINS IS ALL ABOUT USING IT AS A SERVICE.

Jenkins is supposed to run on some (if you want to put it this way) "background server", doing tasks like

  • building software in an automated way
  • running unit tests, code coverage and stylecheck test
    additionally it can
  • deploy the build results to testing environments
  • trigger tests of the deployed software remotely
  • collect the test results
  • display them as report on the jobs dashboard page
    etc.

And it's supposed to do all this with NO INTERACTION required!

If you don't get this concept - and do not accept that this is the main usage of Jenkins - then you are definitely on a wrong path !

Sorry ...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to