Draft
Conversation
maximenoel8
force-pushed
the
remove_extended_choice
branch
5 times, most recently
from
fed3341 to
fe3e98e
Compare
maximenoel8
force-pushed
the
remove_extended_choice
branch
from
7da3796 to
35f533b
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Improvement
extendedChoice plugin is obsolete.
Take the advantage of the new Jenkins to use more recent plugin.
After some research, the best solution to keep the checkbox is activeChoice. The simple solution will be string input. But I don't like it, it's error prone.
We also use Jenkins secret to manage secrets and don't have a file full of secrets on the Jenkins server.
Update sleMU and BV parameters and pipelines to impact the new changes.
Move old parameters to legaly folder so we can keep the compatibility to current ci server.