Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Antwort: Re: Automatically keeping version numbers in sync

On Fri, Jun 22, 2012 at 7:46 AM,  <marc.breitling@xxxxxxxxxxxxxxxx> wrote:
>
> tycho-user-bounces@xxxxxxxxxxx schrieb am 22.06.2012 05:21:12:
>
>> On Fri, Jun 22, 2012 at 11:11 AM, Igor Fedorenko <igor@xxxxxxxxxxxxxx>
>> wrote:
>> > For any given project the release process can be easily automated with a
>> > trivial shell script. Not sure why you need somebody manually change
>> > files...
>>
>> Fair enough.
>> Its always been low on the priority list, an acceptable burden to bear
>> because a better way was always coming.
>>
>> I'd rather it all just worked as part of the maven release process and
>> avoid having to write a script.
>> Fixing it with a script would remove the pain and stop me wanting to
>> get the release process fixed  :)
> Don't know if it will fit for you, but in our environment we got an
> "one-click" jenkins solution with release-build plugin in combination with
> ant-scripts.
> PreReleaseBuild:
> Changing version in pom and manifest from 1.0.0-SNAPSHOT to 1.0.0.FINAL
> using tycho-versions-plugin:set-version.
>
> PostReleaseBuild:
> If the build was successful the working copy will be tagged. Afterwards we
> increment the minor version (1.0.0.FINAL => 1.1.0-SNAPSHOT) and then again
> use tycho-versions-plugin:set-version to change manifest and pom. We have
> reserved the mirco version for bugfixes, so we only have to manage the
> minor, which simplyfies automation. The last step is checkin to repository.
>
> RevertChanges:
> If the release build fails, we revert the changes.
>
>
> With these scripts we are able to release our plugins with nearly one click
> via jenkins. As mentioned above - it works for our environment.
> Perhaps it helps to achieve your goal.
>
>
> Greets Marc

Do you also auto-update the version numbers in the .product files?
With 0.15.0 I the tycho-versions-plugins skips my .product files,
might be related to this:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=358292

When the target is resolved (there is no phase before this that can be
interacted with as I understand) the versions for eg. feature
dependencies must be valid. This means that the product files must be
updated BEFORE the target is resolved and since the
tycho-versions-plugin skips these files I have still not found a way
to do this automatically :-(





>
> If you are not the intended addressee, please inform us immediately that you
> have received this e-mail in error, and delete it. We thank you for your
> cooperation.
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
>


Back to the top