[Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[fkp...@gmail.com]

Hi,
tried to compile the project to start testing related plugins on the project ui.
related tool versions:

1. maven 3.3.9
2. jenkins 2.8 (latest release) - tried also with stable lts 1.651.2 (same problems).

attaching the build log after several retries, I read the past thread on win 7 issues but it seems as a different problem.

Thanks ahead,

Yafim.

[fkp...@gmail.com]

concrete errors output with -e -X flags

[ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:test-hpl (default-test-hpl) on project blueocean: Error preparing the manifest: Failed to open artifact org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar: 1 problem was encountered while building the effective model for org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
[ERROR] [FATAL] Non-parseable POM C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom: end tag name </head> must be the same as start tag <meta> from line 4 (position: TEXT seen ...</title>\n  </head>... @66:10)  @ C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom, line 66, column 10
[ERROR] for project org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version] for project org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:test-hpl (default-test-hpl) on project blueocean: Error preparing the manifest: Failed to open artifact org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error preparing the manifest: Failed to open artifact org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
    at org.jenkinsci.maven.plugins.hpi.HplMojo.execute(HplMojo.java:108)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
    ... 20 more
Caused by: org.kohsuke.stapler.framework.io.IOException2: Failed to open artifact org.jenkins-ci.plugins.workflow:workflow-scm-step:jar:1.15:compile at C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\workflow\workflow-scm-step\1.15\workflow-scm-step-1.15.jar
    at org.jenkinsci.maven.plugins.hpi.MavenArtifact.getResolvedType(MavenArtifact.java:172)
    at org.jenkinsci.maven.plugins.hpi.MavenArtifact.isPlugin(MavenArtifact.java:55)
    at org.jenkinsci.maven.plugins.hpi.HplMojo.buildLibraries(HplMojo.java:128)
    at org.jenkinsci.maven.plugins.hpi.HplMojo.execute(HplMojo.java:96)
    ... 22 more
Caused by: org.apache.maven.project.InvalidProjectModelException: 1 problem was encountered while building the effective model for org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
[FATAL] Non-parseable POM C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom: end tag name </head> must be the same as start tag <meta> from line 4 (position: TEXT seen ...</title>\n  </head>... @66:10)  @ C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom, line 66, column 10
 for project org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version] for project org.jenkins-ci.plugins.workflow:workflow-scm-step:[unknown-version]
    at org.apache.maven.project.DefaultMavenProjectBuilder.transformError(DefaultMavenProjectBuilder.java:193)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:240)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
    at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:258)
    at org.jenkinsci.maven.plugins.hpi.MavenArtifact.resolvePom(MavenArtifact.java:48)
    at org.jenkinsci.maven.plugins.hpi.MavenArtifact.getResolvedType(MavenArtifact.java:170)
    ... 25 more
[ERROR]

[Cliff Meyers]

Hi,

I am not 100% sure at the root issue but can you check the contents of the following file?  C:\Users\kazaky\.m2\repository\org\jenkins-ci\plugins\plugin\2.2\plugin-2.2.pom

From the parser error the file appears to be an HTML document but should be a fairly long XML file. There may have been an issue downloading that file from the repo. Perhaps the contents will offer a clue.

Also, do you have any special repo config in your ~/.m2/settings.xml file?

-Cliff

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/91ffba03-cce6-4c05-afc7-807fbcbf0b2e%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[fkp...@gmail.com]

Hi,
Thanks for the speedy reply.

It is an html file stating that i should check my proxy settings which are defined in the .m2/settings.xml.
I'm trying to reimport it currently as i checked the connection to the proxy and it should be fine (otherwise all the other dependencies won't be downloaded as well - i guess).

[fkp...@gmail.com]

Finally succeed installing it on the machine after reinstalling with jenkins 2.8.
But couldn't use mvn run:hpi - >> installed all the plugins manually from the folder with upload and then ran it. and it works =)
Now the (great) ui works - but when i press new pipeline - it takes me to the old screen - is it ok?

Starting to check compatability between our plugin to the new UI - any suggestions as where should i start the conversion? and how?

 

On Friday, June 10, 2016 at 6:44:30 PM UTC+3, fkp...@gmail.com wrote:

[Tom Fennelly]

Hi there.

The Blue Ocean plugins are not yet in the Update center, so installing it in a Jenkins instance is a bit tricky atm Vs running hpi:run from source.

As for your plugin ... maybe start a new thread about that, giving some details of the plugin etc.

[Michael Neale]

Hey - that's cool!

There is no "create pipeline" feature yet in blue ocean, hence it takes you to the classic UI. 

For building plugins, https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin is a sample plugin that you can look at. 

What is the plugin you are interested? many plugins will need to have the right extension point added in blue ocean which may not already be there. 

[fkp...@gmail.com]

Thanks - but i'm still having strange difficulties runningthe plugin similar to the Win 7 issues that were discussed previously.

i'm adding my screen logs - after several retries to reinstall the plugin (is it fit to run behind a corporate proxy? maybe that's the cause to all the problems) - and now it simply won't run.

be glad for any help.

[Michael Neale]

You said you had it working previously? 

[fkp...@gmail.com]

Very partly by installing HPI's manually - but only some of the functionalities worked (but without any errors)

[Tom Fennelly]

As said earlier .... you will have a job if you are not running via hpi:run. You will need to gather and install more than just the blueocean plugins.

You could use "mvn hpi:assemble-dependencies" to pull together all of the plugins you need. You'd need to run this inside blueocean-plugin/blueocean-plugin.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/1A82YO-Ta2w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d05496c8-f66b-42e1-acb7-42790dbddf71%40googlegroups.com.

[fkp...@gmail.com]

Thanks! that worked. although i still can't simply press run on my pipeline in order to run  - and i have to go to the old interface to do it.
I'm having some kind of exception on symbolic link - could that be the issue?

[James Dumay]

Running pipelines hasn't been implemented yet but someone (Ivan) is working on it :)

It was waiting on some new JDL and rest component work but thats been done. See JENKINS-35813

[Fima]

Thanks!

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ec36d3fc-eba3-4d63-b15a-aa5b2c43c762%40googlegroups.com.