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

Add Warning to Not Login to Nexus or CCM Until After Guide Finishes #161

Open
ryanrichter94 opened this issue Sep 14, 2022 · 0 comments
Open
Labels
0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. Documentation This issue requires a change to documentation. Priority_LOW Represents tickets that are of lower priority and can be taken care of whenever. Task Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.

Comments

@ryanrichter94
Copy link
Member

Is Your Feature Request Related To A Problem? Please describe.

Need to add a warning to not login to Nexus after running Step 2: Nexus setup of the guide. Mainly because this gets rid of the admin.password file that is later used to generate the readme file.

Describe The Solution. Why is it needed?

Some users of the guide are logging into Nexus as at the end of running Step 2: Nexus Setup. The login URL as well as authentication are output at the end of the step in shell.

Additional Context.

NA

Related Issues

@ryanrichter94 ryanrichter94 added Documentation This issue requires a change to documentation. 0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. Priority_LOW Represents tickets that are of lower priority and can be taken care of whenever. Task Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things. labels Sep 14, 2022
@JPRuskin JPRuskin changed the title Add Warning to Not Login to Nexus or CCM Until After Jenkins Step has been run. Add Warning to Not Login to Nexus or CCM Until After Guide Finishes Mar 1, 2024
JPRuskin added a commit that referenced this issue Apr 18, 2024
As some of the changes have resulted in a lot less noise during the script(s) running, this adds a few more bits of output to show folk that progress is being made.

Conversely, this also removes a few of the block-outputs at the end of scripts that tell the user to login - as we don't want them to login until they've completed the guide (see #161).
JPRuskin added a commit that referenced this issue Apr 18, 2024
As some of the changes have resulted in a lot less noise during the script(s) running, this adds a few more bits of output to show folk that progress is being made.

Conversely, this also removes a few of the block-outputs at the end of scripts that tell the user to login - as we don't want them to login until they've completed the guide (see #161).
JPRuskin added a commit that referenced this issue Apr 19, 2024
As some of the changes have resulted in a lot less noise during the script(s) running, this adds a few more bits of output to show folk that progress is being made.

Conversely, this also removes a few of the block-outputs at the end of scripts that tell the user to login - as we don't want them to login until they've completed the guide (see #161).
JPRuskin added a commit that referenced this issue Apr 22, 2024
As some of the changes have resulted in a lot less noise during the script(s) running, this adds a few more bits of output to show folk that progress is being made.

Conversely, this also removes a few of the block-outputs at the end of scripts that tell the user to login - as we don't want them to login until they've completed the guide (see #161).
JPRuskin added a commit that referenced this issue May 3, 2024
As some of the changes have resulted in a lot less noise during the script(s) running, this adds a few more bits of output to show folk that progress is being made.

Conversely, this also removes a few of the block-outputs at the end of scripts that tell the user to login - as we don't want them to login until they've completed the guide (see #161).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - _Triaging New tickets that need to be hashed out a bit more before they hit the backlog. Documentation This issue requires a change to documentation. Priority_LOW Represents tickets that are of lower priority and can be taken care of whenever. Task Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.
Projects
None yet
Development

No branches or pull requests

1 participant