-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add jenkins pipeline example files #8973
Conversation
973887d
to
931279c
Compare
@csrwng ptal, primarily to ensure i've added this template to cluster-up correctly. |
The bindata and cluster up partt LGTM |
@gabemontero ptal |
To walk through the example: | ||
1) Stand up an openshift cluster from origin master, installing the standard imagestreams to the openshift namespace: | ||
|
||
https://github.com/openshift/origin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since your are talking specifically about the imagestreams, should this URL include examples/image-streams/
at the end of it, possibly list the two json files as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well i was more trying to point them to origin since the step is "stand up origin" but i can add a link to the imagestreams as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(ultimately i'll probably want to update this doc to instruct people to use the new cluster up command which would include the imagestreams+template automatically)
Couple of minor comments / questions, otherwise GTM |
14d2f50
to
41b10c4
Compare
@csrwng fyi i found i couldn't specify a filename in the go-bindata path, it ended up adding it with a repeated name (jekinstemplatejsonjenkinstemplatejson" in the method name) which ultimately lead to cluster up failing when i ran it. Not sure if we have unit tests for cluster up that would have caught that? but anyway i'm now adding everything in the dir, but not installing the other files during cluster up. |
|
||
# Jenkins master template: | ||
$ oc create -f https://goo.gl/YROngT | ||
$ oc create -f $ oc create -f https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/master-slave/jenkins-master-template.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's a duplicate $ oc create -f
on this line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one is the slave file and one is the master file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure, but the result is:
**$ oc create -f $ oc create -f** https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/master-slave/jenkins-master-template.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, yes thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my pleasure !
@bparees thanks, I will add a unit tests to cluster up to catch problems with the bindata files. |
63eb999
to
8a5e60b
Compare
ok i think this is all good now, @spadgett can you give it a once over since you're pretty familiar w/ the steps at this point? |
|
||
5) View/Manage jenkins | ||
Once the jenkins pod is running, determine the jenkins service ip ("oc get svc") and go to it in your browser on port 80. Do not confuse | ||
it with the jenkins-jnlp service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the instructions to find the IP address correct using oc cluster up
? I'd expect the default Jenkins route to work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well they're still correct in that it'll work that way, but yes presumably you could access it via the route as well. I don't really like relying on the router because getting it (and DNS) working tend to be problem areas for people, though admittedly that's part of what cluster up is supposed to solve.
@spadgett comments addressed. |
utilize pods run on OpenShift as Jenkins slaves. | ||
|
||
To walk through the example: | ||
1) Stand up an openshift cluster from origin master, installing the standard imagestreams to the openshift namespace: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bparees you need empty line before 1)
otherwise markup will join it with previous line
[merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/5984/) (Image: devenv-rhel7_4272) |
Evaluated for origin merge up to d22ba66 |
[Test]ing while waiting on the merge queue |
continuous-integration/openshift-jenkins/test Running (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4019/) |
Evaluated for origin test up to d22ba66 |
No description provided.