|Re: [hudson-dev] New Hudson-on-Hudson|
Henrik,I fixed the cyclic dependency resolution issue in Rest, maven2 and maven3 plugin in v2 also. Now they should build fine. If you see any issue let me know.
- WInston On 2/7/12 2:06 PM, Henrik Lynggaard Hansen wrote:
2012/2/7 Winston Prakash<winston.prakash@xxxxxxxxx>:On 2/6/12 1:37 PM, Henrik Lynggaard Hansen wrote:The missing bits are: * Dimensions SCM plugin: It appears it depends on a local file repository which I naturally dont have (This job does not exist on the current HonH) * LiveRebel Deploy: Running into the "Nothing to do" git error.Don't know why this fails.It is a know hudson bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=363607 I am seeing a variant of that bug, where clearing the workspace is not enough* Hudson 2 Core: It has a dependency on org.jvnet.hudson.main:rest-plugin:hpi:2.2.0-SNAPSHOT. We need to fix that so we either agree on how to deal with snapshots or point to a released version. * Hudson 2 REST support: appears to depend on core versions (Do we have a nasty circular reference?) [ERROR] Failed to execute goal on project hudson-rest: Could not resolve dependencies for project org.jvnet.hudson.main:hudson-rest:pom:2.2.0-SNAPSHOT: The following artifacts could not be resolved: org.jvnet.hudson.main:hudson-inject:jar:2.2.0-SNAPSHOT, org.jvnet.hudson.main:hudson-service:jar:2.2.0-SNAPSHOT, org.jvnet.hudson.main:hudson-test-utils:jar:2.2.0-SNAPSHOT: Could not find artifact org.jvnet.hudson.main:hudson-inject:jar:2.2.0-SNAPSHOT in hudson.snapshots (https://oss.sonatype.org/content/repositories/snapshots/) -> [Help 1] * Hudson 2 REST client: Depends on REST support 2.2.0-SNAPSHOTS * Hudson 3 REST ciient: Depends on Hudson 3.0.0-SNAPSHOT parentWe extracted out REST plugin and Maven plugin in 2.2.0. So with that release circular dependency was expected. Now the parents of these plugins can be modified to the released version. However, I still found issues with SNAPSHOT versions, from second level dependency tree. I fixed this issue in v3.Ok* Eclipse: Packaging: Untested, don't know what to runPackaging is for creating Linux distribution, so nothing to buildWell, I would still like this job to run and create the distributions so that we can verify the process to be working. It will hopefully encourage someone to create more distribution packages (sidenote: it blows my mind that the jenkins variant has solaris packages, but Oracle backed Hudson don't)In order to load the jobs I need the following * My account transferred to the new instanceThe new instance is still not ready. I'll let you know when it is ready.I know, just stating the obvious, for the sake of other reader and completeness* Ability for the Hudson CLI tool to hit the hudson instance (from outside oracle net)Hmm.. need to veirfy. Not sure if the port is open. Someday, I want to write Hudson CLI based on REST API, to avoid such port problems.since I only give it the web url for Hudson I thought it just used the normal web ports ? I have tried to run the jobcreator against the existing Hudson-on-Hudson, and it works fine. I just loaded hudson-plugins_blacklist as a test. So if the same security/firewall settings are used for the new instance I don't see a problem Best regards Henrik
Back to the top