Bug 496465 - Prep for 4.7 (Oxygen) and 4.6.1 (Neon.1) maintenance builds
Summary: Prep for 4.7 (Oxygen) and 4.6.1 (Neon.1) maintenance builds
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.6.1   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: info
Depends on: 495458 496335 496868 496881 496882 496917 497013
Blocks:
  Show dependency tree
 
Reported: 2016-06-21 09:12 EDT by David Williams CLA
Modified: 2016-07-11 13:30 EDT (History)
21 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2016-06-21 09:12:28 EDT 
+++ This bug was initially created as a clone of Bug #469765 +++


This is just a general bug to make notes of what I (we) need to do to build after current development cycle ... see original bug 469765, bug 436736, and bug 478493 for previous outlines of what must be done.

Reminder to self that much of this should be codified in 
https://wiki.eclipse.org/Platform-releng/Checklist#After_Major_.28June.29_release

= = = = = = 

There is nothing to do right now ... but, I'm opening this now as a reminder for us all to pencil-in some time to take the necessary steps. 

I propose we begin this after Neon officially releases (Wed., June 22) with a goal of being operational in both streams ... say by July 12?.
Comment 1 David Williams CLA 2016-06-24 12:10:13 EDT 
I suggest we wait until bug 495458 before we make specific plans to coordinate the creation of branches, changes of POMs, etc. 

I anticipate that bug  	495458 will be fixed on Monday, and I hope by then to have more concrete instructions for what teams need to do. But, the steps are pretty much outlined in the "previous bugs" mentioned in comment 0 if someone else want's to write them down. 

Also, I propose that we get the "M-builds" and "I-builds" running again next week. The only constraint I have is it has to take place Monday to Wednesday since I will be taking off Thursday and Friday for some family events.
Comment 2 David Williams CLA 2016-06-27 16:54:03 EDT 
Now that all the repos for "4.6" have been tagged with R4_6, I think it is time we "bite the bullet" and begin branching and changing parent poms to build "4.7" and "4.6.1". 

This of course needs to be a "coordinated" change, since we won't be able to build again (even N-builds) for either "production builds" or for "Gerrit builds" until everything has been updated. Since already "late in the day" (Eastern time) I suggest we target to begin this work "Tuesday morning" (any timezone :) and hopefully finish later in the day, so that on Tuesday evening we might be able to get an I-build and on Wednesday an M-build. 

Does anyone see any "blockers" for this plan? For example, someone knows for sure that some component has "all commmitters" on holiday for Tuesday? And Wednesday? 

[P.S. before he left Dani suggested to me get the new builds running "this week" -- I assume so he wouldn't have to be part of the turmoil :) (haha) -- 
and, as I mentioned, I will be offline Thursday and Friday.] 

I will also send note to platform-releng-dev list, but unless we hear otherwise let's assume we begin Tuesday morning and we'll finish when we finish. 

Sound ok?
Comment 3 Eclipse Genie CLA 2016-06-28 01:00:39 EDT 
New Gerrit change created: https://git.eclipse.org/r/76065
Comment 4 Eclipse Genie CLA 2016-06-28 01:01:33 EDT 
New Gerrit change created: https://git.eclipse.org/r/76066
Comment 5 Eclipse Genie CLA 2016-06-28 01:02:17 EDT 
New Gerrit change created: https://git.eclipse.org/r/76067
Comment 6 Sarika Sinha CLA 2016-06-28 01:03:19 EDT 
Gerrit patches for pom updates for 4.7 for jdt.debug, platform.debug and platform ant
Comment 9 Vikas Chandra CLA 2016-06-28 03:04:47 EDT 
Created branches for

ssh://git.eclipse.org/gitroot/pde/eclipse.pde.ui.git
ssh://git.eclipse.org/gitroot/pde/eclipse.pde.build.git

and verified them

On Git Bash
---------------
ssh vchandra@build.eclipse.org 
and then 
git --git-dir=/gitroot/pde/eclipse.pde.build.git branch R4_6_maintenance R4_6
Comment 10 Szymon Ptaszkiewicz CLA 2016-06-28 05:38:18 EDT 
Branches R4_6_maintenance created for eclipse.platform.resources and eclipse.platform.team repositories.
Comment 11 Eclipse Genie CLA 2016-06-28 05:54:53 EDT 
New Gerrit change created: https://git.eclipse.org/r/76090
Comment 12 Sravan Kumar Lakkimsetti CLA 2016-06-28 05:55:56 EDT 
(In reply to Eclipse Genie from comment #11)
> New Gerrit change created: https://git.eclipse.org/r/76090

Hi David,

I did the script changes here. can you please verify and letme know if these changes are good?

Thanks
Sravan
Comment 15 Markus Keller CLA 2016-06-28 08:04:23 EDT 
(In reply to Lakshmi Shanmugam from comment #7)
There were a few more SWT poms in master that required updates:
http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=d63833f0087d8c58b6219c75f2dd150ec302216d
http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=707d4dd62891c962b6a08f5f6541b4170b0b75f9

Lakshmi, please check the R4_6_maintenance branch and apply similar updates if necessary.
Comment 17 Eclipse Genie CLA 2016-06-28 08:27:56 EDT 
New Gerrit change created: https://git.eclipse.org/r/76100
Comment 20 Stephan Herrmann CLA 2016-06-28 08:45:46 EDT 
I guess failures in gerrit builds are expected at this point?

FWIW, I just got 
[FATAL] Non-resolvable parent POM for eclipse.jdt.core:eclipse.jdt.core:4.7.0-SNAPSHOT: Could not find artifact org.eclipse:eclipse-platform-parent:pom:4.7.0-SNAPSHOT in eclipse-hosted (https://repo.eclipse.org/content/repositories/eclipse/) and 'parent.relativePath' points at wrong local POM @ line 15, column 11

Should I just wait for this bug to be fully resolved? Or is there an easy way to already deploy just the parent pom at 4.7.0?
Comment 21 Lars Vogel CLA 2016-06-28 09:00:00 EDT 
(In reply to Markus Keller from comment #19)
> Updated poms in master to 4.7.0:

> Remaining in master: releng, team, resources, equinox.

Can you please also take eclipse.platform.ui.tools which is part of the platform UI project?
Comment 22 David Williams CLA 2016-06-28 09:06:46 EDT 
(In reply to Stephan Herrmann from comment #20)
> I guess failures in gerrit builds are expected at this point?
> 
> FWIW, I just got 
> [FATAL] Non-resolvable parent POM for
> eclipse.jdt.core:eclipse.jdt.core:4.7.0-SNAPSHOT: Could not find artifact
> org.eclipse:eclipse-platform-parent:pom:4.7.0-SNAPSHOT in eclipse-hosted
> (https://repo.eclipse.org/content/repositories/eclipse/) and
> 'parent.relativePath' points at wrong local POM @ line 15, column 11
> 
> Should I just wait for this bug to be fully resolved? Or is there an easy
> way to already deploy just the parent pom at 4.7.0?

No, things won't work well until it is resolved.
Comment 23 Markus Keller CLA 2016-06-28 09:42:07 EDT 
(In reply to Lars Vogel from comment #21)
> Can you please also take eclipse.platform.ui.tools which is part of the
> platform UI project?

Thank for the reminder, done with:
http://git.eclipse.org/c/platform/eclipse.platform.ui.tools.git/commit/?id=df4e1d6255fa24219870b12ce3da0bb985ab890d
Comment 24 Eclipse Genie CLA 2016-06-28 09:51:12 EDT 
New Gerrit change created: https://git.eclipse.org/r/76115
Comment 25 Eclipse Genie CLA 2016-06-28 09:51:36 EDT 
New Gerrit change created: https://git.eclipse.org/r/76116
Comment 26 Markus Keller CLA 2016-06-28 10:04:30 EDT 
Sergey or Szymon, could you please push the resources and team updates for master?
https://git.eclipse.org/r/#/c/76115/
https://git.eclipse.org/r/#/c/76116/
Comment 29 David Williams CLA 2016-06-28 11:54:24 EDT 
FWIW, I have branched the aggregator to R4_6_maintenance and updated all the pom versions there in both maintenance and master. 

Now I'll start looking at all the hard stuff. :) 

Primary goal will be to get an N-build running again so Gerrit will work. 

Then I-build, then M-build, AND THEN start to work on "branding" type issues. 

Thanks all.
Comment 30 Mickael Istria CLA 2016-06-28 12:07:19 EDT 
I triggered https://hudson.eclipse.org/platform/job/deploy-eclipse-platform-parent-pom-4.6/532/ and https://hudson.eclipse.org/platform/job/deploy-eclipse-sdk-target-pom-4.6/377/ which (as the name doesn't tell for the moment) built and deployed parent and TP 4.7.0-SNAPSHOT to Nexus.
Comment 31 David Williams CLA 2016-06-28 13:16:01 EDT 
(In reply to Mickael Istria from comment #30)
> I triggered
> https://hudson.eclipse.org/platform/job/deploy-eclipse-platform-parent-pom-4.
> 6/532/ and
> https://hudson.eclipse.org/platform/job/deploy-eclipse-sdk-target-pom-4.6/
> 377/ which (as the name doesn't tell for the moment) built and deployed
> parent and TP 4.7.0-SNAPSHOT to Nexus.

Those jobs should be triggered upon seeing a change in Git. I know that hasn't always been true, but someone fixed them, at some point to "do it right". 

But, even once they are changed, Gerrit users need a proper N-build (as far as I know). Since they depend on stuff "already built" to build each component. Sad to say.
Comment 32 David Williams CLA 2016-06-28 13:17:56 EDT 
Can someone remind me of what "config" should look like? 

Somehow after creating the R4_6_maintenance branch, now when I try to push, EGit tries to "push all branches". What did I break? 

FWI, my --global config says "push.default = simple" but not sure EGit knows what that means?
Comment 33 Eclipse Genie CLA 2016-06-28 13:36:06 EDT 
New Gerrit change created: https://git.eclipse.org/r/76150
Comment 34 Eclipse Genie CLA 2016-06-28 13:42:31 EDT 
New Gerrit change created: https://git.eclipse.org/r/76151
Comment 35 Markus Keller CLA 2016-06-28 13:46:22 EDT 
(In reply to David Williams from comment #32)
> Can someone remind me of what "config" should look like? 

Something like this is the minimum for a non-Gerrit setup:

[remote "origin"]
	url = ssh://username@git.eclipse.org/gitroot/platform/eclipse.platform.releng.aggregator.git
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "R4_6_maintenance"]
	remote = origin
	merge = refs/heads/R4_6_maintenance
	rebase = true

> Somehow after creating the R4_6_maintenance branch, now when I try to push,
> EGit tries to "push all branches". What did I break? 

Sounds like you could have a broken branch.R4_6_maintenance.push setting. I suggest you just delete any "push" entries, especially if their value is just ":" or "+:".
Comment 36 Eclipse Genie CLA 2016-06-28 13:51:47 EDT 
New Gerrit change created: https://git.eclipse.org/r/76152
Comment 40 Eclipse Genie CLA 2016-06-28 14:49:37 EDT 
New Gerrit change created: https://git.eclipse.org/r/76156
Comment 41 Eclipse Genie CLA 2016-06-28 14:50:31 EDT 
New Gerrit change created: https://git.eclipse.org/r/76157
Comment 44 Eclipse Genie CLA 2016-06-28 15:07:58 EDT 
New Gerrit change created: https://git.eclipse.org/r/76159
Comment 45 David Williams CLA 2016-06-28 15:09:07 EDT 
(In reply to Markus Keller from comment #35)

> > Somehow after creating the R4_6_maintenance branch, now when I try to push,
> > EGit tries to "push all branches". What did I break? 
> 
> Sounds like you could have a broken branch.R4_6_maintenance.push setting. I
> suggest you just delete any "push" entries, especially if their value is
> just ":" or "+:".

Thanks, Markus. Removing the "push" line from "origin" did the trick.
Comment 46 Markus Keller CLA 2016-06-28 15:11:07 EDT 
With Tom's updates for Equinox, master is ready for an N-build.

The product and feature versions are still at 4.6.0, but I guess we'll better wait with that until the build succeeds.

Here's the shell command I used to update most poms (doesn't work for equinox and misses a few special cases):

$ find . -name pom.xml -print0 | xargs -0 sed -i -s -z -r "s~(<(artifactId|groupId)>(eclipse|tests)[^<]+</(artifactId|groupId)>\s+<version>)4\.6\.0-SNAPSHOT</version>~\14.7.0-SNAPSHOT</version>~g"

Find remaining references to 4.6.0 (some of these must stay at 4.6.0!):

$ find . -name pom.xml -print0 | xargs -0 grep --color "4\.6\.0"


For R4_6_maintenance, I've:
- pushed the fixes for SWT (comment 15)
- fixed the parent poms for PDE (on top of comment 16)
- created the remaining branches and pushed all pom updates for platform/jdt/pde
Comment 48 Eclipse Genie CLA 2016-06-28 15:13:49 EDT 
New Gerrit change created: https://git.eclipse.org/r/76161
Comment 49 Eclipse Genie CLA 2016-06-28 15:15:23 EDT 
New Gerrit change created: https://git.eclipse.org/r/76162
Comment 51 Eclipse Genie CLA 2016-06-28 15:17:52 EDT 
Gerrit change https://git.eclipse.org/r/76162 was merged to [R4_6_maintenance].
Commit: http://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=eb2b55c22a0b43e2904ad1392b8b6880bc6863c3
Comment 52 David Williams CLA 2016-06-28 15:22:08 EDT 
(In reply to Markus Keller from comment #46)
> With Tom's updates for Equinox, master is ready for an N-build.
> 

I will try one now, scheduled for 3:30 PM Eastern. 

But, was about to give some status that I started a test build a few hours earlier and it mostly succeeded. (Failed at some "post build" stuff). 

But, that success made me very unhappy because I know for sure not all parent poms were updated yet. So ... something is "leaking"? I recall last year a big issue that 
https://repo.eclipse.org/content/repositories/eclipse/
was "visible" during the whole build so it didn't matter what parent you referred to, it would be found. 

Not sure if we have "regressed" or if there is some new reason why we got success when we should not have.
Comment 53 David Williams CLA 2016-06-28 16:09:52 EDT 
(In reply to David Williams from comment #52)
> (In reply to Markus Keller from comment #46)
> > With Tom's updates for Equinox, master is ready for an N-build.
> > 
> 
> I will try one now, scheduled for 3:30 PM Eastern. 
> 
> But, was about to give some status that I started a test build a few hours
> earlier and it mostly succeeded. (Failed at some "post build" stuff). 
> 
> But, that success made me very unhappy because I know for sure not all
> parent poms were updated yet. So ... something is "leaking"? I recall last
> year a big issue that 
> https://repo.eclipse.org/content/repositories/eclipse/
> was "visible" during the whole build so it didn't matter what parent you
> referred to, it would be found. 
> 
> Not sure if we have "regressed" or if there is some new reason why we got
> success when we should not have.

I do see in our ~/m2/settings.xml that we have the usual mirror of maven central at the eclipse foundation's repo: 

<mirrors>
    <mirror>
      <id>repo.eclipse.org</id>
      <name>Eclipse Central Proxy</name>
      <url>https://repo.eclipse.org/content/repositories/maven_central/</url>
      <mirrorOf>central</mirrorOf>
    </mirror>
</mirrors>

I do not obviously see "eclipse-platform-parent" in there, but does anyone know how to confirm for sure? (i.e. that it is not "reachable", somehow, from that repository?). 

I know last year the problem was that we had the repository 
https://repo.eclipse.org/content/repositories/eclipse 
"globally" defined ... and our parent is in that one. 
Subsequently we put it in a profile and I thought that fixed it. 
(bug 471835).
Comment 54 David Williams CLA 2016-06-28 17:30:40 EDT 
The 3:30 build did complete. Never saw an email for it. Not sure why. 

But it is at the usual place on downloads, the 4.7-N-builds repo was updated, 
and the tests have started to run: 

https://hudson.eclipse.org/shared/view/Eclipse%20and%20Equinox/

Not only that, but the build actually runs! (Well, at least "comes up" :). 

I changed a few things after that build, so I think we will next have the 8 PM nightly N-build, and then try the I-build at 8 AM Wed. and M-build at 10 AM Wednesday. 

I suggest if people have been making changes but resisting updating bundle and feature versions, that before the I-build would be a good time to do that -- otherwise more risk it would fail do to "comparator" issues.  

As for Update Build, unless someone has a good reason to, I'd hesitate to make any substantial (i.e. code changes) changes to R4_6_maintenance stream until we get a good build. 

I will assume no "patch" or Y-build this week -- still some work to do there (for example, I am assume we will need a patch build for both streams? (But, Y-build only on master). JDT Team, let us know if you've been assuming something different. 

Thanks again,
Comment 55 Jay Arthanareeswaran CLA 2016-06-28 23:47:30 EDT 
(In reply to David Williams from comment #54)
> I will assume no "patch" or Y-build this week 

That is fine, David.
Comment 56 Eclipse Genie CLA 2016-06-29 04:53:13 EDT 
New Gerrit change created: https://git.eclipse.org/r/76185
Comment 58 Lakshmi P Shanmugam CLA 2016-06-29 05:28:27 EDT 
(In reply to Markus Keller from comment #15)
> (In reply to Lakshmi Shanmugam from comment #7)
> There were a few more SWT poms in master that required updates:
> http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/
> ?id=d63833f0087d8c58b6219c75f2dd150ec302216d
> http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/
> ?id=707d4dd62891c962b6a08f5f6541b4170b0b75f9
> 
> Lakshmi, please check the R4_6_maintenance branch and apply similar updates
> if necessary.

Thanks Markus, I missed the pom updates in localbuild dir.
The pom updates in the binaries repo are not required since we don't build those platforms anymore. Those projects will be removed from the repo.
Comment 59 Lars Vogel CLA 2016-07-05 01:59:39 EDT 
(In reply to Vikas Chandra from comment #13)
> pde.ui
> http://git.eclipse.org/c/pde/eclipse.pde.ui.git/commit/
> ?id=ea2f26111c30003a2dbfd9c3836a49c746085db0

I think the individual artifact must also be updated to 4.7. Patch on its way.
Comment 60 Eclipse Genie CLA 2016-07-05 02:01:08 EDT 
New Gerrit change created: https://git.eclipse.org/r/76566
Comment 62 Thomas Watson CLA 2016-07-11 09:23:14 EDT 
I probably missed the latest status for maintenance builds.  Are the R4_6_maintenance builds up and running.  I ask because the Equinox framework gerrit builds for R4_6_maintenance are failing because they cannot find the parent pom:

[FATAL] Non-resolvable parent POM for org.eclipse.equinox.framework:rt.equinox.framework:4.6.1-SNAPSHOT: Could not find artifact org.eclipse:eclipse-platform-parent:pom:4.6.1-SNAPSHOT in eclipse-hosted (https://repo.eclipse.org/content/repositories/eclipse/) and 'parent.relativePath' points at wrong local POM @ line 15, column 11

I assume we were supposed to point to a new 4.6.1 parent pom?  If so is there a way to get one published?
Comment 63 David Williams CLA 2016-07-11 10:33:57 EDT 
(In reply to Thomas Watson from comment #62)
> I probably missed the latest status for maintenance builds.  Are the
> R4_6_maintenance builds up and running.  I ask because the Equinox framework
> gerrit builds for R4_6_maintenance are failing because they cannot find the
> parent pom:
> 
> [FATAL] Non-resolvable parent POM for
> org.eclipse.equinox.framework:rt.equinox.framework:4.6.1-SNAPSHOT: Could not
> find artifact org.eclipse:eclipse-platform-parent:pom:4.6.1-SNAPSHOT in
> eclipse-hosted (https://repo.eclipse.org/content/repositories/eclipse/) and
> 'parent.relativePath' points at wrong local POM @ line 15, column 11
> 
> I assume we were supposed to point to a new 4.6.1 parent pom?  If so is
> there a way to get one published?

I think I've fixed the "parent pom" issue. See bug 97176#c5. 

The "deploy prereq" issue looks a little more complicated, and I won't have time to do that right now. (And, have never understood why that was even needed). 

Please comment if "thinks are better".
Comment 64 Thomas Watson CLA 2016-07-11 11:39:48 EDT 
(In reply to David Williams from comment #63)
> I think I've fixed the "parent pom" issue. See bug 97176#c5. 
Wrong bug number?

> 
> The "deploy prereq" issue looks a little more complicated, and I won't have
> time to do that right now. (And, have never understood why that was even
> needed). 
> 
> Please comment if "thinks are better".

Things are getting past the parent pom resolution.
I think they are hitting what you describe above for prereq now:

Downloaded: https://repo.eclipse.org/content/repositories/maven_central/org/eclipse/tycho/org.eclipse.tycho.core.shared/0.25.0/org.eclipse.tycho.core.shared-0.25.0.jar (37 KB at 55.5 KB/sec)
Downloading: https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-sdk-prereqs/4.6.1-SNAPSHOT/maven-metadata.xml
Downloading: https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-sdk-prereqs/4.6.1-SNAPSHOT/eclipse-sdk-prereqs-4.6.1-SNAPSHOT.target
[INFO] o.h.m.e.h.MavenExecutionResultHandler - Build failed with exception(s)
[INFO] o.h.m.e.h.MavenExecutionResultHandler - [1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.eclipse:eclipse-sdk-prereqs:target:4.6.1-SNAPSHOT
[DEBUG] Closing connection to remote
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.eclipse:eclipse-sdk-prereqs:target:4.6.1-SNAPSHOT -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.eclipse:eclipse-sdk-prereqs:target:4.6.1-SNAPSHOT
Comment 65 David Williams CLA 2016-07-11 12:49:03 EDT 
(In reply to Thomas Watson from comment #64)
> (In reply to David Williams from comment #63)
> > I think I've fixed the "parent pom" issue. See bug 97176#c5. 
> Wrong bug number?
> 
> > 
> > The "deploy prereq" issue looks a little more complicated, and I won't have
> > time to do that right now. (And, have never understood why that was even
> > needed). 
> > 
> > Please comment if "thinks are better".
> 
> Things are getting past the parent pom resolution.
> I think they are hitting what you describe above for prereq now:
> 
> Downloaded:
> https://repo.eclipse.org/content/repositories/maven_central/org/eclipse/
> tycho/org.eclipse.tycho.core.shared/0.25.0/org.eclipse.tycho.core.shared-0.
> 25.0.jar (37 KB at 55.5 KB/sec)
> Downloading:
> https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-
> sdk-prereqs/4.6.1-SNAPSHOT/maven-metadata.xml
> Downloading:
> https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-
> sdk-prereqs/4.6.1-SNAPSHOT/eclipse-sdk-prereqs-4.6.1-SNAPSHOT.target
> [INFO] o.h.m.e.h.MavenExecutionResultHandler - Build failed with exception(s)
> [INFO] o.h.m.e.h.MavenExecutionResultHandler - [1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.RuntimeException: Could not resolve target platform specification
> artifact org.eclipse:eclipse-sdk-prereqs:target:4.6.1-SNAPSHOT
> [DEBUG] Closing connection to remote
> [ERROR] Internal error: java.lang.RuntimeException: Could not resolve target
> platform specification artifact
> org.eclipse:eclipse-sdk-prereqs:target:4.6.1-SNAPSHOT -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.RuntimeException: Could not resolve target platform specification
> artifact org.eclipse:eclipse-sdk-prereqs:target:4.6.1-SNAPSHOT

I've not modified the 4.6 "prereqs" job to pull from R4_6_maintenance. 
And, created a new job deploy-eclipse-sdk-target-pom-4.7 which pulls and deploys from the master branch. 

I hope *that* gets you building again since that is the extent of my knowledge. :)
Comment 66 David Williams CLA 2016-07-11 13:23:28 EDT 
I have updated our wiki at 

https://wiki.eclipse.org/Platform-releng/Checklist

to contain most of the major steps mentioned in this bug, including the Gerrit changes which we have not traditionally had to do. 

I am sure I've missed some items in that rough outline but hope it can grow organically over time as people notice things missing or not said very well. 

And with that, will call this bug "fixed". If anything else found missing, please open a new bug (and mark is "blocking" this one, simply so we have a "collected set" at the end of it all).