Project

General

Profile

task #9513

Updated by Andreas Kohlbecker about 3 years ago

Due to the "table to div regression" the [Configure UI is completely broken after upgrade to 2.264](https://issues.jenkins.io/browse/JENKINS-64072) for jobs which are making use of the [scriptler plugin](https://plugins.jenkins.io/scriptler/). This incident has been reported as [JENKINS-65030](https://issues.jenkins.io/browse/JENKINS-65030). 

 Solution: 

 1. downgrade jenkins to version 2.263 - not easy, see #note-2 
 2. replace scripter +    dynamic parameter plugins by something else. The scripter plugin has security issues and the maintained is searching for someone to adopt the plugin. 
     * the *dynamic parameter* may be replaced by the [extended choice parameter](https://plugins.jenkins.io/extended-choice-parameter/) plugin which also can run groovy scripts to provide the parameter list: https://stackoverflow.com/questions/24730186/jenkins-extended-parameter-plugin-groovy-script  

 ## existing groovy stripts 

 edit-int: 

 * getXPathSingleValue 	
 * Git Refs Lookup: was only used in unused jobs `taxeditor-SNAPSHOT`, `taxeditor-JRE-SNAPSHOT` -> jobs deleted now! 
 * Git Tag Lookup --> can be 90% replaced by https://plugins.jenkins.io/git-parameter/. Limitation, the tags can only be filtered by [git-show-ref patterns](https://git-scm.com/docs/git-show-ref) so more tags will be shown. This can be improved by renaming existing tags. 

 ~~~xml 
 <net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition plugin="git-parameter@0.9.13"> 
           <name>RELEASE_TAG</name> <name>BRANCH</name> 
           <uuid>58781131-e61b-434d-9f52-42c3b89089a2</uuid> <uuid>ef8737cf-24cd-47f2-9388-17f7ae481dc4</uuid> 
           <type>PT_TAG</type> <type>PT_BRANCH</type> 
           <branch/> 
           <tagFilter>*</tagFilter> 
           <branchFilter>.*</branchFilter> <branchFilter>origin/hotfix/.*</branchFilter> 
           <sortMode>DESCENDING_SMART</sortMode> 
           <defaultValue>origin/master</defaultValue> 
           <selectedValue>TOP</selectedValue> 
           <quickFilterEnabled>true</quickFilterEnabled> 
           <listSize>5</listSize> 
         </net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition> 

 ~~~ 
 ~~~ 

 * GIT Branch Lookup --> can be 100% replaced by https://plugins.jenkins.io/git-parameter/  


  

 ~~~xml 
 <net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition plugin="git-parameter@0.9.13"> 
           <name>BRANCH</name> <name>RELEASE_TAG</name> 
           <uuid>ef8737cf-24cd-47f2-9388-17f7ae481dc4</uuid> <uuid>58781131-e61b-434d-9f52-42c3b89089a2</uuid> 
           <type>PT_BRANCH</type> <type>PT_TAG</type> 
           <branch/> 
           <tagFilter>*</tagFilter> 
           <branchFilter>origin/hotfix/.*</branchFilter> <branchFilter>.*</branchFilter> 
           <sortMode>DESCENDING_SMART</sortMode> 
           <defaultValue>origin/master</defaultValue> 
           <selectedValue>TOP</selectedValue> 
           <quickFilterEnabled>true</quickFilterEnabled> 
           <listSize>5</listSize> 
         </net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition> 

 
 ~~~ 
 edit-jobber: 

 * cdmserver-find-last-instance: Finds the last instance in a cdmserver 
 * cdmserver-index-job: Triggers and monitors an index or purge job on a cdmserver for a specific instance 
 * cdmserver-instance-action: Allows stopping and starting a cdmsever instance. 
 * cdmserver-monitor-instance-status: monitors the cdmsever until the specified instace shows as specific status or if the timeout is exceeded. Returns true (success) if no instances are configured. If no status is given the script will use 'started' as default. 
 * cdmserver-monitor-instance-up: monitors the cdmsever until the specified instace is started up or if the timeout is exceeded. Returns true (success) if no instances are configured. 
 * cdmserver-monitor-up: monitor cdmsever for all instaces started up. Returns true (success) if no instances are configured. 
 * filtered-cdmserver-instance-names:  
	 list datasource bean names in datasources.xml as whitespace separated text (suitable for dynamic axix), the instance names listed in the filter_str are either used as include ot exclude filter depending on the value of the filter_includes parameter. If the propertiesFile parameter is specified the final instance names will be written into the property key: 'INSTANCE_NAMES'. WRNING!!! You need to use the absolute path of the file!!!! 
 * list-maven-version: Returns a list of all available versions of an e-taxonomy.eu artifact in the wp5.e-taxonomy.eu maven repository 


 ## plugins and options to replace existing scriptler groovy scripts: 

 * https://stackoverflow.com/questions/9893503/getting-project-version-from-maven-pom-in-jenkins#22016841 
 * https://www.jenkins.io/doc/pipeline/steps/pipeline-utility-steps/#code-readmavenpom-code-read-a-maven-project-file

Back