github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 20:07:40 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

$GITHUB_OUTPUT not available between jobs #12031

New Issue
Closed
opened 2025-11-02 09:55:14 -06:00 by GiteaMirror · 15 comments
GiteaMirror commented 2025-11-02 09:55:14 -06:00
Owner
Copy Link

Originally created by @kristophercrawford on GitHub (Nov 16, 2023).

Description

I copied the workflow file from https://github.com/go-gitea/gitea/pull/24230 and ran this on my Gitea instance. The result of the jobs is captured below in screenshots.

image image

Gitea Version

1.21.0+rc2-55

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

2.30.2

Operating System

Ubuntu 22.04

How are you running Gitea?

Pre-compiled binary for arm64 on an Orange Pi 5, running through systemd (gitea and act_runner).

Database

MySQL/MariaDB

Originally created by @kristophercrawford on GitHub (Nov 16, 2023). ### Description I copied the workflow file from https://github.com/go-gitea/gitea/pull/24230 and ran this on my Gitea instance. The result of the jobs is captured below in screenshots. <img width="892" alt="image" src="https://github.com/go-gitea/gitea/assets/32402434/f088fd5f-dd4b-4ec2-9f7e-30a3aab4ca86"> <img width="903" alt="image" src="https://github.com/go-gitea/gitea/assets/32402434/56c6a761-0e6b-4c5a-8027-6ebd023179a0"> ### Gitea Version 1.21.0+rc2-55 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.30.2 ### Operating System Ubuntu 22.04 ### How are you running Gitea? Pre-compiled binary for arm64 on an Orange Pi 5, running through systemd (gitea and act_runner). ### Database MySQL/MariaDB
GiteaMirror added the issue/needs-feedbacktype/bug labels 2025-11-02 09:55:14 -06:00
GiteaMirror commented 2025-11-02 09:55:15 -06:00
Author
Owner
Copy Link

@lng2020 commented on GitHub (Nov 17, 2023):

That workflow file doesn't work for me either.

@lng2020 commented on GitHub (Nov 17, 2023): That workflow file doesn't work for me either.
GiteaMirror commented 2025-11-02 09:55:15 -06:00
Author
Owner
Copy Link

@ednxzu commented on GitHub (Nov 26, 2023):

Same thing,
I opened an issue here because I'm not sure whether it is a gitea or act runner problem.

@ednxzu commented on GitHub (Nov 26, 2023): Same thing, I opened an issue [here](https://gitea.com/gitea/act_runner/issues/428) because I'm not sure whether it is a gitea or act runner problem.
GiteaMirror commented 2025-11-02 09:55:15 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 29, 2023):

I know the reason.
I think this was fixed by https://github.com/go-gitea/gitea/pull/28149

The output results will be saved in DB, but before this fix, the target table does not exsit.
So try the latest version, or add this table by yourself, can fix this issue.

image
↑ Your hello world, timestamp and so on should be here, but this table is missing, so you can not get them in job2.

@yp05327 commented on GitHub (Nov 29, 2023): I know the reason. I think this was fixed by https://github.com/go-gitea/gitea/pull/28149 The output results will be saved in DB, but before this fix, the target table does not exsit. So try the latest version, or add this table by yourself, can fix this issue. ![image](https://github.com/go-gitea/gitea/assets/18380374/7012abad-2af7-4685-bcc0-16dfa99548ad) ↑ Your `hello world`, `timestamp` and so on should be here, but this table is missing, so you can not get them in job2.
GiteaMirror commented 2025-11-02 09:55:16 -06:00
Author
Owner
Copy Link

@ednxzu commented on GitHub (Nov 29, 2023):

Yup, moving to 1.21.1 worked for me. Thanks for looking into it. @kristophercrawford are you still having the issue ?

@ednxzu commented on GitHub (Nov 29, 2023): Yup, moving to 1.21.1 worked for me. Thanks for looking into it. @kristophercrawford are you still having the issue ?
GiteaMirror commented 2025-11-02 09:55:16 -06:00
Author
Owner
Copy Link

@kristophercrawford commented on GitHub (Nov 29, 2023):

No change after updating to Gitea version 1.21.1. Where is the gitea.db file located? I am using the compiled binary installation file on a physical machine running MySQL as the backend database.

image
@kristophercrawford commented on GitHub (Nov 29, 2023): No change after updating to Gitea version 1.21.1. Where is the `gitea.db` file located? I am using the compiled binary installation file on a physical machine running MySQL as the backend database. <img width="1612" alt="image" src="https://github.com/go-gitea/gitea/assets/32402434/862d630a-adac-4324-8125-8ddd19c379f7">
GiteaMirror commented 2025-11-02 09:55:16 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 29, 2023):

I use sqlite for testing and it saves data into gitea.db file.
But it should have no difference between different databases.

If you can access your database, you can check whether there‘s a table named action_task_output and any data in this table.
Or if you can get your Gitea instance's logs, you can check whether there are some logs like Table gitea.action_task_output doesn't exist.
image

If the table is existing, but output still don't work. Maybe there are some other issues.

@yp05327 commented on GitHub (Nov 29, 2023): I use sqlite for testing and it saves data into `gitea.db` file. But it should have no difference between different databases. If you can access your database, you can check whether there‘s a table named `action_task_output` and any data in this table. Or if you can get your Gitea instance's logs, you can check whether there are some logs like `Table gitea.action_task_output` doesn't exist. ![image](https://github.com/go-gitea/gitea/assets/18380374/7af77b77-5300-49da-b5da-c45a509eeed9) If the table is existing, but output still don't work. Maybe there are some other issues.
GiteaMirror commented 2025-11-02 09:55:16 -06:00
Author
Owner
Copy Link

@kristophercrawford commented on GitHub (Nov 29, 2023):

Here is what I am seeing on the db side:

MariaDB [gitea]> describe action_task_output;
+--------------+--------------+------+-----+---------+----------------+
| Field        | Type         | Null | Key | Default | Extra          |
+--------------+--------------+------+-----+---------+----------------+
| id           | bigint(20)   | NO   | PRI | NULL    | auto_increment |
| task_id      | bigint(20)   | YES  | MUL | NULL    |                |
| output_key   | varchar(255) | YES  |     | NULL    |                |
| output_value | mediumtext   | YES  |     | NULL    |                |
+--------------+--------------+------+-----+---------+----------------+
4 rows in set (0.002 sec)

MariaDB [gitea]> select * from action_task_output\G
*************************** 1. row ***************************
          id: 1
     task_id: 822
  output_key: output2
output_value: 8c8c7b6b-ef4b-45bb-a87c-5613a3e9c224
*************************** 2. row ***************************
          id: 2
     task_id: 822
  output_key: output1
output_value: 2023-11-29T12:17:08+00:00
2 rows in set (0.001 sec)

MariaDB [gitea]>

No errors in the gitea.log after upgrading to 1.21.1. The log message here is from before the upgrade.

root@dev-pi:/var/lib/gitea/log# grep '\[E\]' gitea.log
2023/11/29 12:08:05 ...ions/runner/utils.go:45:pickTask() [E] Cannot find needs for task 821: FindTaskOutputByTaskID: Error 1146 (42S02): Table 'gitea.action_task_output' doesn't exist
@kristophercrawford commented on GitHub (Nov 29, 2023): Here is what I am seeing on the db side: ```sql MariaDB [gitea]> describe action_task_output; +--------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +--------------+--------------+------+-----+---------+----------------+ | id | bigint(20) | NO | PRI | NULL | auto_increment | | task_id | bigint(20) | YES | MUL | NULL | | | output_key | varchar(255) | YES | | NULL | | | output_value | mediumtext | YES | | NULL | | +--------------+--------------+------+-----+---------+----------------+ 4 rows in set (0.002 sec) MariaDB [gitea]> select * from action_task_output\G *************************** 1. row *************************** id: 1 task_id: 822 output_key: output2 output_value: 8c8c7b6b-ef4b-45bb-a87c-5613a3e9c224 *************************** 2. row *************************** id: 2 task_id: 822 output_key: output1 output_value: 2023-11-29T12:17:08+00:00 2 rows in set (0.001 sec) MariaDB [gitea]> ``` No errors in the `gitea.log` after upgrading to 1.21.1. The log message here is from before the upgrade. ``` root@dev-pi:/var/lib/gitea/log# grep '\[E\]' gitea.log 2023/11/29 12:08:05 ...ions/runner/utils.go:45:pickTask() [E] Cannot find needs for task 821: FindTaskOutputByTaskID: Error 1146 (42S02): Table 'gitea.action_task_output' doesn't exist ```
GiteaMirror commented 2025-11-02 09:55:17 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 29, 2023):

It seems that we have another issue here. 😕

@yp05327 commented on GitHub (Nov 29, 2023): It seems that we have another issue here. 😕
GiteaMirror commented 2025-11-02 09:55:17 -06:00
Author
Owner
Copy Link

@kristophercrawford commented on GitHub (Nov 29, 2023):

Fresh install of 1.21.1 works on bare metal, upgrading from 1.21.0+rc2-55 to 1.21.1 is what didn't work for me.

@kristophercrawford commented on GitHub (Nov 29, 2023): Fresh install of 1.21.1 works on bare metal, upgrading from 1.21.0+rc2-55 to 1.21.1 is what didn't work for me.
GiteaMirror commented 2025-11-02 09:55:17 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 30, 2023):

Fresh install 1.21.0+rc2, run the workflow, it don't work. Then upgrade it to 1.21.1, rerun the workflow, it worked.
Tried both Mysql 8.0.28 and Sqlite3. 😕

ps: I can only get 1.21.0+rc2 from dl.gitea.com, where did you get 1.21.0+rc2-55?

@yp05327 commented on GitHub (Nov 30, 2023): Fresh install `1.21.0+rc2`, run the workflow, it don't work. Then upgrade it to `1.21.1`, rerun the workflow, it worked. Tried both Mysql 8.0.28 and Sqlite3. 😕 ps: I can only get `1.21.0+rc2` from `dl.gitea.com`, where did you get `1.21.0+rc2-55`?
GiteaMirror commented 2025-11-02 09:55:18 -06:00
Author
Owner
Copy Link

@kristophercrawford commented on GitHub (Nov 30, 2023):

I believe I got it from here: https://dl.gitea.com/gitea/1.21.0-rc2/

Also, I think I figured out our installation differences. I am also using haproxy to terminate ssl for gitea and perform a port translation from 443 on the outside to 3000 on the gitea server. If I disable that by changing the ROOT_URL and access gitea directly and run the same workflow, the data populates as expected in the second job.

Moving the ROOT_URL back to the external domain breaks the output on the second job.

@kristophercrawford commented on GitHub (Nov 30, 2023): I believe I got it from here: https://dl.gitea.com/gitea/1.21.0-rc2/ Also, I think I figured out our installation differences. I am also using haproxy to terminate ssl for gitea and perform a port translation from 443 on the outside to 3000 on the gitea server. If I disable that by changing the `ROOT_URL` and access gitea directly and run the same workflow, the data populates as expected in the second job. Moving the `ROOT_URL` back to the external domain breaks the output on the second job.
GiteaMirror commented 2025-11-02 09:55:18 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 30, 2023):

Thanks for your test and report. I think this information is helpful and important for us to detect the porblem.

@yp05327 commented on GitHub (Nov 30, 2023): Thanks for your test and report. I think this information is helpful and important for us to detect the porblem.
GiteaMirror commented 2025-11-02 09:55:19 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Nov 30, 2023):

Which ROOT_URL (Gitea instance URL) when you register the runner?

@yp05327 commented on GitHub (Nov 30, 2023): Which `ROOT_URL` (Gitea instance URL) when you register the runner?
GiteaMirror commented 2025-11-02 09:55:19 -06:00
Author
Owner
Copy Link

@kristophercrawford commented on GitHub (Nov 30, 2023):

I have tried setting act_runner to use 127.0.0.1:3000, 192.168.10.88:3000, and my external domain. The only time I am seeing output in the job2 data is when I have the ROOT_URL set to the internal IP of 192.168.10.88:3000.

@kristophercrawford commented on GitHub (Nov 30, 2023): I have tried setting act_runner to use 127.0.0.1:3000, 192.168.10.88:3000, and my external domain. The only time I am seeing output in the job2 data is when I have the `ROOT_URL` set to the internal IP of 192.168.10.88:3000.
GiteaMirror commented 2025-11-02 09:55:20 -06:00
Author
Owner
Copy Link

@kristophercrawford commented on GitHub (Nov 30, 2023):

Actually, disregard all of what I said. I was only selecting re-run all jobs after changing my ROOT_URL and observing no in output in the job2 data. I believe what I am observing now is a different bug (This one https://github.com/go-gitea/gitea/issues/25925).

If I switch the ROOT_URL to the external domain and make a new change and commit to the repo, I see output in job2 data as expected.

@kristophercrawford commented on GitHub (Nov 30, 2023): Actually, disregard all of what I said. I was only selecting re-run all jobs after changing my `ROOT_URL` and observing no in output in the job2 data. I believe what I am observing now is a different bug (This one https://github.com/go-gitea/gitea/issues/25925). If I switch the `ROOT_URL` to the external domain and make a new change and commit to the repo, I see output in job2 data as expected.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#12031
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?