Thank you to both of you for your answers. I was thinking about creating
services but my db is created then deleted during the build I was not sure
it was a good practice (and if it is possible) to create dynamically (and
delete then) a service directly from the jenkinsfile yaml.

I will try

Regards (and good Jenkins world for people attending it !)



Le mar. 18 sept. 2018 à 05:01, Jonathan Rogers <[email protected]>
a écrit :

> On 9/17/18 10:47 PM, Carlos Sanchez wrote:
> > You need to use services if you want to expose pods
> > If you put everything in one pod, you can use localhost to talk between
> > containers
>
> I'm not sure if you meant to respond to me or to Tristan FAURE. I would
> also recommend using a service to allow processes in one pod to connect
> to a server in another. However, as Tristan implies, defining a service
> isn't strictly necessary. For example, to determine the IP address for a
> pod if you know its name is "thingy", you could use a command like:
>
> kubectl get pod thingy -o=jsonpath='{.status.podIP}'
>
> --
> Jonathan Rogers
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/6nYxOrwZ5LQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/0ca2a728-8055-8fca-9825-d8070f153cab%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BtQ8YMrSwab28Q_r1KLOwhscCC5Co5gn%3Ddd8mQQs-f4m-hWHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to