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

[#115845521] Move bosh-cli to Makefile #165

Merged
merged 4 commits into from
Mar 21, 2016
Merged

Conversation

combor
Copy link
Contributor

@combor combor commented Mar 17, 2016

What

This is a fix for bosh-cli.sh as #159 introduced SYSTEM_DNS_ZONE_NAME variable. This var is set only by running make so we had to move bosh-cli.sh execution to Makefile. Additionally we re-arranged all targets so it's now possible to execute make $ENV bootstrap. Read the updated README if you want more details.

How to review

Check if make dev bosh-cli works properly and connects to Concourse container. Also, run create-bosh-cloudfoundry pipeline and make sure that test-bosh-cli job succeeds .

Who can review

Not @jimconner or @combor

@combor combor changed the title 115845521 fix bosh cli [#115845521] Move bosh-cli to Makefile Mar 17, 2016
@mtekel mtekel self-assigned this Mar 17, 2016
prod: check-env-vars set_env_class_prod ## Set Envirnoment to Production

.PHONY: bootstrap
bootstrap: vagrant-deploy ## Start bootsrap
Copy link
Contributor

Choose a reason for hiding this comment

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

We don't need a separate target for vagrant-deploy anymore. The contents could be moved into this target like bootstrap-destroy.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Correct. Fixed.

@combor combor force-pushed the 115845521_fix_bosh_cli branch from 101be1b to 6c7d50c Compare March 17, 2016 16:17
@mtekel
Copy link
Contributor

mtekel commented Mar 17, 2016

bosh-cli-test is nice, but does it really need to run on every build (it's being triggered)?

@combor combor force-pushed the 115845521_fix_bosh_cli branch from 6c7d50c to 80d8354 Compare March 17, 2016 16:21
@mtekel
Copy link
Contributor

mtekel commented Mar 17, 2016

Also, given the amount of tests we have now, would it make sense to create a group for tests only?

@dcarley
Copy link
Contributor

dcarley commented Mar 17, 2016

bosh-cli-test is nice, but does it really need to run on every build (it's being triggered)?

Would we know if it was broken if we didn't trigger it on every build?

@mtekel
Copy link
Contributor

mtekel commented Mar 17, 2016

Maybe we can just trigger as apart of review process?

@combor combor force-pushed the 115845521_fix_bosh_cli branch from 80d8354 to 9d9bb42 Compare March 17, 2016 16:27
@combor
Copy link
Contributor Author

combor commented Mar 17, 2016

Also, given the amount of tests we have now, would it make sense to create a group for tests only?

Done.

@dcarley
Copy link
Contributor

dcarley commented Mar 17, 2016

Maybe we can just trigger as apart of review process?

Nah, we should leave it automated. Otherwise we'll forget to run it and then there's no benefit. It shouldn't cause any harm running it each time - I believe it's in parallel to the other tests, so it won't slow anything down.

@jimconner jimconner force-pushed the 115845521_fix_bosh_cli branch from 4dbb4e0 to 3724a6f Compare March 17, 2016 16:44
@@ -25,4 +25,4 @@ $FLY_CMD -t "${FLY_TARGET}" \
intercept \
--build="${BUILD_NUMBER}"\
--step=one-off \
${2:-sh}
"${2:-sh}"
Copy link
Contributor

Choose a reason for hiding this comment

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

squash this in to previous commit

@mtekel
Copy link
Contributor

mtekel commented Mar 17, 2016

Would it be a better test to do some actual operation inside bosh-cli container, like bosh vms? Currently we just check if we can run that container at all... (and if it has true command).

@mtekel
Copy link
Contributor

mtekel commented Mar 17, 2016

Apart from these last remarks it all works as described.

@alext
Copy link
Contributor

alext commented Mar 18, 2016

Would it be a better test to do some actual operation inside bosh-cli container, like bosh vms?

I'm not sure that's necessary. This is intended to verify that the container orchestration works. to get this far it will have had to do a bosh login, so we've already verified that it can talk to bosh etc.

export CONCOURSE_ATC_PASSWORD
./paas-cf/concourse/scripts/bosh-cli.sh {{deploy_env}} true


- name: tag-release
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we want to trigger this from the new test task as well?

@combor combor force-pushed the 115845521_fix_bosh_cli branch from 3724a6f to 73a7f16 Compare March 18, 2016 09:49
@combor
Copy link
Contributor Author

combor commented Mar 18, 2016

All comments resolved. Please re-check.

@mtekel
Copy link
Contributor

mtekel commented Mar 18, 2016

Few things about bosh-cli test:

  1. the commit message is wrong (contains description of curl-ssl)
  2. what exactly is this trying to test? If the test wants to test that we (operators) can still get interactive and working bosh shell, then it should do the same steps as we do - "make dev bosh-cli" - and run a 'bosh vms' or 'bosh cck' command, to verify that the code of the (1) makefile, (2) bosh-cli script and (3) bosh-cli.yml are all working.
  3. If it intends to test only a single aspect of the chain (ability to do fly hijack), then it should be renamed (e.g. test fly-intercept) and we should think about testing other parts of the bosh-cli chain

@combor combor force-pushed the 115845521_fix_bosh_cli branch from 73a7f16 to 07c1d57 Compare March 18, 2016 11:25
@combor
Copy link
Contributor Author

combor commented Mar 18, 2016

  1. the commit message is wrong (contains description of curl-ssl)

Fixed.

@alext
Copy link
Contributor

alext commented Mar 18, 2016

what exactly is this trying to test?

Following a discussion, I think it's reasonable to extend the test to call bosh status. This actually verifies that it can talk to bosh instead of the implicit reliance on the bosh login having happened.

@combor combor force-pushed the 115845521_fix_bosh_cli branch 2 times, most recently from 4360bf3 to 37ac77e Compare March 18, 2016 15:38
@combor combor force-pushed the 115845521_fix_bosh_cli branch 3 times, most recently from 64c4fa7 to 4b5d3b1 Compare March 18, 2016 16:21
We have added new bosh-cli target and simplified existing bootstrap
targets. It's now possible to execute `make dev bosh-cli` and `make dev
bootstrap`.
@combor combor force-pushed the 115845521_fix_bosh_cli branch from 4b5d3b1 to fde728c Compare March 18, 2016 16:36
@combor
Copy link
Contributor Author

combor commented Mar 18, 2016

I believe that all comments have been resolved.

necessary to start with a comletely new deployment.

**Note:** Different AWS accounts use different DNS names, so it'll be necessary
to adjust some of the instructions above accordingly.
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think you meant to add this back in. These docs have moved into the separate linked doc.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Probably it's a rebase leftover. I'll remove it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Removed.

Piotr Komborski added 3 commits March 21, 2016 09:52
We need small adjustments of README after re-arranging Makefile targets.
So we can pass custom command to run inside container.
This is a new job that is testing whether bosh-cli script is not
broken. It uses ruby container and installs bash as all scripts need
it. Next it connects to Concourse container and exits.
@combor combor force-pushed the 115845521_fix_bosh_cli branch from fde728c to d0678ec Compare March 21, 2016 09:53
@mtekel
Copy link
Contributor

mtekel commented Mar 21, 2016

works, merging

mtekel added a commit that referenced this pull request Mar 21, 2016
[#115845521] Move bosh-cli to Makefile
@mtekel mtekel merged commit 2fef897 into master Mar 21, 2016
@mtekel mtekel deleted the 115845521_fix_bosh_cli branch March 21, 2016 14:43
@keymon
Copy link
Contributor

keymon commented Mar 22, 2016

Now self-update-pipelines does not work!!! 😱

It only calls make dev or whatever.

keymon added a commit that referenced this pull request Mar 22, 2016
After #165 you must pass the target `pipelines` to update the pipelines,
but the `self-update-pipeline.sh` script was not updated.
@keymon
Copy link
Contributor

keymon commented Mar 22, 2016

PR to fix self-update #172

keymon added a commit that referenced this pull request Mar 22, 2016
After #165 you must pass the target `pipelines` to update the pipelines,
but the `self-update-pipeline.sh` script was not updated.
keymon added a commit that referenced this pull request Mar 23, 2016
After #165 you must pass the target `pipelines` to update the pipelines,
but the `self-update-pipeline.sh` script was not updated.
keymon added a commit that referenced this pull request Mar 23, 2016
After #165 you must pass the target `pipelines` to update the pipelines,
but the `self-update-pipeline.sh` script was not updated.
keymon added a commit that referenced this pull request Mar 23, 2016
After #165 you must pass the target `pipelines` to update the pipelines,
but the `self-update-pipeline.sh` script was not updated.
keymon added a commit that referenced this pull request Mar 23, 2016
After #165 you must pass the target `pipelines` to update the pipelines,
but the `self-update-pipeline.sh` script was not updated.
keymon added a commit that referenced this pull request Mar 23, 2016
After #165 you must pass the target `pipelines` to update the pipelines,
but the `self-update-pipeline.sh` script was not updated.
richardTowers added a commit that referenced this pull request Apr 26, 2019
Full diff: alphagov/paas-admin@v0.82.0...v0.94.0

Contains the following PRs by human beings:

- #146 Stub APIs needed for the calculator
- #148 Request logging
- #160 Use javascript naming for request log interceptor
- #173 Support: Fix bug showing allocations
- #180 Skip calculator getQuote if there are no items
- #181 Remove low-value, flakey test

And the following dependabot specials:

- #161 Bump nunjucks from 3.1.3 to 3.2.0
- #165 Bump glob from 7.1.2 to 7.1.3
- #164 Bump @types/source-map-support from 0.4.1 to 0.5.0
- #162 Bump webpack-cli from 3.1.0 to 3.3.1
- #170 Bump pino from 5.1.0 to 5.12.3
- #169 Bump @types/jest from 23.3.1 to 24.0.11
- #168 Bump nodemon-webpack-plugin from 4.0.3 to 4.0.8
- #167 Bump express-static-gzip from 1.1.1 to 1.1.3
- #166 Bump @types/uuid from 3.4.3 to 3.4.4
- #163 Bump @types/helmet from 0.0.38 to 0.0.43
- #174 Bump tslint-microsoft-contrib from 5.2.0 to 6.1.1
- #175 Bump qs from 6.5.2 to 6.7.0
- #176 Bump moment from 2.22.2 to 2.24.0
- #177 Bump jest from 23.5.0 to 23.6.0
- #178 Bump @types/passport from 0.4.6 to 1.0.0
- #179 Bump jest and ts-jest
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.

6 participants