[JIRA] (JENKINS-54110) Pipeline's dir() does not work with symlinks
Title: Message Title
Taylor Jones created an issue
Jenkins / JENKINS-54110
Pipeline's dir() does not work with symlinks
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-10-16 18:38
Priority:
Major
Reporter:
Taylor Jones
I'm currently trying to do this as a way of getting around bash's interpreter path length restrictions. Since Jenkins Pipeline generates an obscenely long workspace name, I figured the easiest solution would be to create a symlink in /tmp and just change directory into it. Unfortunately, this does not work. This is easy to reproduce, just run the following Pipeline job:
node {
def id = UUID.randomUUID().toString()
def symlink = "/tmp/${id}"
sh("ln -s ${pwd()} ${symlink}")
sh("ls -lah /tmp")
dir(symlink) {
println("Jenkins thinks we are in ${pwd()}")
sh('echo "But we are actually in `pwd`"')
sh("ls -lah /tmp")
}
sh("rm -fr /tmp/${id}")
}
If you run that, you'll also see that Jenkins generates this odd directory when you try to change into the symlink:
+ ls -lah /tmp
total 3.0M
drwxrwxrwt 43 root root 4.0K Oct 16 18:36 .
dr-xr-xr-x 27 root root 4.0K Oct 16 18:10 ..
lrwxrwxrwx 1 jenkins jenkins40 Oct 16 18:36 136ef826-e9a1-479e-9074-1de076349252 -> /var/build/workspace/jenkinsfile-sandbox
drwxr-xr-x 3 jenkins jenkins 4.0K Oct 16 18:36 136ef826-e9a1-479e-9074-1de076349252@tmp
[JIRA] (JENKINS-35687) Add explicit support for git lfs
Title: Message Title Taylor Jones commented on JENKINS-35687 Re: Add explicit support for git lfs Would it be possible to add support for remotes that are not the default LFS remote URL? It would make it a lot easier for teams that are using a separate LFS repo like Artifactory to create Jenkins jobs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [workflow-plugin] (JENKINS-32400) Import shared Groovy code
Title: Message Title Taylor Jones commented on JENKINS-32400 Re: Import shared Groovy code Any update on this? The current import method is still crzy annoying. 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] [workflow-plugin] (JENKINS-32400) Import shared Groovy code
Title: Message Title
Taylor Jones created an issue
Jenkins / JENKINS-32400
Import shared Groovy code
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
11/Jan/16 10:11 PM
Environment:
Jenkins: 1.625.3 Workflow plugin: 1.11
Priority:
Minor
Reporter:
Taylor Jones
It should be possible to import shared Groovy code from the SCM source in a Workflow job. For instance, if my workflow script (flow.groovy) needs to access variables from another script (constants.groovy) and they are both in the SCM repo that the Workflow job checked out, it should be simple to do. It's not and currently the unabashedly terrible workaround is to do this:
def constants
stage('Import dependencies')
node{
git(url: 'ssh://g...@mygitserver.com:7999/ex/workflow.git', credentialsId: '60cda0cc-f13d-448c-9947-28b926a20628')
constants = load('constants.groovy')
}
This works, but the fact that another node has to be spun up and another git checkout command is required is awful. It should be pretty straightfoward to have Jenkins simply load one of these files. Something like this:
[JIRA] [artifactory] (JENKINS-25028) Support for Jenkins Credentials
Taylor Jones created JENKINS-25028 Support for Jenkins Credentials Issue Type: Improvement Assignee: yossis Components: artifactory Created: 07/Oct/14 5:22 PM Description: The Artifactory plugin allows a user to override the deployer credentials with their own user/pass. However, this user/pass has to be specified for each job that does this. If a particular repo has several jobs, there's a lot of copy/paste going on to keep them all up to date. It would be better if the plugin allowed the use of Jenkins credentials for this. That way, users can keep their user/pass information consolidated in one place for updates to and creation of jobs. Project: Jenkins Priority: Major Reporter: Taylor Jones 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] [promoted-builds] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
Taylor Jones created JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin Issue Type: Bug Assignee: Unassigned Attachments: promotion-limited.png Components: promoted-builds Created: 06/Oct/14 10:45 PM Description: When using the CloudBees folder plugin, clicking on the Promotion Status link for a job will not show the "Build" icon unless you are logged in as an administrator. Similarly, if you attempt to run the Promotion on a slave that is restricted to a folder, the job will become permanently queued. Since the Jenkins team owns both of these plugins, they should work together. According CloudBee's own documentation, the Promoted Builds plugin needs to make use of a particular extension point to function with the Folders plugin: http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/foldersplus-sect-controlledslaves.html. Environment: Jenkins ver. 1.559 RedHat 6.4 Project: Jenkins Priority: Critical Reporter: Taylor Jones 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] [promoted-builds] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
Taylor Jones updated JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin Change By: Taylor Jones (06/Oct/14 10:46 PM) Attachment: promotion-limited.png 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] [promoted-builds] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
Taylor Jones commented on JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin Included screenshots of both views. 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] [promoted-builds] (JENKINS-25011) Promoted Builds does not work with CloudBees Folder plugin
Taylor Jones updated JENKINS-25011 Promoted Builds does not work with CloudBees Folder plugin Change By: Taylor Jones (06/Oct/14 10:48 PM) Attachment: promotion-admin.png 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.
