jtreg jenkins builds 4.1 and calls it 4.2-snapshot

Thu May 14 23:17:12 UTC 2015

Hi Stanislav,

The script is ready for your review and amendments. Thanks for pointing
things out to us, always a good feeling when things are improved.

Cheers,
Mani

On Thu, May 14, 2015 at 11:02 PM, Mani Sarkar <sadhak001 at gmail.com> wrote:

> Stanislav,
>
> I recollect our decision to have -SNAPSHOT and the -b11... versions, and
> to keep them the same, as we were of the idea that we would use the
> -SNAPSHOT version to publish the artefact to the maven central repo.
>
> But I think its a good time to scrap the -SNAPSHOT and use it to build the
> tip instead, but do you want to called it 4.2.0-SNAPSHOT? or 4.2.0-tip? I
> prefer the later, so if you like please go ahead and amend the script for
> us or I can do it for you, as our scripts are pretty much the same in
> principle and steps.
>
> Cheers,
> Mani
>
> On Thu, May 14, 2015 at 10:52 PM, Mani Sarkar <sadhak001 at gmail.com> wrote:
>
>> Hi Stanislav,
>>
>> Your script looks good, very similar to ours on the Cloudbees instance
>> (just did a compare). Except we don't build from tip and tag.
>>
>> We will be happy to get good parts of your script - I like the version
>> numbers you have been extracting.
>>
>> The last I remember (let me dig the emails) that we were adviced to build
>> from the tag, hence this line:
>>
>> tagName=$(hg tags | grep jtreg | head -1 | gawk '{ print $1 }')
>>
>> and then
>>
>> hg clone http://hg.openjdk.java.net/code-tools/jtreg -r ${tagName}
>>
>> I'll tidy up the script so that we can improve this script.
>>
>> Cheers,
>> Mani
>>
>> On Wed, May 13, 2015 at 2:18 PM, Stanislav Baiduzhyi <sbaiduzh at redhat.com
>> > wrote:
>>
>>> So, inspired by original script but heavily reorganized to build both
>>> tip and
>>> latest tag:
>>> https://gist.github.com/TheIndifferent/8573be7b18c2fdcf772f
>>>
>>> As can be seen in the logs of latest builds, asmtools was missing, so
>>> had to
>>> expand that one. And build now happens 2 times, one of them is for
>>> latest tag
>>> left without much modification, and added the current tip building as
>>> 4.2.0
>>> snapshot.
>>>
>>> Main concern at the moment is when the project will move to 4.3
>>> snapshots the
>>> hardcoded constant has to be modified.
>>>
>>> Would like to hear any objections or improvement suggestions, maybe it
>>> will
>>> make sense to follow jenkins advice and add that script to the source
>>> repo and
>>> launch from there...
>>>
>>> On Wednesday 13 May 2015 11:49:00 Martijn Verburg wrote:
>>> > Hi Stanislav,
>>> >
>>> > You've been added.  Mani is the original author for the build scripts
>>> here
>>> > so you'll want to get a review from him.
>>> >
>>> > Cheers,
>>> > Martijn
>>> >
>>> > On 13 May 2015 at 11:42, Stanislav Baiduzhyi <sbaiduzh at redhat.com>
>>> wrote:
>>> > > Hi Martijn,
>>> > >
>>> > > Thanx for fast response. I've just created an account via github,
>>> login
>>> > > TheIndifferent, email baiduzhyi.devel at gmail.com.
>>> > >
>>> > > I am confident but I would not like to do something without
>>> approval, so
>>> > > my
>>> > > plan is to check current build configuration and propose changes to
>>> this
>>> > > mailing list first, and apply them if there will be no objections.
>>> > >
>>> > > On Wednesday 13 May 2015 11:17:22 Martijn Verburg wrote:
>>> > > > Hi Stanislav,
>>> > > >
>>> > > > Do you have a Cloudbees account?  Happy to add you if you're
>>> confident
>>> > > > on
>>> > > > Jenkins and OpenJDK build matters.
>>> > > >
>>> > > > Cheers,
>>> > > > Martijn
>>> > > >
>>> > > > On 13 May 2015 at 10:08, Stanislav Baiduzhyi <sbaiduzh at redhat.com>
>>> > >
>>> > > wrote:
>>> > > > > I was wondering why jtreg 4.2-SNAPSHOT on jenkins does not
>>> include any
>>> > > > > changes
>>> > > > > since 2 month ago. Doing small investigation, here is the result:
>>> > > > > 4.2-SNAPSHOT
>>> > > > > and 4.1-b11 is the same package, taken from the tag jtreg4.1-b11
>>> in
>>> > >
>>> > > jtreg
>>> > >
>>> > > > > source.
>>> > > > >
>>> > > > > Could anyone please look at that, or give me permissions to fix
>>> it
>>> > >
>>> > > myself?
>>> > >
>>> > > > > --
>>> > > > > Regards,
>>> > > > >
>>> > > > >     Stas
>>> > >
>>> > > --
>>> > > Regards,
>>> > >
>>> > >     Stas
>>>
>>> --
>>> Regards,
>>>     Stas
>>>
>>>
>>
>>
>> --
>> @theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
>> <http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
>> (@adoptopenjdk & @adoptajsr programs)
>> *Meet-a-Project - *MutabilityDetector
>> <https://github.com/MutabilityDetector>*  |  **Bitbucket
>> <https://bitbucket.org/neomatrix369>* * |  **Github
>> <https://github.com/neomatrix369>* * |  **LinkedIn
>> <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
>> *Come to Devoxx UK 2015:* http://www.devoxx.co.uk/
>>
>> *Don't chase success, rather aim for "Excellence", and success will come
>> chasing after you!*
>>
>
>
>
> --
> @theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
> <http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
> (@adoptopenjdk & @adoptajsr programs)
> *Meet-a-Project - *MutabilityDetector
> <https://github.com/MutabilityDetector>*  |  **Bitbucket
> <https://bitbucket.org/neomatrix369>* * |  **Github
> <https://github.com/neomatrix369>* * |  **LinkedIn
> <http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
> *Come to Devoxx UK 2015:* http://www.devoxx.co.uk/
>
> *Don't chase success, rather aim for "Excellence", and success will come
> chasing after you!*
>

-- 
@theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
<http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
(@adoptopenjdk & @adoptajsr programs)
*Meet-a-Project - *MutabilityDetector
<https://github.com/MutabilityDetector>*  |  **Bitbucket
<https://bitbucket.org/neomatrix369>* * |  **Github
<https://github.com/neomatrix369>* * |  **LinkedIn
<http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
*Come to Devoxx UK 2015:* http://www.devoxx.co.uk/

*Don't chase success, rather aim for "Excellence", and success will come
chasing after you!*