On 23 Jun 2015, at 21:13, Nick Boldt wrote:
not quite.
Last time I suggested we created a file with a line for each repo, like:
jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1
You had a txt file before that had this information but in a
hard-to-parse format.
I can try parse the buildinfo.json too but thought if you had the
simpler one I could use that instead.
/max
On 06/23/2015 01:10 PM, Max Rydahl Andersen wrote:
> remind me where I can get the list of repo, sha-1 and i'll make this
> happen on all of them.
>
> /max
>
>> Component leads, please tag your repositories!
>>
>> $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is
>> called jbosstools, also often called origin
>> $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD
>> $ git push jbosstools jbosstools-4.3.0.Beta1
>>
>>
>> --
>> Nick Boldt :: JBoss by Red Hat
>> Productization Lead :: JBoss Tools & Dev Studio
>>
http://nick.divbyzero.com
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> /max
>
http://about.me/maxandersen
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
/max
http://about.me/maxandersen