Skip to content
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

Merged
merged 1 commit into from
May 24, 2016
Merged

Conversation

bparees
Copy link
Contributor

@bparees bparees commented May 22, 2016

No description provided.

@bparees bparees force-pushed the cicd_doc branch 5 times, most recently from 973887d to 931279c Compare May 22, 2016 17:26
@bparees
Copy link
Contributor Author

bparees commented May 22, 2016

@csrwng ptal, primarily to ensure i've added this template to cluster-up correctly.

@csrwng
Copy link
Contributor

csrwng commented May 22, 2016

The bindata and cluster up partt LGTM

@bparees
Copy link
Contributor Author

bparees commented May 22, 2016

@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
Copy link
Contributor

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?

Copy link
Contributor Author

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.

Copy link
Contributor Author

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)

@gabemontero
Copy link
Contributor

Couple of minor comments / questions, otherwise GTM

@bparees bparees force-pushed the cicd_doc branch 2 times, most recently from 14d2f50 to 41b10c4 Compare May 23, 2016 00:07
@bparees
Copy link
Contributor Author

bparees commented May 23, 2016

@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
Copy link

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.

Copy link
Contributor Author

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.

Copy link

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, yes thanks.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my pleasure !

@csrwng
Copy link
Contributor

csrwng commented May 23, 2016

@bparees thanks, I will add a unit tests to cluster up to catch problems with the bindata files.

@bparees bparees force-pushed the cicd_doc branch 2 times, most recently from 63eb999 to 8a5e60b Compare May 23, 2016 18:12
@bparees
Copy link
Contributor Author

bparees commented May 23, 2016

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.
Copy link
Member

@spadgett spadgett May 23, 2016

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.

Copy link
Contributor Author

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.

@bparees
Copy link
Contributor Author

bparees commented May 24, 2016

@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:
Copy link
Contributor

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

@bparees
Copy link
Contributor Author

bparees commented May 24, 2016

[merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented May 24, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/5984/) (Image: devenv-rhel7_4272)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to d22ba66

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

openshift-bot commented May 24, 2016

continuous-integration/openshift-jenkins/test Running (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4019/)

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to d22ba66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants