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

Change pipeline sample to use Node.js+MongoDB sample #11476

Merged
merged 1 commit into from Oct 22, 2016
Merged

Change pipeline sample to use Node.js+MongoDB sample #11476

merged 1 commit into from Oct 22, 2016

Conversation

sspeiche
Copy link
Contributor

Since we don't have a ruby slave, we should leverage the nodejs slave we have

@bparees bparees removed their assignment Oct 21, 2016
@bparees
Copy link
Contributor

bparees commented Oct 21, 2016

there's really no point. even if we use the nodejs slave, we're not actually executing any build operations on the slave or leveraging any platform specifics from the slave. The build operations happen in openshift (we just trigger a ruby/nodejs/whatever buildconfig in openshift).

so with that in mind do you still want the example updated?

@sspeiche
Copy link
Contributor Author

Understand on the slave point, was just trying to align the pipeline sample with slaves we have. A common source of confusion I've seen where people see the Ruby sample, the preference is node or java. This PR was to help with that confusion and give a better starting example.

Copy link
Contributor

@bparees bparees left a comment

Choose a reason for hiding this comment

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

one nit and i'm going to assume you've tested this :)

"port": 5432,
"targetPort": 8080,
"nodePort": 0

Copy link
Contributor

@bparees bparees Oct 21, 2016

Choose a reason for hiding this comment

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

delete the extra newline

@bparees bparees self-assigned this Oct 21, 2016
…" Jenkins slave.

fixed space and service dependency annotation
@sspeiche
Copy link
Contributor Author

Push deleted line and also noticed an error in the service grouping annotation and yes I tested it!

@bparees
Copy link
Contributor

bparees commented Oct 21, 2016

did you regen the bootstrap content? travis isn't happy

@sspeiche
Copy link
Contributor Author

I did regen it. I just regen'd locally and git doesn't see a difference. Will continue to investigate.

@bparees
Copy link
Contributor

bparees commented Oct 21, 2016

[merge]

we'll see what the merge queue says.

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to a68d9ae

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to a68d9ae

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10427/) (Base Commit: 2dccff1)

@openshift-bot
Copy link
Contributor

openshift-bot commented Oct 22, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10475/) (Base Commit: d4771f5) (Image: devenv-rhel7_5227)

@openshift-bot openshift-bot merged commit de9f453 into openshift:master Oct 22, 2016
@@ -43,463 +43,455 @@
"strategy": {
"type": "JenkinsPipeline",
"jenkinsPipelineStrategy": {
"jenkinsfile": "node('maven') {\nstage 'build'\nopenshiftBuild(buildConfig: 'ruby-sample-build', showBuildLogs: 'true')\nstage 'deploy'\nopenshiftDeploy(deploymentConfig: 'frontend')\n}"
"jenkinsfile": "node('nodejs') {\nstage 'build'\nopenshiftBuild(buildConfig: '${NAME}' showBuildLogs: 'true')\nstage 'deploy'\nopenshiftDeploy(deploymentConfig: '${NAME}')\n}"

Choose a reason for hiding this comment

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

should add a comma before 'showBuildLogs'

Copy link
Contributor

Choose a reason for hiding this comment

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

thanks @dongboyan77

@sspeiche you said you tested this....

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@bparees I guess not enough, I did deploy the template but I guess I was impatient to wait for Jenkins to run (walks away hanging head in shame)

Copy link
Contributor

Choose a reason for hiding this comment

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

fixing here #11576

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

Successfully merging this pull request may close these issues.

None yet

5 participants