Enhancement for updating build custom fields values #23
Conversation
This file contains 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
mazimkhan
force-pushed
the
master
branch
2 times, most recently
from
98c3295
to
5e9c28a
Compare
|
@kinow Please merge as the related TestLink PR is merged TestLinkOpenSourceTRMS/testlink-code#47 (comment) |
|
Will have a look as soon as I have some time to work on it. Feel free to ping me again here if I take too long to review/merge it @mazimkhan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
testlink-plugin does not have option to update custom fields related to build. Like compiler, build config (release, debug etc.) etc.
This PR implements a new input field for jobs to input build custom fields and back end code to update #testlink.
It depends on TestLink Java API. That also needed enhancement. Corresponding Java API enhancement #kinow/testlink-java-api#71