| You can find out the commit given a date if you use gt rev-parse --since --until, but instead of doing that, it would make sense to record the commit id with the build itself so that it can be used exactly without relying on date strings (or tags).
git rev-parse HEAD gives you the commit ID at the point of checkout, and this can be embedded in the build itself. You can also use git destribe --tag to give you a number since the last tag, which sometimes can be more useful than a hash.
You might choose to embed that value in the build process itself (such as writing it to a file or a property) to follow through with the build, or you might just leave it as the build information - most builds will record what the commit hash was on checkout, which is enough to reproduce nightilies.
For milestone and releases, it might make sense to tag the system. But it's unnecessary to do that for every build.
Alex On 7 Jul 2011, at 21:33, Vivian Kong wrote: I see. But if we don't tag the commit with a label (date stamp that's same with the one in the repo zip file name), how would I know which commit was included in a build? Is there another way to figure that out?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<graycol.gif>"Schaefer, Doug" ---07/07/2011 04:17:49 PM---git rev-parse HEAD seems to do the trick. Also, I'm not certain we need to tag builds anymore. The c
git rev-parse HEAD
seems to do the trick. Also, I’m not certain we need to tag builds anymore. The commit id is a tag. I would only tag the real release points we usually label with CDT_*.
Doug.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Thursday, July 07, 2011 4:12 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0
I think I can get the build to sign now and so looks like I just need to tag the build. Is there an easy way to query which commit was checked out and tag the commit with a date stamp?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<graycol.gif>Vivian Kong---07/06/2011 06:05:53 PM---Thanks! I eventually figured out I can add a profile to the *.tests plugins and specify the profile
Thanks! I eventually figured out I can add a profile to the *.tests plugins and specify the profile when I kick off the build (-Dskip-ui-tests in this case).
But I think -Dmaven.skip.test is more straightforward. Oh well...
And yes we are using tycho 0.13.0-SNAPSHOT right now.
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<graycol.gif>Alex Blewitt ---07/06/2011 05:32:43 PM---Sorry, that should have been -Dmaven.skip.test in the first case. Sent from my iPod
Sorry, that should have been -Dmaven.skip.test in the first case.
Sent from my iPod
On 6 Jul 2011, at 21:48, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:
Running mvn -Dtest.skip.test (or mvn -DskipTests) is the normal way to do it - but I think that it is only supported in tycho 0.13.Snapshot at the moment.
Alex
Sent from my iPod
On 6 Jul 2011, at 20:37, "Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx> wrote:
1) Nope. Comment them out?
2) Nope. Run an mv command after?
Sorry, out of answers for these. I’m pretty new to this stuff too.
Doug
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Wednesday, July 06, 2011 3:35 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 OK Thanks.
Do you know if there is a way to turn off running the JUnit tests? I just want to see if the build runs with no errors and packages the zip file correctly.
Also is there a way to rename the zip file?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/06/2011 03:28:07 PM---Well, if I have to hazard a guess, I'd put the profile in the pom.xml file for cdt.repo. I think the
Well, if I have to hazard a guess, I’d put the profile in the pom.xml file for cdt.repo. I think the pluginRepositories part probably should go in the top level pom with the rest of them.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Wednesday, July 06, 2011 3:15 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 So would I be adding the profile to pom.xml in cdt.repo or the top level pom.xml?
If I'm adding to top level pom.xml, where should I add the profile?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/06/2011 03:12:25 PM---That would be the org.eclipse.cdt.repo project. From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bo
That would be the org.eclipse.cdt.repo project.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Wednesday, July 06, 2011 3:04 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 Ah I see.
I found this post about Eclipse signing with Tycho:
http://aniszczyk.org/2011/05/18/eclipse-org-signing-support-for-maven-tycho/
It said to add the profile to the module that generates the p2 repository. Which module is that for our build?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/06/2011 02:12:21 PM---Excellent :). For #1, these platforms have been removed from Eclipse 3.7 and maven fails when trying
Excellent J.
For #1, these platforms have been removed from Eclipse 3.7 and maven fails when trying to build for them (no SWT fragment). They might be still there in 3.6. This is one area where maven is more picky than PDE build. Note that when adding them back, make sure you add the <environment> entries to the root pom.xml file as well.
For #2, I remove the source bundles from the non-Java projects since maven was failing on them. If there’s no source, there’s no need for a source bundle I guess. Unless it causes problems on the upgrade, I’d say it’s fine.
Doug
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Wednesday, July 06, 2011 1:57 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 Thanks so much Doug!
I got Maven setup on my Windows laptop and kicked off a test build.
I compared the build I got (org.eclipse.cdt.repo.zip) to the last 7.0.x build and saw these differences:
1. cdt.core.ia64, cdt.core.ppc, cdt.core.qnx are missing
2. source bundles for some of the cdt.core.[platform] plugins are not generated
3. sdk feature and source feature/bundles for cdt.xlc and cdt.core.parser.upc features are not generated
I think I can fix #1 but for 2 and 3 I'm not sure how to fix them and I need your help.
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/05/2011 11:06:47 PM---I pushed my final changes. cdt_7_0 builds for me. I haven't tried it mind you to make sure it actual
|
|
|
|
|
|
|
|
|
|
|
Re: [cdt-dev] Mavenize cdt_7_0
|
|
|
|
I pushed my final changes. cdt_7_0 builds for me. I haven’t tried it mind you to make sure it actually runs.
Cheers and thanks Vivian,
Doug
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Tuesday, July 05, 2011 8:48 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 Thanks!
I have just made a few more changes:
- Add Codan feature to top level pom.xml (since Codan wasn't part of the cdt feature in cdt_7_0)
- Add pom.xml to codan feature
- change lrparser project names
- update category.xml and add codan, lrparser, p2 features
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/05/2011 07:33:13 PM---Actually, I think Mike K asked us to remove the c99 plugins and that they weren't used anywhere. I h
Thanks Doug. I have updated the msw feature and plugin from the top level pom.xml
Finally know why I don't see lrparser and lrparser.test plugins. They are named o.e.cdt.core.parser.c99 and o.e.cdt.core.parser.c99.tests for some reason. Can we change this?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/05/2011 05:51:09 PM---Running a test build now. You need to remove the msw plug-in and feature from the top level pom.xml.
|
|
|
|
|
|
|
|
|
|
|
Re: [cdt-dev] Mavenize cdt_7_0
|
|
|
|
Running a test build now. You need to remove the msw plug-in and feature from the top level pom.xml.
Still not sure what you mean by the lrparser stuff missing. I have it here. In fact you put the pom.xml files into those projects directories.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Tuesday, July 05, 2011 5:42 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 I have check in my changes so far to cdt_7_0. I'd appreciate it if you can take a look and see if I missed anything. Thanks.
The lrparser and lrparser.tests plugins are missing in the cdt_7_0 branch and they were in cdt_7_0 in CVS. Were they missed when we move to Git?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/05/2011 05:36:21 PM---Also bring the .gitignore file from the root over too to hide the bin and target directories. From:
Also bring the .gitignore file from the root over too to hide the bin and target directories.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer, Doug
Sent: Tuesday, July 05, 2011 5:18 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0
Not sure what you mean. If a feature isn’t in CDT 7.0.x then you can’t add it now. That would require a release review.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Tuesday, July 05, 2011 4:28 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 I just realize org.eclipse.cdt.core.lrparser and org.eclipse.cdt.core.lrparser.tests plugins are not in cdt_7_0. Can you please add them back?
Also, should org.eclipse.cdt.msw-feature be in cdt_7_0 as well?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/05/2011 03:58:12 PM---And, yes the repo. That's the project that builds the p2 repo. It replaces the master feature. You n
And, yes the repo. That’s the project that builds the p2 repo. It replaces the master feature. You need that too J.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Vivian Kong
Sent: Tuesday, July 05, 2011 3:54 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Mavenize cdt_7_0 Oh and what is org.eclipse.cdt.repo? Do I need to create that in cdt_7_0?
Regards,
Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
<image001.gif>"Schaefer, Doug" ---07/05/2011 03:49:06 PM---No, I just use the XML Editor from the Indigo repo, or even emacs. They're pretty simple files. They
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
