Eclipse Community Forums: Buckminster dev » Buckminster code-base has moved to Git

Home » Eclipse Projects » Buckminster dev » Buckminster code-base has moved to Git

Buckminster code-base has moved to Git [message #690332]

Wed, 29 June 2011 07:44

Eclipse User

Hi,

Being on vacation is funny. Suddenly you are confined to a laptop and
using your cellphone as an internet gateway. Materializing a workspace
with the Buckminster code base in that environment is challenging when
using SVN. This gave me the final incentive to go ahead and resolve:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=341718
"Move Buckminster code base to Git"

The transition is now complete and I was just able to materialize a
brand new workspace (still using my cellphone) in less than 3 minutes.

Bye bye SVN...

- thomas

PS.
This means that we're switching qualifier generation on all Buckminster
features and bundles since we no longer can rely on the SVN revision
number. Git commit-id's doesn't come in lexical order so we will
henceforth use timestamps.

Re: Buckminster code-base has moved to Git [message #690359 is a reply to message #690332]

Wed, 29 June 2011 08:08

Eclipse User

Woo Hoo!!
- henrik
On 6/29/11 1:44 PM, Thomas Hallgren wrote:
> Hi,
>
> Being on vacation is funny. Suddenly you are confined to a laptop and
> using your cellphone as an internet gateway. Materializing a workspace
> with the Buckminster code base in that environment is challenging when
> using SVN. This gave me the final incentive to go ahead and resolve:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=341718
> "Move Buckminster code base to Git"
>
> The transition is now complete and I was just able to materialize a
> brand new workspace (still using my cellphone) in less than 3 minutes.
>
> Bye bye SVN...
>
> - thomas
>
> PS.
> This means that we're switching qualifier generation on all Buckminster
> features and bundles since we no longer can rely on the SVN revision
> number. Git commit-id's doesn't come in lexical order so we will
> henceforth use timestamps.

Re: [buckminster-dev] Buckminster code-base has moved to Git [message #690511 is a reply to message #690359]

Wed, 29 June 2011 11:56

Eclipse User

"Being on vacation" and "materializing a workspace" should not be in the same paragraph ;).<div><br></div><div>Good work Thomas!</div><div><br></div><div>Btw, are you maintaining stable qualifiers? That is, if a bundle doesn't change from build to build are you ensuring that the qualifiers remain the same? I'm trying to get a sense of how people are doing this with git. </div>
<div><br></div><div>Cheers,</div><div>Ian</div><div><br><div class="gmail_quote">On Wed, Jun 29, 2011 at 5:08 AM, Henrik Lindberg <span dir="ltr"><<a href="mailto:henrik.lindberg@cloudsmith.com">henrik.lindberg@cloudsmith.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Woo Hoo!!<br><font color="#888888">
- henrik</font><div><div></div><div class="h5"><br>
On 6/29/11 1:44 PM, Thomas Hallgren wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Being on vacation is funny. Suddenly you are confined to a laptop and<br>
using your cellphone as an internet gateway. Materializing a workspace<br>
with the Buckminster code base in that environment is challenging when<br>
using SVN. This gave me the final incentive to go ahead and resolve:<br>
<br>
<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=341718" target="_blank">https://bugs.eclipse.org/bugs/<u></u>show_bug.cgi?id=341718</a><br>
"Move Buckminster code base to Git"<br>
<br>
The transition is now complete and I was just able to materialize a<br>
brand new workspace (still using my cellphone) in less than 3 minutes.<br>
<br>
Bye bye SVN...<br>
<br>
- thomas<br>
<br>
PS.<br>
This means that we're switching qualifier generation on all Buckminster<br>
features and bundles since we no longer can rely on the SVN revision<br>
number. Git commit-id's doesn't come in lexical order so we will<br>
henceforth use timestamps.<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
buckminster-dev mailing list<br>
<a href="mailto:buckminster-dev@eclipse.org" target="_blank">buckminster-dev@eclipse.org</a><br>
<a href="https://dev.eclipse.org/mailman/listinfo/buckminster-dev" target="_blank">https://dev.eclipse.org/<u></u>mailman/listinfo/buckminster-<u></u>dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>R. Ian Bull | EclipseSource Victoria | +1 250 477 7484<br><a href="http://eclipsesource.com">http://eclipsesource.com</a> | <a href="http://twitter.com/eclipsesource">http://twitter.com/eclipsesource</a><br>

</div>

Re: [buckminster-dev] Buckminster code-base has moved to Git [message #690601 is a reply to message #690511]

Wed, 29 June 2011 15:50

Eclipse User

On 2011-06-29 17:56, Ian Bull wrote:
> "Being on vacation" and "materializing a workspace" should not be in the
> same paragraph ;).
>
I agree. It really shouldn't but I find the thought that I do some
things just for fun comforting. Nobody could claim that this wasn't
according what was planned for the next sprint :-)

> Good work Thomas!
>
> Btw, are you maintaining stable qualifiers? That is, if a bundle doesn't
> change from build to build are you ensuring that the qualifiers remain
> the same? I'm trying to get a sense of how people are doing this with git.
>
Buckminster has a qualifier generator that finds the latest commit that
affects a given subtree (in this case a project). We use the timestamp
of such commits directly for plug-in qualifiers. For features, we
calculate the last timestamp for all included features, plug-ins, and
the feature project itself and use that. There are some corner cases
when this approach isn't fail proof but the way we use it, it works
perfectly. Our qualifiers will remain the same as long as our code is
unchanged.

- thomas

Re: [buckminster-dev] Buckminster code-base has moved to Git [message #691165 is a reply to message #690601]

Thu, 30 June 2011 17:15

Eclipse User

<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Btw, are you maintaining stable qualifiers? That is, if a bundle doesn't<br>
change from build to build are you ensuring that the qualifiers remain<br>
the same? I'm trying to get a sense of how people are doing this with git.<br>
<br>
</blockquote></div>
Buckminster has a qualifier generator that finds the latest commit that affects a given subtree (in this case a project). We use the timestamp of such commits directly for plug-in qualifiers. For features, we calculate the last timestamp for all included features, plug-ins, and the feature project itself and use that. There are some corner cases when this approach isn't fail proof but the way we use it, it works perfectly. Our qualifiers will remain the same as long as our code is unchanged.<br>
</blockquote><div> </div><div>And this works with Git?</div><div><br></div><div>I wonder if this work could be reused in Eclipse Releng Tool [1].</div><div><br></div><div>[1] <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=328745">https://bugs.eclipse.org/bugs/show_bug.cgi?id=328745</a></div>
<meta http-equiv="content-type" content="text/html; charset=utf-8"><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><font color="#888888">
<br>
- thomas</font><div><div></div><div class="h5"><br>
______________________________<u></u>_________________<br>
buckminster-dev mailing list<br>
<a href="mailto:buckminster-dev@eclipse.org" target="_blank">buckminster-dev@eclipse.org</a><br>
<a href="https://dev.eclipse.org/mailman/listinfo/buckminster-dev" target="_blank">https://dev.eclipse.org/<u></u>mailman/listinfo/buckminster-<u></u>dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>R. Ian Bull | EclipseSource Victoria | +1 250 477 7484<br><a href="http://eclipsesource.com">http://eclipsesource.com</a> | <a href="http://twitter.com/eclipsesource">http://twitter.com/eclipsesource</a><br>

Re: [buckminster-dev] Buckminster code-base has moved to Git [message #691293 is a reply to message #691165]

Fri, 01 July 2011 03:21

Eclipse User

On 2011-06-30 23:15, Ian Bull wrote:
>
> Btw, are you maintaining stable qualifiers? That is, if a bundle doesn't
> change from build to build are you ensuring that the qualifiers remain
> the same? I'm trying to get a sense of how people are doing this with git.
>
> Buckminster has a qualifier generator that finds the latest commit that affects a given subtree (in this case a
> project). We use the timestamp of such commits directly for plug-in qualifiers. For features, we calculate the last
> timestamp for all included features, plug-ins, and the feature project itself and use that. There are some corner
> cases when this approach isn't fail proof but the way we use it, it works perfectly. Our qualifiers will remain the
> same as long as our code is unchanged.
>
> And this works with Git?
>
Yes, indeed.

> I wonder if this work could be reused in Eclipse Releng Tool [1].
>
The relevant code can be viewed here:

http://git.eclipse.org/c/buckminster/buckminster.git/tree/org.eclipse.buckminster.git/src/org/eclipse/buckminster/git/internal/GitReaderType.java

Take a look at the method getLastModification() at line 103

Regards,
Thomas Hallgren

Previous Topic:	Problem building rcp product with buckminster
Next Topic:	[buckminster-dev] Project meta data is out of date for tools.buckminster

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Apr 23 00:34:25 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter