kubesphere / kubesphere/ks-devops
Does kubesphere support the graphical display of parameters? Is there a better way to display it?
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
I want to use parameters in the pipeline to obtain the tag of gitlab, The script is as follows:
```groovy
pipeline {
agent {label 'jenkins-slave'}
environment {
//Sonarqube project name
sonar_project = "${project}:${app_name}:${git_branch}"
registry = "xxxxxxxxxx"
image_name = "${registry}/${project}/${app_name}:${git_branch}-${time}"
check_to_tag="${TAG}"
}
parameters {
gitParameter name: 'TAG',
type: 'PT_BRANCH_TAG',
branchFilter: 'origin/(.*)',
defaultValue: 'master',
selectedValue: 'DEFAULT',
sortMode: 'ASCENDING_SMART',
description: 'Select your branch or tag.',
useRepository:" http://10.133.82.120:8070/wangze/elecdetect -gateway.git"
}
stages {
Stage ('code pull '){
steps {
checkout([$class: 'GitSCM', branches: [[name: "${check_to_tag}"]], extensions: [], userRemoteConfigs: [[credentialsId: "${git_auth}", url: "${git_url}"]]])
}
}
}
}
```
However, the kubesphere page does not support this format (the pipeline cannot be displayed on the graphical interface). The kubesphere page is displayed as follows:
Contributor guide
Research direction
Start with the supplied Jenkins declarative pipeline, especially its parameters and environment sections, and compare it with the graphical pipeline page's supported format. Verify whether the Git parameter and tag-selection behavior can be represented graphically; done means the pipeline renders with the requested parameter and checkout behavior, or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, groovy, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100