Actions
Architecture #2192
closedMake cobertura, jenkins and Maven 3 work together
Added by François ARMAND over 12 years ago. Updated about 12 years ago.
Status:
Released
Priority:
1
Assignee:
Category:
Architecture - Dependencies
Target version:
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
Description
They don't seems to want to for now: coverage.xml are not generated anymore.
Updated by Jonathan CLARKE over 12 years ago
- Subject changed from Make cobertura, jenkins and Maven work together to Make cobertura, jenkins and Maven 3 work together
- Description updated (diff)
Updated by Jonathan CLARKE over 12 years ago
- Category set to Architecture - Dependencies
Updated by Jonathan CLARKE about 12 years ago
- Assignee set to François ARMAND
- Priority changed from N/A to 1
- Target version changed from 24 to 46
I just tested again, and Jenkins gives us this:
[INFO] --- cobertura-maven-plugin:2.5.1:instrument (default-cli) @ commons-parent --- [INFO] Skipping cobertura mojo for project with packaging type 'pom' [INFO] [INFO] --- scala-maven-plugin:3.0.2:testCompile (scala-test-compile) @ commons-parent --- [INFO] Checking for multiple versions of scala [WARNING] Expected all dependencies to require Scala version: 2.9.2 [WARNING] com.normation:commons-parent:2.5.0-20120531.221903-18 requires scala version: 2.9.2 [WARNING] net.liftweb:lift-common_2.9.1:2.4 requires scala version: 2.9.1 [WARNING] Multiple versions of scala libraries detected! [INFO] includes = [**/*.scala,**/*.java,] [INFO] excludes = [] [WARNING] No source files found. [INFO] [INFO] <<< cobertura-maven-plugin:2.5.1:cobertura (default-cli) @ commons-parent <<< [INFO] [INFO] --- cobertura-maven-plugin:2.5.1:cobertura (default-cli) @ commons-parent --- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] spring-run-dependencies ........................... SUCCESS [8.063s] [INFO] utils ............................................. SUCCESS [40.835s] [INFO] authorization-api ................................. SUCCESS [7.093s] [INFO] eventlog-api ...................................... SUCCESS [22.401s] [INFO] historization-api ................................. SUCCESS [27.914s] [INFO] commons-parent .................................... SUCCESS [0.463s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:57.873s [INFO] Finished at: Fri Jun 01 00:19:04 CEST 2012 [INFO] Final Memory: 15M/143M [INFO] ------------------------------------------------------------------------ Publishing Cobertura coverage report... No coverage results were found using the pattern '**/target/site/cobertura/coverage.xml' relative to '/var/lib/jenkins/jobs/rudder-commons-2.5-branch/workspace'. Did you enter a pattern relative to the correct directory? Did you generate the XML report(s) for Cobertura? Build step 'Publish Cobertura Coverage Report' changed build result to FAILURE IRC notifier plugin: Sending notification to: #rudder-dev Sending e-mails to: developpeurs@lists.normation.com Finished: FAILURE
Updated by Jonathan CLARKE about 12 years ago
By the way, our Jenkins uses Maven 3.0.4. We can try a more recent version if necessary?
Updated by François ARMAND about 12 years ago
- Status changed from New to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 7e5dc2df815be99050d91a81e8cde0629d5edd4a.
Updated by Nicolas CHARLES about 12 years ago
- Status changed from Pending technical review to 10
This looks valid, thank you Francois
Updated by Jonathan CLARKE about 12 years ago
- Tracker changed from User story to Architecture
- Status changed from 10 to Released
This is clearly not a user story!
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 46 to 50
Updated by Jonathan CLARKE about 12 years ago
- Target version changed from 50 to 2.4.0~beta3
Actions