Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Reproducible Version Qualifiers with only using the git info 
Hi Ed,
even though I don't understand the whole story/problem in deep I'm in the comfortable situation that I control the whole build/deploy cycle and so some things are might be more relaxed for my case.
Anyways if you feel something is missing for jgit-timestamp or not working as exspected, it would be good to open an issue here https://github.com/eclipse/tycho/issues so people can get aware of it an maybe enhance.
As I'll give git-timestmaps a try I even will improve things here myself if I get aware of them. 

Am 21.04.21 um 14:52 schrieb Ed Willink:

Hi
The jgit timestamp provider is an attractive replacement for the Buckminster reference repo and I adopted it for the OCL builds and encouraged UML2 to adopt it too.
However if you read through https://bugs.eclipse.org/bugs/show_bug.cgi?id=529933 you will see my initial enthusiasm for the jgit timestamp provider turn into a realisation that it is unsound in general. But if you have special constraints it may nonetheless be ok for you. 

My builds now always churn qualifiers.

     Regards

         Ed Willink

On 21/04/2021 08:53, Mickael Istria wrote:
On Wed, Apr 21, 2021 at 9:29 AM Christoph Läubrich <laeubi@xxxxxxxxxxxxxx <mailto:laeubi@xxxxxxxxxxxxxx>> wrote: 

    "Version qualifier is calculated based on timestamp of the most
    recent
    commit that touches any file under project base directory"

    so project basedir = "bundle" and not "git-tree"?


     > But it would still be possible to build such a strategy

    would I need a new one or could the jgit be configured to behave that
    way?
You should already be able to use the jgit timastamp provider without using baseline. 

    So do I can assume that this might be uncommon but working
    use-case or
    will it break something?


Yes, it's a working use-case.

    ... I think that would be a really cool feature to have such
    "incremental-build" support in tycho :-)
I don't think it fits the Maven/Tycho layer and their related build model, it's more operating a build strategy, a bit higher-level than just a build tool. 

    one problem I have stumpled in the past was that the features
    don't get
    rebuild (as there is no change from maven POV). I don't know if
    this is
    just unsupprted or I just configured something wrong.
It's a bit tricky: feature qualifier do depend on the change in the feature folder and on content of the feature. Features sometimes require to be "touched" manually for version changes to cascade into them. For your case, since building features is usually very cheap, you may want to try first filtering out only untouched bundles but keep building all features anyway. 

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/tycho-user
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user

Back to the top