All plugins that work in Hudson a)Work in Jenkins b)Do not work in Jenkins c)May or may not work in Jenkins d)None of the above
Question
All plugins that work in Hudson
a)Work in Jenkins
b)Do not work in Jenkins
c)May or may not work in Jenkins
d)None of the above
Solution
c) May or may not work in Jenkins
Explanation: Hudson is a continuous integration tool, which was later forked to create Jenkins when the development team had issues with Oracle. While Jenkins is a fork of Hudson, meaning it was built upon the Hudson code base, it has since evolved and added more features and fixes. Therefore, while many plugins that work in Hudson also work in Jenkins, this is not always the case. Some may have compatibility issues or may have been replaced by newer plugins in Jenkins. So, the correct answer is that plugins that work in Hudson may or may not work in Jenkins.
Similar Questions
Which statement is true about Jenkins plugins?They are not supported in Jenkins.They are used to integrate Jenkins with various tools and technologies.They are only used for monitoring and reporting.They are only used for distributed builds.
)Jenkins native package installations run as by default [15] recheck need to verify a)Localsystem b)Jenkins c)Id of user who installed d)None of the above
Native packages installations install Jenkins as[9] need to verify need to recheck a)Automatic services b)Manual services c)Do not any service installation d)None of the above
The default context for Jenkins running as a war under tomcat is a)Jenkins b)/ c)/Jenkins d)None of the above
The default port on which Jenkins starts is [22] recheck a)8080 b)80 c)9080 d)None of the above
Upgrade your grade with Knowee
Get personalized homework help. Review tough concepts in more detail, or go deeper into your topic by exploring other relevant questions.