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

continuous-deploy-fingerprint outputs build ids even if no one was started #290

Closed
giorgiofellipe opened this issue Jun 27, 2024 · 2 comments · Fixed by #306
Closed

continuous-deploy-fingerprint outputs build ids even if no one was started #290

giorgiofellipe opened this issue Jun 27, 2024 · 2 comments · Fixed by #306
Assignees

Comments

@giorgiofellipe
Copy link

Description of the bug

After running continuous-deploy-fingerprint I have in the outputs the build ids for both platforms, even if they are old ones, no one was started

To Reproduce

Setup continuous-deploy-fingerprint on a project an run the workflow twice

Expected behavior

It is expected (as docs says) to only have the outputs android-build-id and ios-build-id when they have been started in this run

Actual behavior

Always have the outputs android-build-id and ios-build-id

Additional context

@kevinschaffter
Copy link

Can confirm the same issue

@wschurman
Copy link
Member

This is good feedback. I'll update it to also include boolean outputs indicating whether this run started each build. I think including the build ID that matches in the output is still useful regardless of whether this run started one though, since a subsequent step in the workflow could use that info somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants