Skip to content

Commit

Permalink
Initial version
Browse files Browse the repository at this point in the history
  • Loading branch information
alexanderpann committed Sep 10, 2024
1 parent 10bf5bf commit e76acf6
Show file tree
Hide file tree
Showing 43 changed files with 11,543 additions and 2 deletions.
11 changes: 11 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
*.mps merge=mps
trace.info merge=mps
.dependencies merge=mps
dependencies merge=mps
generated merge=mps
*.mpl merge=mps
*.msd merge=mps
*.devkit merge=mps
*.mpr merge=mps
*.mpsr text merge=mps
*.model text merge=mps
16 changes: 16 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
version: 2
updates:
- package-ecosystem: gradle
directory: /
schedule:
interval: weekly
registries: "*"
- package-ecosystem: github-actions
directory: /
schedule:
interval: daily

registries:
itemis:
type: maven-repository
url: https://artifacts.itemis.cloud/repository/maven-mps
18 changes: 18 additions & 0 deletions .github/workflows/PR-into-next-version.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
name: PR to merge into the next version

on:
push:
branches:
- 'maintenance/MPS-*'

jobs:
create-pr:
runs-on: ubuntu-latest
steps:
- name: Create PR
uses: specificlanguages/cascading-merge@v2
with:
branch_prefix: maintenance/MPS-
merge_prefix: merge/MPS-
default_merge_prefix: merge/
token: ${{ secrets.MPS_CI_BUILD_BOT_ACCESS_TOKEN }}
86 changes: 86 additions & 0 deletions .github/workflows/build.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,86 @@

name: MPS-logical-view-checks_CI

on:
push:
branches:
- main
- 'maintenance/*'
pull_request:
workflow_dispatch:
inputs:
publish:
description: Whether to publish the build result to Maven repositories
type: boolean
default: false
required: false

env:
GITHUB_TOKEN: ${{ secrets.MPS_CI_BUILD_BOT_ACCESS_TOKEN }}

jobs:
build:
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v4

- name: Set up JDK
uses: actions/setup-java@v4
with:
java-version: 11
distribution: temurin

- name: Set up Gradle
uses: gradle/actions/setup-gradle@v4

- name: Build mps-logical-view-checks and migrate
run: |
xvfb-run ./gradlew build migrate remigrate \
-Partifacts.itemis.cloud.user=${{secrets.ARTIFACTS_ITEMIS_CLOUD_USER}} \
-Partifacts.itemis.cloud.pw=${{secrets.ARTIFACTS_ITEMIS_CLOUD_PW}}
- name: Dump Java stacks on cancellation
if: cancelled()
run: |
jps -mlv > build/jps.txt
for pid in $(jps -q); do jstack -l -e $pid > build/stack$pid.txt || true; done
- name: Upload logs on cancellation or failure
uses: actions/upload-artifact@v4
if: cancelled() || failure()
with:
name: logs
path: |
build/system/log/
build/system/testlog/
build/jps.txt
build/stack*.txt
- name: Check for no dirty files after build and migration
run: |
if [[ -n $(git status --porcelain | head --lines=1) ]]
then
echo "Dirty files detected after build/migration, run './gradlew build migrate remigrate' and/or update .gitignore to fix:"
git status
echo ">>>>>>>>>>>>>>>>>>>>>"
git diff
echo "<<<<<<<<<<<<<<<<<<<<<"
exit 1
fi
- name: Publish

# Only publish on push (to maintenance or main) or when explicitly requested
if: ${{ github.event_name == 'push' || (github.event_name == 'workflow_dispatch' && inputs.publish == 'true') }}

run: |
./gradlew publish -x build \
-Partifacts.itemis.cloud.user=${{secrets.ARTIFACTS_ITEMIS_CLOUD_USER}} \
-Partifacts.itemis.cloud.pw=${{secrets.ARTIFACTS_ITEMIS_CLOUD_PW}}
- name: Archive distribution
uses: actions/upload-artifact@v4
with:
name: com.mbeddr.logicalview.checks
path: build/artifacts/com.mbeddr.logicalview.checks/
30 changes: 30 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# -----------------------------------------------------------
# General
/.idea/
/.gradle/

junitvmwatcher*.properties
build.properties
junit*.properties
/gradle.properties

classes_gen/
source_gen/
source_gen.caches/

workspace.xml

# -----------------------------------------------------------
# * tests
test_gen/
test_gen.caches/
TEST-*.xml
TESTS-*.xml

# ---------------------------------------
# RCP
build/
!/build/scripts/build.xml

# Mac-specific
.DS_Store
128 changes: 128 additions & 0 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or
advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[email protected].
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series
of actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or
permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within
the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.
Loading

0 comments on commit e76acf6

Please sign in to comment.