Fix get build number of AQL #749
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yahavi
added
bug
github-actions
bot
removed
the
safe to test
Or-Geva
suggested changes
Jul 19, 2023
...fo-extractor/src/main/java/org/jfrog/build/extractor/clientConfiguration/util/AqlHelper.java
Outdated
Show resolved
Hide resolved
yahavi
force-pushed
the
latest-build-number-fix
branch
from
e3c6d3d to
3ce3ef0
Compare
yahavi
force-pushed
the
latest-build-number-fix
branch
from
3ce3ef0 to
11cf5a8
Compare
yahavi
added
the
safe to test
github-actions
bot
removed
the
safe to test
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix an issue caused by #740.
In AQL queries for builds, we always try to get the latest build number, regardless of its value.
We should try to get the latest build number only in one of the following conditions: