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

Build steps for Jenkins job to deploy the dashboard #201

Closed
5 of 6 tasks
as33ms opened this issue Jul 3, 2015 · 7 comments
Closed
5 of 6 tasks

Build steps for Jenkins job to deploy the dashboard #201

as33ms opened this issue Jul 3, 2015 · 7 comments
Assignees
Milestone

Comments

@as33ms
Copy link
Contributor

as33ms commented Jul 3, 2015

The idea behind this story is to have it documented, the steps that are required to setup dashboard on any new computer (here, jenkins). Once we have them, those steps will be used to configure the Jenkins jobs.

This would contain items like:

  • Installing relevant dependencies (one time activity in Jenkins)
  • Cloning of relevant repositories (one time activity in Jenkins)
  • Documenting all the steps required to compile / build the software
  • Add documentation to README
  • Running meteor with a specific settings file to deploy the changes on jenkins.apinf.com's temp folder (usually, the build folder).
  • Running the tests on this temp deployment (and once successful, follow up with deployment to pre-release)
@bajiat
Copy link
Contributor

bajiat commented Jul 23, 2015

@ashakunt Hi Aseem, can you tell me the status of this task?

@as33ms
Copy link
Contributor Author

as33ms commented Jul 24, 2015

Steps were already written in jenkins jobs but they were technical views. We should have them added to README, which was not done.

I was able to run two separate instances of meteor at differnet ports on my machine. So, it matches the proof of concept about running multiple builds together.

@as33ms
Copy link
Contributor Author

as33ms commented Jul 24, 2015

The task now mainly depends on "writing unit tests" or "functional tests" and once that is done, running tests on temp deployment would be completed.

@bajiat
Copy link
Contributor

bajiat commented Jul 24, 2015

Thanks for the update!
We will add testing to the automation process once we have clarity on how to test. In order to move forward, separate deployment from testing for the time being.

@bajiat
Copy link
Contributor

bajiat commented Jul 27, 2015

@ashakuntal Are you still interested on working on this task in Sprint 8? If yes, is 1 your current estimate for remaining effort?

@as33ms
Copy link
Contributor Author

as33ms commented Jul 28, 2015

@baijat, I was going through the steps required to document in README and I see them already documented here: https://github.com/brylie/meteor-api-umbrella#installation; hence, this task can now be closed.

@as33ms
Copy link
Contributor Author

as33ms commented Jul 28, 2015

I will move this to closed now. For running tests, we should probably handle that in another task (and when we have them). Please move this to ready / backlog if you disagree.

@as33ms as33ms closed this as completed Jul 28, 2015
brylie pushed a commit that referenced this issue Jan 10, 2017
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

3 participants