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

What should be the jobs that we will propose when jenkins docker is created #23

Open
cmoulliard opened this issue Jun 3, 2015 · 2 comments

Comments

@cmoulliard
Copy link
Collaborator

Basic

screenshot 2015-06-03 11 14 58

More elaborated

screenshot 2015-06-03 11 14 42

or

...

@christian-posta
Copy link
Owner

Here's what I was thinking:

  • <project-name>-ci continuous integration step
  • <project-name>-it automated integration testing
  • <project-name>-dev-deploy deploy to dev namespace in kube
  • <project-name>-dev-at run any automated acceptance tests
  • <project-name>-qa-deploy deploy to QA namespace in kube
  • <project-name>-qa-at run any automated acceptance tests
  • <project-name>-qa-perf run any (optional) automated perf testing?
  • <project-name>-prod-deploy deploy to prod
  • <project-name>-prod-smoke simple smoke tests in prod

BTW... maybe we can open issues like this over at fabric8io? This sort of stuff is useful to discuss there because others might have thoughts, and we'll be implementing this over there :)

@cmoulliard
Copy link
Collaborator Author

@christian-posta Agree with you to open other issues to discuss them with Fabric8 community

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

No branches or pull requests

2 participants