[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-31972) Possibility to get branch name instead of commit id
Title: Message Title
Karl Fritsche created an issue
Jenkins / JENKINS-31972
Possibility to get branch name instead of commit id
Issue Type:
Improvement
Assignee:
Unassigned
Components:
bitbucket-pullrequest-builder-plugin
Created:
08/Dec/15 10:34 PM
Priority:
Minor
Reporter:
Karl Fritsche
Today I tried this plugin and I would love to see one addiiton. We have mutliple repositories to checkout in one job and therefor I can't use $ {sourceBranch}
as the commit id seems to be in there. Would it be possible to add $ {sourceBranchName}
/$ {targetBranchName}
where the name of the branch is used instead of the commit id?
Then I could use this for all repositories to checkout. We use alternative checkout method here. So if the branch X is not existing it falls back to master.
Add Comment
[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-31972) Possibility to get branch name instead of commit id
Title: Message Title
Karl Fritsche updated an issue
Jenkins / JENKINS-31972
Possibility to get branch name instead of commit id
Change By:
Karl Fritsche
Today I tried this plugin and I would love to see one addiiton.We have mutliple repositories to checkout in one job and therefor I can't use $ \ {sourceBranch} as the commit id seems to be in there.Would it be possible to add $ \ {sourceBranchName}/$ \ {targetBranchName} where the name of the branch is used instead of the commit id?Then I could use this for all repositories to checkout. We use alternative checkout method here. So if the branch X is not existing it falls back to master.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [copy-to-slave] (JENKINS-23043) Build hangs while copying artifacts to slave
Karl Fritsche commented on JENKINS-23043 Build hangs while copying artifacts to slave Did you tried with the newest version of jenkins (1.566)? >From the changelog it seems there were some problems with the remote client. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copy-to-slave] (JENKINS-23308) CopyToSlave: Variables doesn't work in custom workspaces
Karl Fritsche created JENKINS-23308 CopyToSlave: Variables doesnt work in custom workspaces Issue Type: Bug Affects Versions: current Assignee: Vivekanand SV Components: copy-to-slave Created: 04/Jun/14 9:48 AM Description: When using a variable in a custom workspace, it doesn't get replaced for copy-to-slave. I see correctly "Building remotely on Jenkins-Worker-01 (Remote-Worker) in workspace /var/lib/jenkins/jobs/a_name/workspace" in the log and "/var/lib/jenkins/jobs/a_name/workspace" is the $PARAMETER. But the copytoslave uses $PARAMETER as a string... Interesting point is, it gets resolved correctly for the slave, but not the master. How to reproduce: Creating a project with "Use custom workspace: $PARAMETER" Enable "Copy files into the job's workspace before building" with "This job's workspace on the master (not advised)" Start the build with $PARAMETER=/var/lib/jenkins/jobs/a_job/workspace/ Got: copy-to-slave Copying '.,*', excluding '/.git/,*/.gitignore', from 'file:/$%7BPARAMETER%7D' on the master to 'file:/var/lib/jenkins/jobs/a_job/workspace/' on 'slave'. Expected: copy-to-slave Copying '.,*', excluding '/.git/,*/.gitignore', from 'file:/var/lib/jenkins/jobs/a_job/workspace/' on the master to 'file:/var/lib/jenkins/jobs/a_job/workspace/' on 'slave'. Environment: Jenkins 1.566 CopyToSlave 1.4.3 Ubuntu 14.04. Project: Jenkins Priority: Major Reporter: Karl Fritsche This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copy-to-slave] (JENKINS-18360) Incorrect use of project.getWorkspace()
Karl Fritsche commented on JENKINS-18360 Incorrect use of project.getWorkspace() Could this also be a problem, when using variables in the custom workspace setting? See JENKINS-23308 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
