[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title ikedam commented on JENKINS-28585 Re: Flexible Publish no longer expands variables in multiconfiguration job Released flexible-publish-0.15.2 fixing this issue. It will be available in a day. Please try that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28585 Flexible Publish no longer expands variables in multiconfiguration job Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28585 Re: Flexible Publish no longer expands variables in multiconfiguration job Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java http://jenkins-ci.org/commit/flexible-publish-plugin/ab0a50453b112f04a0c3b5a0ce68e77aae0ffdf9 Log: [FIXED JENKINS-28585] Skips aggregation processing if no publisher supports aggregation. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28585 Re: Flexible Publish no longer expands variables in multiconfiguration job Code changed in jenkins User: ikedam Path: src/test/java/org/jenkins_ci/plugins/flexible_publish/MatrixAggregationTest.java http://jenkins-ci.org/commit/flexible-publish-plugin/0dc77cfd866e4fc6162c17e8442fe906eea441a7 Log: JENKINS-28585 Added a test to reproduce JENKINS-28585 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish-plugin] (JENKINS-28585) Flexible Publish no longer expands variables in multiconfiguration job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28585 Re: Flexible Publish no longer expands variables in multiconfiguration job Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java src/test/java/org/jenkins_ci/plugins/flexible_publish/MatrixAggregationTest.java http://jenkins-ci.org/commit/flexible-publish-plugin/d487888d9793215ae18a87cae9700a9cff3fa0cc Log: Merge pull request #14 from ikedam/feature/ JENKINS-28585 _ErrorWithNonAggregatable JENKINS-28585 Skips aggregation processing if no publisher supports aggregation. Compare: https://github.com/jenkinsci/flexible-publish-plugin/compare/2419aefa645e...d487888d9793 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28780) P4 Publish Assets - Shelve Change uses questionable logic
Title: Message Title A C created an issue Jenkins / JENKINS-28780 P4 Publish Assets - Shelve Change uses questionable logic Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 06/Jun/15 4:41 AM Environment: Jenkins 1.6.16 P4 1.2.3 Priority: Major Reporter: A C Test case: Freestyle job * configured P4 SCM * Build step: batchfile command to p4 edit a file in the configured workspace * Post build action Perforce: Publish Assets using the same P4 config as the checkout, set to use the Shelve Change option. Ancillary details: P4 config was set to use a Static workspace, and job was configured to use a
[JIRA] [nunit-plugin] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27906 Re: Fail to read NUnit3 output xml Code changed in jenkins User: Bruno P. Kinoshita Path: src/test/java/hudson/plugins/nunit/NUnitReportTransformerTest.java src/test/resources/hudson/plugins/nunit/issue-27906.xml http://jenkins-ci.org/commit/nunit-plugin/0ca5a2ba4231405b3061925002317914f4c6856d Log: JENKINS-27906 Added test case Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-10234) Junit result archiver getting stuck for a long time in concurrent builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-10234 Re: Junit result archiver getting stuck for a long time in concurrent builds Code changed in jenkins User: Martin Bektchiev Path: src/main/java/hudson/plugins/nunit/NUnitPublisher.java http://jenkins-ci.org/commit/nunit-plugin/1e89e0267814d280b7051d7d70d5d2939326b182 Log: Do not wait for checkpoint from previous build Fixes an issue with result archiver getting stuck for a long time in concurrent builds. A similar issue has been fixed in the JUnit Jenkins plugin: https://issues.jenkins-ci.org/browse/JENKINS-10234 https://github.com/jenkinsci/jenkins/commit/90ff9f806fcac1a58f4bd40bfcc4ed5273ff116a Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Kohsuke Kawaguchi reopened an issue
jieryn's PR has been merged, but it's a temporary pain reliever and not a fix. I discussed this in here but my suggestion is to do chmod non-recursively to just touch files & directories managed by RPM. IIUC, this is what Daniel Beck is proposing.
When that change is made, this bug should be marked as fixed.
Until that day, those who are affected by this issue can use JENKINS_INSTALL_SKIP_CHOWN switch to mitigate the pain. The switch should be considered temporary — it will be removed when the proper fix is made.
Jenkins / JENKINS-23273
RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Change By:
Kohsuke Kawaguchi
Resolution:
Fixed
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message becau
[JIRA] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
SCM/JIRA link daemon resolved as Fixed
Jenkins / JENKINS-23273
RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Change By:
SCM/JIRA link daemon
Status:
Open Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Code changed in jenkins User: jieryn Path: rpm/build/SOURCES/jenkins.sysconfig.in rpm/build/SPECS/jenkins.spec http://jenkins-ci.org/commit/packaging/1e4744ef8ff3cf0f16ea03aabf4afe2478a3e32e Log: [FIXED JENKINS-23273] /etc/sysconfig option to skip (off default) long chown
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Code changed in jenkins User: Kohsuke Kawaguchi Path: rpm/build/SOURCES/jenkins.sysconfig.in rpm/build/SPECS/jenkins.spec http://jenkins-ci.org/commit/packaging/58084e56eee77341e580474a5dd1176a2e0148fa Log: Merge pull request #2 from jieryn/
JENKINS-23273
[FIXED JENKINS-23273] /etc/sysconfig option to skip (off default) lon…
Compare: https://github.com/jenkinsci/packaging/compare/dab31b61b6e6...58084e56eee7
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-plugin] (JENKINS-10128) SSH Plugin: NullPointerException when no SSH site is specified in the job configuration
Title: Message Title John Tatum commented on JENKINS-10128 Re: SSH Plugin: NullPointerException when no SSH site is specified in the job configuration https://github.com/jenkinsci/ssh-plugin/pull/13 has been created to address this issue. Pleast test and comment if able. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-merge-request-jenkins] (JENKINS-28779) NoSuchMethodRequest when verifying cron syntax
Title: Message Title recampbell commented on JENKINS-28779 Re: NoSuchMethodRequest when verifying cron syntax I think this is another fallout from this commit here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-merge-request-jenkins] (JENKINS-23194) NoSuchMethod when configuring mergeRequest Builder
Title: Message Title recampbell commented on JENKINS-23194 Re: NoSuchMethod when configuring mergeRequest Builder JENKINS-23194 captures the larger impact, which helps indicate the severity. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-28040) Allow logstash plugin to feed a syslog server
Title: Message Title Felix Langelier commented on JENKINS-28040 Re: Allow logstash plugin to feed a syslog server Just want to let you know that the generated Syslog messages will comply to the CEE format. So, if you have a logging infrastructure based on Elasticsearch this feature will make log parsing way easier with rsyslog using the mmjsonparse and omelasticsearch module. I think it`s a good idea to have it in the Logstash jenking plugin because it's related to ELK. Ref: http://www.rsyslog.com/doc/v8-stable/configuration/modules/omelasticsearch.html http://www.rsyslog.com/doc/mmjsonparse.html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab-merge-request-jenkins] (JENKINS-28779) NoSuchMethodRequest when verifying cron syntax
Title: Message Title recampbell created an issue Jenkins / JENKINS-28779 NoSuchMethodRequest when verifying cron syntax Issue Type: Bug Assignee: Unassigned Components: gitlab-merge-request-jenkins Created: 05/Jun/15 9:03 PM Environment: 1.580 Priority: Critical Reporter: recampbell When configuring either the global configuration page or individual job pages, there will be a error in the _javascript_ console: https:///descriptorByName/org.jenkinsci.plugins.gitlab.GitlabBuildTrigger/checkCron?value=H%2F5%20*%20*%20*%20* : Failed to load resource: the server responded with a status of 500 (Internal Server Error) This causes form submission to break, making this a pretty severe issue. The root cause is: javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at
[JIRA] [rundeck-plugin] (JENKINS-28778) Make delay between polling (for Rundeck job to finish) configurable per job
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-28778 Make delay between polling (for Rundeck job to finish) configurable per job Issue Type: Improvement Assignee: Vincent Behar Components: rundeck-plugin Created: 05/Jun/15 8:51 PM Priority: Minor Reporter: Marcin Zajączkowski Currently the plugin checks if Rundeck job finished every 5 seconds. For short-lasting jobs it can artificially increase the whole build. It would be useful to (optionally) be able to configure a delay for given job. Add Comment
[JIRA] [delivery-pipeline-plugin] (JENKINS-28777) Ability to get SCM changes to display from selected job (not the first)
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-28777 Ability to get SCM changes to display from selected job (not the first) Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 05/Jun/15 8:45 PM Priority: Minor Reporter: Marcin Zajączkowski I like an ability to display SCM changes for the newest pipeline, but in one of my pipelines the first job clones CMS content to make a Git tag. The real SCM changes are contained in the second job which clones the main application(s) sources (and use CMS tag from the previous step to make a build). In that case it would be useful to be able to (optionally) select SCM changes from which job should be used to display it in the pipeline view. Add Comment
[JIRA] [support-core-plugin] (JENKINS-20542) Summarize contents of queue
Title: Message Title Steven Christou closed an issue as Fixed Jenkins / JENKINS-20542 Summarize contents of queue Change By: Steven Christou Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-commons-plugin] (JENKINS-28657) Support creation of named fingerprints in DockerFingerprints
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-28657 Support creation of named fingerprints in DockerFingerprints Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-commons-plugin] (JENKINS-28657) Support creation of named fingerprints in DockerFingerprints
Title: Message Title Oleg Nenashev started work on JENKINS-28657 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-commons-plugin] (JENKINS-28776) Show docker icons in build actions
Title: Message Title Oleg Nenashev started work on JENKINS-28776 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-commons-plugin] (JENKINS-28776) Show docker icons in build actions
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28776 Show docker icons in build actions Issue Type: Improvement Assignee: Oleg Nenashev Components: docker-commons-plugin Created: 05/Jun/15 8:27 PM Priority: Minor Reporter: Oleg Nenashev These icons can be also shared across all other Docker plugins when we fix it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [android-emulator-plugin] (JENKINS-28775) Seeing two devices with "adb devices" after upgrade
Title: Message Title Yenchi Lin commented on JENKINS-28775 Re: Seeing two devices with "adb devices" after upgrade Lowering to minor as I found a workaround with newer spoon release that supports running tests only on specific device serial Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-28775) Seeing two devices with "adb devices" after upgrade
Title: Message Title Yenchi Lin updated an issue Jenkins / JENKINS-28775 Seeing two devices with "adb devices" after upgrade Change By: Yenchi Lin Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-28634) The vSphere Cloud Plugin does not work with VMware vSphere Essentials
Title: Message Title Lisa Sittler closed an issue as Fixed Jenkins / JENKINS-28634 The vSphere Cloud Plugin does not work with VMware vSphere Essentials Change By: Lisa Sittler Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25648) P4_CHANGELIST variable points to unshelved cl , not synced CL
Title: Message Title A C commented on JENKINS-25648 Re: P4_CHANGELIST variable points to unshelved cl , not synced CL Yes, another task for shelving / unshelving would be a preferable solution. This would make managing build artifacts via shelves much simpler in complex build scenarios (eg, artifact aggregation from upstream builds). Currently I must perform such management separate from the plugin with command-line p4 steps. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-28775) Seeing two devices with "adb devices" after upgrade
Title: Message Title Yenchi Lin created an issue Jenkins / JENKINS-28775 Seeing two devices with "adb devices" after upgrade Issue Type: New Feature Assignee: Christopher Orr Components: android-emulator-plugin Created: 05/Jun/15 5:54 PM Environment: Jenkins 1.580.3.4 running on Cloudbees with Android Emulator Plugin 2.13.1 Priority: Major Reporter: Yenchi Lin With plugin 2.13.1 we now see two devices pointing to the same emulator instance which caused our test runner (spoon) to think there are two distinct devices and fail no matter what. Here is the console output: ===begin copy & paste === [android] Using Android SDK: /opt/android/android-sdk-linux [android] Creating Android AVD: /scratch/jenkins/workspace/Android Integration (DEV)/label/android/node_index/1/.android/avd/hudson_en-US_240_WVGA_android-16_armeabi-v7a_1.avd [android] /opt/android/android-sdk-linux/tools/android create avd -f -a -c 64M -s WVGA800 -n hudson_en-US_240_WVGA_android-16_armeabi-v7a_1 -t android-16 --abi armeabi-v7a $ /opt/android/android-sdk-linux/platform-tools/adb start-server daemon not running. starting it now on port 5938 *
[JIRA] [android-emulator-plugin] (JENKINS-28775) Seeing two devices with "adb devices" after upgrade
Title: Message Title Yenchi Lin updated an issue Jenkins / JENKINS-28775 Seeing two devices with "adb devices" after upgrade Change By: Yenchi Lin Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28752) DockerTraceabiltyReport marks imageId as nonNull but for certain events its not always possible to obtain it.
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-28752 DockerTraceabiltyReport marks imageId as nonNull but for certain events its not always possible to obtain it. Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28752) DockerTraceabiltyReport marks imageId as nonNull but for certain events its not always possible to obtain it.
Title: Message Title Oleg Nenashev started work on JENKINS-28752 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28760) P4 Plugin does not respect line endings for template workspaces
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28760 Re: P4 Plugin does not respect line endings for template workspaces Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/workspace/TemplateWorkspaceImpl.java http://jenkins-ci.org/commit/p4-plugin/eb00de82a1322518911301602cf287a8179fe4cc Log: Merge pull request #15 from tanium/line-endings Fix JENKINS-28760: Set line endings explicitly for template workspaces Compare: https://github.com/jenkinsci/p4-plugin/compare/edad6bc3223e...eb00de82a132 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28760) P4 Plugin does not respect line endings for template workspaces
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28760 Re: P4 Plugin does not respect line endings for template workspaces Code changed in jenkins User: Matt Hauck Path: src/main/java/org/jenkinsci/plugins/p4/workspace/TemplateWorkspaceImpl.java http://jenkins-ci.org/commit/p4-plugin/1924028b673aff678fb0e906de82af975e7be04f Log: Fix JENKINS-28760: Set line endings explicitly for template workspaces Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-28301) Update P4 Documentation regarding Pin parameter
Title: Message Title Paul Allen closed an issue as Fixed Documents updated... https://github.com/jenkinsci/p4-plugin#building-at-a-change Jenkins / JENKINS-28301 Update P4 Documentation regarding Pin parameter Change By: Paul Allen Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Jeff Dege commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Same - encountered the issue with 2.5, rolled back to 2.4.5 and it was gone. (Jenkins 1.612) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-28774) Many hudson.plugins.fitnesse.FitnesseResults objects remain in memory
Title: Message Title Kirill Popov commented on JENKINS-28774 Re: Many hudson.plugins.fitnesse.FitnesseResults objects remain in memory Not sure if it's related or not but just after creation of new job containing "Publish fitnesse results report" post-build step, the following message appears in console: Jun 5, 2015 3:38:35 PM hudson.model.Descriptor verifyNewInstance WARNING: Father of hudson.plugins.fitnesse.FitnesseResultsRecorder@358e3609 and its getDescriptor() points to two different instances. Probably malplaced @Extension. See http://hudson.361315.n4.nabble.com/Help-Hint-needed-Post-build-action-doesn-t-stay-activated-td2308833.html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28745) Again - Animated ball in job's build history widget won't open Console Output
Title: Message Title Daniel Beck resolved as Duplicate Duplicates JENKINS-28704 . Jenkins / JENKINS-28745 Again - Animated ball in job's build history widget won't open Console Output Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-28774) Many hudson.plugins.fitnesse.FitnesseResults objects remain in memory
Title: Message Title Kirill Popov updated an issue Jenkins / JENKINS-28774 Many hudson.plugins.fitnesse.FitnesseResults objects remain in memory Change By: Kirill Popov Environment: Linux amd64 Jenkins ver. 1.609.1 running as standalone Fitnesse plugin: 1.13 (installed through Jenkins update center) JDK: jdk1.6.0_29 Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-28774) Many hudson.plugins.fitnesse.FitnesseResults objects remain in memory
Title: Message Title Kirill Popov created an issue Jenkins / JENKINS-28774 Many hudson.plugins.fitnesse.FitnesseResults objects remain in memory Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 05/Jun/15 3:31 PM Environment: Jenkins ver. 1.609.1 Fitnesse plugin: 1.13 JDK: jdk1.6.0_29 Labels: fitnesse heap memory-leak Priority: Minor Reporter: Kirill Popov It seems that having "Publish fitnesse results report" post-build step in a job makes Fitnesse plugin produce huge amounts of hudson.plugins.fitnesse.FitnesseResults objects which have links and therefore are not being collected by GC. After an empty Jenkins server startup there are no such objects: $ ./jmap -histo 4324 | sort -n -k 2 -r | grep -E 'hudson.plugins.fitnesse.FitnesseResults$' $
[JIRA] [core] (JENKINS-28278) Environment variables "stuck" on windows slave
Title: Message Title Daniel Beck resolved as Duplicate Appears to duplicate JENKINS-27739 for which I've proposed a fix. Jenkins / JENKINS-28278 Environment variables "stuck" on windows slave Change By: Daniel Beck Status: Open Resolved Assignee: Kohsuke Kawaguchi Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parallel-test-executor-plugin] (JENKINS-28285) Not possible for the test job to copy artifacts from the job calling the test job
Title: Message Title Daniel Beck resolved as Not A Defect Questions on how to use Jenkins and its plugins should be asked on the jenkinsci-users mailing list. Jenkins / JENKINS-28285 Not possible for the test job to copy artifacts from the job calling the test job Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [depgraph-view-plugin] (JENKINS-28773) Extension points not working
Title: Message Title
omer schleifer created an issue
Jenkins / JENKINS-28773
Extension points not working
Issue Type:
Bug
Assignee:
wolfs
Components:
depgraph-view-plugin
Created:
05/Jun/15 2:33 PM
Priority:
Major
Reporter:
omer schleifer
This plugin intends to support multiple EdgeProvider implementations using Guice MultiBinder. However it is impossible to add a new binding in another plugin as suggested. The reason is that while you can use the same setBinder to add multiple bindings, you can not add another setBinder. writing another module with code like this:
@Override protected void configure() { LOG.info("NetDependModule configure was called. " + Thread.currentThread().getStackTrace()); Multibinder edgeProviderMultibinder = Multibinder.newSetbBBinder(binder(), EdgeProvider.class); edgeProviderMultibinder.addBinding().to(EdgeProviderImpl.class); }
]
Will result in this error: A binding to java.util.Set was already configured at hudson.plugins.depgraph_view.model.graph.DependencyGraphModule.configure(DependencyGraphModule.java:36). at com.picscout.netdepend.netdepend_graph.NetDependModule.configure(NetDependModule.java:48)
Need to somehow expose the orignal set binding , or use an extension point all() to get all instances of providers.
(B.T.W , not sure it is relevant but the code in GitHub doesn't compile, missing Messages.java class , maybe other issues as well)
[JIRA] [test1] (TEST-47) Run API test sets on HP ALM from Jenkins
Title: Message Title Mahdad Hosseini Kamal created an issue test / TEST-47 Run API test sets on HP ALM from Jenkins Issue Type: Patch Assignee: Kohsuke Kawaguchi Components: test1, test2 Created: 05/Jun/15 2:23 PM Labels: plugin git build configuration Priority: Critical Reporter: Mahdad Hosseini Kamal Dear all, I have a set of API tests (REST tests) on HP ALM which I can run them from ALM without any problem. However, when I buld them through Jenkins I get the following error: Cannot get RemoteAgent's ClassID for test type However, I can perfectly run GUI tests on ALM from Jenkins and the connectivity patch between ALM and UFT is installed. I would appreciate your help regarding this issue. Thanks Mahdad
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Daniel Beck commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 Steven Williams Interesting. https://github.com/jenkinsci/subversion-plugin/commit/966d051476cfbe880c6a820570ab370b3ec6da4d#commitcomment-11542216 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openstack-cloud-plugin] (JENKINS-28772) Optional.get() cannot be called on an absent value - while provisioning the node
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-28772 Optional.get() cannot be called on an absent value - while provisioning the node Issue Type: Bug Assignee: Marat Mavlyutov Attachments: config.xml Components: openstack-cloud-plugin Created: 05/Jun/15 2:09 PM Priority: Major Reporter: Oliver Gondža I am getting the exception while provisioning node using openstack cloud plugin 1.7. javax.servlet.ServletException: java.lang.IllegalStateException: Optional.get() cannot be called on an absent value at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) a
[JIRA] [configurationslicing-plugin] (JENKINS-28771) Slicing UI available for regular users, but only visible in 'Manage Jenkins'
Title: Message Title Nathan Neulinger created an issue Jenkins / JENKINS-28771 Slicing UI available for regular users, but only visible in 'Manage Jenkins' Issue Type: Bug Assignee: mdonohue Components: configurationslicing-plugin Created: 05/Jun/15 1:55 PM Priority: Minor Reporter: Nathan Neulinger A regular user can go to the configuration slicing UI via direct URL, but if they don't have access to 'Manage Jenkins' they can't see the link to it. Seems like this is either an oversight (if they SHOULD have that ability), or a security issue (if only admins are supposed to be able to use the plugin). If it's intended to be available to users that can edit the jobs and not just admins - consider making the config slicing link available in the main jenkins menu so that others can see it. If not, please fix the security/access checks. Even better - integrate w/ matrix auth plugin as it's own specific permission. Add Comment
[JIRA] [docker-build-publish-plugin] (JENKINS-28770) Support for promoted build plugin to promote images
Title: Message Title Andy Smith created an issue Jenkins / JENKINS-28770 Support for promoted build plugin to promote images Issue Type: New Feature Assignee: Michael Neale Components: docker-build-publish-plugin Created: 05/Jun/15 1:47 PM Priority: Major Reporter: Andy Smith We're trying to use the Docker Build and Publish plugin in conjunction with the Promoted builds plugin. We continuously integrate and build an image for each commit. We then want the option to "promote" an image for release. This will involve tagging the release with our release version. The git plugin provide an environment variable for this (PROMOTED_GIT_COMMIT), it would be incredibly useful for us if this plugin provided the image id (PROMOTED_DOCKER_IMAGEID). I'm not quite sure how this would be done but I did find the part of the promoted builds plugin that appears to take PROMOTED_GIT_COMMIT: https://github.com/jenkinsci/promoted-builds-plugin/blob/726f7a0966f54c796e6e36aca8be58f1833a15c3/src/main/java/hudson/plugins/promoted_builds/Promotion.java#L119
[JIRA] [maven-plugin] (JENKINS-28294) "JDK 5 not supported with Maven" error with JDK 6
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-28294 "JDK 5 not supported with Maven" error with JDK 6 Again, the issue is Maven Plugin's tight integration of Jenkins and Maven. Jenkins' remoting model requires that all slaves run in compatible JRE's, and this appears to extend to Maven Project plugin builds. While the error message appears to be outdated now, https://github.com/jenkinsci/maven-plugin/blob/0963b19fef1cb3fbc9da2fa10649c9970b12f4a7/src/main/java/hudson/maven/AbstractMavenProcessFactory.java#L289 the basic requirement is there by design. If you want to build projects using any JDK just like on the command line, use Freestyle projects. You'll lose the tight integration, but that's the cause of this problem anyway. Keeping this open for the outdated message, the rest is by design. If you object to the automatic JDK upgrade implemented as a fallback, please file an improvement request that this be configurable or removed (whichever you prefer). Change By: Daniel Beck Priority: Major Trivial Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You receive
[JIRA] [performance-plugin] (JENKINS-28426) JMeterCSV always reports 100% 0f errors
Title: Message Title harrish thangavel edited a comment on JENKINS-28426 Re: JMeterCSV always reports 100% 0f errors Am also facing the same problem and i dont have field name in jtl file(as configured). Can yuu you tell me as how to solve this. ?completely blocked on this.Any help regarding this will be helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28368) Error "JDK 5 not supported to run Maven" while running Java 6
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-28368 Error "JDK 5 not supported to run Maven" while running Java 6 Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28426) JMeterCSV always reports 100% 0f errors
Title: Message Title harrish thangavel commented on JENKINS-28426 Re: JMeterCSV always reports 100% 0f errors Am also facing the same problem and i dont have field name in jtl file(as configured). Can yuu tell me as how to solve this. ? completely blocked on this.Any help regarding this will be helpful. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28260) Java String Index Out of Range
Title: Message Title Daniel Beck commented on JENKINS-28260 Re: Java String Index Out of Range Mark Waite We only have the wiki page on issue tracking, but it's mostly descriptive based on what I've seen in the past. In core, we usually resolve duplicate issues using the Resolution Duplicate by convention/habit. I think one of the advantages is that all further actions/comments/votes/watches can be centralized that way. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21930) Jobs fail due to "node went offline during the build"
Title: Message Title Damien Coraboeuf commented on JENKINS-21930 Re: Jobs fail due to "node went offline during the build" After analysis of the stack trace and of the code of 1.584, it happens after the run is complete, when the AbstractBuildRunner attempts to write the annotated log. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28769) enable codemirror on workflow DSL
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-28769 enable codemirror on workflow DSL Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 05/Jun/15 1:07 PM Priority: Minor Reporter: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups
[JIRA] [git-plugin] (JENKINS-28260) Java String Index Out of Range
Title: Message Title Mark Waite commented on JENKINS-28260 Re: Java String Index Out of Range Daniel Beck it is definitely a duplicate and the duplicate is linked in the bug report. Is the general bug reporting workflow that duplicates are resolved, even when the bug which they duplicate is not yet resolved? I've been assuming (without any basis in anything I read) that duplicate bugs stayed open until the bug they duplicate was resolved. If that's not the case,then there may be several git and git client bugs which should be resolved as duplicates. Is there a general page which I should be reading about the bug workflow and bug handling policies? I'd like to be consistent with the rest of the community, or at least with the "standard way" of doing things if there is a standard way. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-28768) docker plugin can not find template
Title: Message Title Oleg Fayans created an issue Jenkins / JENKINS-28768 docker plugin can not find template Issue Type: Bug Assignee: Kanstantsin Shautsou Attachments: jenkins.png Components: docker-plugin Created: 05/Jun/15 12:40 PM Labels: plugin Priority: Major Reporter: Oleg Fayans I've configured jenkins to use docker plugin, as described here. I configured the job that would build rpms on a docker container. and restricted the execution to the configured docker image However, when I start the job, it hangs forever waiting for the available executor and in the logs I see: INFO: Will provision "f22_builder" for: f22_builder Jun 05, 2015 2:23:36 PM com.nirima.jenkins.plugins.docker.DockerCloud provision WARNING: Bad template f22_builder: null. Trying next template... which means, it does not recognize the image as a proper template. This issue have emerged in the docker-plugin version 0.9. In earlier
[JIRA] [core] (JENKINS-21930) Jobs fail due to "node went offline during the build"
Title: Message Title Damien Coraboeuf commented on JENKINS-21930 Re: Jobs fail due to "node went offline during the build" It seems the code mentioned above does not exist any longer. Might it be that it has been solved for another ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21930) Jobs fail due to "node went offline during the build"
Title: Message Title Damien Coraboeuf commented on JENKINS-21930 Re: Jobs fail due to "node went offline during the build" Hi, We experiment this issue on Jenkins 1.584. The scenario is the following: we have a job which puts a node offline in order to run some maintenance on it, using the computer.setTemporarilyOffline(true, new OfflineCause.UserCause(User.current(), "Putting the slave offline for maintenance purpose")) code some jobs are still running on this node some of those still running jobs are then failing because of the error mentioned in this issue - not always, but time to time Do you know if a workaround or solution has been found for this problem? Thanks, Damien. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metrics-plugin] (JENKINS-28620) NPE on the startup after updating to metrics 3.0.10 plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28620 Re: NPE on the startup after updating to metrics 3.0.10 plugin Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/metrics/util/AutoSamplingHistogram.java http://jenkins-ci.org/commit/metrics-plugin/dd09a076b96362e5347ca759cd95fdbcef3ed98e Log: Merge pull request #9 from jenkinsci/better-safety [FIXED JENKINS-28620] Add better safety to the AutoSamplingHistogram Compare: https://github.com/jenkinsci/metrics-plugin/compare/f2d3bef26f9e...dd09a076b963 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Daniel Beck started work on JENKINS-27739 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-perf-plugin] (JENKINS-28767) Cucumber Performance Reporting Not generating project performance graph
Title: Message Title Arish Arbab created an issue Jenkins / JENKINS-28767 Cucumber Performance Reporting Not generating project performance graph Issue Type: Bug Assignee: Unassigned Attachments: Cucumber-perf-report-jenkins-conf.JPG, Cucumber-perf-report-jenkins-report.JPG Components: cucumber-perf-plugin Created: 05/Jun/15 11:24 AM Environment: Jenkins 1.609 Priority: Critical Reporter: Arish Arbab I have added cucumber-perf-plugin in the jenkins. After the successfull execution of my build when I open "Cucumber Project Performance Report" then it shows the report without the graph. Do we need to configure some additional fields ?
[JIRA] [metrics-plugin] (JENKINS-28620) NPE on the startup after updating to metrics 3.0.10 plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28620 Re: NPE on the startup after updating to metrics 3.0.10 plugin Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/metrics/util/AutoSamplingHistogram.java http://jenkins-ci.org/commit/metrics-plugin/453b1f952ce4054c65a308481d2e8e4a1eabf6f1 Log: [FIXED JENKINS-28620] Add better safety to the AutoSamplingHistogram Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metrics-plugin] (JENKINS-28620) NPE on the startup after updating to metrics 3.0.10 plugin
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28620 NPE on the startup after updating to metrics 3.0.10 plugin Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [elasticbox-plugin] (JENKINS-28766) StringIndexOutOfBoundsException
Title: Message Title Andrea Wong updated an issue Jenkins / JENKINS-28766 StringIndexOutOfBoundsException Change By: Andrea Wong Summary: StringIndexOutOfBoundsException Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [elasticbox-plugin] (JENKINS-28765) Jenkins fails to start after upgraded ElasticBox CI to 0.9.12
Title: Message Title Andrea Wong updated an issue Jenkins / JENKINS-28765 Jenkins fails to start after upgraded ElasticBox CI to 0.9.12 Change By: Andrea Wong Environment: Tested on Jenkins 1.609 and 1.616CentOS 6.6java version " 1. 8 7 . 0" 0_75 Elasticbox CI version o 0.9.12, 0.9.11, 0.9.10.2, 0.9.10.1 and 0.9.10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [elasticbox-plugin] (JENKINS-28766) StringIndexOutOfBoundsException
Title: Message Title Andrea Wong created an issue Jenkins / JENKINS-28766 StringIndexOutOfBoundsException Issue Type: Bug Assignee: Unassigned Components: elasticbox-plugin Created: 05/Jun/15 11:12 AM Environment: CentOS 6.6 Jenkins v 1.609 and 1.616 Elasticbox CI 0.9.9 Java 1.7.0_75 Priority: Major Reporter: Andrea Wong When trying to build the instance through Jenkins, it keeps failing with the following messages. I've tried creating the instance manually on ElasticBox with the same box template and that created without any problem. [ElasticBox] - Executing Deploy Box build step [ElasticBox] - Deploying box null ERROR: Build step failed with exception java.lang.StringIndexOutOfBoundsException: String index out of range: -31 at java.lang.String.substring(String.java:1911) at com.elasticbox.Client.getSchemaVersion(Client.java:107) at com.elasticbox.Client.deploy(Client.java:640) at com.elasticbox.jenkins.builders.DeployBox.deploy(DeployBox.java:174) at com.elasticbox.jenkins.builders.DeployBox.doPerform(DeployBox.java:290) at com.elasticbox.jenkins.builders.DeployBox.perform(DeployBox.java:330) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.Abs
[JIRA] [elasticbox-plugin] (JENKINS-28765) Jenkins fails to start after upgraded ElasticBox CI to 0.9.12
Title: Message Title Andrea Wong created an issue Jenkins / JENKINS-28765 Jenkins fails to start after upgraded ElasticBox CI to 0.9.12 Issue Type: Bug Assignee: Unassigned Components: elasticbox-plugin Created: 05/Jun/15 11:04 AM Environment: Tested on Jenkins 1.609 and 1.616 CentOS 6.6 java version "1.8.0" Elasticbox CI version o 0.9.12, 0.9.11, 0.9.10.2, 0.9.10.1 and 0.9.10 Labels: plugin jenkins Priority: Major Reporter: Andrea Wong After upgraded the plugin to 0.9.12, Jenkins failed to start. Tried 0.9.11, 0.9.10.2, 0.9.10.1 and 0.9.10 and they all failed with the same following messages. hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.I
[JIRA] [active-choices-plugin] (JENKINS-28764) Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Title: Message Title
Johan Haleby created an issue
Jenkins / JENKINS-28764
Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
active-choices-plugin
Created:
05/Jun/15 10:36 AM
Environment:
Version 1.0 of Active Choices plugin
Priority:
Major
Reporter:
Johan Haleby
I'm using a "Active Choices Parameter" on a parameterized build (by selecting "This build is parameterized" in the job settings). If I've defined a global environment variables/properties or password in Jenkins (defined under "Manage Jenkins" -> "Configure System" -> "Global Properties" and "Manage Jenkins" -> "Configure System" -> "Global Passwords") I cannot seem to use these (for example $ {MY_ENV_NAME}
) as an input parameter to Scriptler scripts. This means that I have to duplicate my global environment variable value when used together with the active choice plugin which is not optimal. The passwords are also visible in clear text when configuring the project.
[JIRA] [dynamicparameter-plugin] (JENKINS-25748) Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Title: Message Title Johan Haleby commented on JENKINS-25748 Re: Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts Ioannis Moutsatsos Seems promising but I don't get this to work in Active Choices plugin either. I'll add the same issue on it's issue tracker. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials-plugin] (JENKINS-25412) Update JSch to 0.1.49
Title: Message Title Dennis Philpot commented on JENKINS-25412 Re: Update JSch to 0.1.49 Hi, i would appriciate an update too! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Title: Message Title Nick Brown edited a comment on JENKINS-21785 Re: Check for changes in folders linked via svn:externals fails due to missing credentials Added Updated to latest of everything yesterday (Jenkins 1.616 and SVN 2.5), added additional credentials and now have polling without errors however has . However I have a strange side effect when using relative external paths and polling a branch . I have a job that works fine on trunk including with externals but when I replicate that job and tweak the URLs to a branch the external polling still reports it is comparing the revisions from trunk even though the externals are defined with relative paths '../../../etc.' When the job runs it of course does the correct thing getting the relative externals from the branch but the polling log shows it is looking at them in trunk. Any ideas?Also I still can't use 'Prepare an environment for the run' to define 'Properties Content' variables that can then be used in the module URLs for polling. They do work fine when the job runs but polling fails and results in the job triggered every cycle. Last time I tried, if I use job parameters rather than variables defined as I mentioned they do work... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Title: Message Title Nick Brown edited a comment on JENKINS-21785 Re: Check for changes in folders linked via svn:externals fails due to missing credentials Added additional credentials and now have polling without errors however has a strange side effect. I have a job that works fine on trunk including with externals but when I replicate that job and tweak the URLs to a branch the external polling still reports it is comparing the revisions from trunk even though the externals are defined with relative paths '../../../etc.' When the job runs it of course does the correct thing getting the relative externals from the branch but the polling log shows it is looking at them in trunk. Any ideas?Also I still can't use 'Prepare an environment for the run' to define 'Properties Content' variables that can then be used in the module URLs for polling. They do work fine when the job runs but polling errors fails and results in the job triggered every cycle. Last time I tried if I use job parameters rather than variables defined as I mentioned they do work... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Title: Message Title Nick Brown edited a comment on JENKINS-21785 Re: Check for changes in folders linked via svn:externals fails due to missing credentials Added additional credentials and now have polling without errors however has a strange side effect. I have a job that works fine on trunk including with externals but when I replicate that job and tweak the URLs to a branch the external polling still reports it is comparing the revisions from trunk even though the externals are defined with relative paths '../../../etc.' When the job runs it of course does the correct thing getting the relative externals from the branch but the polling log shows it is looking at them in trunk. Any ideas?Also I still can't use 'Prepare an environment for the run' to define 'Properties Content' variables that can then be used in the module URLs for polling. They do work fine when the job runs but polling fails and results in the job triggered every cycle. Last time I tried , if I use job parameters rather than variables defined as I mentioned they do work... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28704) [Regression] Ball on build in progress does not open console
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28704 [Regression] Ball on build in progress does not open console Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28704) [Regression] Ball on build in progress does not open console
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28704 Re: [Regression] Ball on build in progress does not open console Code changed in jenkins User: Daniel Beck Path: changelog.html war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/9b3039295edb69bd90c74621b367cb1bbf6ad25f Log: Merge pull request #1727 from thomassuckow/feature/ JENKINS-28704 [FIXED JENKINS-28704] Regression for build-history link not opening console Compare: https://github.com/jenkinsci/jenkins/compare/aa0d84a19a30...9b3039295edb Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28704) [Regression] Ball on build in progress does not open console
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28704 Re: [Regression] Ball on build in progress does not open console Code changed in jenkins User: Thomas Suckow Path: changelog.html war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/2522ffcb7da066cf52445c3c3a9eedcc0d55fcc2 Log: [FIXED JENKINS-28704] Regression for build-history link not opening console Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28206) Build selector "Downstream build of" should be usable as parameter or source filter
Title: Message Title Tom Ghyselinck assigned an issue to ikedam Hi ikedam, Automatic assignment did not seem to work. You helped us a lot last time with the initial implementation of the "Downstream build of". I don't know if you can help us out again. It's a very important issue for us since every update of the Copy Artifact Plugin takes more than one day from our time to rebuild all base Jobs, used by other packaging Jobs. Thank you very much in advance! Jenkins / JENKINS-28206 Build selector "Downstream build of" should be usable as parameter or source filter Change By: Tom Ghyselinck Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Title: Message Title Nick Brown commented on JENKINS-21785 Re: Check for changes in folders linked via svn:externals fails due to missing credentials Added additional credentials and now have polling without errors however has a strange side effect. I have a job that works fine on trunk including with externals but when I replicate that job and tweak the URLs to a branch the external polling still reports it is comparing the revisions from trunk even though the externals are defined with relative paths '../../../etc.' When the job runs it of course does the correct thing getting the relative externals from the branch but the polling log shows it is looking at them in trunk. Any ideas? Also I still can't use 'Prepare an environment for the run' to define 'Properties Content' variables that can then be used in the module URLs for polling. They do work fine when the job runs but polling errors and results in the job triggered every cycle. Last time I tried if I use job parameters rather than variables defined as I mentioned they do work... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
Title: Message Title Andrei Costescu commented on JENKINS-26303 Re: Not compatible with Subversion plugin 2.5 Should I reopen the issue? As far as I understand the configuration I tried should have worked (contains the fix) right? (I see all linked duplicate cases are closed now as well) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-28482) Stack trace in jelly when trying to view all
Title: Message Title hcguersoy commented on JENKINS-28482 Re: Stack trace in jelly when trying to view all Hi, we observed this issue after upgrading jenkins to LTS Version 1.609.1 and the plugin to 1.4.7. Downgrading the plugin to 1.4.5 helped (1.4.6 is broken, too). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-28763) NullPointerException in AdvancedQueueSorter ItemInfo
Title: Message Title Tom Ghyselinck created an issue Jenkins / JENKINS-28763 NullPointerException in AdvancedQueueSorter ItemInfo Issue Type: Bug Assignee: Magnus Sandberg Components: prioritysorter-plugin Created: 05/Jun/15 9:31 AM Environment: Jenkins 1.609.1 LTS Priority Sorter Plugin 3.0 Labels: queue Priority: Blocker Reporter: Tom Ghyselinck Hi, We have a new issue with the PrioritySorter Plugin. Our Jenkins server seems to get locked at some point in time. Many Jobs are in starvation, waiting for nodes with certain labels/label combinations. (i.e. Waiting for next available executor on ...) The log shows a lot of these entries: Jun 05, 2015 11:16:07 AM SEVERE hudson.triggers.SafeTimerTask run Timer task hudson.model.Queue$MaintainTask@7f953205 failed java.lang.NullPointer
[JIRA] [gerrit-trigger-plugin] (JENKINS-27741) Jenkins fails to report gerrit notifications spontaneously and on restart.
Title: Message Title rsandell commented on JENKINS-27741 Re: Jenkins fails to report gerrit notifications spontaneously and on restart. The log you provided indicates that no jobs where triggered, and if no jobs are triggered then there is nothing to report to Gerrit. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22890) Jobs Failing Warning: this build has no associated authentication
Title: Message Title Daniel Beck commented on JENKINS-22890 Re: Jobs Failing Warning: this build has no associated authentication This should not affect success of the build. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [violations-plugin] (JENKINS-28762) violations plugin breaks jobs GUI and fail builds those configured with "compiler warning"
Title: Message Title hiteswar kumar created an issue Jenkins / JENKINS-28762 violations plugin breaks jobs GUI and fail builds those configured with "compiler warning" Issue Type: Bug Assignee: peterkittreilly Attachments: Stacktrace-brokenJobsGUIDueToViolationsPlugin.txt, Stacktrace-failedBuildDueToViolationsPlugin.txt Components: violations-plugin, warnings-plugin Created: 05/Jun/15 8:40 AM Environment: Jenkins ver.- LTS 1.554.2 Priority: Major Reporter: hiteswar kumar [ISSUE] After installing of violation plugins 0.7.11, it had started broken GUI of jobs and and failing builds of jobs those having enabled warning plugin (4.42). [StackTrace] stacktrace attached for reference: Stacktrace-failedBuildDueToViolationsPlugin.txt Stacktrace-brokenJobsGUIDueToViolationsPlugin.txt
[JIRA] [subversion-plugin] (JENKINS-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title Oliver Gondža resolved as Duplicate Jenkins / JENKINS-27079 ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState Change By: Oliver Gondža Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-28748) git plugin submodule init fail on large submodule
Title: Message Title Florent Le Saout commented on JENKINS-28748 Re: git plugin submodule init fail on large submodule In fact we use kerberos ticket to authenticate with the server. To be honest I'm not very familiar with that, but basically I do get a ticket before doing clone or submodule update and then it's transparent. But I guess at some point this ticket need to be verified by the server to grant the access. So I'm not sure that we can do the same with git protocol, but maybe. The problem is anyway to convince IT to do so, and specially since there is other project on this server and they never complained about that... I mentioned the other ticket (9168) since maybe we have common behaviour with --progress option transparently done in command line and not in the plugin for submodule init ? Basically I think I will have to live with https server... So I have to find something to make it work properly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-26205) Throttle matrix project doesn't work with label
Title: Message Title krizleebear updated an issue Jenkins / JENKINS-26205 Throttle matrix project doesn't work with label configuration file reproducing the problem. you'll need to create some nodes with given labels. see my comment on that. Change By: krizleebear Attachment: config_throttle_concurrent_builds.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-26205) Throttle matrix project doesn't work with label
Title: Message Title krizleebear commented on JENKINS-26205 Re: Throttle matrix project doesn't work with label I see the same issue at our installation. When starting a matrix configuration job, all configurations will be started immediately, even if I specify Maximum Total Concurrent Builds = 1 Maximum Concurrent Builds Per Node = 1 I made sure I checked Throttle Matrix configuration builds = TRUE Hint: We also use label names instead of host names to select our slave nodes. Reproducing the problem: I provided a simple configuration XML that reproduces this error. In order to get it going, you'll need to create slave nodes with the labels market_CHINA market_EU market_JAPAN market_NAR market_ROW market_TW Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [maven-plugin] (JENKINS-28761) Add maven site link when a workflow job produces a maven site
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-28761 Add maven site link when a workflow job produces a maven site Issue Type: New Feature Assignee: Unassigned Attachments: Screen Shot 2015-06-04 at 16.40.40.png Components: maven-plugin Created: 05/Jun/15 7:55 AM Environment: Jenkins 1.580.13.1 Workflow 1.4 Labels: workflow Priority: Minor Reporter: Nigel Harniman This may be best delivered via a new publisher plugin**
