-
Notifications
You must be signed in to change notification settings - Fork 61
[263] Release Action can skip intermediate steps #306
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
[263] Release Action can skip intermediate steps #306
Conversation
@jiripetrlik What about using a different logic here - if component version is not defined then we can consider component build to be skipped? What do you think about it? |
0474a77
to
b804fd7
Compare
@sutaakar Test runs: |
b804fd7
to
e68134f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anishasthana The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Closes #263
It was necessary to use only one additional parameter for the list of released components because Github allows only 10 workflow parameters. I was also forced to use "if" for steps instead of jobs. It is because if I skip the job then all dependent jobs are also skipped which is not desirable.
Example runs (all bash code was commented out to not perform real release):