[JIRA] (JENKINS-57735) Cannot use groovy with() on "currentBuild"
Title: Message Title
Aaron Marasco updated an issue
Jenkins / JENKINS-57735
Cannot use groovy with() on "currentBuild"
Change By:
Aaron Marasco
Summary:
Cannot use groovy with() on {{ " currentBuild }} "
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199679.1559127861000.14927.1559127900494%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57735) Cannot use groovy with() on {{currentBuild}}
Title: Message Title
Aaron Marasco created an issue
Jenkins / JENKINS-57735
Cannot use groovy with() on {{currentBuild}}
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-05-29 11:04
Environment:
Jenkins 2.150.3 Pipeline 2.6
Priority:
Minor
Reporter:
Aaron Marasco
Trying to follow the Groovy Style Guide's item 9 "Using with() and tap() for repeated operations on the same bean:"
currentBuild.with {
result = 'FAILURE'
description += "\nFailed in ${stage_name} stage"
}
Resulted in:
groovy.lang.MissingPropertyException: No such property: description for class: groovy.lang.Binding
at groovy.lang.Binding.getVariable(Binding.java:63)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264)
at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:268)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:29)
...
The workaround is simply:
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Aaron Marasco commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Nils El-Himoud where are you going with that? We don't want to run every command twice. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183003.149756330.90.1557831182456%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41894) deleteDir() for cwd removes workspace when run in docker.image('builder').inside
Title: Message Title
Aaron Marasco commented on JENKINS-41894
Re: deleteDir() for cwd removes workspace when run in docker.image('builder').inside
Jesse Glick is it reasonable to throw some kind of exception or user-friendlier error when this is attempted, since it's a limitation of Docker and not going to be fixed? "You cannot use that command in this context" or similar?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title Aaron Marasco commented on JENKINS-43758 Re: Parameters disappear from pipeline job after running the job Just stumbled on this bug as well, wondering why I lose my JobDSL parameters after a run. Alexander Komarov has a great workaround above, but I really need what Michal Rysanek is asking for - a way to get the current properties so I can add to them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-51038) Re-defining existing job loses environment variables
Title: Message Title Aaron Marasco commented on JENKINS-51038 Re: Re-defining existing job loses environment variables I just stumbled on JENKINS-43758 and am 99% sure this is what was biting me in this bug report! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-23786) Permit "Execute shell" jobs to return 2 for "unstable"
Title: Message Title Aaron Marasco commented on JENKINS-23786 Re: Permit "Execute shell" jobs to return 2 for "unstable" Alexej Ismailov all of the above examples, being from 2016, were probably using the "classic" interface which has a field in the UI. In pipeline code, you want to use the "returnStatus" flag when calling sh - see https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#sh-shell-script - unfortunately you cannot use "returnStdout" at the same time; see JENKINS-44930. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-40167) readYaml and readJSON require a workspace even if the workspace is not needed
Title: Message Title Aaron Marasco commented on JENKINS-40167 Re: readYaml and readJSON require a workspace even if the workspace is not needed I was able to confirm readJSON worked outside of a node block using pipeline-utility-steps 2.2.0. Thanks for the heads-up Michael Letterle. One less Jenkins bug number in my groovy code. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-46569) Job execution time includes waiting time
Title: Message Title Aaron Marasco commented on JENKINS-46569 Re: Job execution time includes waiting time Josh Wand the problem with that workaround is that each stage/node needs its own timeout. :-/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-56289) All publisher results should be combined
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-56289 All publisher results should be combined Issue Type: Bug Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 2019-02-26 13:54 Priority: Major Reporter: Aaron Marasco I have the publishValgrind step defined in various locations within my pipeline. It currently (correctly) aggregates all the results into /valgrindResult, but incorrectly inserts N links on the left side of the job saying "Valgrind Results" with the link repeated. This wouldn't be a big deal, except it also inserts N copies of the trending graphs at the top of the job, pushing the pipeline details offscreen. Add Comment
[JIRA] (JENKINS-50914) Pipeline snippet generator doesn't work for the publishValgrind step
Title: Message Title Aaron Marasco commented on JENKINS-50914 Re: Pipeline snippet generator doesn't work for the publishValgrind step Same thing for the runValgrind step... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Aaron Marasco edited a comment on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 [~wfollonier] sorry I don't have much to contribute, as noted in the other ticket, I got it working and went on my merry way. As [~nneul] noted above - my setup was pretty much the same. The Jenkins _user_ on the Linux server had the ssh keys _outside of Jenkins itself_ (in a standard Unix manner) and I had to manually copy them into the GUI. Edit: For some reason it stripped the link from "other ticket" to https://issues.jenkins-ci.org/browse/JENKINS-54746?focusedCommentId=357252 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Aaron Marasco commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 Wadeck Follonier sorry I don't have much to contribute, as noted in the other ticket, I got it working and went on my merry way. As Nathan Neulinger noted above - my setup was pretty much the same. The Jenkins user on the Linux server had the ssh keys outside of Jenkins itself (in a standard Unix manner) and I had to manually copy them into the GUI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title
Aaron Marasco edited a comment on JENKINS-38906
Re: Remove lock resource name from global configuration when lock is released
Using code from comments above, I have a Jenkins job that runs weekly to remove the ones that start with certain phrases . *This may have race conditions* (see later comments) :{code:java}stage ("JENKINS-38906") { def manager = org.jenkins.plugins.lockableresources.LockableResourcesManager.get() def resources = manager.getResources().findAll { (!it.locked) && ( it.name.startsWith("docker_rpminstalled") || it.name.startsWith("docker-rpmbuild") || it.name.startsWith("rpm-deploy") ) } currentBuild.description = "${resources.size()} locks" resources.each { println "Removing ${it.name}" manager.getResources().remove(it) } manager.save()} // stage{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Aaron Marasco commented on JENKINS-38906 Re: Remove lock resource name from global configuration when lock is released Thanks Sami Korhonen for the heads-up. I don't need to worry about race conditions in my unique situation. However, I'll make a note in case others just see it and copypasta. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Aaron Marasco edited a comment on JENKINS-54884 Re: ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working Updated all plugins and now have 1.29.4; confirmed everything works now after some changes I needed for JENKINS-54746 - [comment| https://issues.jenkins-ci.org/browse/JENKINS-54746?focusedCommentId=357252=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-357252 ]. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Aaron Marasco commented on JENKINS-54884 Re: ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working Updated all plugins and now have 1.29.4; confirmed everything works now after some changes I needed for JENKINS-54746 - https://issues.jenkins-ci.org/browse/JENKINS-54746?focusedCommentId=357252=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-357252 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title
Aaron Marasco edited a comment on JENKINS-54746
Re: Can't connect via SSH on 1.29.1
I was able to workaround the problem by manually pasting the key from {{~jenkins/.ssh/id_rsa}} into the GUI under Credentials -> (Selected One) -> Update. It had the (only) radio button "Enter directly" already selected, but then it was blank. It was previously something like "from a file" I swear. Once I did that, all my remote nodes came back up; no need to change any configuration in them (to address fix from [~dpogue] above; they already had "Known Host"). https://jenkins/credentials/store/system/domain/_/credential//update
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Aaron Marasco commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 I was able to workaround the problem by manually pasting the key from ~jenkins/.ssh/id_rsa into the GUI under Credentials -> (Selected One) -> Update. It had the (only) radio button "Enter directly" already selected, but then it was blank. It was previously something like "from a file" I swear. Once I did that, all my remote nodes came back up; no need to change any configuration in them (to address fix from Darryl Pogue above; they already had "Known Host"). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Aaron Marasco commented on JENKINS-54884 Re: ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working CentOS 7 running the LTS version of Jenkins. All other plugins are up-to-date. The git server is BitBucket. Shouldn't matter, but it might. $ sudo -u jenkins openssl rsa -text -noout -in ~jenkins/.ssh/id_rsa | grep bit Private-Key: (2048 bit) No passphrase. $ sudo grep -v '^#' /etc/sysconfig/jenkins | grep -v '^$' JENKINS_HOME="/var/lib/jenkins" JENKINS_JAVA_CMD="" JENKINS_USER="jenkins" JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -Dorg.jenkinsci.plugins.docker.workflow.client.DockerClient.CLIENT_TIMEOUT=60 -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=400" JENKINS_PORT="-1" JENKINS_LISTEN_ADDRESS="" JENKINS_HTTPS_PORT="8080" JENKINS_HTTPS_KEYSTORE="" JENKINS_HTTPS_KEYSTORE_PASSWORD="" JENKINS_HTTPS_LISTEN_ADDRESS="" JENKINS_AJP_PORT="8009" JENKINS_AJP_LISTEN_ADDRESS="" JENKINS_DEBUG_LEVEL="5" JENKINS_ENABLE_ACCESS_LOG="no" JENKINS_HANDLER_MAX="100" JENKINS_HANDLER_IDLE="20" JENKINS_ARGS="" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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
[JIRA] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Aaron Marasco commented on JENKINS-54884 Re: ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working If it matters, all plugins: _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 All changes plugin (all-changes): 1.5 Static Analysis Utilities (analysis-core): 1.95 Ant Plugin (ant): 1.9 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.5-3.0 Authentication Tokens API Plugin (authentication-tokens): 1.3 Basic Branch Build Strategies Plugin (basic-branch-build-strategies): 1.1.1 Blue Ocean (blueocean): 1.9.0 Autofavorite for Blue Ocean (blueocean-autofavorite): 1.2.2 Bitbucket Pipeline for Blue Ocean (blueocean-bitbucket-pipeline): 1.9.0 Common API for Blue Ocean (blueocean-commons): 1.9.0 Config API for Blue Ocean (blueocean-config): 1.9.0 Blue Ocean Core JS (blueocean-core-js): 1.9.0 Dashboard for Blue Ocean (blueocean-dashboard): 1.9.0 Display URL for Blue Ocean (blueocean-display-url): 2.2.0 Events API for Blue Ocean (blueocean-events): 1.9.0 Git Pipeline for Blue Ocean (blueocean-git-pipeline): 1.9.0 GitHub Pipeline for Blue Ocean (blueocean-github-pipeline): 1.9.0 i18n for Blue Ocean (blueocean-i18n): 1.9.0 JIRA Integration for Blue Ocean (blueocean-jira): 1.9.0 JWT for Blue Ocean (blueocean-jwt): 1.9.0 Personalization for Blue Ocean (blueocean-personalization): 1.9.0 Pipeline implementation for Blue Ocean (blueocean-pipeline-api-impl): 1.9.0 Blue Ocean Pipeline Editor (blueocean-pipeline-editor): 1.9.0 Pipeline SCM API for Blue Ocean (blueocean-pipeline-scm-api): 1.9.0 REST API for Blue Ocean (blueocean-rest): 1.9.0 REST Implementation for Blue Ocean (blueocean-rest-impl): 1.9.0 Web for Blue Ocean (blueocean-web): 1.9.0 bouncycastle API Plugin (bouncycastle-api): 2.17 Branch API Plugin (branch-api): 2.1.1 Build Alias Setter Plugin (build-alias-setter): 0.4 Build Environment Plugin (build-environment): 1.6 Build Flow plugin (build-flow-plugin): 0.20 Build Timeout (build-timeout): 1.19 user build vars plugin (build-user-vars-plugin): 1.5 Build Trigger Badge Plugin (buildtriggerbadge): 2.9 built-on-column (built-on-column): 1.1 Clone Workspace SCM Plug-in (clone-workspace-scm): 0.6 Bitbucket Branch Source Plugin (cloudbees-bitbucket-branch-source): 2.2.15 Folders Plugin (cloudbees-folder): 6.7 Command Agent Launcher Plugin (command-launcher): 1.2 Conditional BuildStep (conditional-buildstep): 1.3.6 Config File Provider Plugin (config-file-provider): 3.4.1 Console Tail Plugin (console-tail): 1.1 Copy Artifact Plugin (copyartifact): 1.41 Credentials Plugin (credentials): 2.1.18 Credentials Binding Plugin (credentials-binding): 1.17 CVS Plug-in (cvs): 2.14 Dashboard View (dashboard-view): 2.10 Delivery Pipeline Plugin (delivery-pipeline-plugin): 1.3.1 description setter plugin (description-setter): 1.10 disk-usage plugin (disk-usage): 0.28 Display URL API (display-url-api): 2.3.0 Docker Commons Plugin (docker-commons): 1.13 Docker Pipeline (docker-workflow): 1.17 Durable Task Plugin (durable-task): 1.28 Email Extension Plugin (email-ext): 2.63 Environment Injector Plugin (envinject): 2.1.6 EnvInject API Plugin (envinject-api): 1.5 Environment Script Plugin (environment-script): 1.2.5 Extended Choice Parameter Plug-In (extended-choice-parameter): 0.76 External Monitor Job Type Plugin (external-monitor-job): 1.7 Extra Columns Plugin (extra-columns): 1.20 Fail The Build Plugin
[JIRA] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title
Aaron Marasco updated an issue
Jenkins / JENKINS-54884
ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Change By:
Aaron Marasco
With those two plugins installed, all git+ssh stopped working, even if it had nothing to do with slave nodes.{code:java} > git fetch --tags --progress ssh://git@git:7999/proj/jenkins-backups.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://git@git:7999/proj/jenkins-backups.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1819) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://git@git:7999/proj/jenkins-backups.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2016) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1735) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:420) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:886) ... 11 moreERROR: Error fetching remote repo 'origin' {code} This would happen when pipeline branches were checked as well . Reverting to ssh-slaves 1.28.1 (and uninstalling trilead-api) fixed it. : {code :java }Started by timer[Tue Nov 27 06:36:00 EST 2018] Starting branch indexing... > git --version # timeout=10using GIT_SSH to set credentials > git ls-remote ssh://git@git:7999/proj/opencpi.git # timeout=10ERROR: [Tue Nov 27 06:36:00 EST 2018] Could not update folder level actions from source e9d3dadd-64f7-458c-b3ba-98edd9652a8chudson.plugins.git.GitException: Command "git ls-remote ssh://git@git:7999/proj/opencpi.git" returned status code 128:stdout: stderr: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2016) at
[JIRA] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Aaron Marasco updated an issue Jenkins / JENKINS-54884 ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working Change By: Aaron Marasco Environment: Jenkins ver. 2.138.3 ssh-slaves 1.29.1trillead-api 1.01 (? dunno; erased) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54884) ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-54884 ssh-slaves or trilead-api stops all git over ssh (git+ssh) from working Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: ssh-plugin, trilead-api-plugin Created: 2018-11-27 13:05 Environment: ssh-slaves 1.29.1 trillead-api 1.01 (? dunno; erased) Priority: Major Reporter: Aaron Marasco With those two plugins installed, all git+ssh stopped working, even if it had nothing to do with slave nodes. > git fetch --tags --progress ssh://git@git:7999/proj/jenkins-backups.git +refs/heads/*:refs/remotes/origin/* ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from ssh://git@git:7999/proj/jenkins-backups.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1819) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress
[JIRA] (JENKINS-43754) Global pipeline library & simple 'checkout scm' rebuilds each polling cycle
Title: Message Title Aaron Marasco commented on JENKINS-43754 Re: Global pipeline library & simple 'checkout scm' rebuilds each polling cycle I guess I misunderstood the whole problem, sorry. That fixes half of my problems but I guess I haven't seen if it triggers false every hour on me. My other problem was that every insignificant branch was getting built when I only wanted specific ones. This might help you then; I've been using it for a while. Sucks that you still get "aborted" builds - https://gist.github.com/AaronDMarasco-VSI/a1f3829869cbf3256ca52919eba1cd16 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-43754) Global pipeline library & simple 'checkout scm' rebuilds each polling cycle
Title: Message Title Aaron Marasco commented on JENKINS-43754 Re: Global pipeline library & simple 'checkout scm' rebuilds each polling cycle I just stumbled upon basic-branch-build-strategies-plugin which should be able to fix your problems. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-47496) No automatic builds for tags
Title: Message Title Aaron Marasco commented on JENKINS-47496 Re: No automatic builds for tags Stephen Connolly thanks for that plug-in; it's exactly what I needed. No more needing checkboxes in my job asking "Do you really mean it?" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-43754) Global pipeline library & simple 'checkout scm' rebuilds each polling cycle
Title: Message Title Aaron Marasco commented on JENKINS-43754 Re: Global pipeline library & simple 'checkout scm' rebuilds each polling cycle Another workaround would involve checking the new currentBuild.getBuildCauses() provided by JENKINS-41272. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-43754) Global pipeline library & simple 'checkout scm' rebuilds each polling cycle
Title: Message Title Aaron Marasco commented on JENKINS-43754 Re: Global pipeline library & simple 'checkout scm' rebuilds each polling cycle My workaround is to add a checkbox that the user has to check to force the rebuild to actually happen. :-/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title
Aaron Marasco edited a comment on JENKINS-38906
Re: Remove lock resource name from global configuration when lock is released
Using code from comments above, I have a Jenkins job that runs weekly to remove the ones that start with certain phrases:{code:java} // AV-4738 and stage (" JENKINS-38906 ") { def manager = org.jenkins.plugins.lockableresources.LockableResourcesManager.get()def resources = manager.getResources().findAll {(!it.locked) && (it.name.startsWith("docker_rpminstalled") ||it.name.startsWith("docker-rpmbuild") ||it.name.startsWith("rpm-deploy"))} currentBuild.description = "${ resources. size()} locks" resources. each {println "Removing ${it.name}" manager.getResources().remove(it)}manager.save() } // stage {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title
Aaron Marasco commented on JENKINS-38906
Re: Remove lock resource name from global configuration when lock is released
Using code from comments above, I have a Jenkins job that runs weekly to remove the ones that start with certain phrases:
// AV-4738 and JENKINS-38906
def manager = org.jenkins.plugins.lockableresources.LockableResourcesManager.get()
def resources = manager.getResources().findAll {
(!it.locked) && (
it.name.startsWith("docker_rpminstalled") ||
it.name.startsWith("docker-rpmbuild") ||
it.name.startsWith("rpm-deploy")
)
}
resources.each {
println "Removing ${it.name}"
manager.getResources().remove(it)
}
manager.save()
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-47323) ClassCastException: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem
Title: Message Title Aaron Marasco commented on JENKINS-47323 Re: ClassCastException: hudson.matrix.MatrixConfiguration cannot be cast to hudson.model.TopLevelItem Sorry, but this was filed over a year ago so I've worked around it. Pretty sure we just dropped the delivery pipeline plugin altogether shortly after this was filed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53332) Allow picking a lockable resource from a node label
Title: Message Title Aaron Marasco commented on JENKINS-53332 Re: Allow picking a lockable resource from a node label I think this is a dupe/specialized case of JENKINS-44141. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53332) Allow picking a lockable resource from a node label
Title: Message Title Aaron Marasco assigned an issue to Aaron Marasco Jenkins / JENKINS-53332 Allow picking a lockable resource from a node label Change By: Aaron Marasco Assignee: Aaron Marasco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-53332) Allow picking a lockable resource from a node label
Title: Message Title Aaron Marasco assigned an issue to Unassigned Jenkins / JENKINS-53332 Allow picking a lockable resource from a node label Change By: Aaron Marasco Assignee: Aaron Marasco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-54107) raw HTML output when Stapler Security Hardening enabled
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-54107 raw HTML output when Stapler Security Hardening enabled Issue Type: Bug Assignee: Unassigned Components: lastfailureversioncolumn-plugin Created: 2018-10-16 16:34 Environment: Jenkins 2.138.2 Priority: Minor Reporter: Aaron Marasco As noted in the upgrade guide, resolved by adding -Dorg.kohsuke.stapler.jelly.CustomJellyContext.escapeByDefault=false to server configuration. Noted on wiki as well. Add Comment
[JIRA] (JENKINS-53438) archiveArtifacts should ignore @tmp directories
Title: Message Title
Aaron Marasco updated an issue
Jenkins / JENKINS-53438
archiveArtifacts should ignore @tmp directories
Change By:
Aaron Marasco
When using the command "{{archiveArtifacts}}", my job failed because it tried to grab an internally-used Jenkins durability directory: {code :java }archiveArtifacts allowEmptyArchive: false, artifacts: 'workspaces/**', defaultExcludes: false{code} Result:{code :java }java.nio.file.NoSuchFileException: ///workspaces/platforms@tmp/durable-3b0d9a40/jenkins-result.txt{code} I have not tried it yet, but I am hoping that "{{, excludes: ' \ * \ */ \ *@tmp/'}}" added to the end will solve the problem.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-53438) archiveArtifacts should ignore @tmp directories
Title: Message Title
Aaron Marasco updated an issue
Jenkins / JENKINS-53438
archiveArtifacts should ignore @tmp directories
Change By:
Aaron Marasco
When using the command "{{archiveArtifacts}}", my job failed because it tried to grab an internally-used Jenkins durability directory:{code}archiveArtifacts allowEmptyArchive: false, artifacts: 'workspaces/**', defaultExcludes: false{code}Result:{code}java.nio.file.NoSuchFileException: ///workspaces/platforms@tmp/durable-3b0d9a40/jenkins-result.txt{code}I have not tried it yet, but I am hoping that " {{, excludes: '**/*@tmp/'}} " added to the end will solve the problem.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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] (JENKINS-53438) archiveArtifacts should ignore @tmp directories
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-53438 archiveArtifacts should ignore @tmp directories Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-06 10:55 Environment: Jenkins 2.121.1 Labels: archiving artifact durability Priority: Minor Reporter: Aaron Marasco When using the command "archiveArtifacts", my job failed because it tried to grab an internally-used Jenkins durability directory: archiveArtifacts allowEmptyArchive: false, artifacts: 'workspaces/**', defaultExcludes: false Result: java.nio.file.NoSuchFileException: ///workspaces/platforms@tmp/durable-3b0d9a40/jenkins-result.txt I have not tried it yet, but I am hoping that , excludes: '*/@tmp/' added to the end will solve the problem.
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Aaron Marasco commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Stephen Connolly I didn't see anything in that PR addressing a possible leading "-" - are you assuming the path length should fix "most" cases? That's the problem I had as well as others previously (e.g. Alp Dener). Otherwise, kudos and thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Aaron Marasco edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
We just ran into a problem where the name of our git branch is "feature \ - \ -XXX" and Jenkins decided the name was too long, so stripped feature. Leaving a directory that starts with " \ - \ -". {code}13:22:18 [CentOS 6: Main RPM Build] Found files starting with hyphen13:22:18 [CentOS 6: Main RPM Build] error: Bad exit status from /var/tmp/rpm-tmp.mTAEkR (%install) {code}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Aaron Marasco commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline We just ran into a problem where the name of our git branch is "feature-XXX" and Jenkins decided the name was too long, so stripped feature. Leaving a directory that starts with "-". 13:22:18 [CentOS 6: Main RPM Build] Found files starting with hyphen 13:22:18 [CentOS 6: Main RPM Build] error: Bad exit status from /var/tmp/rpm-tmp.mTAEkR (%install) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] (JENKINS-4816) Allow for grepping console output
Title: Message Title
Aaron Marasco edited a comment on JENKINS-4816
Re: Allow for grepping console output
Yes, Ctrl-F would help. With parallel pipelines, it would be great if I could select the prefix in the log that Jenkins gives me:{code :java }[CentOS 6: Main RPM Build] > git rev-parse refs/remotes/origin/master^{commit} # timeout=10[CentOS 6: Main RPM Build] > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10[CentOS 6: Main RPM Build] Checking out Revision 066bdb39d4591827debcc8dcb388520174b5d748 (refs/remotes/origin/master)[CentOS 6: Main RPM Build] > git config core.sparsecheckout # timeout=10[CentOS 6: Main RPM Build] > git checkout -f 066bdb39d4591827debcc8dcb388520174b5d748[CentOS 7: Main RPM Build] > git rev-parse refs/remotes/origin/master^{commit} # timeout=10[CentOS 7: Main RPM Build] > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10[CentOS 7: Main RPM Build] Checking out Revision 066bdb39d4591827debcc8dcb388520174b5d748 (refs/remotes/origin/master)[CentOS 7: Main RPM Build] > git config core.sparsecheckout # timeout=10[CentOS 7: Main RPM Build] > git checkout -f 066bdb39d4591827debcc8dcb388520174b5d748[CentOS 7: Main RPM Build] > git branch -a -v --no-abbrev # timeout=10[CentOS 7: Main RPM Build] > git checkout -b master 066bdb39d4591827debcc8dcb388520174b5d748{code} So that it filters out and _only_ shows me one of them at a time. "Pipeline Steps" is broken down _too_ small, while the main interleaved console leaves some to be desired. _Note:_ as of Aug 2018, the plugins noted above are all 3+ years old, meaning they're unlikely to work with Workflow / Pipelines.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
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] (JENKINS-4816) Allow for grepping console output
Title: Message Title
Aaron Marasco commented on JENKINS-4816
Re: Allow for grepping console output
Yes, Ctrl-F would help. With parallel pipelines, it would be great if I could select the prefix in the log that Jenkins gives me:
[CentOS 6: Main RPM Build] > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
[CentOS 6: Main RPM Build] > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
[CentOS 6: Main RPM Build] Checking out Revision 066bdb39d4591827debcc8dcb388520174b5d748 (refs/remotes/origin/master)
[CentOS 6: Main RPM Build] > git config core.sparsecheckout # timeout=10
[CentOS 6: Main RPM Build] > git checkout -f 066bdb39d4591827debcc8dcb388520174b5d748
[CentOS 7: Main RPM Build] > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
[CentOS 7: Main RPM Build] > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
[CentOS 7: Main RPM Build] Checking out Revision 066bdb39d4591827debcc8dcb388520174b5d748 (refs/remotes/origin/master)
[CentOS 7: Main RPM Build] > git config core.sparsecheckout # timeout=10
[CentOS 7: Main RPM Build] > git checkout -f 066bdb39d4591827debcc8dcb388520174b5d748
[CentOS 7: Main RPM Build] > git branch -a -v --no-abbrev # timeout=10
[CentOS 7: Main RPM Build] > git checkout -b master 066bdb39d4591827debcc8dcb388520174b5d748
So that it filters out and only shows me one of them at a time. "Pipeline Steps" is broken down too small, while the main interleaved console leaves some to be desired.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-26802) Copying artifacts from many projects
Title: Message Title Aaron Marasco commented on JENKINS-26802 Re: Copying artifacts from many projects I'm assuming that with pipelines, this is pretty much OBE. You can manipulate/loop variables and call the plugin as many times as you want. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47927) Final text fields cannot use other fields to initialize
Title: Message Title Aaron Marasco closed an issue as Won't Fix As noted, this seems to be a "trying to use data too early" issue. Jenkins / JENKINS-47927 Final text fields cannot use other fields to initialize Change By: Aaron Marasco Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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,
[JIRA] (JENKINS-51144) Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds
Title: Message Title Aaron Marasco commented on JENKINS-51144 Re: Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds Linking to JENKINS-51038 because if that was fixed, I wouldn't have to be doing this history-wandering via currentBuild.upstreamBuilds... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-51144) Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-51144 Parameters given to seed job via pipeline jobDsl don't show up as "Build Variables" in downstream's currentBuild.upstreamBuilds Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-05-04 18:13 Environment: EnvInject 2.1.5 Job DSL 1.69 Jenkins 2.107.2 Priority: Major Reporter: Aaron Marasco I have a pipeline that calls a job dsl that calls a pipeline. We'll call them "job1", "launcher", and "job2." The idea is that I can manually run "launcher" from the Jenkins GUI, or if somebody checked a box on "job1" then it will call the launcher for you. In the job1, I use: jobDsl targets: "launcher_for_testing.groovy", lookupStrategy: 'JENKINS_ROOT', // Default I think additionalParameters: [ 'GIT_SELECTED_BRANCH': BRANCH_NAME, ], removedJobAction: 'DISABLE', sandbox: true In the launcher dsl script, I can access the "GIT_SELECTED_BRANCH" variable. If manually launched, it is a parameter of the job via the Jenkins GUI and everything is fine. If it is launched via job1, it works fine too, until... After it does a bunch of stuff to work around JENKINS-51038... def my_job =
[JIRA] (JENKINS-44128) Pass custom parameters to job-dsl via pipeline step jobDsl
Title: Message Title Aaron Marasco commented on JENKINS-44128 Re: Pass custom parameters to job-dsl via pipeline step jobDsl For folks wandering here by searches, the final implemented keyword in those diffs is "additionalParameters", not "params" as originally requested in the ticket description. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-51044) Using non-pipeline directives in pipeline job definitions should result in warning or error
Title: Message Title Aaron Marasco updated an issue Jenkins / JENKINS-51044 Using non-pipeline directives in pipeline job definitions should result in warning or error Change By: Aaron Marasco Summary: Using conflicting non- pipeline directives in pipeline job definitions should result in warning or error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-51044) Using conflicting pipeline directives should result in error
Title: Message Title Aaron Marasco commented on JENKINS-51044 Re: Using conflicting pipeline directives should result in error More experimentation seems to imply the directives are always ignored in any pipelineJob, even if I don't set the definition - which also makes sense. These things are supposed to be in the groovy script, so are ignored and the user should be notified. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-51044) Using conflicting pipeline directives should result in error
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-51044 Using conflicting pipeline directives should result in error Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-04-30 10:42 Environment: EnvInject 2.1.5 Job DSL 1.69 Jenkins 2.107.2 Priority: Minor Reporter: Aaron Marasco It seems that certain directives within a pipelineJob are totally ignored if using the definition directive to read in an external groovy script. At a minimum, it seems label and steps are, and possibly wrappers. For a new user (like me!) this can be frustrating. If a directive is invalid or ignored, there should be some message sent to the seed job's console (minimum) or the seed job should have result set to unstable/failed. Add Comment
[JIRA] (JENKINS-51038) Re-defining existing job loses environment variables
Title: Message Title Aaron Marasco commented on JENKINS-51038 Re: Re-defining existing job loses environment variables Since the queue command doesn't seem to be designed to pass parameters, with this not working, I'm running out of ideas on how to have a Job DSL launcher for a pipeline job work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Aaron Marasco edited a comment on JENKINS-51035
Re: Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
I think importing of previous jobs might be broken - I'm having major problems with environment variables JENKINS- 50138 51038
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Aaron Marasco edited a comment on JENKINS-51035
Re: Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
I think importing of previous jobs might be broken - I'm having major problems with environment variables and am about to file a bug for it. JENKINS-50138
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-51038) Re-defining existing job loses environment variables
Title: Message Title
Aaron Marasco created an issue
Jenkins / JENKINS-51038
Re-defining existing job loses environment variables
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-04-27 19:32
Environment:
EnvInject 2.1.5 Job DSL 1.69 Jenkins 2.107.2
Priority:
Major
Reporter:
Aaron Marasco
If I define a pipeline job with environment variables in it, on the second (and subsequent) runs, the environment disappears.
def my_job = pipelineJob("/${ROOT}/${BRANCH_FOLDER}/${pf}/${test}")
my_job.with {
description "${test} on ${pf} (${BRANCH_FOLDER})".replaceAll('_', ' ')
displayName test.replaceAll('_', ' ')
definition {
cps {
script(readFileFromWorkspace('jenkins/runtime/groovy/Jenkinsfile_example_job_to_run.groovy'))
sandbox()
}
}
environmentVariables {
envs(
Upstream_Job_Name: JOB_NAME,
Upstream_Job_Build: BUILD_NUMBER,
GIT_BRANCH: BRANCH_FOLDER,
PLATFORM: pf,
COMPONENT_TO_TEST: test,
)
keepBuildVariables(true)
}
quietPeriod 1 // 1 second
} // my_job
// Launch it!
queue(my_job) // should be able to be a string too
Delete the job
Run the job
Save off target job's config.xml on server
[JIRA] (JENKINS-51035) Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
Title: Message Title
Aaron Marasco commented on JENKINS-51035
Re: Regression: Job DSL `folder('existing-folder')` creation destroys any views in that folder
I think importing of previous jobs might be broken - I'm having major problems with environment variables and am about to file a bug for it.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-48070) Re-entrant calls in a load() groovy script jump to top of lock not top of function
Title: Message Title
Aaron Marasco updated an issue
Jenkins / JENKINS-48070
Re-entrant calls in a load() groovy script jump to top of lock not top of function
Change By:
Aaron Marasco
I've got a groovy script that I call using {{load()}} in my {{Jenkinsfile}}. I needed it to call itself with a different parameter when exception handling. However, it doesn't call itself in a way you would expect:{code:java}def call(in_path) {timeout(1) { def my_path = in_path print "Start of call(${my_path}) FINDMEAGAIN" lock ("mylock") {print "Start of call(${my_path}):lock block"try { print "Start of call(${my_path}):try block" error "Nope!"} catch (err) { print "In Exception - calling self" def my_pathp = my_path + "X" if (my_pathp.length() < 50) {print "Calling call(${my_pathp})"call(my_pathp) } print "Back to call(${my_path})"} } return null}}{code}You would expect to see the {{FINDMEAGAIN}} in the console multiple times. Or you would expect the {{lock}} to hang trying to re-lock. Instead, I get this:{noformat}Start of call(rpms/centos7) FINDMEAGAIN[Pipeline] lockTrying to acquire lock on [mylock]Lock acquired on [mylock][Pipeline] {[Pipeline] echoStart of call(rpms/centos7):lock block[Pipeline] echoStart of call(rpms/centos7):try block[Pipeline] error[Pipeline] echoIn Exception - calling self[Pipeline] echoCalling call(rpms/centos7X)[Pipeline] echoStart of call(rpms/centos7):lock block[Pipeline] echoStart of call(rpms/centos7):try block[Pipeline] error[Pipeline] echoIn Exception - calling self[Pipeline] echoCalling call(rpms/centos7X)[Pipeline] echoStart of call(rpms/centos7):lock block[Pipeline] echoStart of call(rpms/centos7):try block[Pipeline] error[Pipeline] echoIn Exception - calling self{noformat}This repeats until a stack overflow. I assume the variables not changing is a groovy thing concerning references vs copies or something, but that doesn't explain why the call is not going to the top.In experimenting, I found that if this snippet wasn't in {{call()}}, but something defined above it and called within, it worked as expected. j
Add Comment
[JIRA] (JENKINS-43077) withEnv does not set some environment variables
Title: Message Title Aaron Marasco commented on JENKINS-43077 Re: withEnv does not set some environment variables If it helps, I'm even hitting this now in a non-Docker environment. One call tree is: try => stage => parallel closure => node => timestamps => lock. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-42219) Invalid build aliases should be cleaned up
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-42219 Invalid build aliases should be cleaned up Issue Type: New Feature Assignee: Oliver Gondža Components: build-alias-setter-plugin Created: 2017/Feb/21 3:17 PM Environment: Plugin version 0.4 Labels: deletion Priority: Minor Reporter: Aaron Marasco My build alias list is now over three pages long, and some are over a year old. When the plugin adds an alias, it should scan the existing aliases and remove ones that point to builds that are no longer available. Another option is to hook into the project deletion somehow and remove the link(s) then. I don't know enough about the internals to tell if that is a valid event. Add Comment
[JIRA] (JENKINS-40615) Parameterised build passing to downstream build
Title: Message Title Aaron Marasco commented on JENKINS-40615 Re: Parameterised build passing to downstream build I have had this issue as well in the past. I just use the "Predefined Parameters" option and then hand-copy them: # Current build parameters didn't work... TARGET_OS=$TARGET_OS GIT_BRANCH_NAME=$GIT_BRANCH_NAME 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] (JENKINS-36114) Support Aggregate-only action
Title: Message Title Aaron Marasco commented on JENKINS-36114 Re: Support Aggregate-only action The publisher itself shouldn't matter. I want the publisher to only be invoked by the master/parent of the matrix run. 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] (JENKINS-36114) Support Aggregate-only action
Title: Message Title
Aaron Marasco created an issue
Jenkins / JENKINS-36114
Support Aggregate-only action
Issue Type:
New Feature
Assignee:
bap
Components:
flexible-publish-plugin
Created:
2016/Jun/21 12:43 PM
Labels:
aggregation
Priority:
Minor
Reporter:
Aaron Marasco
I cannot find an easy way to ONLY execute a step if it is the Matrix Aggregate. I was hoping "Never" on the section but then "Always" on the (checked) "Condition for Matrix Aggregation" would do it. I think "Condition for Matrix Aggregation" should have a new "Only" option that only runs at the end on the parent run. Currently, the workaround is "Execute Shell" and then:
if [ -z "${AXIS}" ]; then echo Master job, running next job; exit 0; fi
echo Not master job, aborting
exit 1
[JIRA] [multi-branch-project-plugin] (JENKINS-32244) Environment variable for current branch
Title: Message Title Aaron Marasco commented on JENKINS-32244 Re: Environment variable for current branch Thank you for the workaround snippet! The git plugin gives you $GIT_BRANCH but that has an extra "origin/" prefix that I couldn't figure out how to cleanly strip for a parameterized trigger of another job so came to file this bug. 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] [multi-branch-project-plugin] (JENKINS-32244) Environment variable for current branch
Title: Message Title
Aaron Marasco edited a comment on JENKINS-32244
Re: Environment variable for current branch
Thank you for the workaround snippet! The git plugin gives you {{$GIT_BRANCH}}, but that has an extra "origin/" prefix that I couldn't figure out how to cleanly strip for a parameterized trigger of another job , so came to file this bug.
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] [multi-branch-project-plugin] (JENKINS-32244) Environment variable for current branch
Title: Message Title
Aaron Marasco edited a comment on JENKINS-32244
Re: Environment variable for current branch
Thank you for the workaround snippet! The git plugin gives you {{$GIT_BRANCH}} , but that has an extra "origin/" prefix that I couldn't figure out how to cleanly strip for a parameterized trigger of another job so came to file this bug.
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] [prescmbuildstep-plugin] (JENKINS-34851) Strange quote rules for parameters
Title: Message Title Aaron Marasco closed an issue as Not A Defect Jenkins / JENKINS-34851 Strange quote rules for parameters Change By: Aaron Marasco Status: Open Closed Resolution: Not A Defect 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] [prescmbuildstep-plugin] (JENKINS-34851) Strange quote rules for parameters
Title: Message Title Aaron Marasco commented on JENKINS-34851 Re: Strange quote rules for parameters I thin this was a red herring and I have other problems. 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] [prescmbuildstep-plugin] (JENKINS-34851) Strange quote rules for parameters
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-34851 Strange quote rules for parameters Issue Type: Bug Assignee: Unassigned Components: prescmbuildstep-plugin Created: 2016/May/16 11:58 AM Environment: Jenkins 1.651.2 all-changes (All changes plugin): 1.3 analysis-core (Static Analysis Utilities): 1.76 ant (Ant Plugin): 1.3 antisamy-markup-formatter (OWASP Markup Formatter Plugin): 1.3 authentication-tokens (Authentication Tokens API Plugin): 1.2 build-alias-setter (Build Alias Setter Plugin): 0.4 build-environment (Build Environment Plugin): 1.6 build-flow-plugin (Build Flow plugin): 0.19 build-timeout (build timeout plugin): 1.16 build-user-vars-plugin (user build vars plugin): 1.5 buildtriggerbadge (Build Trigger Badge Plugin): 2.2 built-on-column (built-on-column): 1.1 clone-workspace-scm (Clone Workspace SCM Plug-in): 0.6 conditional-buildstep (conditional-buildstep): 1.3.3 console-column-plugin (Console Column Plugin): 1.5 console-tail (Console Tail Plugin): 1.1 copyartifact (Copy Artifact Plugin): 1.38 credentials (Credentials Plugin): 1.28 cvs (CVS Plug-in): 2.12 description-setter (description setter plugin): 1.10 disk-usage (disk-usage plugin): 0.28 diskcheck (diskcheck): 0.26 durable-task (Durable Task Plugin): 1.9 email-ext (Email Extension Plugin): 2.42 envinject (Environment Injector Plugin): 1.92.1 environment-script (Environment Script Plugin): 1.2.2 extended-choice-parameter (Extended Choice Parameter Plug-In): 0.72 external-monitor-job (External Monitor Job Type Plugin): 1.4 extra-columns (Extra Columns Plugin): 1.17 flexible-publish (Flexible Publish Plugin): 0.15.2 git (Git plugin): 2.4.4 git-client (Git client plugin): 1.19.6 git-notes (git-notes Plugin): 0.0.4 git-parameter (Git Parameter Plug-In): 0.5.1 git-tag-message (Git Tag Message Plugin): 1.5 greenballs (Green Balls): 1.15 groovy-label-assignment (Groovy Label Assignment plugin): 1.1.1 icon-shim (Icon Shim Plugin): 2.0.3 javadoc (Javadoc Plugin): 1.3 jobConfigHistory (Job Configuration History Plugin): 2.14 jquery (jQuery plugin): 1.11.2-0 junit (JUnit Plugin): 1.13 lastfailureversioncolumn (Last Failure Version Column): 1.1 ldap (LDAP Plugin): 1.12 linenumbers (Line Numbers plugin): 1.1 mailer (Mailer Plugin): 1.17 mapdb-api
[JIRA] [git-plugin] (JENKINS-23477) git-client-plugin sparse checkout path field does not expand variables
Title: Message Title
Aaron Marasco commented on JENKINS-23477
Re: git-client-plugin sparse checkout path field does not expand variables
On the remote Jenkins workspace:
$ cat .git/info/sparse-checkout
examples/
hdl/platforms/${HDL_PLATFORM}
Where HDL_PLATFORM is an axis in a matrix project.
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] [thinBackup] (JENKINS-32725) ThinBackup forces Quiet Mode even after reconfiguration
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-32725 ThinBackup forces Quiet Mode even after reconfiguration Issue Type: Bug Assignee: Thomas Fürer Components: thinBackup Created: 02/Feb/16 11:44 AM Environment: Jenkins 1.634 Priority: Minor Reporter: Aaron Marasco I kept wondering why Jenkins wanted to shut down when I got to work in the morning, and I finally spotted this in the logs: Feb 02, 2016 6:32:03 AM org.jvnet.hudson.plugins.thinbackup.utils.Utils waitUntilIdleAndSwitchToQuietMode INFO: Force quiet mode for jenkins now and wait unilt all executors are idle. So I changed the ThinBackup settings and removed the checkbox concerning waiting/forcing idle. It saved the settings, but didn't seem to tell the running process/thread, because after canceling the "shutdown" from the GUI, it immediately tried again with the same log message. Expected outcome: After telling it NOT to try to force an idle state, it should have stopped trying. (Also, there's a typo in that INFO message.)
