Thanks for the details, Paul!
I have created two bugzillas:
- Enable auto-tagging (https://bugs.eclipse.org/bugs/show_bug.cgi?id=370193)
- Include test in the regular testrun (https://bugs.eclipse.org/bugs/show_bug.cgi?id=370202)
From: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Webster
Sent: Monday, January 30, 2012 2:26 PM
To: E4 Project developer mailing list
Subject: Re: [e4-dev] Including Search Console tests in build process and execute them automatically
On Mon, Jan 30, 2012 at 3:56 AM, Branekov, Danail <danail.branekov@xxxxxxx> wrote:
"auto-tagging" sounds good, but how does it work? http://wiki.eclipse.org/E4/Git says that the script which was used for updating the map files is outdated. Does it mean that the build would consider take the content from the integration branch and updating maps files is no longer required?
Right. It's a step at the beginning of a build that updates a cached git repo to the integration branch, and then generates the map file qualifiers from that build input and checks them in for all of our projects. It makes developers pushing to origin/integration the same as releasing for a build, and anyone can do it since EGit can handle that (as opposed to the linux scripts :-). It's controlled by that repositories.txt file. It's possible to simply specify your dev branch instead of an integration branch so your latest work will always be tagged (that has to be decided on a repo by repo basis).
Hi floor. Make me a sammich! - GIR