Unverified Commit e8701c00 authored by Hilmar Falkenberg's avatar Hilmar Falkenberg Committed by GitHub
Browse files

cleanup old build descriptors (#1014)

in case of reactivation, just pick them from latest main branch
parent cad02071
version: 2.1
jobs:
build:
working_directory: ~/cwa-server
machine:
image: ubuntu-1604:202004-01
docker_layer_caching: true
steps:
- checkout
- run:
name: Update to OpenJDK 11
command: |
sudo apt-get install openjdk-11-jre
sudo update-alternatives --set java /usr/lib/jvm/java-11-openjdk-amd64/bin/java
java -version
- run:
name: Generate cumulative pom.xml checksum
command: |
find . -type f -name "pom.xml" -exec sh -c "sha256sum {} >> ~/pom-checksum.tmp" \;
sort -o ~/pom-checksum ~/pom-checksum.tmp
when: always
- restore_cache:
key: cwa-server-{{ checksum "~/pom-checksum" }}
- run: ./mvnw --batch-mode dependency:go-offline
- run:
name: Analyze on SonarCloud
command: |
export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64
./mvnw --batch-mode verify sonar:sonar --fail-never
- save_cache:
paths:
- ~/.m2
key: cwa-server-{{ checksum "~/pom-checksum" }}
- run:
name: Run all tests on Docker
command: |
docker-compose -f docker-compose-it.yaml up -d objectstore
docker-compose -f docker-compose-it.yaml up -d create-bucket
docker-compose -f docker-compose-it.yaml run run-tests
- run:
name: Save test results
command: |
mkdir -p ~/test-results/junit/
find . -type f -regex ".*/target/surefire-reports/.*xml" -exec cp {} ~/test-results/junit/ \;
when: always
- store_test_results:
path: ~/test-results
- store_artifacts:
path: ~/test-results/junit
workflows:
main:
jobs:
- build:
context: SonarCloud
---
name: "\U0001F6A8 Bug Report"
about: Did you come across a bug or unexpected behaviour differing from the docs?
labels: bug
---
<!--
Thanks for reporting a bug 🙌 ❤️
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
Also, be sure to check our documentation first: <URL>
-->
## Describe the bug
<!-- Describe your issue, but please be descriptive! Thanks again 🙌 ❤️ -->
## Expected behaviour
<!-- A clear and concise description of what you expected to happen. -->
## Steps to reproduce the issue
<!-- include screenshots, logs, code or other info to help explain your problem -->
<!--
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
-->
## Technical details
- Host Machine OS (Windows/Linux/Mac):
## Possible Fix
<!--- Not obligatory, but suggest a fix or reason for the bug -->
## Additional context
<!-- Add any other context about the problem here. -->
---
name: "\U0001F381 Feature Request"
about: Do you have an idea for a new feature?
labels: feature request
---
<!--
Thanks for requesting a feature 🙌 ❤️
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
-->
## Feature description
<!---
Provide a detailed description of the feature or improvement you are proposing. What specific solution would you like? What is the expected behaviour?
Add any other context, screenshots, or code snippets about the feature request here as well.
-->
## Problem and motivation
<!---
Why is this change important to you? What is the problem this feature would solve? How would you use it? How can it benefit other users?
-->
## Is this something you're interested in working on
<!--- Yes or No -->
---
name: "\u23F1\uFE0F Enhancement Request"
about: Do you have an idea for an enhancement?
labels: enhancement
---
<!--
Thanks for proposing an enhancement 🙌 ❤️
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
-->
## Current Implementation
<!-- Describe or point to the current implementation that you would like to see improved -->
## Suggested Enhancement
<!-- Outline the idea of your enhancement, by e.g., describing the algorithm you propose. You can also create a Pull Request to outline your idea -->
## Expected Benefits
<!-- Summarize how your enhancement could aid the implementation (performance, readability, memory consumption, battery consumption, etc.). Please also back up with measurements or give detailed explanations for reduced runtimes, memory consumption, etc. -->
---
name: "\U00002753 Questions?"
about: If you have *specific* questions about pieces of the code or documentation for this component, please post them here.
labels: question
---
<!--
Thanks for submitting your question 🙌 ❤️
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. Also, please, have a look at our FAQs and existing questions before opening a new question.
-->
## Your Question
<!-- Include details about your question. -->
* Source File:
* Line(s):
* Question:
---
name: "\U0001F4AC Anything else?"
about: For conceptual questions, please consider to open an issue in the documentation repository.
---
<!--
Thanks for contributing to the project 🙌 ❤️
Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
Also, be sure to check our readme first: https://github.com/corona-warn-app/cwa-server
-->
## Support and Feedback
The following channels are available for discussions, feedback, and support requests:
| Type | Channel |
| ------------------------ | ------------------------------------------------------ |
| **General Discussion** | <a href="https://github.com/corona-warn-app/cwa-documentation/issues/new/choose" title="General Discussion"><img src="https://img.shields.io/github/issues/corona-warn-app/cwa-documentation/question.svg?style=flat-square"></a> </a> |
| **Concept Feedback** | <a href="https://github.com/corona-warn-app/cwa-documentation/issues/new/choose" title="Open Concept Feedback"><img src="https://img.shields.io/github/issues/corona-warn-app/cwa-documentation/architecture.svg?style=flat-square"></a> |
| **Backend Issue** | <a href="https://github.com/corona-warn-app/cwa-server/issues/new/choose" title="Open Backend Issue"><img src="https://img.shields.io/github/issues/corona-warn-app/cwa-server?style=flat-square"></a> |
| **Other Requests** | <a href="mailto:corona-warn-app.opensource@sap.com" title="Email CWD Team"><img src="https://img.shields.io/badge/email-CWD%20team-green?logo=mail.ru&style=flat-square&logoColor=white"></a> |
## Documentation
The full documentation for the Corona-Warn-App can be found in the [cwa-documentation](https://github.com/corona-warn-app/cwa-documentation) repository. The documentation repository contains technical documents, architecture information, and whitepapers related to this implementation.
\ No newline at end of file
<!--
Thank you for supporting us with your Pull Request! 🙌 ❤️
Before submitting, please take the time to check the points below and provide some descriptive information.
* [ ] If this PR comes from a fork, please [Allow edits from maintainers](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
* [ ] Set a meaningful title. Format: {task_name} (closes #{issue_number}). For example: Use logger (closes #41)
* [ ] [Link your Pull Request to an issue](https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) (if applicable)
* [ ] Create Work In Progress [WIP] pull requests only if you need clarification or an explicit review before you can continue your work item.
* [ ] Make sure that your PR is not introducing _unncessary_ reformatting (e.g., introduced by on-save hooks in your IDE)
* [ ] Make sure each new `.java` source file you add has a correct license header.
-->
## Checklist
* [ ] Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
* [ ] Make sure `mvn install` runs for the whole project and, if you touched any code in the respective service, submission and distribution service can be run with `spring-boot:run`
## Description
<!-- Please be brief in describing which issue is solved by your PR or which enhancement it brings -->
name: "Code scanning - action"
on:
push:
branches:
- master
jobs:
CodeQL-Build:
strategy:
fail-fast: false
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v2
# Initializes the CodeQL tools for scanning.
- name: Initialize CodeQL
uses: github/codeql-action/init@v1
with:
languages: java
- name: Java Setup
uses: actions/setup-java@v1
with:
java-version: 11
- name: Build
run: ./mvnw --batch-mode clean compile
- name: Perform CodeQL Analysis
uses: github/codeql-action/analyze@v1
name: "Dockerfile-Linting"
on:
pull_request:
branches:
- master
paths:
- '**/Dockerfile'
jobs:
distribution:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Pull HaDoLint image
run: docker pull hadolint/hadolint
- name: Lint Dockerfile
run: docker run --rm --interactive hadolint/hadolint < ./services/distribution/Dockerfile
submission:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- name: Pull HaDoLint Image
run: docker pull hadolint/hadolint
- name: Lint Dockerfile
run: docker run --rm --interactive hadolint/hadolint < ./services/submission/Dockerfile
name: "CI"
on:
pull_request:
branches:
- master
jobs:
fileheader:
runs-on: ubuntu-latest
name: 'license file header'
steps:
- uses: actions/checkout@v2
- name: Java Setup
uses: actions/setup-java@v1
with:
java-version: 11
- name: Verify License File Headers
run: mvn --batch-mode clean license:check-file-header -Dlicense.failOnMissingHeader=true -Dlicense.failOnNotUptodateHeader=true
name: "ci"
on:
pull_request:
branches:
- master
paths:
- '**/*.md'
jobs:
markdownlint:
runs-on: ubuntu-latest
name: 'github actions: markdownlint'
steps:
- uses: actions/checkout@v2
- name: markdownlint
uses: nosborn/github-action-markdown-cli@v1.1.1
with:
files: .
config_file: ./codestyle/.markdownlint.yml
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment