ullspec which points to
the the imagestream, e.g.:
internalregistry.com/imagestreamnamespace/imagestreamname:imagestreamtag
>
> Thanks,
> Luiz
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
&g
ting a 403.
>
Thanks, that explanation helps.
> On Thu, Oct 3, 2019 at 11:18 AM Ben Parees wrote:
>
>>
>>
>> On Thu, Oct 3, 2019 at 10:52 AM David Eads wrote:
>>
>>> There is no plan to switch to 401.
>>>
>>
>> Would plans be created
for your answers!
>>>>>> André
>>>>>>
>>>>>> ___
>>>>>> dev mailing list
>>>>>> dev@lists.openshift.redhat.com
>>>>>> http://lists.op
/installing_vsphere/installing-vsphere.html#installation-registry-storage-config_installing-vsphere
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
t=webmail>
> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_-605702793579341_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
&g
On Thu, Jun 21, 2018 at 4:00 PM, Charles Moulliard
wrote:
>
>
> On Thu, Jun 21, 2018 at 4:21 PM, Ben Parees wrote:
>
>>
>>
>> On Thu, Jun 21, 2018 at 6:36 AM, Charles Moulliard
>> wrote:
>>
>>> Hi Charles,
>>>
>>> The info s
gt;>>>> ig/buildconfig_controller.go
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Charles
>>>>>> ___
>>>>>> dev mailing list
>>>>>> dev@lists.openshift.redhat.com
>>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> TAKO SCHOTANUS
>>>>>
>>>>> SENIOR SOFTWARE ENGINEER
>>>>>
>>>>> Red Hat
>>>>>
>>>>> <https://www.redhat.com/>
>>>>> <https://red.ht/sig>
>>>>>
>>>>>
>>>>
>>>
>>> --
>>>
>>> TAKO SCHOTANUS
>>>
>>> SENIOR SOFTWARE ENGINEER
>>>
>>> Red Hat
>>>
>>> <https://www.redhat.com/>
>>> <https://red.ht/sig>
>>>
>>> ___
>>> dev mailing list
>>> dev@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>
>>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
Had you recently created the project? It takes some time for the default
secrets to be created after a new project/namespace is created and if you
start a build before then, you can see this issue.
Ben Parees | OpenShift
On Thu, May 31, 2018, 02:57 Tran Tien Dung wrote:
> Hi,
> Someth
care
about:
https://github.com/openshift/origin/pull/17314/commits/fc47ea3baba0631ba84e82a80a98c10670dabbd8
>
> Simo.
>
> --
> Simo Sorce
> Sr. Principal Software Engineer
> Red Hat, Inc
>
> ___
> dev mailing list
> d
a checkbox for it. But also…
>
>
> * Invalid value: "hostPath": hostPath volumes are not allowed to be used*
>
You'll have to take that up w/ Kubernetes plugin maintainers:
https://plugins.jenkins.io/kubernetes
Hence my recommendation you use DOCKER_HOST instead.
>
>
&g
gt; existing/legacy projects not having docker.sock is quite a hill to climb.
>
> Thanks for your advice though, that has been gratefully received.
>
> Alan.
>
> On 5 Dec 2017, at 13:41, Ben Parees wrote:
>
>
>
>
>
> On Dec 5, 2017 07:57, "Alan Christie"
On Dec 5, 2017 07:57, "Alan Christie"
wrote:
I’m using Jenkins from the CI/CD catalogue and am able to spin up slaves
and use an `ImageStream` to identify my own slave image. That’s useful, but
what I want to be able to do is build and run Docker images, primarily for
unit/functional test purpose
l and/or criminal penalties as detailed in as amended Privacy
> Act of 1974 and DoD 5400.11-R.
>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
enshift/origin/_output/local/go/src/github.com/
> openshift/origin/test/integration/dockerregistryclient_test.go:57 +0x30
> github.com/openshift/origin/test/integration.retryWhenUnreachable(
> 0xc4211a8000, 0xc420045d98, 0x0, 0x0, 0x0, 0x0, 0x600)
> /root/go/src/github.com/openshift/origin/_outp
t to do. Jeff
Cantril can point you to it.
>
> Thanks!
>
> --
>
> TAKO SCHOTANUS
>
> SENIOR SOFTWARE ENGINEER
>
> Red Hat
>
> <https://www.redhat.com/>
> <https://red.ht/sig>
>
>
> ______
On Fri, Aug 11, 2017 at 12:07 PM, Bamacharan Kundu
wrote:
>
>
> On 08/11/2017 09:22 PM, Ben Parees wrote:
> >
> >
> > On Fri, Aug 11, 2017 at 11:09 AM, Bamacharan Kundu > <mailto:bku...@redhat.com>> wrote:
> >
> > Hi Ben,
&
On Fri, Aug 11, 2017 at 11:09 AM, Bamacharan Kundu
wrote:
> Hi Ben,
>
> On 08/11/2017 07:37 PM, Ben Parees wrote:
> >
> >
> > On Thu, Aug 10, 2017 at 12:48 PM, Bamacharan Kundu > <mailto:bku...@redhat.com>> wrote:
> >
> > Hi,
&
t;: "ImageStreamTag",
> "name": "${JOBID}:test"
> }
> }
> }
> ],
> "strategy": {
> "type": "Custom&qu
On Wed, Aug 9, 2017 at 10:00 AM, Devan Goodwin wrote:
> On Wed, Aug 9, 2017 at 9:58 AM, Ben Parees wrote:
> >
> >
> > On Wed, Aug 9, 2017 at 8:49 AM, Devan Goodwin
> wrote:
> >>
> >> We are working on a more robust project export/import process
a good idea...what's
going to repopulate that w/ the right prefix/project in the new cluster?
What if the image field was pointing to docker.io or some other external
registry?
In short, you're attempting to tackle a very complex problem where the
answer is frequen
list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
mage as your builder image for your s2i strategy build.
(You can even make the s2i build be triggered by the new builder image
produced by the docker build, so any time it changes, your app gets
rebuilt).
>
>
> Sincerely,
>
> Ralf Herzog
>
>
>
>
___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
and tag me (bparees)?
>
>
> Thanks,
>
> Lala
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Ben Parees | OpenShift
__
___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
so a great way to fork s2i and add your own customizations!)
>
> Please respond with any questions.
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
B
ing list
>> dev@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>
>>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
t; ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
t; Here is the output of the CLI:
>
>
>
>
>
>
>
> *De :* Ben Parees [mailto:bpar...@redhat.com]
> *Envoyé :* jeudi 19 mai 2016 13:01
> *À :* ABDALA Olga
> *Cc :* dev
> *Objet :* Re: [Origin] Fail to build from remote Git repository
>
>
>
>
> On May
_______
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
; http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
> Thanks,
> Tomas Nozicka
>
> _______
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
g to do with routing / port forwarding.
>
> @Ben thanks I'll checkout what those templates offer.
>
>
> On 03/02/2016 05:45 PM, Ben Parees wrote:
>
>
>
> On Wed, Mar 2, 2016 at 11:41 AM, Aaron Weitekamp <
> aweit...@redhat.com> wrote:
>
>> On Wed,
On Wed, Mar 2, 2016 at 11:41 AM, Aaron Weitekamp
wrote:
> On Wed, Mar 2, 2016 at 9:05 AM, Ben Parees wrote:
>
>> Take a look at this template which deploys mysql:
>>
>> https://github.com/openshift/origin/blob/master/examples/db-templates/mysql-ephemeral-template.json
&g
65/openshift-v3-confusion-on-services-and-routes
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
stead a text input.
>
> Thanks,
> Philippe
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@
ntended
> recipient and may contain confidential or privileged information
> and it can not be forwarded or shared without permission.
> Thank you!
>
> ___________
> dev mailing list
> dev@lists.openshift.redhat.com
> htt
> gtalk:
>
>
> *mateus.caruc...@getupcloud.com twitter:
> @MateusCaruccio <https://twitter.com/MateusCaruccio>*
> This message and any attachment are solely for the intended
> recipient and may contain confidential or privileged information
> and it can not be forwarded or shared wit
!
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
you!
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
> _______
> dev mailing list
> dev@lists.openshift.redhat.com
> http://l
gt;>>> env var.
>>>>>
>>>>> What is the best way to do that?
>>>>> Wouldn't be good to have some kind of template processing like [1]?
>>>>> Something like this:
>>>>>
>>>>> for tpl in $PHP_INI_SCAN_DIR/*.template; do
>>>>>envsubst < $tpl > ${tpl%.template}
>>>>> done
>>>>>
>>>>> There is any reason not to adopt this approach? Is it something origin
>>>>> would accept as a PR?
>>>>>
>>>>> [1]
>>>>> https://github.com/openshift/sti-php/blob/04a0900b68264642def9aaea9465a71e1075e713/5.6/s2i/bin/run#L20-L21
>>>>>
>>>>>
>>>>> *Mateus Caruccio*
>>>>> Master of Puppets
>>>>> +55 (51) 8298.0026
>>>>> gtalk:
>>>>>
>>>>>
>>>>> *mateus.caruc...@getupcloud.com twitter:
>>>>> @MateusCaruccio <https://twitter.com/MateusCaruccio>*
>>>>> This message and any attachment are solely for the intended
>>>>> recipient and may contain confidential or privileged information
>>>>> and it can not be forwarded or shared without permission.
>>>>> Thank you!
>>>>>
>>>>> ___
>>>>> dev mailing list
>>>>> dev@lists.openshift.redhat.com
>>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>>>>
>>>>>
>>>>
>>>
>>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
without permission.
>> Thank you!
>>
>> ___
>> dev mailing list
>> dev@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>>
>>
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
On Wed, Feb 3, 2016 at 9:40 AM, Mateus Caruccio <
mateus.caruc...@getupcloud.com> wrote:
> On Tue, Feb 2, 2016 at 9:51 PM, Ben Parees wrote:
>
>>
>>
>> On Tue, Feb 2, 2016 at 12:21 PM, Mateus Caruccio <
>> mateus.caruc...@getupcloud.com> wrote:
>>
the intended
> recipient and may contain confidential or privileged information
> and it can not be forwarded or shared without permission.
> Thank you!
>
> On Tue, Feb 2, 2016 at 12:50 PM, Ben Parees wrote:
>
>>
>>
>> On Tue, Feb 2, 2016 at 2:39 AM, Honza Hor
into an appropriate location and then process them. (or process
them into the appropriate location).
so this file would not be a part of the php56 image.
> Also adding Remi to comment on this.
>
> Honza
>
> On 02/02/2016 12:54 AM, Ben Parees wrote:
>
>> I think that sou
ission.
> Thank you!
>
> ___________
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
for the intended
> recipient and may contain confidential or privileged information
> and it can not be forwarded or shared without permission.
> Thank you!
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
&
y attachment are solely for the intended
> recipient and may contain confidential or privileged information
> and it can not be forwarded or shared without permission.
> Thank you!
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/opens
pper into all images?
>
> Honza
>
> On 01/19/2016 05:05 PM, Ben Parees wrote:
>
>> That's a good point. We do have the mechanism in place to do that.
>>
>> Michal, any objection to adding the NSS env definitions to our
>> scl_enable script?
>
information
> and it can not be forwarded or shared without permission.
> Thank you!
>
> On Tue, Jan 19, 2016 at 1:52 PM, Ben Parees wrote:
>
>> Ok, can you try the centos image (centos/python-34-centos7)?
>>
>>
>> Honza: do you know when the RHEL SCL python
ntended
> recipient and may contain confidential or privileged information
> and it can not be forwarded or shared without permission.
> Thank you!
>
> On Tue, Jan 19, 2016 at 1:15 PM, Ben Parees wrote:
>
>> Yes there is a trick, documented here:
>>
>>
>> ht
or privileged information
> and it can not be forwarded or shared without permission.
> Thank you!
>
> ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
shed to the external registry.
You would have to run oc import-image to pick up the change.
The only case where the imagestream is automatically updated is when the
imagestream is pointing to the internal openshift registry and a new image
is pushed to the openshift registry.
> 2016-01-15
; ___
> dev mailing list
> dev@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
--
Ben Parees | OpenShift
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
54 matches
Mail list logo
