release-next-version.yml should not fail when there is no release #11158
Comments
rwinch
added a commit
that referenced
this issue
Apr 21, 2022
This is necessary to support caching of tasks that use RepsitoryRef as inputs or outputs. Issue gh-11158
rwinch
added a commit
to rwinch/spring-security
that referenced
this issue
Apr 21, 2022
- Improve speed by using single job and multiple steps - Check output of tasks rather than rely on status codes to fail Issue spring-projectsgh-11158
rwinch
added a commit
to rwinch/spring-security
that referenced
this issue
Apr 21, 2022
Rather than having the task fail if the milestone is not due today, it now outputs to a file true or false. This allows the pipeline to determine if it should continue or not without causing a failure. Issue spring-projectsgh-11158
rwinch
added a commit
to rwinch/spring-security
that referenced
this issue
Apr 21, 2022
Rather than having the task fail if the milestone is not due today, it now outputs to a file true or false. This allows the pipeline to determine if it should continue or not without causing a failure. Closes spring-projectsgh-11158
eleftherias
pushed a commit
that referenced
this issue
Apr 27, 2022
Rather than having the task fail if the milestone is not due today, it now outputs to a file true or false. This allows the pipeline to determine if it should continue or not without causing a failure. Issue gh-11158
eleftherias
pushed a commit
that referenced
this issue
Apr 27, 2022
- Improve speed by using single job and multiple steps - Check output of tasks rather than rely on status codes to fail Issue gh-11158
eleftherias
pushed a commit
that referenced
this issue
Apr 27, 2022
This is necessary to support caching of tasks that use RepsitoryRef as inputs or outputs. Issue gh-11158
sjohnr
pushed a commit
that referenced
this issue
May 16, 2022
sjohnr
pushed a commit
that referenced
this issue
May 16, 2022
sjohnr
pushed a commit
that referenced
this issue
May 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently release-next-version.yml fails when there is not a scheduled release or when there are open issues and a release is scheduled. The release should not be initiated when the pre-conditions fail. However, it should also not fail.
The text was updated successfully, but these errors were encountered: