[JIRA] (JENKINS-39094) FilterPathImpl not ignoring file
Title: Message Title
Heiko Nardmann created an issue
Jenkins / JENKINS-39094
FilterPathImpl not ignoring file
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2016/Oct/19 7:00 AM
Priority:
Minor
Reporter:
Heiko Nardmann
I'm using two Jenkinsfiles to describe similar pipelines, e.g.
//streamProject/components/A/Jenkins/Jenkinsfile.release
//streamProject/components/A/Jenkins/Jenkinsfile.coverage
The first one is a normal release pipeline which gets triggered by Perforce changes. The second one is scheduled to run once daily. Now I do not want the first pipeline to start if the second pipeline script is changed. Therefore I have the following inside Jenkinsfile.release:
checkout([$class: 'PerforceScm',
credential: 'p4user',
filter: [[$class: 'FilterPathImpl', path: '//streamProject/components/A/.p4ignore.txt'],
[$class: 'FilterPathImpl', path: '//streamProject/components/A/Jenkins/Jenkinsfile.coverage']],
populate: [$class: 'AutoCleanImpl', delete: true, modtime: false, parallel: [enable: false], pin: '', quiet: true, replace: true],
workspace: [$class: 'StreamWorkspaceImpl', charset: 'none', format: 'jenkins_${NODE_NAME}_${JOB_NAME}', pinHost: false, streamName: '//streamProject']
]
)
[JIRA] (JENKINS-31039) Queue items are ephemeral leading to api users to lose track of builds.
Title: Message Title Axel Shevchenok commented on JENKINS-31039 Re: Queue items are ephemeral leading to api users to lose track of builds. Hi there! For anyone facing the same issue, we've managed it quite simply: in case of Jenkins API raising HTTPError with 404 code (which means that requested queue item is lost) - just enqueue it again, with the same parameters, as usual: result = jenkins_job.invoke(build_params) You can do this as many times a you need. We found that 3 times is sufficient for our needs, which is 10-15, even 20 minutes of job waiting for build slave to be available. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39095) RpmSignPlugin does not sign all packages but reports success
Title: Message Title Sebastian Denz created an issue Jenkins / JENKINS-39095 RpmSignPlugin does not sign all packages but reports success Issue Type: Bug Assignee: Unassigned Components: rpmsign-plugin Created: 2016/Oct/19 7:13 AM Environment: CentOS Linux release 7.2.1511 (Core) Priority: Major Reporter: Sebastian Denz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39096) duplicate display of "Label This Build"
Title: Message Title Heiko Nardmann created an issue Jenkins / JENKINS-39096 duplicate display of "Label This Build" Issue Type: Bug Assignee: Unassigned Attachments: Duplicate-Label_This_Build-and-Changes.png Components: p4-plugin Created: 2016/Oct/19 7:14 AM Priority: Minor Reporter: Heiko Nardmann I experiencing the same problem regarding double (or even multiple) display of "Label This Build" as it is described inside JENKINS-30425 (see p4plugin-changelog-missing-3.png). Since this old issue has solved the other reported problem this new issue shall track the "Label This Build" problem. Inside the the folder for that build /var/lib/jenkins/jobs/.../builds/2 I see two changelog files: changelog0.xml changelog1.xml They are identical (verified using diff). That might also be the reason why I also see duplicate change entries?
[JIRA] (JENKINS-39096) duplicate display of "Label This Build"
Title: Message Title
Heiko Nardmann updated an issue
Jenkins / JENKINS-39096
duplicate display of "Label This Build"
Change By:
Heiko Nardmann
I experiencing the same problem regarding double (or even multiple) display of "Label This Build" as it is described inside JENKINS-30425 (see p4plugin-changelog-missing-3.png). Since this old issue has solved the other reported problem this new issue shall track the "Label This Build" problem.Inside the the folder for that build {{/var/lib/jenkins/jobs/.../builds/2}} I see two changelog files:* changelog0.xml* changelog1.xml They are identical (verified using {{diff}}).That might also be the reason why I also see duplicate change entries?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit ht
[JIRA] (JENKINS-39095) RpmSignPlugin does not sign all packages but reports success
Title: Message Title
Sebastian Denz updated an issue
Jenkins / JENKINS-39095
RpmSignPlugin does not sign all packages but reports success
Change By:
Sebastian Denz
Environment:
CentOS Linux release 7.2.1511 (Core) Jenkins 2.7.1RpmSignPlugin 0.4.6
While trying to sign a folder with a large amount of RPMs,the plugin does not sign all Files, but reports success at the end.{noformat}Started by user adminBuilding in workspace /home/jenkins/test[RpmSignPlugin] - Starting signing RPMs ...[RpmSignPlugin] - Importing private key[test] $ gpg --import -gpg: key E4091234: already in secret keyringgpg: Total number processed: 1gpg: secret keys read: 1gpg: secret keys unchanged: 1[RpmSignPlugin] - Imported private key[test] $ gpg --fingerprint i...@doesntmatter.depub 4096R/E4091234 2010-06-11 Key fingerprint = A40A 6F3E A5BA B218 94FB 0A2F 8AE5 FF0B E409 1234uid doesntmatter [RpmSignPlugin] - Publishing *.rpm[RpmSignPlugin] - Running rpm --define "_gpg_name i...@doesntmatter.de" --resign /home/jenkins/test/sandbox-0.76-1-1.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-10.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-100.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-11.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-12.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-13.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-14.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-15.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-16.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-17.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-18.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-19.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-2.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-20.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-21.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-22.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-23.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-24.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-25.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-26.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-27.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-28.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-29.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-3.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-30.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-31.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-32.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-33.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-34.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-35.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-36.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-37.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-38.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-39.el6.noarch.rpm /home/jenkins/test/sandbox-0.76-1-4.el6.noarch.rpm /
[JIRA] (JENKINS-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Oliver Gondža commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes Joshua Harlow, No good news from cloud-init land? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38859) ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild
Title: Message Title Chen Cohen assigned an issue to Chen Cohen Jenkins / JENKINS-38859 ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild Change By: Chen Cohen Assignee: hagzag Chen Cohen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38859) ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild
Title: Message Title Chen Cohen commented on JENKINS-38859 Re: ClassCastException: sun.nio.cs.UTF_8 cannot be cast to com.tikal.jenkins.plugins.multijob.MultiJobBuild$SubBuild I was unable to reproduce your issue. Please add your recreation steps. Thanks, Chen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39097) PANIC : Broken AVD system path
Title: Message Title kavitha Ramasamy created an issue Jenkins / JENKINS-39097 PANIC : Broken AVD system path Issue Type: Bug Assignee: Christopher Orr Attachments: Existing Emulator.png, Glopal properties.png, New Emulator.png, SDK root config.png Components: android-emulator-plugin Created: 2016/Oct/19 7:37 AM Environment: Jenkins Version : 2.7.4 Git : 3.0.0 Gradle : 3.1 Android Emulator : 2.15 Java version : 1.8 OS : Windows 10 Emulator name : Galaxy_Nexus_API_22 Labels: jenkins plugin Priority: Major Reporter: kavitha Ramasamy Hi, I have using jenkins for CI process. I had Create a new project(Gradle) in jenkins using Git URL. and i had configure the android lint for get report its working fine and the Build is success. After that i added the Android Emulator and i created the new Emulator then build the project it showing the error like, 12:58:20 Started by user anonymous 12:58:20 Building in workspace C:\Program Files (x86)\Jenkins\workspace\Lazhora 12:58:20 > git.exe rev-parse --is-inside-work-tree # timeout=10 12:58:20 Fetching changes from the remote Git repository 12:58:20 > git.exe config remote.origin.url https://preeth...@bitbucket.org/karthee/lazhora.git # timeout=10 12:58:20 Fetching upstream changes from https://preeth...@bitbucket.org/karthee/lazhora.git 12:58:20 > git.exe --version # timeout=10 12:58:20 > git.exe fetch --tags --progres
[JIRA] (JENKINS-39066) hudson.util.ArgumentListBuilder quoting incorrectly in procStarter
Title: Message Title Joseph Petersen commented on JENKINS-39066 Re: hudson.util.ArgumentListBuilder quoting incorrectly in procStarter So mark as resolved or look into why it is behaving differently on Unix and Windows? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39098) Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone
Title: Message Title saiful faizee created an issue Jenkins / JENKINS-39098 Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone Issue Type: Bug Assignee: Mark Waite Attachments: Screenshot - 19_10_2016 , 3_50_54 PM.png Components: git-plugin Created: 2016/Oct/19 7:52 AM Priority: Critical Reporter: saiful faizee Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39059) Use different cause for deleting a node and make it internationalizable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39059 Re: Use different cause for deleting a node and make it internationalizable Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanComputer.java src/main/resources/com/redhat/foreman/Messages.properties http://jenkins-ci.org/commit/foreman-node-sharing-plugin/8cae2f558f6f110c457ace3694dea9e793ac60cf Log: JENKINS-39059 Added PendingTermination cause PendingTermination cause is internationalized and is used for signaling removal process is undergoing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39059) Use different cause for deleting a node and make it internationalizable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39059 Re: Use different cause for deleting a node and make it internationalizable Code changed in jenkins User: Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanComputer.java src/main/resources/com/redhat/foreman/Messages.properties http://jenkins-ci.org/commit/foreman-node-sharing-plugin/a41c25ce09dc7fa45fb95b35c1015149b9ddfc27 Log: Merge pull request #23 from pjanouse/JENKINS-39059-PendingTermination JENKINS-39059 Added PendingTermination cause Compare: https://github.com/jenkinsci/foreman-node-sharing-plugin/compare/bf183b96625b...a41c25ce09dc Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39090) Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins
Title: Message Title Stephen Connolly closed an issue as Cannot Reproduce No startup log supplied No working version of credentials supplied A clean Jenkins 2.26 with Credentials 2.1.7 starts up without issue The diff cannot have any effect on the login form There is no dependency relationship between the active directory plugin and the credentials plugin If you can supply the start-up log and the version of credentials that was working for you, please feel free to re-open, otherwise this issue is "Cannot Reproduce" as based on the information you provided I have been unable to reproduce this Jenkins / JENKINS-39090 Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins Change By: Stephen Connolly Status: Open Closed Resolution: Cannot Reproduce Add Comment
[JIRA] (JENKINS-39099) ${BUILDS_THIS_YEAR} drops trailing 0
Title: Message Title
daniel jansson created an issue
Jenkins / JENKINS-39099
${BUILDS_THIS_YEAR} drops trailing 0
Issue Type:
Bug
Assignee:
Unassigned
Components:
versionnumber-plugin
Created:
2016/Oct/19 8:16 AM
Environment:
Jenkins 2.7.4 VersionNumber-plugin 1.8.1
Labels:
plugins
Priority:
Minor
Reporter:
daniel jansson
Hi We are using version format $ {BUILD_YEAR} .$ {BUILDS_THIS_YEAR} which works great for us until ${BUILDS_THIS_YEAR} ends with a 0, IE 10, 20. Then $ {BUILDS_THIS_YEAR} will return 1 and 2, without the 0. This also happens when we are using $ {BUILDS_THIS_YEAR, } , then it resolves to 001 instead of 0010. If you could fix this we would be very pleased regards Daniel
Add Comment
[JIRA] (JENKINS-32736) Ability to support simple arithmetic with the build version number
Title: Message Title
daniel jansson updated an issue
Jenkins / JENKINS-32736
Ability to support simple arithmetic with the build version number
Change By:
daniel jansson
Thank you for the versionnumber Jenkins plugin.I would like the versionnumber Jenkins plugin to support simple arithmetic to calculate the build version number. An example version number format string:{code:java}1.0.(1200 * ${YEARS_SINCE_PROJECT_START}) + ${BUILD_MONTH, X}${BUILD_DAY, XX}.${BUILDS_TODAY, X}{code}In this way, if my project started in 2015, the last build in that year would have a version number of 1.0.1231.1 for example.And then instead of having to increment the minor version number, the next build in the new year would be 1.0.1301.1 for example.It doesn't seem that the plugin currently supports this.Thank you.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and
[JIRA] (JENKINS-36446) Bug when change auth system
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-36446 Bug when change auth system Change By: Stephen Connolly Component/s: core Component/s: credentials-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36446) Bug when change auth system
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-36446 Bug when change auth system Change By: Stephen Connolly Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36446) GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start
Title: Message Title Stephen Connolly assigned an issue to Kirill Merkushev Jenkins / JENKINS-36446 GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start Change By: Stephen Connolly Assignee: Stephen Connolly Kirill Merkushev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36446) GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-36446 GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start Change By: Stephen Connolly Summary: Bug when change auth system GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39076) Stack Overflow when trying to save system configuration
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-39076 Stack Overflow when trying to save system configuration Change By: Daniel Beck Component/s: jira-trigger-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39076) Stack Overflow when trying to save system configuration
Title: Message Title Daniel Beck commented on JENKINS-39076 Re: Stack Overflow when trying to save system configuration May be caused by https://github.com/jenkinsci/jenkins/pull/2509 Jesse Glick Could you PTAL? Does https://github.com/jenkinsci/jira-trigger-plugin/blob/e6ea6e0b54ad910d38700d2a539801cd008b3f75/src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/JiraTriggerGlobalConfiguration.groovy#L32...L37 look correct to you? This super call just shouldn't be there I think… Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39054) Shell interpreter doesn't work on windows when PATH to sh.exe contains a space
Title: Message Title Daniel Beck commented on JENKINS-39054 Re: Shell interpreter doesn't work on windows when PATH to sh.exe contains a space Which Java version is this? I think there was a security update 1-2 years ago that changed the behavior here and broke a lot of applications relying on this. For the time being, would Progra~1 or whatever it is be a pragmatic workaround? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36446) GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start
Title: Message Title Stephen Connolly commented on JENKINS-36446 Re: GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start https://github.com/jenkinsci/github-plugin/blob/a9b9b2893c0eec322d4687ce76131950df991180/src/main/java/org/jenkinsci/plugins/github/GitHubPlugin.java#L36 is the issue here. This fix is probably to move the migration to after=EXTENSIONS_AUGMENTED as that is the only time when a plugin can know that all the other plugins (e.g. the credentials plugin) have been initialized and are available to the uber-classloader. Given that the migration specifically performs credentials migration: https://github.com/jenkinsci/github-plugin/blob/a9b9b2893c0eec322d4687ce76131950df991180/src/main/java/org/jenkinsci/plugins/github/migration/Migrator.java#L43 this would explain the issue. Downgrading may have changed the plugin key hash and consequently allowed the graph to "magically" resolve by chance such that credentials gets loaded into the uber-classloader before the git plugin runs its migration. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39024) Jenkins REST API xml files are not parseable
Title: Message Title Daniel Beck commented on JENKINS-39024 Re: Jenkins REST API xml files are not parseable are not parseable, due to some element values could contain special characters, like "&&"... etc. What specifically is broken in the attached file? There's no && except in the comment on top, and I think that was added by you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39090) Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins
Title: Message Title Stephen Connolly commented on JENKINS-39090 Re: Upgrade from Credentials 2.1.6 to Credentials 2.1.7 prevents logins Also check if this is a dupe of JENKINS-36446 (i.e. do you have the git plugin installed, did your startup log contain: Jul 05, 2016 4:08:30 PM hudson.ExtensionComponent compareTo WARNING: null java.lang.NoSuchMethodError: com.cloudbees.plugins.credentials.Messages.CredentialsProviderFilter_None_DisplayName()Ljava/lang/String; at com.cloudbees.plugins.credentials.CredentialsProviderFilter$None$DescriptorImpl.getDisplayName(CredentialsProviderFilter.java:161) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:97) at hudson.ExtensionComponent.compareTo(ExtensionComponent.java:42) // SNIP at hudson.ExtensionList.get(ExtensionList.java:147) at com.cloudbees.jenkins.GitHubPushTrigger$DescriptorImpl.get(GitHubPushTrigger.java:329) at org.jenkinsci.plugins.github.migration.Migrator.migrate(Migrator.java:40) at org.jenkinsci.plugins.github.GitHubPlugin.postInitialize(GitHubPlugin.java:39) at hudson.PluginManager$2$1$2.run(PluginManager.java:429) //SNIP the critical lines being org.jenkinsci.plugins.github.migration.Migrator.migrate(Migrator.java:40) working its way towards java.lang.NoSuchMethodError: com.cloudbees.plugins.credentials.Messages.CredentialsProviderFilter_None_DisplayName()Ljava/lang/String; exception) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38676) git summary should show the repository URL
Title: Message Title Primož Prislan commented on JENKINS-38676 Re: git summary should show the repository URL What if you can add an option (checkbox) to display just repo URL or not? Why do I have to enter "special" name to every repository I use? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38966) Rename job: No valid crumb was included in the request
Title: Message Title Daniel Beck commented on JENKINS-38966 Re: Rename job: No valid crumb was included in the request What version of Jenkins is this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38954) No valid crumb in doDelete of build
Title: Message Title Daniel Beck resolved as Duplicate The first part is not a bug, the second duplicates JENKINS-34254. Jenkins / JENKINS-38954 No valid crumb in doDelete of build Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/
[JIRA] (JENKINS-39099) ${BUILDS_THIS_YEAR} drops trailing 0
Title: Message Title
daniel jansson closed an issue as Not A Defect
Sorry. The problem was else where
Jenkins / JENKINS-39099
${BUILDS_THIS_YEAR} drops trailing 0
Change By:
daniel jansson
Status:
Open Closed
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Daniel Beck commented on JENKINS-38914 Re: hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Could you clarify, are you using extremely long parameter values for your builds? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38911) Incorrect JDK tool version used for builds after new tool added
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-38911 Incorrect JDK tool version used for builds after new tool added Change By: Daniel Beck Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38911) Incorrect JDK tool version used for builds after new tool added
Title: Message Title Daniel Beck commented on JENKINS-38911 Re: Incorrect JDK tool version used for builds after new tool added Wow, I thought this was fixed in the context of JENKINS-755 (in which I explained this insane behavior in comments), but it appears not. wtf. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38911) Incorrect JDK tool version used for builds after new tool added
Title: Message Title Daniel Beck resolved as Duplicate Looks like a duplicate of JENKINS-10191 Jenkins / JENKINS-38911 Incorrect JDK tool version used for builds after new tool added Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/
[JIRA] (JENKINS-38842) Sort workspace folder by descending number order
Title: Message Title Daniel Beck commented on JENKINS-38842 Re: Sort workspace folder by descending number order autobuild folder with archive of builds and the order of the folders is ascending which results that old builds are up in the page instead of down. That's not how workspaces are supposed to be used, so I doubt we'll ever address this in core. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38842) Sort workspace folder by descending number order
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-38842 Sort workspace folder by descending number order Change By: Daniel Beck Component/s: plugin-proposals Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36446) GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start
Title: Message Title Stephen Connolly commented on JENKINS-36446 Re: GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start https://github.com/jenkinsci/github-plugin/pull/150 is my suggested fix of this issue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38822) Service fails to restart when both .jpi and .hpi files found
Title: Message Title Daniel Beck commented on JENKINS-38822 Re: Service fails to restart when both .jpi and .hpi files found What exactly is the error? And what do you expect to happen here? Note that Jenkins has been renaming plugins from hpi to jpi for a long time, so this looks more like a messed up configuration to me than a bug. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title Daniel Beck commented on JENKINS-38819 Re: Build history not visible for user who copied jobs I don't have access to logs or command line access on our Jenkins installation, but may be able to get assistance get that if it will help fix the issue. Without at least the Jenkins log output, this issue cannot be investigated. Get help from your Jenkins admin, and ask them to provide the logs at the /log/all URL. Also, anything interesting in your browser's script console/JS error log? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38770) Not all builds show in the build history dashboard on job
Title: Message Title Daniel Beck commented on JENKINS-38770 Re: Not all builds show in the build history dashboard on job The builds list is paginated, buttons to the top right of the widget allow you to navigate through the build pages. Could this be the problem? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38716) editor not accessible to screenreader
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-38716 editor not accessible to screenreader Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38634) Can't copy text from certain fields using Safari 10
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-38634 Can't copy text from certain fields using Safari 10 Change By: Daniel Beck Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38612) With the new Timezone expression in Cron, should the help tab not reflect the timezone listed in the expression?
Title: Message Title Daniel Beck commented on JENKINS-38612 Re: With the new Timezone _expression_ in Cron, should the help tab not reflect the timezone listed in the _expression_? Still? Oleg Nenashev maybe it's time you gave this task to someone else? I'd be happy to take over. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38610) Jenkins hangs after plugin install
Title: Message Title Daniel Beck resolved as Incomplete No response to request for more information in two weeks, so resolving as incomplete. Jenkins / JENKINS-38610 Jenkins hangs after plugin install Change By: Daniel Beck Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https:/
[JIRA] (JENKINS-38413) Jenkins is not loading properly
Title: Message Title Daniel Beck resolved as Not A Defect This is an issue tracker, not a support site. And for a bug report, this contains too little information. Read these: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue http://www.catb.org/~esr/faqs/smart-questions.html Jenkins / JENKINS-38413 Jenkins is not loading properly Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubsc
[JIRA] (JENKINS-38819) Build history not visible for user who copied jobs
Title: Message Title max lehmann commented on JENKINS-38819 Re: Build history not visible for user who copied jobs Well, this is frustrating. Build history was missing yesterday, but this morning it's back. Which is good, but doesn't help us to diagnose the issue. As I recall there was nothing interesting around js nor anything useful in the network traffic at the time - when checking this morning the whole area of the page is back so no way to look for useful data for diagnosing the problem. I'd like to not close this just yet in case it recurs, at which point I'll chase for more data for you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39059) Use different cause for deleting a node and make it internationalizable
Title: Message Title Pavel Janoušek updated JENKINS-39059 Merged. Jenkins / JENKINS-39059 Use different cause for deleting a node and make it internationalizable Change By: Pavel Janoušek Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39038) Blank passwords break login mechanism of AccuRev plug-in
Title: Message Title Joseph Petersen resolved as Fixed Fixed in 0.7.5 Jenkins / JENKINS-39038 Blank passwords break login mechanism of AccuRev plug-in Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5122) Using AccuRev account with no password causes OBF: to populate in the password field
Title: Message Title Joseph Petersen resolved as Fixed Fixed in version 0.7.5 Jenkins / JENKINS-5122 Using AccuRev account with no password causes OBF: to populate in the password field Change By: Joseph Petersen Status: Open Resolved Assignee: Scott Tatum Joseph Petersen Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message bec
[JIRA] (JENKINS-37792) Pipeline Config: Notifications per stage
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37792 Re: Pipeline Config: Notifications per stage Code changed in jenkins User: Andrew Bayer Path: src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTBuildConditionsContainer.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTNotifications.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPostBuild.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPostStage.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/PostStage.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Root.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidator.groovy src/main/resources/ast-schema.json src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/PostStageTest.java src/test/resources/postStage/failingNotifications.groovy src/test/resources/postStage/globalAndLocalAlways.groovy src/test/resources/postStage/localAll.groovy src/test/resources/postStage/localAlways.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/9517f02825eaa52f20dde2e73c70eed2a8260a59 Log: Merge pull request #30 from jenkinsci/JENKINS-37792 JENKINS-37792 Per stage post build steps Compare: https://github.com/jenkinsci/pipeline-model-definition-plugin/compare/b7a3ec68779e...9517f02825ea Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39024) Jenkins REST API xml files are not parseable
Title: Message Title Stefan Veres updated an issue Jenkins / JENKINS-39024 Jenkins REST API xml files are not parseable Change By: Stefan Veres Attachment: testReport_eap_1_fine.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39024) Jenkins REST API xml files are not parseable
Title: Message Title Stefan Veres updated an issue Jenkins / JENKINS-39024 Jenkins REST API xml files are not parseable Change By: Stefan Veres Attachment: testReport_eap_1.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39024) Jenkins REST API xml files are not parseable
Title: Message Title Stefan Veres commented on JENKINS-39024 Re: Jenkins REST API xml files are not parseable hello Daniel Beck , if you try to parse that document, it will throw you exception: Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 400; columnNumber: 158; The content of elements must consist of well-formed character data or markup. Due to nature of the value (exception stack trace) you cannot 100% predict, what XML special character (< > &&, etc.) will occur. '&&' what I mentioned in the comment, is in attached testRepot_eap_1.xml, (parsing of that throws: Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 147; columnNumber: 127; The entity name must immediately follow the '&' in the entity reference.) So in order to work with them I need to put these problematic elements values into the , like in "testRepot_eap_1_fine testReport_eap_1.xml testReport_eap_1_fine.xml .xml" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10209) AccuRev plugin should work around accurev's "spontaneous logout" behaviour
Title: Message Title Joseph Petersen resolved as Fixed I taken steps to ensure ACCUREV_HOME is set to the node's root path to ensure it has write access. If the login process is still a issue, I would definitely look into retry login. Jenkins / JENKINS-10209 AccuRev plugin should work around accurev's "spontaneous logout" behaviour Change By: Joseph Petersen Status: Reopened Resolved Assignee: Scott Tatum Joseph Petersen Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39024) Jenkins REST API xml files are not parseable
Title: Message Title Stefan Veres edited a comment on JENKINS-39024 Re: Jenkins REST API xml files are not parseable hello [~danielbeck] ,if you try to parse that document, it will throw you exception: Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 400; columnNumber: 158; The content of elements must consist of well-formed character data or markup.Due to nature of the value (exception stack trace) you cannot 100% predict, what XML special character (< > &&, etc.) will occur.'&&' what I mentioned in the comment, is in attached testRepot_eap_1.xml,(parsing of that throws: Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 147; columnNumber: 127; The entity name must immediately follow the '&' in the entity reference.)So in order to work with them I need to put these problematic elements values into the , like in "testRepot_eap_1_fine [^testReport_eap_1 .xml ] [^testReport_eap_1_fine.xml] .xml " Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39024) Jenkins REST API xml files are not parseable
Title: Message Title Stefan Veres edited a comment on JENKINS-39024 Re: Jenkins REST API xml files are not parseable hello [~danielbeck] ,if you try to parse that document, it will throw you exception: Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 400; columnNumber: 158; The content of elements must consist of well-formed character data or markup.Due to nature of the value (exception stack trace) you cannot 100% predict, what XML special character (< > &&, etc.) will occur.'&&' what I mentioned in the comment, is in attached " testRepot_eap_1.xml " ,(parsing of that throws: Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 147; columnNumber: 127; The entity name must immediately follow the '&' in the entity reference.)So in order to work with them I need to put these problematic elements values into the , like in "testRepot_eap_1_fine.xml" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38842) Sort workspace folder by descending number order
Title: Message Title Oleg Nenashev commented on JENKINS-38842 Re: Sort workspace folder by descending number order > That's not how workspaces are supposed to be used, so I doubt we'll ever address this in core. Under "we" Daniel Beck likely means the Jekins core team. But any well-designed pull requests (e.g. adding proper extension points to the core) will be appreciated Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39100) NPE in Build/Publish Docker Container step
Title: Message Title pjdarton created an issue Jenkins / JENKINS-39100 NPE in Build/Publish Docker Container step Issue Type: Bug Assignee: magnayn Components: docker-plugin Created: 2016/Oct/19 9:47 AM Environment: docker plugin 0.16.2 jenkins 2.7 insecure docker registry and docker hosts Labels: nullpointer Priority: Major Reporter: pjdarton If you have credentials == None and a "Build / Publish Docker Containers" build step then, when the build step executes, you get a NullPointerException: Docker Build ERROR: Build step failed with exception java.lang.NullPointerException at com.nirima.jenkins.plugins.docker.utils.JenkinsUtils.makeAuthConfig(JenkinsUtils.java:173) at com.nirima.jenkins.plugins.docker.utils.JenkinsUtils.getAuthConfigurations(JenkinsUtils.java:150) at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$Run.buildImage(DockerBuilderPublisher.java:273) at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$Run.run(DockerBuilderPublisher.java:230) at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher.perform(DockerBuilderPublisher.java:361) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.bu
[JIRA] (JENKINS-39101) Config variable in global function is null
Title: Message Title
Lars Bilke created an issue
Jenkins / JENKINS-39101
Config variable in global function is null
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2016/Oct/19 9:54 AM
Environment:
Jenkins 2.26 workflow-cps-global-lib-plugin 2.4
Priority:
Major
Reporter:
Lars Bilke
I am creating a global function as [described here](https://github.com/jenkinsci/workflow-cps-global-lib-plugin#define-more-structured-dsl). Accessing the `config`-variable inside the function always returns null: ``` def call(body) { // evaluate the body block, and collect configuration into the object def config = [:] body.resolveStrategy = Closure.DELEGATE_FIRST body.delegate = config body() echo "$ {config.name} " echo config.name echo "$ {config.foo} " echo config.foo ``` When called: ``` myStep { name: 'linux-build' foo: "bar" } ``` This prints `null` four times. Am I doing something wrong or is it a bug?
Add Comment
[JIRA] (JENKINS-39101) Config variable in global function is null
Title: Message Title
Lars Bilke updated an issue
Jenkins / JENKINS-39101
Config variable in global function is null
Change By:
Lars Bilke
I am creating a global function as [described here](https://github.com/jenkinsci/workflow-cps-global-lib-plugin#define-more-structured-dsl). Accessing the `config`-variable inside the function always returns null:```def call(body) {// evaluate the body block, and collect configuration into the objectdef config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configbody()echo "${config.name}"echo config.nameecho "${config.foo}"echo config.foo```When called: ``` myStep {name: 'linux-build'foo: "bar"} ``` This prints `null` four times. Am I doing something wrong or is it a bug?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from i
[JIRA] (JENKINS-39101) Config variable in global function is null
Title: Message Title
Lars Bilke updated an issue
Jenkins / JENKINS-39101
Config variable in global function is null
Change By:
Lars Bilke
I am creating a global function as [described here](https://github.com/jenkinsci/workflow-cps-global-lib-plugin#define-more-structured-dsl). Accessing the `config`-variable inside the function always returns null:{code: groovy java }def call(body) {// evaluate the body block, and collect configuration into the objectdef config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configbody()echo "${config.name}"echo config.nameecho "${config.foo}"echo config.foo{code}When called: {code:java} myStep {name: 'linux-build'foo: "bar"} {code} This prints `null` four times. Am I doing something wrong or is it a bug?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe f
[JIRA] (JENKINS-39102) Would be nice to have option to inline first image
Title: Message Title gerard davison created an issue Jenkins / JENKINS-39102 Would be nice to have option to inline first image Issue Type: Bug Assignee: huybrechts Components: junit-attachments-plugin Created: 2016/Oct/19 9:56 AM Priority: Minor Reporter: gerard davison In a lot of cases there will be just one image for a unit attachment, and it would save a bunch of time if this was inlined, I understand this might not be the default option though, perhaps configured using a preference? Add Comment
[JIRA] (JENKINS-39101) Config variable in global function is null
Title: Message Title
Lars Bilke updated an issue
Jenkins / JENKINS-39101
Config variable in global function is null
Change By:
Lars Bilke
I am creating a global function as [described here](https://github.com/jenkinsci/workflow-cps-global-lib-plugin#define-more-structured-dsl). Accessing the `config`-variable inside the function always returns null: ``` {code:groovy} def call(body) {// evaluate the body block, and collect configuration into the objectdef config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configbody()echo "${config.name}"echo config.nameecho "${config.foo}"echo config.foo ``` {code} When called:myStep {name: 'linux-build'foo: "bar"}This prints `null` four times. Am I doing something wrong or is it a bug?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and
[JIRA] (JENKINS-39101) Config variable in global function is null
Title: Message Title
Lars Bilke updated an issue
Jenkins / JENKINS-39101
Config variable in global function is null
Change By:
Lars Bilke
I am creating a global function as [described here](https://github.com/jenkinsci/workflow-cps-global-lib-plugin#define-more-structured-dsl). Accessing the ` {{ config ` }} -variable inside the function always returns {{ null }} :{code:java}def call(body) {// evaluate the body block, and collect configuration into the objectdef config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configbody()echo "${config.name}"echo config.nameecho "${config.foo}"echo config.foo } {code}When called:{code:java}myStep {name: 'linux-build'foo: "bar"}{code}This prints ` {{ null ` }} four times. Am I doing something wrong or is it a bug?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" grou
[JIRA] (JENKINS-39101) Config variable in global function is null
Title: Message Title
Lars Bilke updated an issue
Jenkins / JENKINS-39101
Config variable in global function is null
Change By:
Lars Bilke
I am creating a global function as [described here ]( | https://github.com/jenkinsci/workflow-cps-global-lib-plugin#define-more-structured-dsl ) ] . Accessing the {{config}}-variable inside the function always returns {{null}}:{code:java}def call(body) {// evaluate the body block, and collect configuration into the objectdef config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configbody()echo "${config.name}"echo config.nameecho "${config.foo}"echo config.foo}{code}When called:{code:java} myStep {name: 'linux-build'foo: "bar"}{code}This prints {{null}} four times. Am I doing something wrong or is it a bug?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this grou
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Ben Herfurth commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Why cant the hash just be shortened? It worked for all of us before the change. Now it does not work anymore ==> change it back please. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38903) Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner
Title: Message Title Pavel Janoušek updated JENKINS-38903 Jenkins / JENKINS-38903 Split the Exceptions handling for node provision and adding a node to Jenkins in NodeProvisioner Change By: Pavel Janoušek Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33083) Missing Icons in the Job overview
Title: Message Title Jeremy Green closed an issue as Duplicate Closing as Duplicate since duplicates JENKINS-30830, and that issue has a merged (but unreleased) pull request. Jenkins / JENKINS-33083 Missing Icons in the Job overview Change By: Jeremy Green Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. F
[JIRA] (JENKINS-38637) Support for serverCredentialMappings in mavenSettingsConfigFile / globalMavenSettingsConfigFile
Title: Message Title Daniel Spilker commented on JENKINS-38637 Re: Support for serverCredentialMappings in mavenSettingsConfigFile / globalMavenSettingsConfigFile PR: https://github.com/jenkinsci/job-dsl-plugin/pull/938 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39103) Incorrect validation error in Build/Publish Docker Container step
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-39103 Incorrect validation error in Build/Publish Docker Container step Change By: pjdarton Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39103) Incorrect validation error in Build/Publish Docker Container step
Title: Message Title pjdarton created an issue Jenkins / JENKINS-39103 Incorrect validation error in Build/Publish Docker Container step Issue Type: Bug Assignee: magnayn Components: docker-plugin Created: 2016/Oct/19 10:22 AM Environment: docker-plugin 0.16.2 Priority: Minor Reporter: pjdarton The "Build / Publish Docker Containers" build step's web user-interface is misleading. The "Image" validation code complains about valid input. The "Image" help-text is incomplete. In the "Build / Publish Docker Containers" build step, the "Image" field is set to be the tags that are to be applied to the newly-created image. The syntax of these tags can have a variety of format depending on the complexity (see https://docs.docker.com/engine/reference/commandline/tag/ for details). e.g. it can be as simple as "myimage", but it could be "myimage:mytag", or even "myregistry:1234/myimage:mytag". The online-help for this field says that it's Repository name (and optionally a tag) to be applied to the resulting image in case of success. New line separated values. This is not entirely correct - it can also include a registry name (and optionally a port) prefixed to a "/" and then the repository name (and optionally a tag). The web-ui validation code is even more restrictive than the help-text and insists that the only valid option is just a repository name on its own. e.g. if you give an image name of myimage:mytag then it complains: Tag myimage:mytag doesn't match ^([a-z0-9-_.]+)$ (and it has similar complains about myregistry/myimage:mytag and myregistry:1234/myimage:mytag) Note: Despite all the complaints fr
[JIRA] (JENKINS-39104) Add new template build step should do variable substitution
Title: Message Title
pjdarton created an issue
Jenkins / JENKINS-39104
Add new template build step should do variable substitution
Issue Type:
Improvement
Assignee:
magnayn
Components:
docker-plugin
Created:
2016/Oct/19 10:39 AM
Priority:
Minor
Reporter:
pjdarton
The "Add a new template to all docker clouds" build step makes an excellent follow-on build step to the "Build / Publish Docker Containers" build step. e.g. you can create an image tagged as myregistry:1234/myimage:version-$ {BUILD_NUMBER} and you'll get myimage:version-1, myimage:version-2 etc pushed to your registry in subsequent builds. However, if you use the "Add a new template to all docker clouds" build step and specify a "Docker Image" field of "myregistry:1234/myimage:version-${BUILD_NUMBER} " then that's exactly what you'll get - it won't replace $ {BUILD_NUMBER} with the build number. What should happen is that all of the plain-text fields should be subjected to Jenkins' variable substitution so that all text fields can be parameterised.
Add Comment
[JIRA] (JENKINS-39104) Add new template build step should do variable substitution
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-39104
Add new template build step should do variable substitution
Change By:
pjdarton
The "Add a new template to all docker clouds" build step makes an excellent follow-on build step to the "Build / Publish Docker Containers" build step.e.g. you can create an image tagged as myregistry:1234/myimage:version-$ \ {BUILD_NUMBER} and you'll get myimage:version-1, myimage:version-2 etc pushed to your registry in subsequent builds.However, if you use the "Add a new template to all docker clouds" build step and specify a "Docker Image" field of "myregistry:1234/myimage:version-$ \ {BUILD_NUMBER}" then that's *exactly* what you'll get - it won't replace $ \ {BUILD_NUMBER} with the build number.What should happen is that all of the plain-text fields should be subjected to Jenkins' variable substitution so that all text fields can be parameterised.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message bec
[JIRA] (JENKINS-32257) GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes
Title: Message Title rsandell resolved as Fixed Fixed in Version 2.18.0 (released Dec 1 2015) with a configuration option Jenkins / JENKINS-32257 GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes Change By: rsandell Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://g
[JIRA] (JENKINS-32257) GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes
Title: Message Title rsandell edited a comment on JENKINS-32257 Re: GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes Fixed a workaround in Gerrit Trigger Version 2.18.0 (released Dec 1 2015) with a configuration option . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39105) Add new template build step should be able to update template
Title: Message Title pjdarton created an issue Jenkins / JENKINS-39105 Add new template build step should be able to update template Issue Type: Improvement Assignee: magnayn Components: docker-plugin Created: 2016/Oct/19 10:51 AM Priority: Trivial Reporter: pjdarton At present, the "Add a new template to all docker clouds" build step silently skips any cloud which already has a template based on the specified image. What I'd like is the ability to update the template. i.e. have a Jenkins build which first built a new docker image (using the "Build / Publish Docker Containers" build step) and then updates the docker cloud templates to use it. (it would also be nice to be able to be more selective about which clouds the template was applied to...) This would mean that it would be necessary to use something other than "Docker Image" as a means of identifying which template to replace, because a primary use case here is to "stop using myimage:oldversion and use myimage:newversion instead". (and you can't use labels because that's also something one is likely to want to update too). Add Comment
[JIRA] (JENKINS-32569) ATH: CompressingArtifactManager::setup() failures in ParameterizedTrigger tests
Title: Message Title Oleg Nenashev commented on JENKINS-32569 Re: ATH: CompressingArtifactManager::setup() failures in ParameterizedTrigger tests Oliver Gondža says the PR has been closed somehow: https://github.com/jenkinsci/acceptance-test-harness/pull/78#issuecomment-218722800 , The issue does not appear in ATH tests from what I see Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32569) ATH: CompressingArtifactManager::setup() failures in ParameterizedTrigger tests
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-32569 ATH: CompressingArtifactManager::setup() failures in ParameterizedTrigger tests Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38932) Support the ScriptTrigger (via XTrigger) plugin
Title: Message Title James Coleman commented on JENKINS-38932 Re: Support the ScriptTrigger (via XTrigger) plugin I updated to latest version Monday and its working. I can see the Xtrig icon in addition to the regular ones (source control, manual build). The hover over the BuildTriggerBadge icons gives the cause so you can already get that extra info (on which sub-trigger caused the trigger in case of Xtrigger). So, really the info added by BuildTriggerBadge already provides all that you would need. Very useful. Not just pretty! :-D Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38993) Deterministic order of build condition block execution in Declarative
Title: Message Title Andrew Bayer commented on JENKINS-38993 Re: Deterministic order of build condition block execution in Declarative Stephen Connolly Any thoughts on what the order should be? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Daniel Beck commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version It's 2016 and there is still no way to install a plugin at a specific version (inlcuding it's dependencies) from the commandline? As I wrote above, Jenkins update sites have no metadata on obsolete releases, so this isn't quite this easy. Jenkins CLI has a command to install/update a plugin that takes a URL as argument. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36446) GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start
Title: Message Title Kanstantsin Shautsou commented on JENKINS-36446 Re: GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start ALWAYS report exact plugin version on what it happened. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32495) Testinprogress plugin: Wrong icons
Title: Message Title Magnus Brange commented on JENKINS-32495 Re: Testinprogress plugin: Wrong icons This has been fixed in https://github.com/jenkinsci/testInProgress-plugin/pull/14 only needs to be merged. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39066) hudson.util.ArgumentListBuilder quoting incorrectly in procStarter
Title: Message Title Daniel Beck commented on JENKINS-39066 Re: hudson.util.ArgumentListBuilder quoting incorrectly in procStarter The latter, if I didn't have an existing giant to-do list Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32495) Testinprogress plugin: Wrong icons
Title: Message Title Magnus Brange updated JENKINS-32495 Jenkins / JENKINS-32495 Testinprogress plugin: Wrong icons Change By: Magnus Brange Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32495) Testinprogress plugin: Wrong icons
Title: Message Title Magnus Brange started work on JENKINS-32495 Change By: Magnus Brange Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39024) Jenkins REST API xml files are not parseable
Title: Message Title Daniel Beck commented on JENKINS-39024 Re: Jenkins REST API xml files are not parseable Seems like we could just escape any problematic sequences – i.e. go for && rather than ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39106) Unable to use reference repository
Title: Message Title Marcus Sjölin created an issue Jenkins / JENKINS-39106 Unable to use reference repository Issue Type: Bug Assignee: Unassigned Components: bitbucket-plugin Created: 2016/Oct/19 11:58 AM Priority: Critical Reporter: Marcus Sjölin I am unable to clone using the git parameter --reference, which is allowed by Jenkins git-plugin. This is much appreciated in larger code bases. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-31837) More logging information
Title: Message Title Metin Savignano resolved as Fixed Jenkins / JENKINS-31837 More logging information Change By: Metin Savignano Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Heiko Nardmann created an issue Jenkins / JENKINS-39107 expose "Stream Codeline" as an environment variable Issue Type: Improvement Assignee: Unassigned Attachments: Stream_Codeline.png Components: p4-plugin Created: 2016/Oct/19 12:22 PM Priority: Minor Reporter: Heiko Nardmann I retrieve the pipeline script from SCM. See attached screenshot for context. Now it would be helpful to be able to use the value of (at least) "Stream Codeline" inside my pipeline script. As far as I understand this is not possible so far? Add Comment
[JIRA] (JENKINS-23265) TestLink plugin indicates test case as "not run" and TestLink is not updated with build status
Title: Message Title Tushar Likhar commented on JENKINS-23265 Re: TestLink plugin indicates test case as "not run" and TestLink is not updated with build status Same error i am facing, in console output everything is shown as correct but TestLink status is not run. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38993) Deterministic order of build condition block execution in Declarative
Title: Message Title Stephen Connolly commented on JENKINS-38993 Re: Deterministic order of build condition block execution in Declarative OK, this may be somewhat controversial... The only reason for a "success" condition is if that condition runs after "always"... if it were to run before "always" then we could just replace it with steps / stage at the end of the scope that the conditions apply to. Thus, as we are not allowing repeats, we have to start with the most general condition and then proceed to the most specific. Where conditions of the same level of specificity are mutually exclusive, run the defined order should be alphanumeric sort 1. Always - the most generic condition 2. Changed - the second most generic condition, won't match every build, but can potentially match builds of any status 3. The group of mutually exclusive conditions Aborted Failure Success Unstable Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38993) Deterministic order of build condition block execution in Declarative
Title: Message Title Stephen Connolly edited a comment on JENKINS-38993 Re: Deterministic order of build condition block execution in Declarative OK, this may be somewhat controversial...The only reason for a "success" condition is if that condition runs after "always"... if it were to run before "always" then we could just replace it with steps / stage at the end of the scope that the conditions apply to.Thus, as we are not allowing repeats, we have to start with the most general condition and then proceed to the most specific.Where conditions of the same level of specificity are mutually exclusive, run the defined order should be alphanumeric sort (not that the defined order impacts anything as they are all mutually exclusive, so only one will ever run) 1. Always - the most generic condition2. Changed - the second most generic condition, won't match every build, but can potentially match builds of any status3. The group of mutually exclusive conditions* Aborted* Failure* Success* Unstable This also helps with failures in more generic conditions, as the Failure / Aborted conditions will be in the final set Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36446) GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start
Title: Message Title Stephen Connolly commented on JENKINS-36446 Re: GitHub plugin runs Migration prior to EXTENSIONS_AUGMENTED and can cause Jenkins instance to fail to start Kanstantsin Shautsou well the original reporter was blaming the credentials plugin, though the issue is the github plugin... so I do not have the version of the github plugin that was causing issues for them... must be recent enough, as https://github.com/jenkinsci/github-plugin/blob/9b5fba601717c07d13686a61845200e74c3e4884/src/main/java/org/jenkinsci/plugins/github/GitHubPlugin.java#L39 would match the stack trace exactly... I'm willing to bet it was 1.19.0 on that basis Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39098) Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-39098 Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39098) Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone
Title: Message Title Mark Waite commented on JENKINS-39098 Re: Always show errors when key in git path, Git > Repository Url. The tooltip guidelina said must follow exactly as during git clone I don't understand your bug description, and I don't understand the picture you're showing. Please help open source maintainers (like me) by submitting step by step descriptions of the problem you're seeing and what you would like to see. I don't understand your reference to "tooltip guideline" nor why it "must follow exactly as during git clone". What were you trying to do? What was the behavior you observed? What behavior did you expect? What alternatives have you explored and what did you learn from those alternatives? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38966) Rename job: No valid crumb was included in the request
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-38966 Rename job: No valid crumb was included in the request Change By: Ulli Hafner Environment: jenkins 2.19.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38966) Rename job: No valid crumb was included in the request
Title: Message Title Ulli Hafner commented on JENKINS-38966 Re: Rename job: No valid crumb was included in the request Sorry, forgot to update environment: Latest LTS 2.19.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Robert Saric commented on JENKINS-32118 Re: Opening Robot Framework log failed A more universal workaround is described [here](http://stackoverflow.com/a/36996036/451962). To fix this error add below entry to Jenkins configuration file (jenkins.xml): -Dhudson.model.DirectoryBrowserSupport.CSP= and restart Jenkins (with http://(jenkins_url)/safeRestart). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
