I'm still trying to figure out why the Jenkins Artifactory plugin is broken,
and I'm trying to walk through the plugin architecture. The problem is I
reach this point in the Groovy console:
p = Jenkins.getInstance().getPlugin("artifactory");
xml = p.getConfigXml();
xml.asString();
And that gives me:
java.io.FileNotFoundException: /var/lib/jenkins/artifactory.xml (No such
file or directory)
... and there's also the oddity of the Artifactory Plugin itself, which is:
/**
* Used only as a placeholder for the release permissions.
*
* @author Yossi Shaul
*/
public class ArtifactoryPlugin extends Plugin {
private static final PermissionGroup GROUP =
new PermissionGroup(ArtifactoryPlugin.class,
Messages._permission_group());
public static final Permission RELEASE = new Permission(GROUP,
"Release",
Messages._permission_release(), Hudson.ADMINISTER,
PermissionScope.JENKINS);
public static final Permission PROMOTE = new Permission(GROUP,
"Promote",
Messages._permission_promote(), Hudson.ADMINISTER,
PermissionScope.JENKINS);
}
... so apparently the ArtifactoryPlugin is doing some really strange things
within the Jenkins system. What's going on? How does any code in the plugin
actually get run?
-- Chris
--
View this message in context:
http://forums.jfrog.org/Why-is-the-Artifactory-plugin-written-so-strangely-tp7579681.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
