Hudson logo

Jobs Status

All
 Dashboard 
   S   WJobLast SuccessLast FailureLast DurationConsole  
Success33%
WDescription%
Build stability: 2 out of the last 3 builds failed.33
deploy-individual-bundles
Description
This job deploys individual bundles to Nexus outside a Kura release.
4 mo 26 days (#3) 4 mo 26 days (#2) 4 min 54 secConsole output 
Failed0%
WDescription%
Build stability: All recent builds failed.0
Test Result: 0 tests failing out of a total of 1,122 tests.100
Coverage: All coverage targets have been met. 100
kura-develop 27 days (#1131) 5 days 0 hr (#1159) 46 minConsole output 
Success100%
WDescription%
Build stability: No recent builds failed.100
kura-develop-deploy-from-archived-workspace
Description
(Attempt to) Deploy Maven artifacts to Eclipse Nexus from the archived workspace of the last successful release candidate build.
Even this simple task is not that simple.

Apparently Maven is not able to just deploy what was already built [1].
"mvn jar:jar deploy:deploy" seems to work for all the projects but "web2" deploys an artifact which is smaller than normal.
The link above explains that this does not always work (multimodule projects, different packaging types) so we will not use it (but it would be very fast).

The only alternative is "mvn delpoy -Dmaven.test.skip=true" but Maven will execute the earlier phases too so we will not deploy the exact same binaries from the RC build :-(.
Also we have this stupid Hudson Clone Workspace SCM Plug-in bug [2] but there's a workaround [3].

The flow is thus less than ideal and we should consider a cleaner approach.

Classes are typically not recompiled except the following (why???)
[INFO] ------------------------------------------------------------------------
[INFO] Building Java API for working with Human Interface USB Devices (HID) 1.1.100-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ com.codeminders.hidapi ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 7 source files to /jobs/genie.kura/kura-develop-deploy-from-archived-workspace/workspace/target-platform/com.codeminders.hidapi-parent/com.codeminders.hidapi/target/classes

[INFO] ------------------------------------------------------------------------
[INFO] Building Serial Device based on SODA DK comm 1.2.100-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ org.eclipse.soda.dk.comm ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 26 source files to /jobs/genie.kura/kura-develop-deploy-from-archived-workspace/workspace/target-platform/org.eclipse.soda.dk.comm-parent/org.eclipse.soda.dk.comm/target/classes

[INFO] ------------------------------------------------------------------------
[INFO] Building org.eclipse.kura.web2 2.0.100-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- tycho-compiler-plugin:0.26.0:compile (default-compile) @ org.eclipse.kura.web2 ---
[INFO] Compiling 2 source files to /jobs/genie.kura/kura-develop-deploy-from-archived-workspace/workspace/kura/org.eclipse.kura.web2/target/classes

web2 javascripts would be recompiled:

[INFO] --- tycho-compiler-plugin:0.26.0:compile (default-compile) @ org.eclipse.kura.web2 ---
[INFO] Compiling 2 source files to /home/cristiano/dev/git/cdealti/kura/kura/org.eclipse.kura.web2/target/classes

and the all javascript is generated:
[INFO] --- gwt-maven-plugin:2.7.0:compile (default) @ org.eclipse.kura.web2 ---
[INFO] auto discovered modules [org.eclipse.kura.web.denali]
[INFO] Compiling module org.eclipse.kura.web.denali
[INFO] Compiling 10 permutations
...
but this can be disabled with -Dgwt.compiler.skip=true

References
[1] http://stackoverflow.com/questions/6308162/maven-the-packaging-for-this-project-did-not-assign-a-file-to-the-build-artifac
[2] http://stackoverflow.com/questions/35014569/jenkins-clone-workspace-plugin-does-not-clone-git-directory
[3] https://jowisoftware.de/wp/2012/03/building-a-simple-jenkins-pipeline/
3 mo 19 days (#13) 3 mo 19 days (#8) 5 min 8 secConsole output 
Unstable0%
WDescription%
Test Result: 2 tests failing out of a total of 2 tests.0
Build stability: 3 out of the last 5 builds failed.40
kura-develop-test 1 yr 11 mo (#80) 1 yr 11 mo (#79) 5 min 50 secConsole output 
Aborted100%kura-develop-test-archive-workspace
Description
Temporary job to test workspace archival through Hudson Clone SCM Workspace Plugin.
It should support the flow of deploying the build artifacts to Nexus from another job after the release QA is complete.
It does not seem to be an uncommon requirement but the simple task of just deploying what has already been built and installed is not straightforward (early phases will be run).
Cruel world!
N/AN/AN/AConsole output 
Success40%
WDescription%
Build stability: 3 out of the last 5 builds failed.40
kura-milestone
Description
This build creates milestone release based on a specific tag.
7 days 3 hr (#7) 5 mo 15 days (#5) 18 minConsole output 
Success100%
WDescription%
Build stability: No recent builds failed.100
kura-pub-downloads
Description
Job to publish artifacts to the Eclipse download server.
3 mo 6 days (#5) N/A7.5 secConsole output 
Failed20%
WDescription%
Build stability: 4 out of the last 5 builds failed.20
kura-release 7 mo 26 days (#48) 3 mo 6 days (#51) 12 minConsole output 
Success100%
WDescription%
Test Result: 0 tests failing out of a total of 688 tests.100
Coverage: All coverage targets have been met. 100
Build stability: No recent builds failed.100
kura-release-candidate
Description
This job builds a Kura release candidate from a release-x.y.z branch.
WARNING: The Maven build artifacts (jars) MUST NOT be deployed to any Eclipse repository; Only the Kura installers are needed.
The build must be manually started.
3 mo 7 days (#31) N/A37 minConsole output 
Pending100%kura-release-candidate-deploy-from-archived-workspace
Description
(Attempt to) Deploy Maven artifacts to Eclipse Nexus from the archived workspace of the last successful release candidate build.
Even this simple task is not that simple.

Apparently Maven is not able to just deploy what was already built [1].
"mvn jar:jar deploy:deploy" seems to work for all the projects but "web2" deploys an artifact which is smaller than normal.
The link above explains that this does not always work (multimodule projects, different packaging types) so we will not use it (but it would be very fast).

The only alternative is "mvn delpoy -Dmaven.test.skip=true" but Maven will execute the earlier phases too so we will not deploy the exact same binaries from the RC build :-(.
Also we have this stupid Hudson Clone Workspace SCM Plug-in bug [2] but there's a workaround [3].

The flow is thus less than ideal and we should consider a cleaner approach.

Classes are typically not recompiled except the following (why???)
[INFO] ------------------------------------------------------------------------
[INFO] Building Java API for working with Human Interface USB Devices (HID) 1.1.100-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ com.codeminders.hidapi ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 7 source files to /jobs/genie.kura/kura-develop-deploy-from-archived-workspace/workspace/target-platform/com.codeminders.hidapi-parent/com.codeminders.hidapi/target/classes

[INFO] ------------------------------------------------------------------------
[INFO] Building Serial Device based on SODA DK comm 1.2.100-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ org.eclipse.soda.dk.comm ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 26 source files to /jobs/genie.kura/kura-develop-deploy-from-archived-workspace/workspace/target-platform/org.eclipse.soda.dk.comm-parent/org.eclipse.soda.dk.comm/target/classes

[INFO] ------------------------------------------------------------------------
[INFO] Building org.eclipse.kura.web2 2.0.100-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- tycho-compiler-plugin:0.26.0:compile (default-compile) @ org.eclipse.kura.web2 ---
[INFO] Compiling 2 source files to /jobs/genie.kura/kura-develop-deploy-from-archived-workspace/workspace/kura/org.eclipse.kura.web2/target/classes

web2 javascripts would be recompiled:

[INFO] --- tycho-compiler-plugin:0.26.0:compile (default-compile) @ org.eclipse.kura.web2 ---
[INFO] Compiling 2 source files to /home/cristiano/dev/git/cdealti/kura/kura/org.eclipse.kura.web2/target/classes

and the all javascript is generated:
[INFO] --- gwt-maven-plugin:2.7.0:compile (default) @ org.eclipse.kura.web2 ---
[INFO] auto discovered modules [org.eclipse.kura.web.denali]
[INFO] Compiling module org.eclipse.kura.web.denali
[INFO] Compiling 10 permutations
...
but this can be disabled with -Dgwt.compiler.skip=true

References
[1] http://stackoverflow.com/questions/6308162/maven-the-packaging-for-this-project-did-not-assign-a-file-to-the-build-artifac
[2] http://stackoverflow.com/questions/35014569/jenkins-clone-workspace-plugin-does-not-clone-git-directory
[3] https://jowisoftware.de/wp/2012/03/building-a-simple-jenkins-pipeline/
N/AN/AN/AN/A 
Icon:  S M L

Powered by Hudson Open Source Continuous Integration Server from the Eclipse Foundation