-
Notifications
You must be signed in to change notification settings - Fork 13
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
Complete Environment should match C4B-Azure and C4B-Ansible #291
Labels
Enhancement
Enhancements are things that are improvements or features.
Comments
JPRuskin
added a commit
that referenced
this issue
Mar 4, 2025
Configuring the Nexus users and (optionally) SSL earlier in the Nexus script allows us to use the correct users and FQDNs immediately, and result in a more immediately available environment. Now that we are always doing these actions (e.g. securing the repositories), this should also reduce a lot of confusion with what the SSL script does.
JPRuskin
added a commit
that referenced
this issue
Mar 4, 2025
Brings Jenkins configuration from the Set-SSL script to the Jenkins script, resulting in a correctly configured installation.
JPRuskin
added a commit
that referenced
this issue
Mar 4, 2025
JPRuskin
added a commit
that referenced
this issue
Mar 4, 2025
Customers are being confused by Set-SSL. This change removes remaining non-SSL-related operations from the script, which should allow it to be re-run if required (or accidentally) without issue.
JPRuskin
added a commit
that referenced
this issue
Mar 4, 2025
JPRuskin
added a commit
that referenced
this issue
Mar 4, 2025
Previously, re-running could result in a user being in use and consequently not being dropped.
JPRuskin
added a commit
that referenced
this issue
Mar 17, 2025
JPRuskin
added a commit
that referenced
this issue
Mar 17, 2025
Previously, re-running could result in a user being in use and consequently not being dropped.
JPRuskin
added a commit
that referenced
this issue
Mar 17, 2025
We should no longer tempt customer's fates by providing multiple things to enter into the terminal. Instead, we have a single thing to run, and we can drill in if we need to.
JPRuskin
added a commit
that referenced
this issue
Mar 17, 2025
We should no longer tempt customer's fates by providing multiple things to enter into the terminal. Instead, we have a single thing to run, and we can drill in if we need to.
JPRuskin
added a commit
that referenced
this issue
Mar 26, 2025
Configuring the Nexus users and (optionally) SSL earlier in the Nexus script allows us to use the correct users and FQDNs immediately, and result in a more immediately available environment. Now that we are always doing these actions (e.g. securing the repositories), this should also reduce a lot of confusion with what the SSL script does.
JPRuskin
added a commit
that referenced
this issue
Mar 26, 2025
Brings Jenkins configuration from the Set-SSL script to the Jenkins script, resulting in a correctly configured installation.
JPRuskin
added a commit
that referenced
this issue
Mar 26, 2025
JPRuskin
added a commit
that referenced
this issue
Mar 26, 2025
Customers are being confused by Set-SSL. This change removes remaining non-SSL-related operations from the script, which should allow it to be re-run if required (or accidentally) without issue.
JPRuskin
added a commit
that referenced
this issue
Mar 26, 2025
JPRuskin
added a commit
that referenced
this issue
Mar 26, 2025
Previously, re-running could result in a user being in use and consequently not being dropped.
JPRuskin
added a commit
that referenced
this issue
Mar 26, 2025
We should no longer tempt customer's fates by providing multiple things to enter into the terminal. Instead, we have a single thing to run, and we can drill in if we need to.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Is Your Feature Request Related To A Problem? Please describe.
The C4B-Azure and Quickstart Guide environments have diverged a little, and this should be corrected.
Describe The Solution. Why is it needed?
Supporting the Chocolatey for Business environments is easier if the environments are more consistent.
There are also technical improvements that can be brought across!
Additional Context
No response
Related Issues
No response
The text was updated successfully, but these errors were encountered: