Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Duplicate
-
None
-
Jenkins ver. 2.63
GitLab plugin 1.4.5
Description
So, I've already had to abandon multibranch pipelines because they don't get the gitlab variables that I need for my build. Now, I'm working on a regular pipeline and it doesn't have access to the global BRANCH variable.
So, I can't do pleasant stage conditions like this
when {
branch 'master'
}
I have to write gnarlier conditions
when { environment name: 'gitlabBranch', value: 'master' }
Attachments
Issue Links
- duplicates
-
JENKINS-45198 Set Env Variables for SCM with Checkout SCM
-
- Closed
-
Code changed in jenkins
User: Oleg Nenashev
Path:
src/main/java/hudson/remoting/Channel.java
src/main/java/hudson/remoting/Request.java
http://jenkins-ci.org/commit/remoting/47b20daa35a2277ca67dc97c0e366cee88d13a9c
Log:
JENKINS-45233- Log errors when Response message cannot be delivered due to the closed channel (#177)JENKINS-45233- Address comments from @jglickJENKINS-45233- get rid of gratituos synchronization