[JIRA] (JENKINS-56810) Add current date in startDate when creating new version
Title: Message Title Olivier Lamy updated JENKINS-56810 Jenkins / JENKINS-56810 Add current date in startDate when creating new version Change By: Olivier Lamy Status: In Review Fixed but Unreleased Resolution: Fixed 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-56810) Add current date in startDate when creating new version
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-56810 Add current date in startDate when creating new version Change By: Olivier Lamy Labels: jira-plugin-3.0.6 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-35229) Plugin manager Updates never completes
Title: Message Title wgracelee commented on JENKINS-35229 Re: Plugin manager Updates never completes I recently had the same problem on one jenkins instance. It's running v 2.167. On other instance running on same version, it didn't happen. Could I get some help on how to fix it? The thread dump is attached as thread.txt (output of /threadDump) 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-35229) Plugin manager Updates never completes
Title: Message Title wgracelee updated an issue Jenkins / JENKINS-35229 Plugin manager Updates never completes Change By: wgracelee Attachment: thread.txt 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-48720) Warnings Plugin wants "Error" but JCReport apparently writes "error"
Title: Message Title Tobias Redl commented on JENKINS-48720 Re: Warnings Plugin wants "Error" but JCReport apparently writes "error" Ulli Hafner maybe a good way to go would be to use issueLevel.toLowerCase()... then, isn't it? Or is there a special reason to check just for the capitalized words? 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-52308) Update File Leak Detector and File Leak Detector Plugin to ASM 6.2
Title: Message Title Oleg Nenashev commented on JENKINS-52308 Re: Update File Leak Detector and File Leak Detector Plugin to ASM 6.2 Removed the Triaged label so that the Java 11 Support Team reviews feasibility of the ASM 7 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-52308) Update File Leak Detector and File Leak Detector Plugin to ASM 6.2
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52308 Update File Leak Detector and File Leak Detector Plugin to ASM 6.2 Change By: Oleg Nenashev Labels: java10 java11 newbie-friendly triaged 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-52308) Update File Leak Detector and File Leak Detector Plugin to ASM 6.2
Title: Message Title Oleg Nenashev commented on JENKINS-52308 Re: Update File Leak Detector and File Leak Detector Plugin to ASM 6.2 It would be better to keep the version aligned with Jenkins core. That version comes from https://github.com/kohsuke/package-renamed-asm/blob/asm6/pom.xml#L35 and now it is 6.2 Updating to a newer version may make sense, but we will need to update ASM in the Jenkins core as well, I believe CC Baptiste Mathus Ramon Leon Adrien Lecharpentier 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-56805) Compatibility with Configuration As Code Plugin
Title: Message Title Oleg Nenashev commented on JENKINS-56805 Re: Compatibility with Configuration As Code Plugin Maybe you want to install https://plugins.jenkins.io/configuration-as-code-support which adds support for Matrix Auth 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-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref commented on JENKINS-55787 Re: Switch labels from entry to checkbox Adrien Lecharpentier: once this change is mostly done, JENKINS-56109 / jenkinsci/jenkins#3895 will change the layout away from tables. Note: I'm currently taking a short hiatus from jenkins. 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-55787) Switch labels from entry to checkbox
Title: Message Title Adrien Lecharpentier commented on JENKINS-55787 Re: Switch labels from entry to checkbox Thank you Josh Soref! I'm speaking about mailer-plugin, as you filled a PR on this plugin. I've attached the screenshots in the PR you opened to see the diff. Even if I agree with you that we should have the checkbox before the label, the fact that all Jenkins configurations are structured like a table (with the left column the label and the right column for the field), I fear that changing this might cause some incomprehension. 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-54159) Support configuration as code plugin
Title: Message Title Tim Jacomb commented on JENKINS-54159 Re: Support configuration as code plugin Hi Jie Shen Any luck with this? 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-21475) Multiple LDAP OU support
Title: Message Title Asif Shaikh commented on JENKINS-21475 Re: Multiple LDAP OU support I see that you've added multiple server support, but would it be possible to add multiple OU support within the same server configuration? We have multiple root OUs that we need to query. However, when I don't provide a search DN, I get timeouts due to LDAP referrals. Our firewall rule allows access to only a single LDAPS vip. We can't use referrals. 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-49774) NPE in Autofavorite plugin
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-49774 NPE in Autofavorite plugin Change By: Nick Jones Priority: Major Blocker 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-55956) Remove JAXB dependency from timestamper plugin
Title: Message Title Jesse Glick updated JENKINS-55956 Jenkins / JENKINS-55956 Remove JAXB dependency from timestamper plugin Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed 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-56684) Config as Code Nullpointer when instanceCapStr is not initialized
Title: Message Title Jake Remitz updated an issue Jenkins / JENKINS-56684 Config as Code Nullpointer when instanceCapStr is not initialized Change By: Jake Remitz Labels: configuration-as-code ec2-plugin 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-52308) Update File Leak Detector and File Leak Detector Plugin to ASM 6.2
Title: Message Title
Duane Francis edited a comment on JENKINS-52308
Re: Update File Leak Detector and File Leak Detector Plugin to ASM 6.2
Which file-leak-detector do we want to update to? Current version is 7.1 for ASM{color:#009eff}3 March 2019: ASM 7.1 (tag ASM_7_1){color} {color:#009eff}Do we still want to check for 6.2 for ASM?{color}{color:#009eff}Thanks{color}
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-49774) NPE in Autofavorite plugin
Title: Message Title Nick Jones reopened an issue Jenkins / JENKINS-49774 NPE in Autofavorite plugin Change By: Nick Jones Resolution: Cannot Reproduce Status: Closed Reopened 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-49774) NPE in Autofavorite plugin
Title: Message Title Nick Jones commented on JENKINS-49774 Re: NPE in Autofavorite plugin As I just noted on https://issues.jenkins-ci.org/browse/JENKINS-50715, we just added Blue Ocean for the first time to our production Jenkins system today, and immediately started seeing this very problem on the first build (#1) of any new branch or PR for every multibranch pipeline job. We're running Jenkins 2.164.1 LTS and the latest versions of all plugins, including Autofavorite 1.2.3. Blue Ocean was installed without a restart (as it was new) but I'm awaiting system availability to restart to remove it; having every build #1 fail is untenable. 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-52308) Update File Leak Detector and File Leak Detector Plugin to ASM 6.2
Title: Message Title Duane Francis commented on JENKINS-52308 Re: Update File Leak Detector and File Leak Detector Plugin to ASM 6.2 Which file-leak-detector do we want to update to? Current version is 7.1 for ASM 3 March 2019: ASM 7.1 (tag ASM_7_1) 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-56813) Job filter: exclude disabled jobs does not work
Title: Message Title Christoph Vogtländer created an issue Jenkins / JENKINS-56813 Job filter: exclude disabled jobs does not work Issue Type: Bug Assignee: Sven Schoenung Components: view-job-filters-plugin Created: 2019-03-29 18:00 Environment: Windows 2012 Server Jenkins ver. 2.150.3 Priority: Minor Reporter: Christoph Vogtländer When defining a job filter on a view, using the "Job-Status" filter with "Disabled" and type set to "Exclude matching", will still show disabled jobs. E.g. define two filters: All jobs (or regular _expression_ where the _expression_ includes some disabled jobs) Job-Status: Disabled, Filter-type: Exclude matching Including disabled jobs seems to work fine. Strangely, when using two "Job-status" filters, the exclude filter works as expected: E.g.: Job-status: disabled, Filter-type: include matching Job-status: disabled, Filter-type: exclude matching will result in an empty list which is correct.
[JIRA] (JENKINS-56770) Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes
Title: Message Title Yixiao Lin commented on JENKINS-56770 Re: Parameterized Remote Trigger is not compatible with Jenkins 2.102+ due to JEP-200 changes We experience the same issue. Would be great if this is fixed. 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Maxfield Stewart commented on JENKINS-51057 Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM Álvaro Iradier Confirmed by the way that your script needs a newer/newest version of plugins, not entirely sure which ones. Of 3 4 deployments I managed, 1 the script was not working for ( couldn't get the parent dispatcher via this$0 ) until I moved to the latest versions. Tested on Blue ocean 1.13 and 1.14, Jenkins v2.168. Doesn't seem to work on versions of Blue Ocean older than 1.10/Jenkins 2.147. 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-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Nick Jones edited a comment on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites We installed Blue Ocean this morning (latest released versions of all plugins) and immediately started having the first build of every new branch/PR fail due to this bug. I'm going to uninstall. In our case, it was Blue Ocean 1.14.0, Autofavorite 1.2.3, and Jenkins 2.164.1 LTS. 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-56812) java.lang.AssertionError: class hudson.security.csrf.DefaultCrumbIssuer is missing its descriptor
Title: Message Title Arnaud Héritier moved an issue Jenkins / JENKINS-56812 java.lang.AssertionError: class hudson.security.csrf.DefaultCrumbIssuer is missing its descriptor Change By: Arnaud Héritier Project: Infrastructure Jenkins Key: INFRA JENKINS - 2064 56812 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: plugins.jenkins.io 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-51913) Post-build action "Archive the artifacts" prints exception to console when no artifacts found
Title: Message Title Vincent Massol commented on JENKINS-51913 Re: Post-build action "Archive the artifacts" prints exception to console when no artifacts found Jesse Glick Thanks for the idea, I've implemented it. Let's see if it works better. Will report back here. 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-52397) Org Scan blows up when repository has no tags
Title: Message Title Andrew Bayer resolved as Fixed Apparently resolved in GitHub branch source 2.4.2. Jenkins / JENKINS-52397 Org Scan blows up when repository has no tags Change By: Andrew Bayer Status: Open Resolved Resolution: Fixed Released As: 2.4.2 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-46503) Pipeline hanging after updating Jenkinsfile but before starting to build
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-46503 Pipeline hanging after updating Jenkinsfile but before starting to build Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate 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-56535) Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents
Title: Message Title Muhammad Faizan ul haq commented on JENKINS-56535 Re: Caused: java.io.IOException: Unexpected termination of the channel for Azure Agents We fought a little and found the issue. We spun up a test-jenkins from a backup of our production jenkins server. Both server had same ID and somehow after aprox two hours of an agent creation, the agents created by one server were being removed by other server. Jie Shen can probably explain this. 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-56463) API token matched for user foo but the impersonation failed
Title: Message Title Jimmy Atcuit commented on JENKINS-56463 Re: API token matched for user foo but the impersonation failed I have the same issue with this plugins. The api keys don't work anymore with ldap logins. 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-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Nick Jones commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites We installed Blue Ocean this morning (latest released versions of all plugins) and immediately started having the first build of every new branch/PR fail due to this bug. I'm going to uninstall. 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-56779) yamllint never finds issues
Title: Message Title g hs1 commented on JENKINS-56779 Re: yamllint never finds issues 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-56779) yamllint never finds issues
Title: Message Title g hs1 updated JENKINS-56779 Jenkins / JENKINS-56779 yamllint never finds issues Change By: g hs1 Status: Open Fixed but Unreleased Resolution: Fixed 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-45489) checkout(scm) step can return wrong variables when used following another Git checkout
Title: Message Title Mark Waite commented on JENKINS-45489 Re: checkout(scm) step can return wrong variables when used following another Git checkout Richard Bowater the most direct work around is to compute the SHA1 of the working directory with a call to a shell script, batch script, or powershell script. Refer to the[ example in a stackoverflow article|https://stackoverflow.com/questions/45236824/get-git-commit-sha-in-jenkins-pipeline]. The technique is also in the pipeline script utilities that I use. 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-45489) checkout(scm) step can return wrong variables when used following another Git checkout
Title: Message Title Mark Waite edited a comment on JENKINS-45489 Re: checkout(scm) step can return wrong variables when used following another Git checkout [~rjbwtr] the most direct work around is to compute the SHA1 of the working directory with a call to a shell script, batch script, or powershell script. Refer to the[ example in a stackoverflow article|https://stackoverflow.com/questions/45236824/get-git-commit-sha-in-jenkins-pipeline].The technique is also in the [pipeline script utilities|https://github.com/MarkEWaite/jenkins-pipeline-utils/blob/ff4ba450a69ff158274b72b600bf5e1364bcc57c/src/com/markwaite/Build.groovy#L39] that I use. 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-45489) checkout(scm) step can return wrong variables when used following another Git checkout
Title: Message Title
Richard Bowater edited a comment on JENKINS-45489
Re: checkout(scm) step can return wrong variables when used following another Git checkout
I've just run up against this too.{code}Fetching changes from the remote Git repositoryFetching without tagsChecking out Revision 5cc3005a298d50fa0c2bc919293fcf3b3ed936de (print-env)Commit message: "Print more env"GIT_COMMIT=eb65cd4f46c828362429cbbd2d904f114bb4b801GIT_BRANCH=master{code}Doesn't seem to be an obvious way to work around it? My particular use case is:* a global shared library configured to checkout from git* a multibranch pipeline configured to load Jenkinsfiles from the shared libraries aboveWe're using pipelines to build and test shared libraries before deployment, but branch builds are being unpredictable due to the environment variables being incorrect.
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-45489) checkout(scm) step can return wrong variables when used following another Git checkout
Title: Message Title
Richard Bowater edited a comment on JENKINS-45489
Re: checkout(scm) step can return wrong variables when used following another Git checkout
I've just run up against this too.{code}Fetching changes from the remote Git repositoryFetching without tagsChecking out Revision 5cc3005a298d50fa0c2bc919293fcf3b3ed936de (print-env)Commit message: "Print more env"GIT_COMMIT=eb65cd4f46c828362429cbbd2d904f114bb4b801GIT_BRANCH=master{code} Doesn't seem to be an obvious way to work around 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-45489) checkout(scm) step can return wrong variables when used following another Git checkout
Title: Message Title
Richard Bowater edited a comment on JENKINS-45489
Re: checkout(scm) step can return wrong variables when used following another Git checkout
I've just run up against this too. ``` {code} Fetching changes from the remote Git repositoryFetching without tagsChecking out Revision 5cc3005a298d50fa0c2bc919293fcf3b3ed936de (print-env)Commit message: "Print more env"GIT_COMMIT=eb65cd4f46c828362429cbbd2d904f114bb4b801GIT_BRANCH=master ``` {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-45489) checkout(scm) step can return wrong variables when used following another Git checkout
Title: Message Title Richard Bowater commented on JENKINS-45489 Re: checkout(scm) step can return wrong variables when used following another Git checkout I've just run up against this too. ``` Fetching changes from the remote Git repository Fetching without tags Checking out Revision 5cc3005a298d50fa0c2bc919293fcf3b3ed936de (print-env) Commit message: "Print more env" GIT_COMMIT=eb65cd4f46c828362429cbbd2d904f114bb4b801 GIT_BRANCH=master ``` 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-51913) Post-build action "Archive the artifacts" prints exception to console when no artifacts found
Title: Message Title
Jesse Glick commented on JENKINS-51913
Re: Post-build action "Archive the artifacts" prints exception to console when no artifacts found
Without having dug into the details of whether validateAntFileMask preserves Ant’s own optimizations that allow fileset scans to be more efficient when the pattern is “rooted” in a literal directory prefix, I would suggest checking whether this helps:
dir('tmp-jenkins-png') {
archiveArtifacts artifacts: "**/*.png", allowEmptyArchive: true
}
which would guarantee that the validator is not peeking outside this directory. Of course if your copy command has selected only PNG files to begin with, you could just use artifacts: '**' as the pattern.
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-38973) Multibranch-Pipeline Not Honoring Git Timeout
Title: Message Title Sebastien Hoareau commented on JENKINS-38973 Re: Multibranch-Pipeline Not Honoring Git Timeout Not exactly the same, but we have a similar problem with the shallow clone option: the plugin doesn't seem to take into account either (no --depth=xx on the git fetch command line) 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-56811) vSphere plugin instant clone support
Title: Message Title Gianluca Massera created an issue Jenkins / JENKINS-56811 vSphere plugin instant clone support Issue Type: Improvement Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2019-03-29 14:05 Environment: Jenkins version 2.146.1 vSphere Cloud plugin version 2.19 Labels: plugin Priority: Minor Reporter: Gianluca Massera I'm starting using vSphere cloud plugin to generate nodes and VMs on demand and on per-job in the pipeline. Looking at the documentation, there is no mention of the "instant clone" feature of vSphere but only "linked clone". https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-853B1E2B-76CE-4240-A654-3806912820EB.html I'm wondering if vSphere Cloud plugin can be improved to support "instant clone". Add Comment
[JIRA] (JENKINS-56810) Add current date in startDate when creating new version
Title: Message Title Mathieu Paré updated an issue Jenkins / JENKINS-56810 Add current date in startDate when creating new version Change By: Mathieu Paré Labels: jira-plugin-3.0.6 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-56810) Add current date in startDate when creating new version
Title: Message Title Mathieu Paré updated an issue Jenkins / JENKINS-56810 Add current date in startDate when creating new version Change By: Mathieu Paré Labels: jira-plugin-3.0.6 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-56810) Add current date in startDate when creating new version
Title: Message Title
Mathieu Paré created an issue
Jenkins / JENKINS-56810
Add current date in startDate when creating new version
Issue Type:
New Feature
Assignee:
Mathieu Paré
Components:
jira-plugin
Created:
2019-03-29 13:49
Priority:
Minor
Reporter:
Mathieu Paré
When creating a new version in Jira through Jenkins we want to set the current date in "Start Date" for Version Reports. Currently we have to manually edit them in Jira after each build in Jenkins. This field was never added to the Jira Rest Java Client Library even though it is available on the Jira Rest API (undocumented). If I query a particular version with a "Start Date" already filled in Jira, I can see the field "startDate".
{ "self": "https://.../rest/api/latest/version/21755", "id": "21755", "name": "CLAP-3.0.2", "archived": false, "released": false, "startDate": "2019-03-14", "userStartDate": "March 14, 2019", "projectId": 12400 }
Add Comment
[JIRA] (JENKINS-56810) Add current date in startDate when creating new version
Title: Message Title Mathieu Paré started work on JENKINS-56810 Change By: Mathieu Paré Status: Open In Progress 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-56810) Add current date in startDate when creating new version
Title: Message Title Mathieu Paré updated JENKINS-56810 Jenkins / JENKINS-56810 Add current date in startDate when creating new version Change By: Mathieu Paré Status: In Progress Review 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-56807) Jenkins can not call batch file
Title: Message Title Baptiste Mathus resolved as Not A Defect Hello! Please rather use the users Mailing list to get some help. This does not look like you're hitting a bug, but need help setting up your Jenkins environment. Please use the Users ML described on https://jenkins.io/mailing-lists/, we'll be happy to see how we can help you ther Thank you! Jenkins / JENKINS-56807 Jenkins can not call batch file Change By: Baptiste Mathus Status: Open Resolved Resolution: Not A Defect 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-54767) Global variables are overriding local variables
Title: Message Title Jan Bottek commented on JENKINS-54767 Re: Global variables are overriding local variables fisnik hajredini thx for the fast replay. sorry for my question, but how can i see now in which version of the plugin this issue is solved? because issue is still open and on your mentioned CI i didn't see the code for the plugin itself, or what i overlook? 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-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url {{ JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }} But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:{{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
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-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url {{ JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }} But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:{{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
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-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url {{ JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }} But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:{{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}} but On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. It To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
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-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.extBut I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path: {{ /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext }} but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All short url shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
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-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach updated an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Daniel Jeznach I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.extBut I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.extbut lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild.All short url from job page have their respective symlinks except lastCompletedBuild.Is it intentional? 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-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach updated an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Daniel Jeznach Labels: symlink 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-56347) Kubernetes plugin provisioning pods twice in 1.14.6
Title: Message Title Raúl Cruz commented on JENKINS-56347 Re: Kubernetes plugin provisioning pods twice in 1.14.6 We have the same problem here, it started to happend once we added this: https://github.com/jenkinsci/kubernetes-plugin/#over-provisioning-flags Then we removed the flags but it was still happening, so we downgraded to 1.14.5 and now is not happening. 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-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach created an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-29 11:29 Environment: Jenkins 2.46.2 openjdk 1.8.0 ubnutu 16.04 lts Priority: Minor Reporter: Daniel Jeznach I maintain few jenkinses, various versions (2.x). Some of them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path: /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All short url from job page have their respective symlinks except lastCompletedBuild. Is it intentional?
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-27413
Re: Handle file parameters
my 5 cents, this code shows how to load a properties file into the environment, in the example the properties come from a String but also you can load a file from disk with the readProperties pipeline utility step ``` {code} node { def configPrperties = """ VAR01 = value1 VAR02 = value2 """ def config = readProperties(text: configPrperties) config.each { k, v -> env."${k}" = v } sh 'export'} ``` {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-27413) Handle file parameters
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-27413
Re: Handle file parameters
my 5 cents, this code shows how to load a properties file into the environment, in the example the properties come from a String but also you can load a file from disk with the readProperties pipeline utility step ``` node { def configPrperties = """ VAR01 = value1 VAR02 = value2 """ def config = readProperties(text: configPrperties) config.each { k, v -> env."${k}" = v } sh 'export' } ```
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-56228) Job triggered multiple times by maven dependencies
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Solved in 3.6.8 Jenkins / JENKINS-56228 Job triggered multiple times by maven dependencies Change By: Cyrille Le Clerc Status: Open Closed Resolution: Fixed 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-56808) Tech support analyst jobs
Title: Message Title Nathan Will assigned an issue to Nathan Will Jenkins / JENKINS-56808 Tech support analyst jobs Change By: Nathan Will Assignee: Joseph Petersen Nathan Will 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-56808) Tech support analyst jobs
Title: Message Title Nathan Will created an issue Jenkins / JENKINS-56808 Tech support analyst jobs Issue Type: Story Assignee: Joseph Petersen Components: accurev-plugin Created: 2019-03-29 10:19 Environment: Tech support analyst jobs Priority: Minor Reporter: Nathan Will Technical Support Analysts are trained IT support professionals, who resolve a variety of technical issues relating to their organization's computer systems, telecommunication network, LANs, WANs and desktop computers, whether these components are located onsite or in the field. Organizations are dependent on support analysts to actualize their organization's potential. Technical Support Analysts are experts who provide the foundation of an organization's digital infrastructure. Specifically, Technical Support Analysts are specialists who provide technical support, advice, and assistance to an organization and its customers. They help resolve hardware, software and other technical problems. They often provide front-line support for system issues, whether these issues be in the organization or at a customer's premise. Now the concept of freelancing has come into the picture. As a freelance technical support analyst, you can enjoy the benefits of flexibility. If you are looking for freelance opportunities in this field, register on FieldEngineer.com. Here you can find terrific job opportunities tailored to your needs. Currently, the site provides a one-stop solution, with more than 40,000+ freelancers from over 180 countries. Read More: [Tech support analyst jobs|https://www.fieldengineer.com/skills/technical-support-analyst]
[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.
Title: Message Title jlpinardon edited a comment on JENKINS-52750 Re: dir step creates a @tmp directory at level. So, if I correctly understand the answer above, the point is that Jenkins needs some space to record its own stuff when a job is running. IMHA (but perhaps there are some cases I don't imagine where it is not possible ?) the better place to do that is the _build workspace_, whatever the current working directory is. At least, jenkins is sure to be able (i.e. have rwx rights) to create its temp directory.I guess that it should not be too difficult for a jenkins code to retrieve the aboslute path of the build workspace.Besides, _as a jenkins admin_, I wouldn't still see this temporary directory once the build is achieved. _Please, let this place as clean as you found it and sweep your own dust_ ! ;). Especially given that this temp dir looks to be empty in most cases when the build is over.Best Reards Regards 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-52750) dir step creates a @tmp directory at level.
Title: Message Title jlpinardon commented on JENKINS-52750 Re: dir step creates a @tmp directory at level. So, if I correctly understand the answer above, the point is that Jenkins needs some space to record its own stuff when a job is running. IMHA (but perhaps there are some cases I don't imagine where it is not possible ?) the better place to do that is the build workspace, whatever the current working directory is. At least, jenkins is sure to be able (i.e. have rwx rights) to create its temp directory. I guess that it should not be too difficult for a jenkins code to retrieve the aboslute path of the build workspace. Besides, as a jenkins admin, I wouldn't still see this temporary directory once the build is achieved. Please, let this place as clean as you found it and sweep your own dust ! . Especially given that this temp dir looks to be empty in most cases when the build is over. Best Reards 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-56526) excludeMessage does not match description text
Title: Message Title Ulli Hafner updated JENKINS-56526 Jenkins / JENKINS-56526 excludeMessage does not match description text Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed 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-56797) Implement quality checks for the project
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-56797 Implement quality checks for the project Change By: David Olorundare As the audit-logging project grows, there is need to ensure consistency of submissions made by both old and new contributors to the project, in order to maintain a certain quality standard. The following are to be implemented; * default pull request(PR) template(s) to enforce consistent format for contributors submitting new PRs. * default clientside and serverside commit-templates to enforce specific git commit-policies. * contribution-guide document that outlines useful information for new contributors to the project and best practices that should be adhere to when contributing. * other relevant code and/or project-level QA checks to maintain the quality of submissions made to the project. 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-43540) builds/lastSuccessfulBuild symlink is not created
Title: Message Title Daniel Jeznach commented on JENKINS-43540 Re: builds/lastSuccessfulBuild symlink is not created I have similiar issue with no lastCompletedBuild, looks related. 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-53931) Role Strategy: Configuration-as-Code compatibility
Title: Message Title Jon Brohauge commented on JENKINS-53931 Re: Role Strategy: Configuration-as-Code compatibility An Nguyen You could fork the project and introduce the fix in a PR. Afterwards ask the maintainer to review the PR. 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title vaishal shah commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Hi Team, Did anyone found any solution for Declarative Pipeline? Please share details if any solution will be there. Thanks, Vaishal 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-12258) Plugin is missing descriptor, which throws spurious exception text in jenkins.err.log
Title: Message Title Kalpesh Jain edited a comment on JENKINS-12258 Re: Plugin is missing descriptor, which throws spurious exception text in jenkins.err.log Team getting Can you check below issue can anybody help me am getting on this unix server Java version "1 . 8.0_151" Jenkins version-jenkins-2.164.1-1.2.noarch Mar 29, 2019 12:18:23 AM org.eclipse.jetty.server.HttpChannel handleExceptionWARNING: ERROR dispatch failedjava.lang.AssertionError: class hudson.security.csrf.DefaultCrumbIssuer is missing its descriptor at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1546) at hudson.security.csrf.CrumbIssuer.getDescriptor(CrumbIssuer.java:151) at hudson.Functions.getCrumbRequestField(Functions.java:1812) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:55) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at
[JIRA] (JENKINS-45763) Remove views from config.xml for backing up.
Title: Message Title Ian Williams commented on JENKINS-45763 Re: Remove views from config.xml for backing up. Have you considered using folders instead of views? cloudbees-folder 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-56807) Jenkins can not call batch file
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-56807 Jenkins can not call batch file Change By: Isa Vilacides Component/s: _unsorted Component/s: jenkinsfile-runner 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-12258) Plugin is missing descriptor, which throws spurious exception text in jenkins.err.log
Title: Message Title Kalpesh Jain commented on JENKINS-12258 Re: Plugin is missing descriptor, which throws spurious exception text in jenkins.err.log Team getting below issue can anybody help me on this. Mar 29, 2019 12:18:23 AM org.eclipse.jetty.server.HttpChannel handleException WARNING: ERROR dispatch failed java.lang.AssertionError: class hudson.security.csrf.DefaultCrumbIssuer is missing its descriptor at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1546) at hudson.security.csrf.CrumbIssuer.getDescriptor(CrumbIssuer.java:151) at hudson.Functions.getCrumbRequestField(Functions.java:1812) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.parser.EscapingExpression.evaluate(EscapingExpression.java:24) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:55) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at
[JIRA] (JENKINS-56676) Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
Title: Message Title Anda Sorina Laakso commented on JENKINS-56676 Re: Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException These is indeed a bug for the case when the path contains spaces. It has been fixed already, but the fix will be available only in 5.8. 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-53459) Warnings related to JDK tools in Jenkins 2.121.3
Title: Message Title Ian Williams commented on JENKINS-53459 Re: Warnings related to JDK tools in Jenkins 2.121.3 You say you went from to 2.89.4 to 2.121.3 Please reveiw:JENKINS-54018 issue and comments. Seems like a similar issue. Try explicitly install jdk-tools 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-55994) Demo and Test Automation for showing Jenkinsfile Runner on Java 11
Title: Message Title Evaristo Gutierrez updated JENKINS-55994 Jenkins / JENKINS-55994 Demo and Test Automation for showing Jenkinsfile Runner on Java 11 Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed 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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots:{{Jenkins.instance.pluginManager.plugins.sort(false) { }} {{ { a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase()} .each }} {{ .each { plugin ->}}{{ println "${plugin.getShortName()}:${plugin.getVersion()} | ${plugin.getDisplayName()} "}}{{ }; return}}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots:{ \ { Jenkins.instance.pluginManager.plugins.sort(false) { }} \ {{ a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase() }.each }} \ {{ { plugin ->}} \ {{ println "${plugin.getShortName() }:${plugin.getVersion() } | ${plugin.getDisplayName() }"}} \ {{ }; return }}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots: {{Jenkins.instance.pluginManager.plugins.sort(false) }} { {{ a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase()} }}{{ .each { plugin -> }} {{ println "${plugin.getShortName()}:${plugin.getVersion()} | ${plugin.getDisplayName()} " }} {{ }; return }}
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-56807) Jenkins can not call batch file
Title: Message Title wu jie created an issue Jenkins / JENKINS-56807 Jenkins can not call batch file Issue Type: Task Assignee: Unassigned Attachments: image-2019-03-29-16-42-55-319.png, image-2019-03-29-16-45-23-038.png, image-2019-03-29-16-47-13-313.png, image-2019-03-29-16-48-14-532.png Components: jenkinsfile-runner Created: 2019-03-29 08:53 Environment: Jenkins 2.164 windows 10 professional edition Priority: Minor Reporter: wu jie I hope Jenkins can call this batch file to execute.But the rusult is unexpected. it indicates that D:\Devapp\Jenkins\workspace\D1HA13T>D1HA13.cydsn\D1HA13.bat make: makefile: No such file or directory make: *** No rule to make target 'makefile'. Stop. The relatvie path is shown as below The content of D1HA13 batch file is shown as below If I input the command " make -fD1HA13.cydsn/makefile clean" instead of batch file path, Jenkin can run correctly. *I want to know how to inplement batch file in Jenkins.*Thanks in advanced!!!
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots: {\{ Jenkins.instance.pluginManager.plugins.sort(false) { }} \{{ a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase() }.each }} \ { { { plugin -> }} \{{ println "${plugin.getShortName() }:${plugin.getVersion() } | ${plugin.getDisplayName() }" }} \{{ }; return }}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots:{ \ { Jenkins.instance.pluginManager.plugins.sort(false) { }} \ {{ a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase() }.each }} \ {{ { plugin ->}} \ {{ println "${plugin.getShortName() }:${plugin.getVersion() } | ${plugin.getDisplayName() }"}} \ {{ }; return }}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots:{{Jenkins.instance.pluginManager.plugins.sort(false) { }} {{ { a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase()} .each }} {{ .each { plugin ->}}{{ println "${plugin.getShortName()}:${plugin.getVersion()} | ${plugin.getDisplayName()} "}}{{ }; return}}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots: {{Jenkins.instance.pluginManager.plugins.sort(false) }} { {{ a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase()} }}{{ .each { plugin -> }} {{ println "${plugin.getShortName()}:${plugin.getVersion()} | ${plugin.getDisplayName()} " }} {{ }; return }}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots: {{Jenkins.instance.pluginManager.plugins.sort(false) }} { {{ a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase()} }}{{ .each { plugin -> }} {{ println "${plugin.getShortName()}:${plugin.getVersion()} | ${plugin.getDisplayName()} " }} {{ }; return }}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams edited a comment on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots:{{Jenkins.instance.pluginManager.plugins.sort(false) \ { a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase()}.each { plugin -> }} {{ println "${plugin.getShortName()}:${plugin.getVersion()} | ${plugin.getDisplayName()} " }} {{ }; return}}
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-53545) Error while saving System Configuration in Jenkins
Title: Message Title
Ian Williams commented on JENKINS-53545
Re: Error while saving System Configuration in Jenkins
You can also run this one-liner system groovy to list the plugins in lieu of screenshots: Jenkins.instance.pluginManager.plugins.sort(false) { a, b -> a.getShortName().toLowerCase() <=> b.getShortName().toLowerCase()}.each { plugin -> {{ println "${plugin.getShortName()}:${plugin.getVersion()} | ${plugin.getDisplayName()} "}} }; return
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-54767) Global variables are overriding local variables
Title: Message Title fisnik hajredini commented on JENKINS-54767 Re: Global variables are overriding local variables We have added a helper function where we get the environment data. You can check our Jenkins CI/CD on https://github.com/pelagicore/pelux-manifests.git 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-51913) Post-build action "Archive the artifacts" prints exception to console when no artifacts found
Title: Message Title Vincent Massol commented on JENKINS-51913 Re: Post-build action "Archive the artifacts" prints exception to console when no artifacts found Side note: I'm using a "rsync -R" command because I wanted to keep the path of the artifacts because I have several artifacts with the same name at different locations and I was hoping that "archiveArtifacts" would support this and show the artifacts in a tree for example or with a full path. At some point, for some job, I saw a tree but I can't find it again. 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-56045) Not able to upgrade the jenkins version from 1.58 to 2.121 | Error - java.lang.NoSuchMethodError: com.google.common.util.concurrent
Title: Message Title Ian Williams commented on JENKINS-56045 Re: Not able to upgrade the jenkins version from 1.58 to 2.121 | Error - java.lang.NoSuchMethodError: com.google.common.util.concurrent I can't speak specifically to your error, but it's major leap from 1.580.1 up, especially with security issues. Have you tried going incrementally to the latest (LTS) 1.651.3, then up to a 2.x release (eg: LTS 2.7.4) and finally up to latest LTS? Have you reviewed the Upgrade Notes ? WeblLogic Socket Subsystem Messages BEA-000449 Warning: Closing socket as no data read from it during the configured idle timeout of idleTimeout secs Description Closing socket as no data read from it during the configured idle timeout of idleTimeout secs Cause The WebLogic Server or the network may be overloaded which is causing the socket to idle timeout. Action Capacity tuning of the server is required. Note: latest 2.x requires Java 1.8+ Add Comment
[JIRA] (JENKINS-56806) remove workspace dependency
Title: Message Title
Christopher Fenner updated an issue
Jenkins / JENKINS-56806
remove workspace dependency
Change By:
Christopher Fenner
In a pipeline's post section I would like to invoke the influx step without having a node to not block an executor on my Jenkins. {code:java}pipeline{ agent none stages{... } post{always{ influxDb influx (...)} }}{code} Is the dependency to a workspace necessary or could this be changed?Currently I get this:{code :java }org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{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-56676) Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException
Title: Message Title Johan Klintholm commented on JENKINS-56676 Re: Microfocus Plugin 5.7 crash - ArgumentOutOfRangeException I have had similar experiences. What I can also see is that it affects only test set paths containing spaces. If I change name of a test set so that the entire path is void of spaces, the plugin actually works. Seems to be a really simple case of regression here. 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-56806) remove workspace dependency
Title: Message Title
Christopher Fenner created an issue
Jenkins / JENKINS-56806
remove workspace dependency
Issue Type:
Improvement
Assignee:
Aleksi Simell
Components:
influxdb-plugin
Created:
2019-03-29 08:23
Priority:
Minor
Reporter:
Christopher Fenner
In a pipeline's post section I would like to invoke the influx step without having a node to not block an executor on my Jenkins.
pipeline{
agent none
stages{
...
}
post{
always{
influxDb(...)
}
}
}
Is the dependency to a workspace necessary or could this be changed? Currently I get this:
org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node
[JIRA] (JENKINS-51913) Post-build action "Archive the artifacts" prints exception to console when no artifacts found
Title: Message Title
Vincent Massol commented on JENKINS-51913
Re: Post-build action "Archive the artifacts" prints exception to console when no artifacts found
I've improve a bit my script:
// Save videos generated by Docker-based tests, if any
// Note: We use the "find" shell command since there's some limitation currently with archiveArtifacts,
// see https://issues.jenkins-ci.org/browse/JENKINS-51913
echoXWiki "Looking for test videos in ${pwd()}"
def findPath = "-path '*/target/*' -not \\( -path '*/tmp-jenkins-flv/*' -prune \\)"
def rsyncCommand = "rsync -R {} tmp-jenkins-flv/"
sh "find . ${findPath} -type f -name '*.flv' -exec ${rsyncCommand} \\;"
archiveArtifacts artifacts: "tmp-jenkins-flv/**/*.flv", allowEmptyArchive: true
// Save images generated by functional tests, if any
// Note: We use the "find" shell command since there's some limitation currently with archiveArtifacts,
// see https://issues.jenkins-ci.org/browse/JENKINS-51913
// Note: we look for screenshots only in the screenshots directory to avoid false positives such as PNG images
// that would be located in a XWiki distribution located in target/.
echoXWiki "Looking for test failure images in ${pwd()}"
findPath = "-path '*/target/*/screenshots' -not \\( -path '*/tmp-jenkins-png/*' -prune \\)"
rsyncCommand = "rsync -R {} tmp-jenkins-png/"
sh "find . ${findPath} -type f -name '*.png' -exec ${rsyncCommand} \\;"
archiveArtifacts artifacts: "tmp-jenkins-png/**/*.png", allowEmptyArchive: true
Jesse Glick However, this morning, I noticed that it's still failing with:
➡ Looking for test videos in /home/hudsonagent/jenkins_root/workspace/ki_xwiki-platform_stable-10.11.x
[Pipeline] sh
+ find . -path */target/* -not ( -path */tmp-jenkins-flv/* -prune ) -type f -name *.flv -exec rsync -R {} tmp-jenkins-flv/ ;
[Pipeline] archiveArtifacts
Archiving artifacts
java.lang.InterruptedException: no matches found within 1
at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:2802)
at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2711)
at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2662)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to agent-1-3
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:957)
at hudson.FilePath.act(FilePath.java:1068)
at hudson.FilePath.act(FilePath.java:1057)
at hudson.FilePath.validateAntFileMask(FilePath.java:2660)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:243)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at
[JIRA] (JENKINS-51913) Post-build action "Archive the artifacts" prints exception to console when no artifacts found
Title: Message Title
Vincent Massol edited a comment on JENKINS-51913
Re: Post-build action "Archive the artifacts" prints exception to console when no artifacts found
I've improve improved a bit my script:{code}// Save videos generated by Docker-based tests, if any// Note: We use the "find" shell command since there's some limitation currently with archiveArtifacts,// see https://issues.jenkins-ci.org/browse/JENKINS-51913echoXWiki "Looking for test videos in ${pwd()}"def findPath = "-path '*/target/*' -not \\( -path '*/tmp-jenkins-flv/*' -prune \\)"def rsyncCommand = "rsync -R {} tmp-jenkins-flv/"sh "find . ${findPath} -type f -name '*.flv' -exec ${rsyncCommand} \\;"archiveArtifacts artifacts: "tmp-jenkins-flv/**/*.flv", allowEmptyArchive: true// Save images generated by functional tests, if any// Note: We use the "find" shell command since there's some limitation currently with archiveArtifacts,// see https://issues.jenkins-ci.org/browse/JENKINS-51913// Note: we look for screenshots only in the screenshots directory to avoid false positives such as PNG images// that would be located in a XWiki distribution located in target/.echoXWiki "Looking for test failure images in ${pwd()}"findPath = "-path '*/target/*/screenshots' -not \\( -path '*/tmp-jenkins-png/*' -prune \\)"rsyncCommand = "rsync -R {} tmp-jenkins-png/"sh "find . ${findPath} -type f -name '*.png' -exec ${rsyncCommand} \\;"archiveArtifacts artifacts: "tmp-jenkins-png/**/*.png", allowEmptyArchive: true{code}[~jglick] However, this morning, I noticed that it's still failing with:{noformat}➡ Looking for test videos in /home/hudsonagent/jenkins_root/workspace/ki_xwiki-platform_stable-10.11.x[Pipeline] sh+ find . -path */target/* -not ( -path */tmp-jenkins-flv/* -prune ) -type f -name *.flv -exec rsync -R {} tmp-jenkins-flv/ ;[Pipeline] archiveArtifactsArchiving artifactsjava.lang.InterruptedException: no matches found within 1 at hudson.FilePath$ValidateAntFileMask.hasMatch(FilePath.java:2802) at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2711) at hudson.FilePath$ValidateAntFileMask.invoke(FilePath.java:2662) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to agent-1-3 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1068) at hudson.FilePath.act(FilePath.java:1057) at hudson.FilePath.validateAntFileMask(FilePath.java:2660) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:243) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused: hudson.FilePath$TunneledInterruptedException at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3043) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at
[JIRA] (JENKINS-56805) Compatibility with Configuration As Code Plugin
Title: Message Title
Palash Oswal updated an issue
Jenkins / JENKINS-56805
Compatibility with Configuration As Code Plugin
Change By:
Palash Oswal
Hudson throws this error when Configuration as Code plugin tries to load matrix auth :{code:java} java.lang.IllegalStateException: No configurator implementation to manage class hudson.security.GlobalMatrixAuthorizationStrategy at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.configure(HeteroDescribableConfigurator.java:95) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.check(HeteroDescribableConfigurator.java:101) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.check(HeteroDescribableConfigurator.java:43) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:338) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:273) at io.jenkins.plugins.casc.ConfigurationAsCode.lambda$checkWith$8(ConfigurationAsCode.java:645) at io.jenkins.plugins.casc.ConfigurationAsCode.invokeWith(ConfigurationAsCode.java:608) at io.jenkins.plugins.casc.ConfigurationAsCode.checkWith(ConfigurationAsCode.java:645) at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:630) at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:542) at io.jenkins.plugins.casc.ConfigurationAsCode.configure(ConfigurationAsCode.java:272) at io.jenkins.plugins.casc.ConfigurationAsCode.init(ConfigurationAsCode.java:264)Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)Caused: java.lang.Error at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1068) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused: org.jvnet.hudson.reactor.ReactorException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) at jenkins.InitReactorRunner.run(InitReactorRunner.java:48) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1102) at jenkins.model.Jenkins.(Jenkins.java:904) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Caused: hudson.util.HudsonFailedToLoad at hudson.WebAppMain$3.run(WebAppMain.java:250) {code} It's currently not
[JIRA] (JENKINS-56787) A project which is checked out via Jenkins can not be built correctly
Title: Message Title wu jie edited a comment on JENKINS-56787 Re: A project which is checked out via Jenkins can not be built correctly Hi Ivan，thanks for your response. I change the version from 2.169 to 2.164, this issue is fixed. This is makefile can be ran in local before. I check the Jenkins workspace and find that the icon of many files is marked a "x" include included makefile file. If I open makefile ,input a whitespace and save it, the "x" will disappear. And then this makefile can be impelemented. I check the makefile which got by Jenkins V2.164 is without "x" mark. I guess this maybe an operation error with some unkown reason. 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-56787) A project which is checked out via Jenkins can not be built correctly
Title: Message Title wu jie commented on JENKINS-56787 Re: A project which is checked out via Jenkins can not be built correctly Hi Ivan，thanks for your response. I change the version from 2.169 to 2.164, this issue is fixed. This is makefile can be ran in local before. I check the Jenkins workspace and find that the icon of many files is marked a "x" include makefile file. If I open makefile ,input a whitespace and save it, the "x" will disappear. And then this makefile can be impelemented. I check the makefile which got by Jenkins V2.164 is without "x" mark. I guess this maybe an operation error with some unkown reason. 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-54040) Profile based defaults for jobs
Title: Message Title Sami Korhonen commented on JENKINS-54040 Re: Profile based defaults for jobs This seems to be implemented in commercial version. Closing the issue 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-54040) Profile based defaults for jobs
Title: Message Title Sami Korhonen updated JENKINS-54040 Jenkins / JENKINS-54040 Profile based defaults for jobs Change By: Sami Korhonen Status: Open Fixed but Unreleased Resolution: Won't Do 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.
