Skip to content

Connect i-Code build to SonarCloud #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
begarco opened this issue Aug 1, 2018 · 0 comments · Fixed by #190 or #191
Closed

Connect i-Code build to SonarCloud #145

begarco opened this issue Aug 1, 2018 · 0 comments · Fixed by #190 or #191
Labels
enhancement
Milestone
Version 4.0.0

Comments

@begarco
Copy link
Contributor

begarco commented Aug 1, 2018

Expected behavior

At each build, i-Code should be analyzed by SonarCloud.

Actual behavior

There is no analysis.

Steps to reproduce behavior

See build log.

Detection version

3.0.1
@begarco begarco mentioned this issue Aug 1, 2018
Merged
@begarco begarco added this to the Version 4.0.0 milestone Sep 17, 2019
begarco added a commit that referenced this issue Sep 17, 2019
@begarco
[#145] Add coverage with jacoco
d40851c
@begarco begarco mentioned this issue Feb 9, 2020
Merged
begarco added a commit that referenced this issue Feb 10, 2020
@begarco
Dev 4.0.0 (#189)
7e8a14a 
* Refactoring for i-Code 4 (#164)

* start of refactoring to remove rcp from command line and core analyzer

* Second step

* All languages are built

* Fix export string problem and add new supported features

* All rules integrated.

* Finalized command line version.
- three languages supported
- plugin system available
- packaging on build available
- directory as argument available
- deletion of parallel analysis

* Add version information to command line

* Add parametrized unit tests

* Update .travis.yml

* fix encoding issues, prepare new packagings and clean up repository

* update pom to fix issues and deploy library

* fix shell-rules pom

* minor changes

* Refactoring

* Add functional icode-ide working with a icode-libray jar put in icode-library-plugin // Refactor code // Add some license headers

* RCP versions are reintegrated as icode-ide

* Update CI (deploy and jdk) + start new readme

* Update .travis.yml

* Change to icode 4 + README

* Change README

* Update README.md

* Fix compatibility with JRE>8 && update CI

* deploy only on build on jdk11

* Remove build on jdk8

* [#166] Fix #166 by adding heredoc support to metrics

* [#166] Fix #166 by adding heredoc support to metrics

* [#166] Fix #166 by adding here string support to shell metrics

* [#145] Add coverage with jacoco

* [#142] Add i-Code version in xml reports

* Fix #168: support of for with double parentheses

* Fix #158 Remove 'read' from active wait functions

* #187 Complete contributing requirements

* #187 Fix layout

* #187 fix plan

* #187 Add issue templates

* #187 add a template with checklist for PR

* Delete PULL_REQUEST_TEMPLATE.md

Move template into .github folder

* Delete ISSUE_TEMPLATE.md

Move template into .github

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

* #165 add execution rights for icode-app scripts

* #158 fix tests

* #165 Update README to match the new structure

* Update .travis.yml

* Update .travis.yml

* Update .travis.yml

* Update README.md

* Add coverage for SonarQube

* Use Junit Jupiter 5 to run tests

* Convert test to JUnit 5 tests with generalisation of chercker tests

* add sonar-project.properties
@begarco begarco mentioned this issue Feb 10, 2020
Merged
@begarco begarco mentioned this issue Feb 10, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
Version 4.0.0
Development

Successfully merging a pull request may close this issue.

Version 4.0.0 cnescatlab/i-CodeCNES
Dev 4.0.0 cnescatlab/i-CodeCNES
1 participant
@begarco