Skip to content

Common parser functionality for static code analysis tools on continuous integration servers to read reports and send the data to Artemis

License

Notifications You must be signed in to change notification settings

ls1intum/static-code-analysis-parser

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

49 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

static-code-analysis-parser

Common parser functionality for static code analysis tools on continuous integration servers to read reports and send the data to Artemis

Deployment

  1. Make sure you have a Sonatype JIRA account. Store the credentials in the settings.xml in the m2 home folder

  2. Make sure you have a valid GPG certificate (follow the instructions on https://central.sonatype.org/publish/requirements/gpg)

  3. Store the used key in your Maven settings.xml file, usually placed in ~/.m2: https://central.sonatype.org/publish/publish-maven

  4. Run export GPG_TTY=$(tty)

  5. Run mvn clean deploy -P release
    This should create the jar file, sources, javadoc and the pom file. All files should also have an additional signed *.asc file. You might find the files in your m2 home folder.

  6. Verify the artifact and release it to Maven Central:

    1. Open https://oss.sonatype.org/#stagingRepositories, close the repository to start the validation
    2. As soon as the validation has finished successfully, release the artifact.
    3. After some time, the new release should be available on https://search.maven.org/artifact/de.tum.in.ase/static-code-analysis-parser
    4. You can also check https://packages.atlassian.com/maven-external/de/tum/in/ase/static-code-analysis-parser

About

Common parser functionality for static code analysis tools on continuous integration servers to read reports and send the data to Artemis

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages