[platform-releng-dev] A word on "production builds" ...

[David M Williams <david_williams@xxxxxxxxxx>]

> So basically, you're against faster
feedback loops and being notified early that Platform build fails ? You're
not interested in already knowing that build days

> "[ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.21.0:validate-version (default-validate-version) on project org.eclipse.e4.ui.bindings.tests:
> Unqualified OSGi version 0.9.200.qualifier must match unqualified Maven version 0.9.100-SNAPSHOT for SNAPSHOT builds -> [Help 1]"
> whereas no production build seems to have caught this error yet ?

Despite your loaded language, you have inadvertently given a good example ... of how *that* build is inadequate. :)  [Seriously, just kidding, with my language, but there is a "bug" in that build, or some limitation, as Git history shows that issue that was fixed 7 days ago.]

And, even faster detection of that particular type of problem can be achieved by installing the "releng tool" and turn on the preference that shows such POM/MANIFEST version "mismatches" directly in your workbench.

While I won't waste our (and reader's) time arguing pros and cons on this list -- we both obviously have our biases about "the best" way to work -- I do believe there are many ways to do things. Some are very much "developer" oriented, and some people these days shy away from "self hosting" that others embrace. But, some methods are very much "adopter" oriented, which is how I define "a production build" (to answer one of your questions) -- it is one that we deliver to the release train and adopters as our official downloads and repository. And we have a number of criteria for those, such as repeatability, maintainability, valid qualifiers, etc., we've listed a couple of times, and while not perfect, I think our current production build is headed in the right direction. If and when the PMC decides someone else should produce the production build, using what ever methodology they want, that's fine with me. But, for now, that's my assignment ... and I do the best I can (with the help of a great many people ... including you!). I think the Gerrit builds that others have set up (and that I know little about) serve a good, useful purpose for some people, for some purposes, but the end result is not production quality bits -- at least for our large, complicated project. I know some people will say, "Well, it could, if you made the investment to refactor your repositories and code so that it better fit the Maven/Tycho model... " but ... as far as I know ... no one is willing to make that large investment, up front, and instead we all try to make slow and incremental progress.

'Nough said? (I've already been too wordy. :)   Appreciate your (and everyone's) help, and any  constructive  suggestion is always welcome. Its probably best to enter those as a bugzilla entries where issues/suggestions can be tracked and prioritized more easily along with everything else that needs to get done.





From:        Mickael Istria <mistria@xxxxxxxxxx>
To:        platform-releng-dev@xxxxxxxxxxx,
Date:        10/07/2014 09:16 AM
Subject:        Re: [platform-releng-dev] BUILD FAILED - compilation failure - re-try at 2:15 AM Eastern (1007-0215)
Sent by:        platform-releng-dev-bounces@xxxxxxxxxxx

---

On 10/07/2014 02:55 PM, Daniel Megert wrote:
Gerrit allows people to subscribe to notifications that they are interested in. Sending the notifications to a/this list where everyone has to read them without a way to unsubscribe is wrong.
This build is not at all tied to Gerrit. If this build fails, there are big chances that "production builds" fail too.
So basically, you're against faster feedback loops and being notified early that Platform build fails ? You're not interested in already knowing that build days" [ERROR] Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:0.21.0:validate-version (default-validate-version) on project org.eclipse.e4.ui.bindings.tests: Unqualified OSGi version 0.9.200.qualifier must match unqualified Maven version 0.9.100-SNAPSHOT for SNAPSHOT builds -> [Help 1]" whereas no production build seems to have caught this error yet ?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev