...

A job can generate output variables that can be used by another job that depends on it.; this is the preferred way to share data between jobs.

Another way of sharing data, especially between jobs, would be to produce and store artifact(s) in a job and obtain them in another job.

Environment variables can also be used to access some data and share them, with care. Environment variables are available There are also typical environment variables available at workflow, job or step level. GitHub fills out some environment variables by default.

It's also possible to access secrets, defined  defined in GitHub project settings, as environment variables or as a step input.Another way of sharing data, especially between jobs, would be to produce and store artifact(s) in a job and obtain them in another job.

Examples

Basic JUnit example

...

In Jira, Xray now shows the results of the automated tests in a brand new Test Execution issue. Test issues corresponding to each test method will be auto-provisioned, if they don't exist yet; otherwise, results will be reported against existing Tests.

Tips

• for editing workflow YAML files, you can do it directly from GitHub UI as it provides syntax highlighting, auto-completion, and more
• in the workflow definition, configure it to cache Maven dependencies (more info here)
• it's possible to re-run jobs from GitHub UI
  • 
• instead of using curl command to interact with Xray REST API, you can abstract it in a GitHub Action and use input parameters to be passed to the REST call

References

• Introduction to GitHub Actions
• Building and testing Java with Maven with GitHub Actions