[Jenkins-events] Fwd: Stickers + t shirts
Alyssa Tong
alytong13 at gmail.com
Fri Oct 28 16:51:39 UTC 2016
Hi Enio,
Apologies as I was not clear. The blog needs to be publishable, quality
content. This means a lot of time and effort needs to be put into it.
Here are some quality worthy blogs as examples: sample 1
<https://jenkins.io/blog/2016/08/11/speaker-blog-edx-jenkins-world/>, sample
2 <https://jenkins.io/blog/2016/08/17/jenkins-world-speaker-blog-aquilent/>
thanks,
alyssa
On Thu, Oct 27, 2016 at 12:03 PM, Enio Machado <
enio.machado at magazineluiza.com.br> wrote:
> Hi Alyssa,
> yes, sure.
>
> Basically I setup Jenkins for two projects. The jenkins this Deployado in
> a weblogic.
>
>
>
>
> First project, I've set some shell scripts to perform the updating of
> docker containers of a billing system (developed with angular js).
> The shell script I created from the beginning was to facilitate the
> updating of the containers, which are in total 7-8.
> When I finished this shell scripts, I wanted to work with jenkins to
> orchestrate these demands as the need to deploy (updating).
> The artifacts are updated developed in the bit bucket by developers.
>
>
>
>
>
>
>
> For the second project was performed an integration together with jenkins
> + maven to deploy bpel process of financial processes.
> BPEL processes are updated in bitbucket, and as the demand for updating,
> our team performs deploy activity.
>
>
>
>
> The idea is that for activities in dev and test environments, the own
> developers have autonomy to execute the activities.
>
> Pain Points:
>
> Synchronize Jenkins with AD (Active Directory) for authentication, and
> then segregate execution of jenkins jobs by User.
>
>
> We still in test.
>
> Any doubts please contact me.
>
> Thank you,
>
> Em 27 de outubro de 2016 14:38, Alyssa Tong <alytong13 at gmail.com>
> escreveu:
>
>> Hi Enio,
>>
>> Typically, we use swags for events and meetups, I would be happy to send
>> some shirts and stickers to you in exchange for a technical blog. It would
>> be great to see how you and your team are using Jenkins, what were the pain
>> points and how you solved it.
>>
>> thnx
>> alyssa
>>
>> 2016-10-27 4:28 GMT-07:00 Enio Machado <enio.machado at magazineluiza.com.br
>> >:
>>
>>> Hi Alyssa,
>>> How are you?
>>>
>>> we have about 22 people in our team.
>>> If you can, send for us 22 stickers and 10 t-shirts.
>>>
>>> I appreciate thanks a lot,
>>>
>>> 2016-10-26 18:26 GMT-02:00 Alyssa Tong <alytong13 at gmail.com>:
>>>
>>>> Hi Enio,
>>>>
>>>> How many stickers and t-shirts do you have in mind?
>>>>
>>>> thnx
>>>> alyssa
>>>>
>>>> ---------- Forwarded message ----------
>>>>> From: Oleg Nenashev <o.v.nenashev at gmail.com>
>>>>> Date: 2016-10-26 12:44 GMT-07:00
>>>>> Subject: [Jenkins-events] Fwd: Stickers + t shirts
>>>>> To: events at lists.jenkins-ci.org
>>>>> Cc: enio.machado at magazineluiza.com.br
>>>>>
>>>>>
>>>>> Hi Enio,
>>>>>
>>>>> Have we met before?
>>>>> Anyway, I'm forwarding it to the Events team.
>>>>>
>>>>> BR, Oleg
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: Enio Machado <enio.machado at magazineluiza.com.br>
>>>>> Date: 2016-10-26 21:07 GMT+02:00
>>>>> Subject: Stickers + t shirts
>>>>> To: o.v.nenashev at gmail.com
>>>>>
>>>>>
>>>>> Hi ,
>>>>> we've implemented jenkins in our company to test all your
>>>>> orchestration and availability for deployments, and we are having a good
>>>>> experience.
>>>>>
>>>>> Could you please send for us some stickers and t shirts jenkins: Thank
>>>>> you.
>>>>>
>>>>> Address:
>>>>>
>>>>> Enio Machado de Oliveira
>>>>> Rua do comercio 1926, Franca - SP, Centro
>>>>> Brazil
>>>>> CEP 14400-660
>>>>>
>>>>> Kindly,
>>>>>
>>>>>
>>>>> <https://magazineluiza.onelink.me/589508454?pid=AssinaturaEmail&c=MagazineLuiza>
>>>>>
>>>>> *‘Esta mensagem é direcionada apenas para os endereços constantes no
>>>>> cabeçalho inicial. Se você não está listado nos endereços constantes no
>>>>> cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa
>>>>> mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão
>>>>> imediatamente anuladas e proibidas’.*
>>>>>
>>>>> *‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para
>>>>> assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não
>>>>> poderá aceitar a responsabilidade por quaisquer perdas ou danos causados
>>>>> por esse e-mail ou por seus anexos’.*
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Jenkins-events mailing list
>>>>> Jenkins-events at lists.jenkins-ci.org
>>>>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-events
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> <https://magazineluiza.onelink.me/589508454?pid=AssinaturaEmail&c=MagazineLuiza>
>>>
>>> *‘Esta mensagem é direcionada apenas para os endereços constantes no
>>> cabeçalho inicial. Se você não está listado nos endereços constantes no
>>> cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa
>>> mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão
>>> imediatamente anuladas e proibidas’.*
>>>
>>> *‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para
>>> assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não
>>> poderá aceitar a responsabilidade por quaisquer perdas ou danos causados
>>> por esse e-mail ou por seus anexos’.*
>>>
>>
>>
>
>
> <https://magazineluiza.onelink.me/589508454?pid=AssinaturaEmail&c=MagazineLuiza>
>
> *‘Esta mensagem é direcionada apenas para os endereços constantes no
> cabeçalho inicial. Se você não está listado nos endereços constantes no
> cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa
> mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão
> imediatamente anuladas e proibidas’.*
>
> *‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para
> assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não
> poderá aceitar a responsabilidade por quaisquer perdas ou danos causados
> por esse e-mail ou por seus anexos’.*
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-events/attachments/20161028/880b4660/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Selection_023.png
Type: image/png
Size: 156381 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-events/attachments/20161028/880b4660/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Selection_026.png
Type: image/png
Size: 73688 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-events/attachments/20161028/880b4660/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Selection_022.png
Type: image/png
Size: 100921 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-events/attachments/20161028/880b4660/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Selection_024.png
Type: image/png
Size: 107347 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-events/attachments/20161028/880b4660/attachment-0007.png>
More information about the Jenkins-events
mailing list