Ah, I don't even see that option (or the rest of the Build Environment section). In the past, we sometimes set up Jenkins jobs as 'freestyle' for various reasons instead of officially as a maven job, then just invoked maven externally as a command-line call
I tried setting up the same project as a maven 2/3 job and now the plugin resolution works fine for it. And the Build Environment section shows up. It seems odd that the freestyle Jenkins job would have this trouble with plugins, but I don't care enough to investigate further. Just setting the job up initially as maven is a good enough solution. Thanks. -- View this message in context: http://forums.jfrog.org/Plugin-repositories-not-found-tp6450926p6458293.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
