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

CI environment on docker #31

Closed
DawidCh opened this Issue Apr 8, 2016 · 6 comments

Comments

Projects
None yet
4 participants
@DawidCh
Collaborator

DawidCh commented Apr 8, 2016

I as developer would like to have CI environment set up with the docker, instead of building environment from scratch using build scripts, to execute all the tests faster.

@DawidCh DawidCh self-assigned this Apr 8, 2016

@DawidCh

This comment has been minimized.

Show comment
Hide comment
@DawidCh

DawidCh Apr 18, 2016

Collaborator

... and in parallel.

Collaborator

DawidCh commented Apr 18, 2016

... and in parallel.

@StavrevaS

This comment has been minimized.

Show comment
Hide comment
@StavrevaS

StavrevaS Apr 20, 2016

Collaborator

I am not sure if we can have benefit here. First of all, if you run tests in parallel with more docker containers on your developer machine, I assume that the resources of that machine will be soon exhausted. So you cannot do your developer tasks. If you plan to also develop on the docker container, it must have access to the network (Internet and internal). And you have to be careful to save the image updates, otherwise you will lose your work.

Collaborator

StavrevaS commented Apr 20, 2016

I am not sure if we can have benefit here. First of all, if you run tests in parallel with more docker containers on your developer machine, I assume that the resources of that machine will be soon exhausted. So you cannot do your developer tasks. If you plan to also develop on the docker container, it must have access to the network (Internet and internal). And you have to be careful to save the image updates, otherwise you will lose your work.

@DawidCh

This comment has been minimized.

Show comment
Hide comment
@DawidCh

DawidCh Apr 20, 2016

Collaborator

I meant to have docker containers used for testing purposes only. Currently our CI builds environment around 30 minutes. We can save the time by downloading docker image and run the tests against the container.

Collaborator

DawidCh commented Apr 20, 2016

I meant to have docker containers used for testing purposes only. Currently our CI builds environment around 30 minutes. We can save the time by downloading docker image and run the tests against the container.

@DawidCh

This comment has been minimized.

Show comment
Hide comment
@DawidCh

DawidCh Mar 3, 2017

Collaborator

@digitalfishpond finish configuration for shippable, as agreed.

For consideration: create jenkins job which will do following sequence:

  1. BuildALL
  2. Run unit tests and it tests.
  3. Build docker image (use curently created job as template)
  4. Run ws and web tests against the image
  5. Push image to dockerhub.
    The procedure above should take less time and jenkins resources than our current process.

Prerequisits list:

  • get knowledge about running docker image under jenkins
  • expose email client port from docker image to be reachable from web and ws tests
    Post build action:
  • gather all tests results (unit, it, ws and web)
Collaborator

DawidCh commented Mar 3, 2017

@digitalfishpond finish configuration for shippable, as agreed.

For consideration: create jenkins job which will do following sequence:

  1. BuildALL
  2. Run unit tests and it tests.
  3. Build docker image (use curently created job as template)
  4. Run ws and web tests against the image
  5. Push image to dockerhub.
    The procedure above should take less time and jenkins resources than our current process.

Prerequisits list:

  • get knowledge about running docker image under jenkins
  • expose email client port from docker image to be reachable from web and ws tests
    Post build action:
  • gather all tests results (unit, it, ws and web)
@digitalfishpond

This comment has been minimized.

Show comment
Hide comment
@digitalfishpond

digitalfishpond Mar 21, 2017

Contributor

[DoD]

Job 1
Git pull
Build enterprise version
Run Unit tests
Run Integration tests
Build docker image and publish on Artifactory

Job 2
Pull docker image from Artifcatory
Run selenium
Option to build image again, so run Job 1 again

Job 3
Pull docker image from Artifcatory
Run webservice tests
Option to build image again, so run Job 1 again

Job 4
Pull docker image from Artifcatory
Run Canoo tests
Option to build image again, so run Job 1 again

Job 5
pipeline to run them all

Contributor

digitalfishpond commented Mar 21, 2017

[DoD]

Job 1
Git pull
Build enterprise version
Run Unit tests
Run Integration tests
Build docker image and publish on Artifactory

Job 2
Pull docker image from Artifcatory
Run selenium
Option to build image again, so run Job 1 again

Job 3
Pull docker image from Artifcatory
Run webservice tests
Option to build image again, so run Job 1 again

Job 4
Pull docker image from Artifcatory
Run Canoo tests
Option to build image again, so run Job 1 again

Job 5
pipeline to run them all

@DawidCh DawidCh added this to the 17.0.0 milestone Mar 23, 2017

@digitalfishpond

This comment has been minimized.

Show comment
Hide comment
@digitalfishpond

digitalfishpond Mar 31, 2017

Contributor

So far, implemented on branch 'fb_web_integration_tests', and in Jenkins (jobs on the tab: 'CD on Docker') the following have been implemented:

  • pull project from Git hub and Git lab
  • build enterprise version
  • run Unit Tests
  • run Integration Tests
  • build Docker Image
  • publish resulting docker image on Artifactory
  • run selenium tests

Remains to be done:

  • (successfully) run webservice tests
  • (successfully) run canoo tests
Contributor

digitalfishpond commented Mar 31, 2017

So far, implemented on branch 'fb_web_integration_tests', and in Jenkins (jobs on the tab: 'CD on Docker') the following have been implemented:

  • pull project from Git hub and Git lab
  • build enterprise version
  • run Unit Tests
  • run Integration Tests
  • build Docker Image
  • publish resulting docker image on Artifactory
  • run selenium tests

Remains to be done:

  • (successfully) run webservice tests
  • (successfully) run canoo tests

@GoebelL GoebelL modified the milestones: 17.0.0, 17.1.0 Apr 27, 2017

@DawidCh DawidCh modified the milestones: 17.2.0, 17.1.0 May 23, 2017

@DawidCh DawidCh assigned DawidCh and unassigned digitalfishpond May 25, 2017

DawidCh pushed a commit that referenced this issue May 25, 2017

DawidCh pushed a commit that referenced this issue May 25, 2017

DawidCh pushed a commit that referenced this issue May 25, 2017

DawidCh pushed a commit that referenced this issue May 25, 2017

DawidCh pushed a commit that referenced this issue May 26, 2017

DawidCh pushed a commit that referenced this issue May 29, 2017

DawidCh pushed a commit that referenced this issue May 29, 2017

DawidCh pushed a commit that referenced this issue May 29, 2017

DawidCh pushed a commit that referenced this issue May 29, 2017

DawidCh pushed a commit that referenced this issue May 30, 2017

DawidCh pushed a commit that referenced this issue May 30, 2017

DawidCh pushed a commit that referenced this issue Jun 14, 2017

DawidCh pushed a commit that referenced this issue Jun 19, 2017

DawidCh pushed a commit that referenced this issue Jun 19, 2017

DawidCh pushed a commit that referenced this issue Jun 19, 2017

DawidCh pushed a commit that referenced this issue Jun 20, 2017

DawidCh pushed a commit that referenced this issue Jun 20, 2017

DawidCh pushed a commit that referenced this issue Jun 20, 2017

DawidCh pushed a commit that referenced this issue Jun 20, 2017

DawidCh pushed a commit that referenced this issue Jun 20, 2017

DawidCh pushed a commit that referenced this issue Jun 20, 2017

DawidCh pushed a commit that referenced this issue Jun 20, 2017

DawidCh pushed a commit that referenced this issue Jun 21, 2017

DawidCh pushed a commit that referenced this issue Jun 22, 2017

@GoebelL GoebelL modified the milestones: 17.2.0, 17.3.0 Jun 29, 2017

@GoebelL GoebelL modified the milestones: 17.3.0, 17.4.0 Aug 14, 2017

@GoebelL GoebelL modified the milestones: 17.4.0, 17.5.0-TomEE Sep 21, 2017

@GoebelL GoebelL added the area/build label Sep 21, 2017

@GoebelL GoebelL closed this Dec 5, 2017

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