Only a small portion of our Confluence documentation has to be migrated to GitHub, so copy-pasting the content manually is sufficient and the fastest solution.
Confluence pages which shall not be moved to GitHub have to be marked as such. Everything else will be moved. [@DEPRECATION] lable will be used to identify those pages which will not be moved. This [@DEPRECATION] label could be set on headline level as well to identify chapter which should not be moved.
Notice: During transition phase:
- Content of the pages or chapters will be moved to Github.
- However, the pages and structures are retained (not deleted)
- Links leading to the new content will be added instead.
- After moving content and adding the link the lable [@DEPRECATION] will be added to chapter or page.
AsIs: Cucumber Tests are stored in and reported to Jira, using the Jira-Xray plugin.
ToBe: Feature files can be exported and directly stored in GitHub.
Test results have to be displayed directly in GitHub workflow / Pull Request. This can be done in two ways:
- using the free Cucumber Report Service, where the results will be published to a cloud hosted service
- Using the generated test report and upload it using a GitHub Action https://github.com/marketplace/actions/publish-test-results
AsIs: The CatenaX-NG ArgoCD environments were used to execute Integration- and E2E-Tests. After the end of the Consortia phase, they are no longer available and have to be replaced by an open solution.
ToBe: The proposed solution is a helm chart with all required dependencies, including EDC Consumer, EDC Provider, MIW, Semantic Hub, Discovery Service, Digital Twin Registry, OAuth Provider and IRS. Implementation of this chart is planned in #312
The chart will then be used in a GitHub workflow to test the E2E Workflow. The already existing Cucumber Tests can be used.
Furthermore, integration tests using mocks of the third-party systems should be extended so testing can be done as much as possible on the local machine or in GitHub workflows, without setting up the entire helm deployment. This is planned in #344
PRs are to be opened directly to eclipse-tractusx/item-relationship-service. Eclipse committers can create branches directly in this project. External contributors can contribute by forking the eclipse-tractusx/item-relationship-service project and create pull requests from their fork.
Non-committers of the core IRS team can still use the catenax-ng/tx-item-relationship-service fork but pull requests still have to be opened directly to eclipse-tractusx/item-relationship-service.
Branch protection of catenax-ng/tx-item-relationship-service:main will be removed so synchronization with the upstream project can be done by one click.