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

ENDOC-645 Support native k8s image builds in CI/CD pipelines #663

Merged
merged 3 commits into from
Jan 20, 2023

Conversation

Lyd1aCla1r3
Copy link
Contributor

i am absolutely overthinking this. @jyunmitch which do you like better?

OR

- Setting the `skipDockerBuild` option allows the user to create a custom image build. No images are generated for the bundle and microservices, but the YAML descriptors and Dockerfile are created in the `.output` folder.
- The command `ent bundle images` returns the Docker image names and tags, which are used to manually build the bundle and microservice images in the `.output` and microservice folders, respectively.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I like this much better. The first one, you have to decipher what is what.

It should match the other flag formats on the page, like this one, it's much easier to read
--fail-fast:
- Fail the command as soon as any subtask fails

  • --max-parallel=<value>:
    • Maximum number of subtasks running simultaneously. The default value is 3. Setting max-parallel=1 results in a sequential process.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i liked the second better too. and yes, these bullets will fall under the commands listed above the first option

@@ -105,6 +105,8 @@ See the [Build and Publish a Simple Bundle](../../tutorials/create/pb/publish-si
|`ent bundle pack`| Generate the bundle artifacts, the bundle image and the microservice images |
|`ent bundle pack --org [organization]`| Generate the bundle artifacts and images, passing the organization name to Docker Hub |
|`ent bundle pack --file [my-dockerfile]`| Use a custom Dockerfile for the bundle |
|`ent bundle pack -s`| Create YAML descriptors and bundle the Dockerfile |
Copy link
Collaborator

Choose a reason for hiding this comment

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

is it bundling the Dockerfile?

Copy link
Member

Choose a reason for hiding this comment

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

Nope. ent bundle pack --help says this "-s, --skip-docker-build Skip the building of Docker images"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

sorry! meant to fix this; copied it before looking at the ENG ticket...

@@ -105,6 +105,8 @@ See the [Build and Publish a Simple Bundle](../../tutorials/create/pb/publish-si
|`ent bundle pack`| Generate the bundle artifacts, the bundle image and the microservice images |
|`ent bundle pack --org [organization]`| Generate the bundle artifacts and images, passing the organization name to Docker Hub |
|`ent bundle pack --file [my-dockerfile]`| Use a custom Dockerfile for the bundle |
|`ent bundle pack --skip-docker-build`| Skip the building of Docker images |
Copy link
Collaborator

Choose a reason for hiding this comment

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

Add just "-s"? I think it would be helpful to let them know that -s works the same. Not sure if it belongs here or down below in the details.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i was on the fence with this... we haven't been using shorthand and just recently changed all the ent ks to ent kubectl... the help text displays -s as an option so i think if they're in deep enough to need a shortcut it's readily available. we can discuss later, too

@Lyd1aCla1r3 Lyd1aCla1r3 merged commit fd06eca into main Jan 20, 2023
@nshaw nshaw deleted the ENDOC-645 branch May 23, 2023 13:45
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.

3 participants