Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
config
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container registry
Model registry
Operate
Environments
Monitor
Service Desk
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
ai3
config
Commits
4a9cc475
Commit
4a9cc475
authored
2 years ago
by
agata
Browse files
Options
Downloads
Patches
Plain Diff
Spiega ambiente di test
parent
2af5e9b9
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+20
-0
20 additions, 0 deletions
README.md
with
20 additions
and
0 deletions
README.md
+
20
−
0
View file @
4a9cc475
...
@@ -97,3 +97,23 @@ The services are slowly being documented:
...
@@ -97,3 +97,23 @@ The services are slowly being documented:
*
[
user-facing account management app
](
roles/accounts/README.md
)
*
[
user-facing account management app
](
roles/accounts/README.md
)
*
[
admin-facing account management app
](
roles/accountadmin/README.md
)
*
[
admin-facing account management app
](
roles/accountadmin/README.md
)
*
[
jabber
](
roles/jabber/README.md
)
*
[
jabber
](
roles/jabber/README.md
)
# Enviroment per i test
Da questo repository, i commit di e su nuove branch ed anche sulla master, innescano
dei processi di test. Quando si chiede il merge di una pull request dall'interfaccia
web di gitlab, si vede l'avanzamento della pipeline e la creazione dell'ambiente di test a
cui è possibile accedere per vedere le modifiche applicate.
Il bottone View App, ha un link simile a questo:
https://vm.investici.org/dash/i65WyixQslIyNNAzNLfQMzQ00zM0UNJRykvMTQUKZ-QXlxgCuUWJuUpWxgbmRjpKyQWlQKaOUmZuYjpISVJpTk5xamWqUq0OFrMMUc0yosQsI1SzjIk1KxYA
Dove abbiamo i comandi rapidi per accedere alle macchine virtuali create da Vagrant
Per esempio
ssh -i ~/.vagrant.d/insecure_private_key -J miscredenza.investici.org vagrant@10.178.116.10
E il comando da eseguire in locale dentro al repositori di Testbed, per vedere il servizio
attraverso un web browser.
./test-browser --proxy=localhost:9051 https://noblogs.org
Le macchine di ambiente di test rimangono attive per 3 ore, ma è anche possibile fermarle a mano,
con un bottone stop, nella pagina della merge request.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment