[JIRA] (JENKINS-60322) updateGitlabCommitStatus doesn't work after cloning the second GitLab project

[gennady.krasni...@softjoys.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gennady Krasnikov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60322  
 
 
  updateGitlabCommitStatus doesn't work after cloning the second GitLab project   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Marky Jackson  
 
 
Components: 
 gitlab-plugin  
 
 
Created: 
 2019-11-28 18:06  
 
 
Environment: 
 Jenkins ver. 2.190.2  1.5.12 GitLab Plugin  GitLab Community Edition 11.6.5  Pipeline from SCM, groovy file  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Gennady Krasnikov  
 

  
 
 
 
 

 
 If there is only one GitLab project which is cloned in the pipeline, updateGitlabCommitStatus works fine. If two different projects were cloned before updateGitlabCommitStatus, it stops to work.  That is if you clone two projects at the very top of the pipeline, no one updateGitlabCommitStatus will work. If you clone the second project on some stage at the end of the pipeline, all updateGitlabCommitStatus above this will work fine, but all updateGitlabCommitStatus after cloning of the second project will fail. There is issue https://github.com/jenkinsci/gitlab-plugin/issues/522 for the plugin about gitlabCommitStatus and it was resolved with documentation changing that it should be close to the corresponding SCM definition: NOTE: If you use Pipeline global libraries, or if you clone your project's Jenkinsfile from a repo different from the one that contains the relevant source code, you need to be careful about when you send project status. In short, make sure you put your gitlabCommitStatus or other similar steps after the SCM step that clones your project's source. Otherwise, you may get HTTP 400 errors, or you may find build status being sent to the wrong repo https://github.com/jenkinsci/gitlab-plugin This doesn't work for updateGitlabCommitStatus. You can try to clone the first project just before updateGitlabCommitStatus, but this will not help. There

[JIRA] (JENKINS-54734) Blue Ocean view for pipeline doesn't show strings which contain any job parameter value

[gennady.krasni...@softjoys.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Gennady Krasnikov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54734  
 
 
  Blue Ocean view for pipeline doesn't show strings which contain any job parameter value   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2018-11-20-20-14-03-949.png  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2018-11-20 17:17  
 
 
Environment: 
 Jenkins ver. 2.138.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Gennady Krasnikov  
 

  
 
 
 
 

 
 For a Pipeline job 
 
mark This project is parameterized and add any string parameter with a given value, say secret1 

 
example_string=secret1
 

 
add pipeline description 

 
#!groovy
def specialPlatformTestDir

specialPlatformTestDir = 'secret2'
echo specialPlatformTestDir

specialPlatformTestDir = 'secret1'
echo specialPlatformTestDir