JavaFX JIRA-related questions

[Richard Bair]

Hi Mark!

On Dec 17, 2012, at 1:00 PM, Mark Fortner <phidias51 at gmail.com> wrote:

> I've filed a number of JIRA issues and I was wondering if there are any
> plans to connect the Hg repo to JIRA?  We do this all the time with SVN and
> GIT and it makes it easier to code review the change, and the unit test
> when we can see the change set.  The change set normally appears in the
> "Source" tab inside the JIRA issue.

Yes. We are working on an infrastructure plan along with OpenJDK (we will be using the same core services / servers / process in the future) which includes updating JIRA whenever patches are integrated into master. We're also looking at Crucible (or Stash) as a means for code review, and having our JIRA instance be the "one truth" and other tools tied / integrated into it.

The first step in our master plan is to get SQE tests open sourced and part of the forest, along with the rest of our closed source bits. We'll then be consolidating our tests & cleaning up the build. Once we've got a nice build in place, we'll be tackling tasks such as integrated code coverage reports etc. At the same time the JDK team is working on getting the JBS (Java Bug System) JIRA instance public and we'll look at migrating over to that (I would guess somewhere in the 6-12 month timeframe). Also a new instance of confluence that we will use to start putting all our docs onto (much shorter timeframe).

The next thing we want to accomplish is to get setup for continuous integration, such that instead of having a bunch of different forests we just have the master forest. We want a system where we have well defined "integration tests" which must all pass before a patch can be integrated into master. We want to have a system where this happens automatically. I submit my patch and it is automatically merged with master, built, and tested on all platforms. If everything builds & all tests pass, then the patch is automatically integrated with master and the JIRA issue updated. From there we kick off a longer set of continuous tests ("nightlies"). If those pass some acceptance threshold then the bits are posted as nightly binaries and we start a longer set (2 weeks? more?) of tests such as stability tests etc.

Also getting code review etc setup. Personally I would love to use something like Stash -- essentially a self-hosted bit-bucket -- that would let us fire up developer forests or sandboxes etc as needed and then issue pull-requests and let that be the mechanism by which a patch gets into the auto-integration queue. But Stash doesn't yet support mercurial so it is a non-starter at this point.

I would also, personally, like to have just a single open repo and not a whole forest. There are tradeoffs here (time to clone a repo -- if you only work on Media for example you might not be used to cloning & building webkit, so each new clone operation will take a lot longer with only one repo -- vs the simplicity of working with a single repo and everybody working on the same project files & having everything to build and test with), but for my money I think we ought to all just use the same repo to avoid the inevitable silo-ing that occurs today.

> Also, whenever I try to use the screenshot feature in JIRA to take a
> screenshot and attach it to the issue, I get an Oracle Technet home page,
> instead of the appropriate applet page.  Could somebody fix that?

Brian?

Richard