Re: How to use extra trusted CA certs when pulling images for a builder

[Gabe Montero]

On Mon, Nov 11, 2019 at 11:27 PM Joel Pearson 
wrote:

> I've now discovered that the cluster-samples-operator doesn't seem honour
> the proxy settings, and I see lots of errors in the
> cluster-samples-operator- pod logs
>
> time="2019-11-12T04:15:49Z" level=warning msg="Image import for
> imagestream dotnet tag 2.1 generation 2 failed with detailed message
> Internal error occurred: Get https://registry.redhat.io/v2/: x509:
> certificate signed by unknown authority"
>
> Is there a way to get that operator to use the same user-ca-bundle?
>

Samples operator just reports the status of the sample imagestreams.  It
does not actually execute the imagestream import, and thus is not the
controller that consumes the user-ca-bundle.

Imagestream import is a function of the imagestream controller in the
openshift-controller-manager and the internal image registry.

That said, my understanding was those items should consume global CA /
cluster image configuration as well.

The folks on here already, plus Oleg, who I have now included, can
elaborate.  My quick scan of the docs did not find where that was explained.


> On Tue, 12 Nov 2019 at 14:46, Joel Pearson 
> wrote:
>
>>
>>
>> On Tue, 12 Nov 2019 at 06:56, Ben Parees  wrote:
>>
>>>
>>>

 Can I use the “trustedCA” part of the proxy configuration without
 actually specifying an explicit proxy?

>>>
>>> you should be able to.  Daneyon can you confirm?  (if you can't i'd
>>> consider it a bug).
>>>
>>> It does work! Thanks for that. user-ca-bundle already existed and had my
>> certificate in there, I just needed to reference user-ca-bundle in the
>> proxy config.
>>
>> apiVersion: config.openshift.io/v1
>> kind: Proxy
>> metadata:
>>   name: cluster
>> spec:
>>   trustedCA:
>> name: user-ca-bundle
>>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift Jenkins - Anonymous Web-hooks

[Gabe Montero]

You need to provide a bearer token with sufficient permissions to all the
OpenShift project(s) involved.

A quick example on how to get such a token is at
https://github.com/openshift/jenkins-openshift-login-plugin#non-browser-access
Apply what is done for the example curl invocation to the webhook
config/invocation.

And remember if your flow is spanning multiple projects, you'll need an SA
with sufficient roles/permissions to each of those projects.

On Fri, Feb 8, 2019 at 1:24 AM Samuel Martín Moro  wrote:

> Hi,
>
> Using the generic webhook trigger plugin myself, while still relying on
> OpenShift authentication logging into Jenkins, I don't remember having
> anything like this.
> Although I can't explain why your plugin would refuse this, unless maybe
> something's wrong in Jenkins permissions matrix?
>
> As far as I've seen, generic triggers from a BuildConfig wouldn't allow
> for multi-branch jobs - or if they do, I'm still looking for a way to
> retrieve the triggering branch as a variable somewhere (note: that ruddra
> sample shows the buildconfig has a "ref: master", which would suggest it is
> not multi-branch capable).
> So far, Jenkins plugins was my next best solution, although not ideal.
>
>
> Anyway, you might be able to create a role - or clusterrole - and
> corresponding binding, with something like this (not tested)
>
> - apiVersion: rbac.authorization.k8s.io/v1
>   kind: ClusterRole
>   metadata:
> name: bitbucket-jenkins-hook
>   rules:
>   - nonResourceURLs: [ "/bitbucket-scmsource-hook/*" ]
> verbs: [ "get", "post" ]
>
> - apiVersion: rbac.authorization.k8s.io/v1
>   kind: ClusterRoleBinding
>   metadata:
> name: bitbucket-jenkins-hook
>   roleRef:
> apiGroup: rbac.authorization.k8s.io
> kind: ClusterRole
> name: bitbucket-jenkins-hook
>   subjects:
>   - apiGroup: rbac.authorization.k8s.io
> kind: Group
> name: system:unauthenticated
>   - apiGroup: rbac.authorization.k8s.io
> kind: Group
> name: system:authenticated
>
> (see: https://kubernetes.io/docs/reference/access-authn-authz/rbac/)
>
>
>
> On Fri, Feb 8, 2019 at 7:14 AM Graham Dumpleton 
> wrote:
>
>> I believe you should be using the web book URL from the pipeline build
>> config.
>>
>> You can get them from the web console page for the pipeline.
>>
>> See:
>>
>> *
>> https://ruddra.com/posts/openshift-python-gunicorn-nginx-jenkins-pipelines-part-three/
>>
>> Graham
>>
>> On 8 Feb 2019, at 5:03 pm, Sean Dawson 
>> wrote:
>>
>> Hi,
>>
>> I have Jenkins running in an OpenShift cluster and I have a multi
>> branch job set up, with the source git repository residing in
>> Bitbucket server.
>>
>> I wan't to set up a web hook from Bitbucket Server to Jenkins to
>> trigger builds as soon as there are changes to the repo. In a vanilla
>> Jenkins installation you are able to simply post the updates to
>> "${JENKINS_URL}/bitbucket-scmsource-hook/notify" as mentioned in this
>> article:
>>
>>
>> https://support.cloudbees.com/hc/en-us/articles/11553051-How-to-Trigger-Multibranch-Jobs-from-Bitbucket-Server-#configurationinbitbucketserver
>>
>> However, our Jenkins instance is the OpenShift version and uses
>> OpenShift to authenticate. When I try to post to this URL I get the
>> following error:
>>
>>{
>>"kind": "Status",
>>"apiVersion": "v1",
>>"metadata": {
>>
>>},
>>"status": "Failure",
>>"message": "forbidden: User \"system:anonymous\" cannot post path
>> \"/bitbucket-scmsource-hook/notify\": no RBAC policy matched",
>>"reason": "Forbidden",
>>"details": {
>>
>>},
>>"code": 403
>>}
>>
>> Does anyone know of a way to allow the "system:anonymous" user to post
>> to that path?
>>
>> Thanks
>>
>> Sean
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>
>
> --
> Samuel Martín Moro
> {EPITECH.} 2011
>
> "Nobody wants to say how this works.
>  Maybe nobody knows ..."
>   Xorg.conf(5)
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Automating overriding of openshift-sync Jenkins plugin configuration

[Gabe Montero]

On Thu, Aug 16, 2018 at 2:37 PM Andrew Feller  wrote:

> Yeah, I think it's this one
> .
> Depending on the level of effort, I might be able to potentially contribute
> on a fix for it.  I didn't know if anyone has a workaround other than
> mounting a Groovy script for Jenkins to load.
>

Yeah a groovy init script is the best workaround until the referenced RFE
happens.


> On Thu, Aug 16, 2018 at 1:41 PM Ben Parees  wrote:
>
>>
>>
>> On Thu, Aug 16, 2018 at 10:52 AM, Andrew Feller 
>> wrote:
>>
>>> Is anyone familiar with overriding the openshift-sync plugin namespace
>>> property?
>>>
>>> I'm working to condense the Jenkins instances we have running with a
>>> central Jenkins running in OpenShift pulling BuildConfigs from remote
>>> namespaces.  However, I rather not manually configure Jenkins
>>> openshift-sync plugin on the namespaces it should be monitoring and hoping
>>> there is a better way than crafting a Groovy script to be loaded by Jenkins
>>> on startup to override this.
>>>
>>
>> Pretty sure this has come up before and might even exist as an RFE
>> (namely the ability to set the list of namespaces to watch via an env var)
>> but i don't think anything has been implemented yet.  Gabe would know for
>> sure.
>>
>>
>>
>>>
>>> Thanks!
>>> --
>>>
>>> [image: BandwidthMaroon.png]
>>>
>>> Andy Feller  •  Sr DevOps Engineer
>>>
>>> 900 Main Campus Drive, Suite 500, Raleigh, NC 27606
>>> 
>>>
>>>
>>> e: afel...@bandwidth.com
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>>
>> --
>> Ben Parees | OpenShift
>>
>>
>
> --
>
> [image: BandwidthMaroon.png]
>
> Andy Feller  •  Sr DevOps Engineer
>
> 900 Main Campus Drive, Suite 500, Raleigh, NC 27606
> 
>
>
> e: afel...@bandwidth.com
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Origin 3.9.0's Jenkins - forgetful agents!

[Gabe Montero]

On Tue, Jul 17, 2018 at 9:09 AM, Alan Christie <
achris...@informaticsmatters.com> wrote:

> Hi Gabe,
>
> I’m annotating the ImageStream, essentially doing this: `slave-label: 
> buildah-slave`.
> The Dockerfile and ImageStream YAML template for my agent (a buildah/skopeo
> agent) based on jenkins-slave-maven-centos can be found at our public
> repo (https://github.com/InformaticsMatters/openshift-
> jenkins-buildah-slave).
>
> I can understand the agent being replaced when the external image changes
> but I was curious about why it might change (for no apparent reason).
>

Just remembered, our background polling mechanism is most likely updating
it.  It gets back to not being able to merge our partial config
with any changes you've made on the Jenkins side.  That said, we could try
to avoid the update if our partial config matches.

Open an issue against https://github.com/openshift/jenkins-sync-plugin, and
I can look into that.  Also, we should update our docs to encourage
folks to use the ConfigMap approach if they are modifying the PodTemplate
config beyond the basics we employ.


> But ... I will take a look at the configMap approach because that sounds a
> lot more useful - especially for a CI/CD process and would allow me to set
> the agent up from the command-line without having to use the Jenkins
> management console.
>
> Where might I find a good reference example for the ConfigMap approach?
>

Check out
https://docs.openshift.org/latest/using_images/other_images/jenkins.html#configuring-the-jenkins-kubernetes-plug-in


>
> Alan Christie
> achris...@informaticsmatters.com
>
>
>
> On 17 Jul 2018, at 13:18, Gabe Montero  wrote:
>
> Hi Alan,
>
> Are you leveraging our feature to inject agents by labelling ImageStreams
> with
> the label "role" set to a value of "jenkins-slave", or annotating an
> ImageStreamTag
> with the same k/v pair?
>
> If so, that is going to update the agent definition every those items are
> are updated
> in OpenShift.  And there is currently no merging of the partial
> PodTemplate config
> we construct from ImageStream / ImageStreamTags with whateve modifications
> to
> the PodTemplate was made from within Jenkins after the agent is initially
> created
> (there are no k8s API we can leverage to do that).
>
> If the default config we provide for IS/ISTs is not sufficient, I would
> suggest switching
> to our ConfigMap version of this injection.  With that form, you can
> specify the
> entire PodTemplate definition, including the settings you noted below,
> where the image
> for the PodTemplate is the docker ref for the IS/IST you are currently
> referencing.
>
> If you are inject agents in another way, please elaborate and we'll go
> from there.
>
> thanks,
> gabe
>
> On Tue, Jul 17, 2018 at 4:45 AM, Alan Christie <
> achris...@informaticsmatters.com> wrote:
>
>> Hi,
>>
>> I’m using Jenkins on an OpenShift Origin 3.9.0 deployment and notice that
>> Jenkins periodically forgets the additional settings for my custom agent.
>>
>> I’m using the built-in Jenkins from the catalogue (Jenkins 2.89.4) with
>> all the plugins updated.
>>
>> Incidentally, I doubt it has anything to do with the origin release as I
>> recall seeing this on earlier (3.7/3.6) releases.
>>
>> It happens when I deploy a new agent to Docker hub so this I can partly
>> understand (i.e. a new ‘latest’ image is available so it’s pulled) -
>> although I do struggle to understand why it creates a *new* Kubernetes pod
>> template in the cloud configuration when one already exists for the same
>> agent (but that’ll probably be the subject of another question). So, each
>> time I push an image I have to fix the cloud configuration for my agent.
>>
>> This I can live with (for now) but it also happens periodically for no
>> apparent reason. I’m not sure about the frequency but I’ll notice every
>> week, or every few weeks, the Kubernetes Pod Template for my agent has
>> forgotten all the _extra_ setup. Things like: -
>>
>> - Run in privileged mode
>> - Additional volumes
>> - Max number of instances
>> - Time in minutes to retain slave when idle
>>
>> Basically anything adjusted beyond the defaults provided when you first
>> instantiate an agent is lost.
>>
>> Has anyone reported this behaviour before?
>> Is there a fix or can anyone suggest an area of investigation?
>>
>> Alan Christie
>> achris...@informaticsmatters.com
>>
>>
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Origin 3.9.0's Jenkins - forgetful agents!

[Gabe Montero]

Hi Alan,

Are you leveraging our feature to inject agents by labelling ImageStreams
with
the label "role" set to a value of "jenkins-slave", or annotating an
ImageStreamTag
with the same k/v pair?

If so, that is going to update the agent definition every those items are
are updated
in OpenShift.  And there is currently no merging of the partial PodTemplate
config
we construct from ImageStream / ImageStreamTags with whateve modifications
to
the PodTemplate was made from within Jenkins after the agent is initially
created
(there are no k8s API we can leverage to do that).

If the default config we provide for IS/ISTs is not sufficient, I would
suggest switching
to our ConfigMap version of this injection.  With that form, you can
specify the
entire PodTemplate definition, including the settings you noted below,
where the image
for the PodTemplate is the docker ref for the IS/IST you are currently
referencing.

If you are inject agents in another way, please elaborate and we'll go from
there.

thanks,
gabe

On Tue, Jul 17, 2018 at 4:45 AM, Alan Christie <
achris...@informaticsmatters.com> wrote:

> Hi,
>
> I’m using Jenkins on an OpenShift Origin 3.9.0 deployment and notice that
> Jenkins periodically forgets the additional settings for my custom agent.
>
> I’m using the built-in Jenkins from the catalogue (Jenkins 2.89.4) with
> all the plugins updated.
>
> Incidentally, I doubt it has anything to do with the origin release as I
> recall seeing this on earlier (3.7/3.6) releases.
>
> It happens when I deploy a new agent to Docker hub so this I can partly
> understand (i.e. a new ‘latest’ image is available so it’s pulled) -
> although I do struggle to understand why it creates a *new* Kubernetes pod
> template in the cloud configuration when one already exists for the same
> agent (but that’ll probably be the subject of another question). So, each
> time I push an image I have to fix the cloud configuration for my agent.
>
> This I can live with (for now) but it also happens periodically for no
> apparent reason. I’m not sure about the frequency but I’ll notice every
> week, or every few weeks, the Kubernetes Pod Template for my agent has
> forgotten all the _extra_ setup. Things like: -
>
> - Run in privileged mode
> - Additional volumes
> - Max number of instances
> - Time in minutes to retain slave when idle
>
> Basically anything adjusted beyond the defaults provided when you first
> instantiate an agent is lost.
>
> Has anyone reported this behaviour before?
> Is there a fix or can anyone suggest an area of investigation?
>
> Alan Christie
> achris...@informaticsmatters.com
>
>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Creating choice-based parameters for Jenkins Pipeline strategy

[Gabe Montero]

Hey Andy,

First, https://github.com/openshift/jenkins-sync-plugin/issues/131 was
about secret/credential mapping
and not directly related to parameters.

That said, our sync plugin does allow for setting env vars on an OpenShift
Pipeline Strategy Build Config,
and we'll map those Jenkins job parameter definitions.

I'm assuming you are referring to that.

Those env vars are always mapped as simple string params.  We are not
currently tracking any changes
to support more than that.  Certainly feel free to open an RFE or card on
our  trello board 
if you have a use case for more sophisticated bc env var to jenkins param
mapping.

As part of the existing support though, if you modify the associated Job
def after the BC is initially created to add parameters,
it should do one of the following:
- if you trigger the build from openshift via 'oc start-build ',
or I believe from Jenkins with all defaults, it will append the default
value
of those params to the list of params for the job run
- if you trigger the build from jenkins, it should take an param settings
you specify

That said, yes, the typo you found would impact any processing of
*ChoiceParameterDefinition*
when you run `oc start-build ...` or I believe Jenkins without any changes
from the parms defaults.

I've opened https://github.com/openshift/jenkins-sync-plugin/pull/243 to
fix that.




On Mon, Jul 9, 2018 at 9:29 AM, Andrew Feller  wrote:

> Can anyone confirm if non-string typed parameters (for example: choice)
> can be declared for Jenkins Pipeline strategy?
>
> jenkins-sync-plugin issue 131
>  appears to
> add support for them except there appears to be a bug due to a typo 
> *(ChoiceParameterDefintion
> probably should be **ChoiceParameterDefinition)* and I can't really find
> anyone talking about this.
>
> Thanks!
> --
>
> [image: BandwidthMaroon.png]
>
> Andy Feller  •  Sr DevOps Engineer
>
> 900 Main Campus Drive, Suite 500, Raleigh, NC 27606
>
>
> e: afel...@bandwidth.com
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Utilizing Jenkins linter with Jenkins hosted within OpenShift

[Gabe Montero]

We support passing in a valid OpenShift token as a bearer token with curl
requests against
a deployment of the OpenShift Jenkins image.

You should be able to leverage the curl based accessed noted at the link
you posted.

See
https://github.com/openshift/jenkins-openshift-login-plugin#non-browser-access
https://github.com/openshift/jenkins#jenkins-admin-user
https://docs.openshift.org/latest/using_images/other_images/jenkins.html#jenkins-openshift-oauth-authentication



On Thu, Jul 5, 2018 at 7:51 AM, Andrew Feller  wrote:

> I imagine developers leveraging Jenkins declarative linter
>  from Jenkins
> hosted within OpenShift is more difficult because OpenShift is handling
> identity management, but has anyone had luck with supporting this?  I
> realize the nature of Jenkins makes this complicated so don't expect there
> to be a great solution here.
>
> Thanks!
>
> --
>
> [image: BandwidthMaroon.png]
>
> Andy Feller  •  Sr DevOps Engineer
>
> 900 Main Campus Drive, Suite 500, Raleigh, NC 27606
>
>
> e: afel...@bandwidth.com
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: deployed Jenkins in the OPENSHIFT GUI how do I connect to it ?

[Gabe Montero]

On Wed, May 9, 2018 at 2:52 PM, Brian Keyes <bke...@vizuri.com> wrote:

> thanks !! , I do see that URL in my case it is https://jenkins-my-jenkins-
> bk.app.mxxnie.sandbox.vizuri.com/ but then I get site cannot be
> reached , this is up on aws so I would imaging now I have to open 8080 on
> the AWS ALB security group to allow the port 8080 to pass , so does this
> sound right ?
>

Well there are varying paths based on how you installed.

There is plenty of doc out there around standing up openshift on AWS.
There are several things to consider.

If you are very very new, I might suggest downloading the CLI "oc" from
https://github.com/openshift/origin/releases
and just run "oc cluster up".  Your various routes will leverage nip.io for
DNS and should be accessible from anywhere.

Otherwise, bottom line, I think you have a lot of reading to do.

Some sample links


https://github.com/openshift/openshift-ansible.git

https://docs.openshift.org/latest/install_config/install/
advanced_install.html#single-master

https://access.redhat.com/documentation/en-us/reference_
architectures/2017/html-single/deploying_openshift_
container_platform_3.5_on_amazon_web_services/index

https://docs.openshift.com/container-platform/3.9/install_config/install/
prerequisites.html#wildcard-dns-prereq

https://github.com/aws-quickstart/quickstart-redhat-openshift

Though others that monitor this list might have better suggestions.



> thanks again , I am very very new to this and stumbling over myself for
> sure !!!!
>
> On Wed, May 9, 2018 at 2:46 PM, Gabe Montero <gmont...@redhat.com> wrote:
>
>>
>>
>> On Wed, May 9, 2018 at 2:22 PM, Brian Keyes <bke...@vizuri.com> wrote:
>>
>>> I have deployed Jenkins ephemeral on the openshift GUI , but how can I
>>> connect to the Jenkins UI I dont see a URL anywhere
>>>
>>
>> Bring up the routes from the console.  You should see a Jenkins route.
>> Click that URL, follow the various prompts, and you
>> should be eventually asked for your userid and password  on the OpenShift
>> cluster.
>>
>>>
>>> thanks
>>>
>>> --
>>> Brian Keyes
>>> Systems Engineer, Vizuri
>>> 703-855-9074(Mobile)
>>> 703-464-7030 x8239 (Office)
>>>
>>> FOR OFFICIAL USE ONLY: This email and any attachments may contain
>>> information that is privacy and business sensitive.  Inappropriate or
>>> unauthorized disclosure of business and privacy sensitive information may
>>> result in civil and/or criminal penalties as detailed in as amended Privacy
>>> Act of 1974 and DoD 5400.11-R.
>>>
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>
>
> --
> Brian Keyes
> Systems Engineer, Vizuri
> 703-855-9074(Mobile)
> 703-464-7030 x8239 (Office)
>
> FOR OFFICIAL USE ONLY: This email and any attachments may contain
> information that is privacy and business sensitive.  Inappropriate or
> unauthorized disclosure of business and privacy sensitive information may
> result in civil and/or criminal penalties as detailed in as amended Privacy
> Act of 1974 and DoD 5400.11-R.
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: deployed Jenkins in the OPENSHIFT GUI how do I connect to it ?

[Gabe Montero]

On Wed, May 9, 2018 at 2:46 PM, Gabe Montero <gmont...@redhat.com> wrote:

>
>
> On Wed, May 9, 2018 at 2:22 PM, Brian Keyes <bke...@vizuri.com> wrote:
>
>> I have deployed Jenkins ephemeral on the openshift GUI , but how can I
>> connect to the Jenkins UI I dont see a URL anywhere
>>
>
> Bring up the routes from the console.  You should see a Jenkins route.
> Click that URL, follow the various prompts, and you
> should be eventually asked for your userid and password  on the OpenShift
> cluster.
>

the console == the OpenShift GUI


>
>> thanks
>>
>> --
>> Brian Keyes
>> Systems Engineer, Vizuri
>> 703-855-9074(Mobile)
>> 703-464-7030 x8239 (Office)
>>
>> FOR OFFICIAL USE ONLY: This email and any attachments may contain
>> information that is privacy and business sensitive.  Inappropriate or
>> unauthorized disclosure of business and privacy sensitive information may
>> result in civil and/or criminal penalties as detailed in as amended Privacy
>> Act of 1974 and DoD 5400.11-R.
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: deployed Jenkins in the OPENSHIFT GUI how do I connect to it ?

[Gabe Montero]

On Wed, May 9, 2018 at 2:22 PM, Brian Keyes  wrote:

> I have deployed Jenkins ephemeral on the openshift GUI , but how can I
> connect to the Jenkins UI I dont see a URL anywhere
>

Bring up the routes from the console.  You should see a Jenkins route.
Click that URL, follow the various prompts, and you
should be eventually asked for your userid and password  on the OpenShift
cluster.

>
> thanks
>
> --
> Brian Keyes
> Systems Engineer, Vizuri
> 703-855-9074(Mobile)
> 703-464-7030 x8239 (Office)
>
> FOR OFFICIAL USE ONLY: This email and any attachments may contain
> information that is privacy and business sensitive.  Inappropriate or
> unauthorized disclosure of business and privacy sensitive information may
> result in civil and/or criminal penalties as detailed in as amended Privacy
> Act of 1974 and DoD 5400.11-R.
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift Jenkins OAuth2 Authentication using Spring Boot

[Gabe Montero]

On Sun, Feb 11, 2018 at 5:43 PM, Tien Hung Nguyen 
wrote:

> Thank you for the information.
>
> I have disabled now the OAuth2 feature of OpenShift and tried to
> authenticate by the default username and password of jenkins to test the
> connection between the Jenkins Server and another Java REST Service.
> However, when I try to do a REST Call on my Java Code by using the
> OpenShift Jenkins Service IP (server: http://172.30.51.151:80), I'm
> getting the the following error (2018-02-11 22:30:00,798 ERROR
> c.c.d.collector.DefaultHudsonClient - client exception loading
> jobs org.springframework.web.client.HttpClientErrorException: 403
> Forbidden):
>

Can you supply the curl command or whatever you used to make the REST
call?  Given the 403, either the credentials
are not being properly supplied, or our default user in the non-oauth case
does not have as much permissions as we thought
it did (depending on which URI you are accessing).


>
> 2018-02-11 22:30:00,274 INFO  c.c.d.collector.CollectorTask -
> http://172.30.51.151:80 2018-02-11 22:30:00,274 INFO
>  c.c.d.collector.CollectorTask - ---
> 2018-02-11 22:30:00,798 ERROR c.c.d.collector.DefaultHudsonClient -
> client exception loading 
> jobsorg.springframework.web.client.HttpClientErrorException:
> 403 Forbidden at org.springframework.web.client.
> DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:91)
> ~[spring-web-4.2.5.RELEASE.jar!/:4.2.5.RELEASE] at
> org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:641)
> ~[spring-web-4.2.5.RELEASE.jar!/:4.2.5.RELEASE] at
> org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:597)
> ~[spring-web-4.2.5.RELEASE.jar!/:4.2.5.RELEASE] at
> org.springframework.web.client.RestTemplate.execute(RestTemplate.java:572)
> ~[spring-web-4.2.5.RELEASE.jar!/:4.2.5.RELEASE] at
> org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:493)
> ~[spring-web-4.2.5.RELEASE.jar!/:4.2.5.RELEASE] at
> com.capitalone.dashboard.collector.DefaultHudsonClient.makeRestCall(DefaultHudsonClient.java:655)
> [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT] at
> com.capitalone.dashboard.collector.DefaultHudsonClient.getJobsCount(DefaultHudsonClient.java:192)
> [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT] at
> com.capitalone.dashboard.collector.DefaultHudsonClient.getInstanceJobs(DefaultHudsonClient.java:110)
> [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT] at
> com.capitalone.dashboard.collector.HudsonCollectorTask.
> collect(HudsonCollectorTask.java:99) [jenkins-build-collector-2.0.
> 5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT] at com.capitalone.dashboard.
> collector.HudsonCollectorTask.collect(HudsonCollectorTask.java:37)
> [jenkins-build-collector-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT] at
> com.capitalone.dashboard.collector.CollectorTask.run(CollectorTask.java:63)
> [core-2.0.5-SNAPSHOT.jar!/:2.0.5-SNAPSHOT] at org.springframework.
> scheduling.support.DelegatingErrorHandlingRunnable.run(
> DelegatingErrorHandlingRunnable.java:54) 
> [spring-context-4.2.5.RELEASE.jar!/:4.2.5.RELEASE]
> at 
> org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:81)
> [spring-context-4.2.5.RELEASE.jar!/:4.2.5.RELEASE] at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> [na:1.8.0_151] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [na:1.8.0_151] at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
> [na:1.8.0_151] at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [na:1.8.0_151] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [na:1.8.0_151] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [na:1.8.0_151] at java.lang.Thread.run(Thread.java:748)
> [na:1.8.0_151]2018-02-11 22:30:00,805 INFO  c.c.d.collector.CollectorTask -
> Error getting jobs for: http://172.30.51.151:80  0s
> 2018-02-11 22:31:49,069 INFO  org.mongodb.driver.connection - Closed
> connection [connectionId{localValue:6, serverValue:31667}] to
> hygieia-mongodb:27017 because it is past its maximum allowed idle
> time.2018-02-11 22:35:00,001 INFO  c.c.d.collector.CollectorTask - Running
> Collector: Hudson
> 2018-02-11 22:35:00,024 INFO  org.mongodb.driver.connection - Opened
> connection [connectionId{localValue:7, serverValue:31729}] to
> hygieia-mongodb:270172018-02-11 22:35:00,039 INFO
>  c.c.d.collector.CollectorTask - ---
> 2018-02-11 22:35:00,040 INFO  c.c.d.collector.CollectorTask -
> http://172.30.51.151:80 2018-02-11 22:35:00,040 INFO
>  c.c.d.collector.CollectorTask - ---
> 2018-02-11 22:35:00,051 ERROR c.c.d.collector.DefaultHudsonClient -
> client exception 

Re: OpenShift Jenkins OAuth2 Authentication using Spring Boot

[Gabe Montero]

On Fri, Feb 9, 2018 at 1:45 PM, Tien Hung Nguyen 
wrote:

> Hello everyone,
>
> I'm having a Spring Boot Rest Microservice and I'm trying to pull some
> information with a Rest call from my Jenkins Server, which is running in an
> OpenShift pod (based on the default openshift/jenkins image), to display
> the information from Jenkins in a unified dashboard.
>
> However, I'm getting some problems with the authentication because OAuth2
> is enabled on the Jenkins Pod. What is the correct way to authenticate my
> Spring Boot Rest Microservice with the Jenkins pod which redirects me at
> the moment to the OpenShift page because of OAuth2?
>
> Currently, I have the required information and credentials in a properties
> file stored that I use for rest call, like username, password, server,
> domain etc., but actually that's mot working to authenticate with the
> jenkins pod.
>
> Could you give me some sample code snippet that shows how to do that in a
> proper way?
>

Toggling the default behavior wrt auth for the openshift jenkins image is
discussed at
https://docs.openshift.org/latest/using_images/other_images/jenkins.html#jenkins-openshift-oauth-authentication

If you are using the openshift example template for provisioning Jenkins,
if you instantiate the template with the parameter ENABLE_OAUTH set to
false,
it will handle the necessary environment variables discussed above.

See
https://github.com/openshift/origin/blob/master/examples/jenkins/jenkins-ephemeral-template.json#L260-L266
and
https://github.com/openshift/origin/blob/master/examples/jenkins/jenkins-persistent-template.json#L277-L282


>
> Regards
> Tien
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: OpenShift Gitlab webhook Jenkins issues.

[Gabe Montero]

Hey Thorvald,

Running your openshift master at loglevel 10 should include the payload of
the webhook POST request when it arrives.
Also, if there were any errors parsing the request, that would show up in
the log as well.

Go ahead and tag me (@gabemontero) when you open the issue and we'll go
from there.

thanks!

On Thu, Aug 24, 2017 at 4:25 AM, Thorvald Hallvardsson <
thorvald.hallvards...@gmail.com> wrote:

> Hi Gabe,
>
> I'm more than happy to report that as an issue. If you could only tell me
> how can I grab the content of the gitlab push event that would be great.
>
> Thanks!
> TH
>
> On 23 August 2017 at 16:33, Gabe Montero <gmont...@redhat.com> wrote:
>
>>
>>
>> On Wed, Aug 23, 2017 at 8:52 AM, Thorvald Hallvardsson <
>> thorvald.hallvards...@gmail.com> wrote:
>>
>>> Hi Ben,
>>>
>>> Name:   nodejs-pipeline-master
>>> Namespace:  jenkins
>>> Created:5 days ago
>>> Labels: app=nodejs-integration
>>> Annotations:pipeline.alpha.openshift.io/uses=[{
>>> <http://pipeline.alpha.openshift.io/uses=%5B%7B>"name": "nodejsci",
>>> "namespace": "", "kind": "DeploymentConfig"}]
>>> Latest Version: 3
>>>
>>> Strategy:   JenkinsPipeline
>>> URL:http://gitlab.os.hr4.local/je
>>> nkins/nodejs-ex-1.git
>>> Ref:manual
>>> Jenkinsfile path:   Jenkinsfile
>>>
>>> Build Run Policy:   Serial
>>> Triggered by:   
>>> Webhook GitHub:
>>> URL:https://master.hr4.local:8443
>>> /oapi/v1/namespaces/jenkins/buildconfigs/nodejs-pipeline-mas
>>> ter/webhooks/EgXVqyOOobmMzjVzQHSh/github
>>> Webhook Generic:
>>> URL:https://master.hr4.local:8443
>>> /oapi/v1/namespaces/jenkins/buildconfigs/nodejs-pipeline-mas
>>> ter/webhooks/bz6uJc9u-0-58EoYKgL3/generic
>>> AllowEnv:   false
>>>
>>> Build   Status  DurationCreation Time
>>> nodejs-pipeline-master-3failed  1s  2017-08-18
>>> 09:27:00 +0100 BST
>>> nodejs-pipeline-master-2failed  1s  2017-08-18
>>> 09:18:46 +0100 BST
>>> nodejs-pipeline-master-1failed  1m2s2017-08-18
>>> 09:16:19 +0100 BST
>>>
>>> No events.
>>>
>>> JSON:
>>> {
>>> "kind": "BuildConfig",
>>> "apiVersion": "v1",
>>> "metadata": {
>>> "name": "nodejs-pipeline-master",
>>> "creationTimestamp": null,
>>> "labels": {
>>> "app": "nodejs-integration"
>>> },
>>> "annotations": {
>>> "pipeline.alpha.openshift.io/uses": "[{\"name\":
>>> \"nodejsci\", \"namespace\": \"\", \"kind\": \"DeploymentConfig\"}]"
>>> }
>>> },
>>> "spec": {
>>> "triggers": [
>>> {
>>> "type": "GitHub",
>>> "github": {
>>> "secret": "EgXVqyOOobmMzjVzQHSh"
>>> }
>>> },
>>> {
>>> "type": "Generic",
>>> "generic": {
>>> "secret": "bz6uJc9u-0-58EoYKgL3"
>>> }
>>> }
>>> ],
>>> "runPolicy": "Serial",
>>> "source": {
>>> "type": "Git",
>>> "git": {
>>> "uri": "http://gitlab.os.hr4.local/je
>>> nkins/nodejs-ex-1.git",
>>> "ref": "manual"
>>> }
>>> },
>>> "strategy": {
>>> "type": "JenkinsPipeline",
>>> "jenkinsPipelineStrategy": {
>>> "jenkinsfilePath": "Jenkinsfile"
>>> }
>>> },
>>> "output": {},
&

Re: OpenShift Gitlab webhook Jenkins issues.

[Gabe Montero]

":"3","name":"#
> 3","status":"NOT_EXECUTED","startTimeMillis":
> 1503044820755,"endTimeMillis":0,"durationMillis":0,"
> queueDurationMillis":0,"pauseDurationMillis":0,"stages":[]}
>
> Status: Failed
> Started:Fri, 18 Aug 2017 09:27:00 BST
> Duration:   1s
> Build Config:   nodejs-pipeline-master
> Build Pod:  nodejs-pipeline-master-3-build
>
> Strategy:   JenkinsPipeline
> URL:http://gitlab.os.hr4.local/jenkins/nodejs-ex-1.git
> Ref:manual
> Commit:  ()
> Jenkinsfile path:   Jenkinsfile
>
> Build trigger cause:GitHub WebHook
> Commit:  ()
> Secret: EgXVqyOOob***
>
> No events.
>
>
> JSON:
> {
> "kind": "Build",
> "apiVersion": "v1",
> "metadata": {
> "name": "nodejs-pipeline-master-3",
> "creationTimestamp": null,
> "labels": {
> "app": "nodejs-integration",
> "buildconfig": "nodejs-pipeline-master",
> "openshift.io/build-config.name": "nodejs-pipeline-master",
> "openshift.io/build.start-policy": "Serial"
> },
> "annotations": {
> "openshift.io/build-config.name": "nodejs-pipeline-master",
> "openshift.io/build.number": "3",
> "openshift.io/jenkins-build-uri": "https://jenkins-jenkins.os.
> hr4.local/job/jenkins-nodejs-pipeline-master/3/",
> "openshift.io/jenkins-console-log-url": "
> https://jenkins-jenkins.os.hr4.local/job/jenkins-nodejs-
> pipeline-master/3/console",
> "openshift.io/jenkins-log-url": "https://jenkins-jenkins.os.
> hr4.local/job/jenkins-nodejs-pipeline-master/3/consoleText",
> "openshift.io/jenkins-status-json": "{\"_links\":{\"self\":{\"
> href\":\"https://jenkins-jenkins.os.hr4.local/job/jenkins-nodejs-pipeline-
> master/3/wfapi/describe\"}},\"id\":\"3\",\"name\":\"#3\",\"
> status\":\"NOT_EXECUTED\",\"startTimeMillis\":
> 1503044820755,\"endTimeMillis\":0,\"durationMillis\":0,\"
> queueDurationMillis\":0,\"pauseDurationMillis\":0,\"stages\":[]}"
> }
> },
> "spec": {
> "serviceAccount": "builder",
> "source": {
> "type": "Git",
> "git": {
> "uri": "http://gitlab.os.hr4.local/jenkins/nodejs-ex-1.git
> ",
> "ref": "manual"
> }
> },
> "revision": {
> "type": "Git",
>     "git": {
> "author": {},
> "committer": {}
> }
> },
> "strategy": {
> "type": "JenkinsPipeline",
> "jenkinsPipelineStrategy": {
> "jenkinsfilePath": "Jenkinsfile"
> }
> },
> "output": {},
> "resources": {},
> "postCommit": {},
> "nodeSelector": {},
> "triggeredBy": [
> {
> "message": "GitHub WebHook",
> "githubWebHook": {
> "revision": {
> "type": "Git",
> "git": {
> "author": {},
> "committer": {}
> }
> },
>

OK, the above snippet is the crux of things here, and lines up with the
stack trace you are seeing on the jenkins side.  Essentially, the commit is
not getting retrieved from the gitlab webhook push event.

At this point, you should probably open an issue at
https://github.com/openshift/origin and we can continue debug / resolution
there.  Among
other things, if you could somehow get the contents of the gitlab push
event json, that would be the most expedient means of determining what is
up.

Per the gitlab spec/version we are working off

Re: OpenShift Gitlab webhook Jenkins issues.

[Gabe Montero]

On Mon, Aug 21, 2017 at 8:08 AM, Thorvald Hallvardsson <
thorvald.hallvards...@gmail.com> wrote:

> Hi Ben,
>
> yes you got right understanding of my problem.
>
> There is no build associated yet, as it doesn't even get to the stage when
> it would fireup any build for the pipeline. It's literally a scond after
> sending the build task to Jenkins
>

To tweak Ben's request slightly, can you provide the *buildconfig* json.
The precise structure of the gitlab webhook will most likely be helpful for
us, especially
in comparison to the gitlab specs  and what the git plugin is spitting out.

>
> OpenShift version is 3.5. Jenkins sync plugin is 0.1.25.
>
> Regards,
> TH
>
>
> On 18 August 2017 at 21:56, Ben Parees  wrote:
>
>>
>>
>> On Fri, Aug 18, 2017 at 4:39 AM, Thorvald Hallvardsson <
>> thorvald.hallvards...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I configured Gitlab webhook for my test pipeline to fire up a build. The
>>> problem is as soon as I commit something jenkins complains with an error
>>> below:
>>>
>>
>> To make sure i understand your scenario, you've defined a pipeline
>> buildconfig in openshift and enabled a gitlab webhook trigger to trigger
>> the build?  (vs defining a gitlab trigger in jenkins itself).
>>
>>
>>
>>>
>>> OpenShift Build jenkins/nodejs-pipeline-master-3 from
>>> http://gitlab.os.hr4.local/jenkins/nodejs-ex-1.git
>>> Checking out git http://gitlab.os.hr4.local/jenkins/nodejs-ex-1.git to
>>> read Jenkinsfile
>>>  > git rev-parse --is-inside-work-tree # timeout=10
>>> Fetching changes from the remote Git repository
>>>  > git config remote.origin.url http://gitlab.os.hr4.local/jen
>>> kins/nodejs-ex-1.git # timeout=10
>>> Fetching upstream changes from http://gitlab.os.hr4.local/jen
>>> kins/nodejs-ex-1.git
>>>  > git --version # timeout=10
>>>  > git fetch --tags --progress http://gitlab.os.hr4.local/jen
>>> kins/nodejs-ex-1.git +refs/heads/*:refs/remotes/origin/*
>>>  > git rev-parse null^{commit} # timeout=10
>>> hudson.plugins.git.GitException: Command "git rev-parse null^{commit}"
>>> returned status code 128:
>>> stdout: null^{commit}
>>>
>>> stderr: fatal: ambiguous argument 'null^{commit}': unknown revision or
>>> path not in the working tree.
>>> Use '--' to separate paths from revisions, like this:
>>> 'git  [...] -- [...]'
>>>
>>> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandI
>>> n(CliGitAPIImpl.java:1799)
>>> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandI
>>> n(CliGitAPIImpl.java:1772)
>>> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandI
>>> n(CliGitAPIImpl.java:1768)
>>> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(
>>> CliGitAPIImpl.java:1415)
>>> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(
>>> CliGitAPIImpl.java:1427)
>>> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGi
>>> tAPIImpl.java:686)
>>> at hudson.plugins.git.GitAPI.revParse(GitAPI.java:316)
>>> at hudson.plugins.git.RevisionParameterAction.toRevision(Revisi
>>> onParameterAction.java:98)
>>> at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:991)
>>> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1108)
>>> at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SC
>>> MStep.java:109)
>>> at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.crea
>>> te(CpsScmFlowDefinition.java:130)
>>> at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.crea
>>> te(CpsScmFlowDefinition.java:59)
>>> at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowR
>>> un.java:232)
>>> at hudson.model.ResourceController.execute(ResourceController.java:97)
>>> at hudson.model.Executor.run(Executor.java:405)
>>> Finished: FAILURE
>>>
>>> It works when I take generic webhook URL however it engages a build
>>> regardless of which branch I'm commiting the change to - which is no ideal.
>>>
>>> Any ideas why commit number in the code above is null ?
>>>
>>
>> can you share the build json associated w/ the build that was kicked off
>> by the webhook trigger?
>>
>> also what version of the openshift sync plugin are you running and what
>> version is your openshift cluster?
>>
>>
>>
>>
>>>
>>> Thanks
>>> TH
>>>
>>> ___
>>> users mailing list
>>> users@lists.openshift.redhat.com
>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>
>>>
>>
>>
>> --
>> Ben Parees | OpenShift
>>
>>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Re: Jenkins integration

[Gabe Montero]

quot;/dev/termination-log",
> "Mode": "Z",
> "RW": true,
> "Propagation": "rprivate"
> }
> ],
> "Config": {
> "Hostname": "jenkins-1-j267m",
> "Domainname": "",
> "User": "19",
> "AttachStdin": false,
> "AttachStdout": false,
> "AttachStderr": false,
> "ExposedPorts": {
> "5/tcp": {},
> "8080/tcp": {}
> },
> "Tty": false,
> "OpenStdin": false,
> "StdinOnce": false,
> "Env": [
> "OPENSHIFT_ENABLE_OAUTH=true",
> "OPENSHIFT_ENABLE_REDIRECT_PROMPT=true",
> "OPENSHIFT_JENKINS_JVM_ARCH=x86_64",
> "KUBERNETES_MASTER=https://kubernetes.default:443;,
> "KUBERNETES_TRUST_CERTIFICATES=true",
> "JNLP_SERVICE_NAME=jenkins-jnlp",
> "JENKINS_JNLP_PORT_5_TCP_ADDR=172.30.98.196",
> "JENKINS_PORT=tcp://172.30.125.4:80",
> "KUBERNETES_PORT_53_UDP=udp://172.30.0.1:53",
> "KUBERNETES_PORT_53_TCP=tcp://172.30.0.1:53",
> "KUBERNETES_PORT_53_TCP_ADDR=172.30.0.1",
> "JENKINS_SERVICE_PORT_WEB=80",
> "JENKINS_JNLP_SERVICE_HOST=172.30.98.196",
> "KUBERNETES_SERVICE_PORT=443",
> "KUBERNETES_SERVICE_PORT_HTTPS=443",
> "KUBERNETES_SERVICE_PORT_DNS=53",
> "KUBERNETES_PORT_443_TCP_ADDR=172.30.0.1",
> "KUBERNETES_PORT_53_UDP_PROTO=udp",
> "KUBERNETES_PORT_53_UDP_PORT=53",
> "KUBERNETES_PORT_53_UDP_ADDR=172.30.0.1",
> "JENKINS_JNLP_SERVICE_PORT=5",
> "JENKINS_JNLP_SERVICE_PORT_AGENT=5",
> "JENKINS_JNLP_PORT_5_TCP=tcp://172.30.98.196:5",
> "JENKINS_PORT_80_TCP=tcp://172.30.125.4:80",
> "JENKINS_PORT_80_TCP_ADDR=172.30.125.4",
> "KUBERNETES_SERVICE_HOST=172.30.0.1",
> "KUBERNETES_PORT_443_TCP=tcp://172.30.0.1:443",
> "KUBERNETES_PORT_53_TCP_PROTO=tcp",
> "JENKINS_JNLP_PORT_5_TCP_PROTO=tcp",
> "JENKINS_JNLP_PORT_5_TCP_PORT=5",
> "JENKINS_SERVICE_HOST=172.30.125.4",
> "JENKINS_PORT_80_TCP_PORT=80",
> "KUBERNETES_PORT_443_TCP_PORT=443",
> "JENKINS_JNLP_PORT=tcp://172.30.98.196:5",
> "JENKINS_PORT_80_TCP_PROTO=tcp",
> "JENKINS_SERVICE_PORT=80",
> "KUBERNETES_PORT=tcp://172.30.0.1:443",
> "KUBERNETES_PORT_53_TCP_PORT=53",
> "KUBERNETES_SERVICE_PORT_DNS_TCP=53",
> "KUBERNETES_PORT_443_TCP_PROTO=tcp",
> "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
> sbin:/bin",
> "JENKINS_VERSION=2.46.3",
> "HOME=/var/lib/jenkins",
> "JENKINS_HOME=/var/lib/jenkins",
> "JENKINS_UC=https://updates.jenkins-ci.org;,
> "LANG=en_US.UTF-8",
> "LC_ALL=en_US.UTF-8"
> ],
> "Cmd": [
> "/usr/libexec/s2i/run"
> ],
> "Image": "openshift/jenkins-2-centos7@sha256:
> ad29fc43c3f9015a0fdbb3f3ba366ff511303f7f3a0bbb1bc4652ecf70eb3712",
> "Volumes": {
> "/var/lib/jenkins": {}
> },
> "WorkingDir": "",
> "Entrypoint": null,
> "OnBuild": null,
> "Labels": {
> "build-date": "20170705",
> "io.kubernetes.container.hash": "ca203105",
> "io.kubernetes.container.name": "jenkins",
> 

Re: modify the redhat docker images

[Gabe Montero]

RE: the Dockerfiles, take a look at https://github.com/openshift/sti-base.

On Wed, Mar 2, 2016 at 12:31 PM, Candide Kemmler 
wrote:

> awesome!
>
> Is there a central place where Dockerfile for those images can be found,
> or alternatively are these images available to serve as a base image to
> start off from?
>
> It is unclear to me where Openshift Origin is fetching the containers from
> (e.g. jboss-webserver30-tomcat7-openshift) and if it is possible to fetch
> them from that same source to expand on them and push them to e.g.
> docker.io.
>
> On 02 Mar 2016, at 18:08, Ben Parees  wrote:
>
> There's actually only one type of image.  S2I starts w/ the builder image,
> then adds your application code to it, producing the application(runtime)
> image.
>
> So the builder image is also the base image for the runtime image, you can
> layer your runtime requirements onto it.
>
>
>
> On Wed, Mar 2, 2016 at 11:04 AM, Candide Kemmler 
> wrote:
>
>> I would like to configure the environment for a java application that
>> works well with one of the provided s2i images, namely
>> jboss-webserver30-tomcat7-openshift:1.2.
>>
>> As I understand it there are two kinds of images associated with s2i
>> builds, the builder images, and the runtime image. In this case, I would
>> like to modify the runtime image and add some binaries.
>>
>> How do I get hold of the original image?
>>
>>
>> ___
>> users mailing list
>> users@lists.openshift.redhat.com
>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>
>
>
> --
> Ben Parees | OpenShift
>
>
>
> ___
> users mailing list
> users@lists.openshift.redhat.com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users