Page History
...
To implement the continuous integration, we'll implement a specific workflow for it and store it .github/workflows/CI-jira-onpremises-example.yaml.
We’ll use the actions/checkout action to checkout the code from our repository to the virtual environment. This action is one of the "standard" actions provided by GitHub (check full list here).
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
name: CI (Jira on-premises example) on: [push] jobs: build: runs-on: ubuntu-latest steps: - uses: actions/checkout@v1 - name: Set up Java uses: actions/setup-java@v1 with: java-version: '1.8' - name: Cache Maven packages uses: actions/cache@v2 with: path: ~/.m2 key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} restore-keys: ${{ runner.os }}-m2 - name: Build with Maven run: mvn clean compile test --file java-junit-calc/pom.xml - name: Submit results to Xray env: JIRA_SERVER_URL: ${{ secrets.jira_server_url }} JIRA_USERNAME: ${{ secrets.jira_username }} JIRA_PASSWORD: ${{ secrets.jira_password }} run: 'curl -H "Content-Type: multipart/form-data" -u $jira$JIRA_userUSERNAME:$jira$JIRA_passwordPASSWORD -F "file=@target/surefire-reports/TEST-com.xpand.java.CalcTest.xml" "$jira$JIRA_serverSERVER_urlURL/rest/raven/1.0/import/execution/junit?projectKey=CALC"' |
In order to submit those results to Xray, we'll just need to invoke the REST API (as detailed in Import Execution Results - REST).
...