pim
opened 1 month ago
-
The terminal opens and I can type in it but there is no interaction
What type of executor the job is using?
I couldn't find the "permission to edit build spec of running job" anywhere
It is not possible to edit build spec of running job, which corresponds to a particular commit. You can only edit build spec on relevant branch, and run build again on branch tip.
-
What type of executor the job is using?
It's using the remote docker executor
It is not possible to edit build spec of running job, which corresponds to a particular commit. You can only edit build spec on relevant branch, and run build again on branch tip.
The documentation says: "Now when a job starts, users with permission to edit build spec of running job will be able to open the interactive shell to check the live environment." I'm still not sure if I have that permission. I'm not trying to change the build spec while it is running per se. (I can change build spec when it is not running of course)
-
It's using the remote docker executor
I ran both OneDev server and agent in a docker container, and create job runing a new command build step with a simple pause instruction, then run it with remote docker job executor on the agent, and the terminal works fine.
The documentation says: "Now when a job starts, users with permission to edit build spec of running job will be able to open the interactive shell to check the live environment." I'm still not sure if I have that permission. I'm not trying to change the build spec while it is running per se. (I can change build spec when it is not running of course)
Yes, as soon as you have the permission to edit the build spec, you should be able to open the terminal. For testing purpose, you may just login as site administrator to see if it works normally. If this still does not work, please check if the issue can be reproduced with a brand new OneDev setup, and then tell me detail steps to reproduce, including OS/browser info and example build spec used.
-
I have tried with multiple accounts. It just looks like it should work but nothing happens in the terminal (as shown in image).
There is no switch or (on executor or agent settings) that I have to enable to make terminals work right? I didn't see any. Onedev is up to date. I'll get back to you if I find the time to setup a new onedev instance.
Tthank you for the swift response each time! This kind of support makes me happy we choose onedev.
-
No any other switches. Please test if it works with other browsers such as Chrome.
-
Also check server log to see if there are any errors printed.
-
Also check server log to see if there are any errors printed.
Check agent log running the job.
-
Feel free to reopen if there is more info
-
Previous Value Current Value Open
Closed
| Type |
Question
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
After enabling the trial subscription I wanted to use the web-terminal on a running (paused) ci-job. The terminal opens and I can type in it but there is no interaction. The web-terminal-demonstration gif shows a hashtag on the start of the line which I also do not see.
In my project I run the CI that is imported from a different project that contains the CI definition. I added the pause statement (as suggested in documentation) in the code that I run inside a docker image and started a job. The job pauses as expected and I see the icon to open the web-terminal (but not the pencil icon as in the previously mentioned demonstration gif). Typing in the terminal does not make anything happen.
I couldn't find the "permission to edit build spec of running job" anywhere but I am owner of the project and admin on the platform. Is this a bug or am I doing something wrong?