Create automated build to validate master branch and promote to openj9 branch

Question

Create automated build to validate master branch and promote to openj9 branch

DanHeidinga opened this issue 7 years ago · 7 comments

Code from the upstream OMR repo is synchronized into the master branch. Once there, we need an automated build that will validate it with openj9 repo and merge it into the openj9-omr repo's openj9 branch.

Answer 1 · 2017-09-18T19:02:00.000Z

FYI @AdamBrousseau

Answer 2 · 2017-09-18T22:48:54.000Z

Token needed for API calls to GitHub from Jenkins.
Added requirements to the existing (bug](https://bugs.eclipse.org/bugs/show_bug.cgi?id=522322) from #3

Answer 3 · 2017-09-20T18:25:19.000Z

Previous comment is actually required for PullRequest builds, not the build that this issue is for (my mistake for confusing the issues). This issue is for the "OMR Acceptance" build which we can now implement since #3 is resolved. I will get going on this today.

Answer 4 · 2017-09-22T19:14:41.000Z

OMR Acceptance build setup as a pipeline. Taking of advantage of the "generic" build jobs pLinux and zLinux and "generic" test jobs pLinux and zLinux. Calls each platform in parallel. Calls the Promote job when everything passes.

High level overview
Pipeline

Sniff repos to get latest SHAs. Ensures we build consist content across all platforms
Parallel
- Build pLinux -> Test pLinux
- Build zLinux -> Test zLinux
Promote

Dry running it now

Answer 5 · 2017-09-27T11:31:35.000Z

Added tagging in the promote job.
Tag format:
Name:
omr_merge_YYYYMMDD_HHMMSS
Annotation:

OMR: <OMR_SHA>
OpenJ9: <OPENJ9_SHA>
OpenJDK: <OPENJDK_SHA>

Everything seems to be working now. We have had 3 levels promote through without issue.

Answer 6 · 2017-09-29T02:17:09.000Z

@DanHeidinga I think we can close this as complete

Answer 7 · 2017-09-29T03:01:59.000Z

Agreed. Thanks for all your work on this @AdamBrousseau - not only on the scripting but working through getting the web hooks, etc configured. Much appreciated!