[JIRA] (JENKINS-35096) Add support for Jenkins Pipeline to the cppcheck-plugin
Title: Message Title Michael Doubez commented on JENKINS-35096 Re: Add support for Jenkins Pipeline to the cppcheck-plugin Fixed: https://github.com/jenkinsci/cppcheck-plugin/pull/39 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Johnson Qu resolved as Fixed Sorry that it's caused by Ngnix conf before Dependency-Track docker. I updated the size limited, so it resolved the issue. Thanks anyway. Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Johnson Qu Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@
[JIRA] (JENKINS-45817) Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable
Title: Message Title Nicolae Pascu assigned an issue to Nicolae Pascu Jenkins / JENKINS-45817 Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable Change By: Nicolae Pascu Assignee: Nicolae Pascu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Johnson Qu reopened an issue Thanks Steve. I upgraded the plugin version to 1.3.2.1, but now I encountered another issue as below. [DependencyTrack] Publishing artifact to Dependency-Track [DependencyTrack] Could not connect to Dependency-Track. Received response code: 413 Request Entity Too Large Build step 'Publish results to Dependency-Track' changed build result to FAILURE Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Johnson Qu Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
Title: Message Title
Ted commented on JENKINS-50993
Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled
I think it is related to state view caching. the ID.log is created on disk and can be viewed by "pipeline steps" (flowGraphTable) -> Select step -> Select Log The stage view log only works if 1) rename the job to another folder using the same name 2) restart jenkins What "sendSplunkConsoleLog" does is
@Override
public boolean start() throws Exception {
//refer to WithContextStep implementation
StepContext context = getContext();
Run run = context.get(Run.class);
ConsoleLogFilter filter = BodyInvoker.mergeConsoleLogFilters(context.get(ConsoleLogFilter.class), new TeeConsoleLogFilter(run));
context.newBodyInvoker().withContext(filter).withCallback(BodyExecutionCallback.wrap(context)).start();
return false;
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42732) Unable to push file into slack with Slack file upload plugin
Title: Message Title Philip Young commented on JENKINS-42732 Re: Unable to push file into slack with Slack file upload plugin Hi Shitij Goyal, Any updates with this issue? We are also having trouble uploading files onto Slack using this plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51060) Environment variables are not passed to cmake when
Title: Message Title
Janne Rönkkö updated an issue
Jenkins / JENKINS-51060
Environment variables are not passed to cmake when
Change By:
Janne Rönkkö
CMake plugin commands do not seem to pass environment to cmake command.{{withEnv(['CC=clang', 'CXX=clang++' \{}} cmakeBuild( {{ buildDir: 'build/debug',}} {{ buildType: 'Debug',}} {{ generator: 'Ninja',}} {{ installation: 'InSearchPath',}} {{ )}} } {{[debug] $ docker exec --workdir /var/lib/jenkins/workspace/job/build/debug 67363250bd775405c7cdf92b70a6d7a70dc136a48c93e350fea9cd12ba50d432 cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /var/lib/jenkins/workspace/job}} {{-- The C compiler identification is GNU 7.2.0}} {{-- The CXX compiler identification is GNU 7.2.0}} {{-- Check for working C compiler: /usr/sbin/cc}} {{-- Check for working C compiler: /usr/sbin/cc – works}} {{-- Detecting C compiler ABI info}} {{-- Detecting C compiler ABI info - done}} {{-- Detecting C compile features}} {{-- Detecting C compile features - done}} {{-- Check for working CXX compiler: /usr/sbin/c++}} {{-- Check for working CXX compiler: /usr/sbin/c++ – works}} {{-- Detecting CXX compiler ABI info}} {{-- Detecting CXX compiler ABI info - done}} {{-- Detecting CXX compile features}} {{-- Detecting CXX compile features - done}} Also, if CMake is installed in /usr/local/bin (and it works in sh step) the CMake builder plugin apparently does not find cmake binary:{{[debug] $ cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /Users/jenkins/workspace/ Qubit/qubit-review job }} [|https://jenkins.intra.vincit.fi/blue/organizations/jenkins/Qubit%2Fqubit-review/detail/qubit-review/165/pipeline/8#step-35-log-2] {{ Cannot run program "cmake" (in directory "/Users/jenkins/workspace/ Qubit job / qubit-review/ build/debug"): error=2, No such file or directory }} In sh step _which cmake_ prints _/usr/local/bin/cmake_ and you can run cmake succesfully
Add Comment
[JIRA] (JENKINS-51060) Environment variables are not passed to cmake when
Title: Message Title
Janne Rönkkö updated an issue
Jenkins / JENKINS-51060
Environment variables are not passed to cmake when
Change By:
Janne Rönkkö
CMake plugin commands do not seem to pass environment to cmake command.{{withEnv(['CC=clang', 'CXX=clang++' \{}} cmakeBuild( {{ buildDir: 'build/debug',}} {{ buildType: 'Debug',}} {{ generator: 'Ninja',}} {{ installation: 'InSearchPath',}} {{ )}}} {{[debug] $ docker exec --workdir /var/lib/jenkins/workspace/job/build/debug 67363250bd775405c7cdf92b70a6d7a70dc136a48c93e350fea9cd12ba50d432 cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /var/lib/jenkins/workspace/job}}{{-- The C compiler identification is GNU 7.2.0}}{{-- The CXX compiler identification is GNU 7.2.0}}{{-- Check for working C compiler: /usr/sbin/cc}}{{-- Check for working C compiler: /usr/sbin/cc -- – works}}{{-- Detecting C compiler ABI info}}{{-- Detecting C compiler ABI info - done}}{{-- Detecting C compile features}}{{-- Detecting C compile features - done}}{{-- Check for working CXX compiler: /usr/sbin/c++}}{{-- Check for working CXX compiler: /usr/sbin/c++ -- – works}}{{-- Detecting CXX compiler ABI info}}{{-- Detecting CXX compiler ABI info - done}}{{-- Detecting CXX compile features}}{{-- Detecting CXX compile features - done}} Also, if CMake is installed in /usr/local/bin (and it works in sh step) the CMake builder plugin apparently does not find cmake binary:{{[ https://jenkins.intra.vincit.fi/blue/organizations/jenkins/Qubit%2Fqubit-review/detail/qubit-review/165/pipeline/8#step-35-log-1][ debug] $ cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /Users/jenkins/workspace/ job Qubit/qubit-review }} {{ [ | https://jenkins.intra.vincit.fi/blue/organizations/jenkins/Qubit%2Fqubit-review/detail/qubit-review/165/pipeline/8#step-35-log-2]Cannot run program "cmake" (in directory "/Users/jenkins/workspace/ job Qubit / qubit-review/ build/debug"): error=2, No such file or directory }} In sh step _which cmake_ prints _/usr/local/bin/cmake_ and you can run cmake succesfully
Add Comment
[JIRA] (JENKINS-51060) Environment variables are not passed to cmake when
Title: Message Title
Janne Rönkkö updated an issue
Jenkins / JENKINS-51060
Environment variables are not passed to cmake when
Change By:
Janne Rönkkö
CMake plugin commands do not seem to pass environment to cmake command.{{withEnv(['CC=clang', 'CXX=clang++' \{}} {{ cmakeBuild( }} {{ buildDir: 'build/debug',}}{{ buildType: 'Debug',}}{{ generator: 'Ninja',}}{{ installation: 'InSearchPath',}}{{ )}} {{ } }} ..CMake uses cc and c++ as compiler: {{[debug] $ docker exec --workdir /var/lib/jenkins/workspace/job/build/debug 67363250bd775405c7cdf92b70a6d7a70dc136a48c93e350fea9cd12ba50d432 cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /var/lib/jenkins/workspace/job}}{{ – -- The C compiler identification is GNU 7.2.0}}{{ – -- The CXX compiler identification is GNU 7.2.0}}{{ – -- Check for working C compiler: /usr/sbin/cc}}{{ – -- Check for working C compiler: /usr/sbin/cc – -- works}}{{ – -- Detecting C compiler ABI info}}{{ – -- Detecting C compiler ABI info - done}}{{ – -- Detecting C compile features}}{{ – -- Detecting C compile features - done}}{{ – -- Check for working CXX compiler: /usr/sbin/c++}}{{ – -- Check for working CXX compiler: /usr/sbin/c++ – -- works}}{{ – -- Detecting CXX compiler ABI info}}{{ – -- Detecting CXX compiler ABI info - done}}{{ – -- Detecting CXX compile features}}{{ – -- Detecting CXX compile features - done}} Also, if CMake is installed in /usr/local/bin (and it works in sh step) the CMake builder plugin apparently does not find cmake binary:{{[ | https://jenkins.intra.vincit.fi/blue/organizations/jenkins/Qubit%2Fqubit-review/detail/qubit-review/165/pipeline/8#step-35-log-1][debug] $ cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /Users/jenkins/workspace/job}}{{[ | https://jenkins.intra.vincit.fi/blue/organizations/jenkins/Qubit%2Fqubit-review/detail/qubit-review/165/pipeline/8#step-35-log-2]Cannot run program "cmake" (in directory "/Users/jenkins/workspace/job/build/debug"): error=2, No such file or directory}}In sh step _which cmake_ prints _/usr/local/bin/cmake_ and you can run cmake succesfully
Add Comment
[JIRA] (JENKINS-51060) Environment variables are not passed to cmake when
Title: Message Title
Janne Rönkkö created an issue
Jenkins / JENKINS-51060
Environment variables are not passed to cmake when
Issue Type:
Bug
Assignee:
Martin Weber
Components:
cmakebuilder-plugin
Created:
2018-05-02 05:37
Environment:
Jenkins ver. 2.107.2
Priority:
Minor
Reporter:
Janne Rönkkö
CMake plugin commands do not seem to pass environment to cmake command. withEnv(['CC=clang', 'CXX=clang++' { cmakeBuild( buildDir: 'build/debug', buildType: 'Debug', generator: 'Ninja', installation: 'InSearchPath', ) {{ }}} ..CMake uses cc and c++ as compiler: [debug] $ docker exec --workdir /var/lib/jenkins/workspace/job/build/debug 67363250bd775405c7cdf92b70a6d7a70dc136a48c93e350fea9cd12ba50d432 cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /var/lib/jenkins/workspace/job {{ – The C compiler identification is GNU 7.2.0}} {{ – The CXX compiler identification is GNU 7.2.0}} {{ – Check for working C compiler: /usr/sbin/cc}} {{ – Check for working C compiler: /usr/sbin/cc – works}} {{ – Detecting C compiler ABI info}} {{ – Detecting C compiler ABI info - done}} {{ – Detecting C compile features}} {{ – Detecting C compile features - done}} {{ – Check for working CXX compiler: /usr/sbin/c++}} {{ – Check for working CXX compiler: /usr/sbin/c++ – works}} {{ – Detecting CXX compiler ABI info}} {{ – Detecting CXX compiler ABI info - done}} {{ – Detecting CXX compile features}} {{ – Detecting CXX compile features - done}} Also, if CMake is installed in /usr/local/bin (and it works in sh step) the CMake builder plugin apparently does not find cmake binary: https://jenkins.intra.vincit.fi/blue/organizations/jenkins/Qubit%2Fqubit-review/detail/qubit-review/165/pipeline/8#step-35-log-1[debug] $ cmake -G Ninja -D CMAKE_BUILD_TYPE=Debug /Users/jenkins/workspace/jobhttps://je
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Olivier Lamy updated JENKINS-25829 Jenkins / JENKINS-25829 Proxy configuration does not work Change By: Olivier Lamy Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Olivier Lamy edited a comment on JENKINS-25829 Re: Proxy configuration does not work oh not yet :) I still need to have first the merge of [https://github.com/jenkinsci/jira-plugin/pull/145]then I will apply some changes to support proxy via an other pr and SNAPSHOT.I'm just waiting a bit of reaction or not from other JIRA maintainers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Olivier Lamy commented on JENKINS-25829 Re: Proxy configuration does not work oh not yet I still need to have first the merge of https://github.com/jenkinsci/jira-plugin/pull/145 then I will apply some changes to support proxy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Vivek Pandey updated JENKINS-25829 Jenkins / JENKINS-25829 Proxy configuration does not work Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Vivek Pandey commented on JENKINS-25829 Re: Proxy configuration does not work Olivier Lamy has PR up https://github.com/jenkinsci/jira-plugin/pull/145 and SNAPSHOT build available: https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/jira/2.5.2-SNAPSHOT/jira-2.5.2-20180501.231733-2.hpi. René Kießig Chester Chee Viachaslau Kabak do you mind testing this SNAPSHOT build? Thanks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett resolved as Fixed Thanks for reporting the issue. I've pushed an updated release which resolves this issue (and a few others). Version 3.1.2.1 will show up in the Jenkins update site in a few hours. Or it can be downloaded and manually installed without waiting for the update site to sync. https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/dependency-check-jenkins-plugin/3.1.2.1/dependency-check-jenkins-plugin-3.1.2.1.hpi Change log: https://wiki.jenkins.io/display/JENKINS/OWASP+Dependency-Check+Plugin Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Steve Springett Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett started work on JENKINS-51053 Change By: Steve Springett Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Vivek Pandey commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Radek Antoniuk Olivier has PR up and snapshot available at https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/jira/2.5.2-SNAPSHOT/jira-2.5.2-20180501.231733-2.hpi, mind giving it a try? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51053 Re: Fail to publish Dependency-Track result Code changed in jenkins User: stevespringett Path: pom.xml src/main/java/org/jenkinsci/plugins/DependencyCheck/DependencyTrackPublisher.java src/main/webapp/help-dt-projectid.html http://jenkins-ci.org/commit/dependency-check-plugin/3776f5f1d591585634cbb295f624b5c41b701259 Log: Fix for JENKINS-51053. FilePath is accessible from master or slave. No need to force execution on slave. Simplified. Added verbage to doc regarding permissions. Updated version to 3.1.2.1 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Title: Message Title Owen Mehegan commented on JENKINS-13810 Re: Maven modules marked to wrong build when running concurrent job Is there any chance this is going to be resolved? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51059) Ensure that seeds are idempotent
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-51059 Ensure that seeds are idempotent Issue Type: Bug Assignee: R. Tyler Croy Components: essentials Created: 2018-05-02 03:40 Priority: Minor Reporter: R. Tyler Croy Right now every time the seeds are run, new "terminus updatet" records are installed, which shuoldn't happen. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49849) Automatically update when new versions of plugins and core are available
Title: Message Title R. Tyler Croy started work on JENKINS-49849 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50949) Track update levels properly in the backend datastore
Title: Message Title R. Tyler Croy updated JENKINS-50949 Jenkins / JENKINS-50949 Track update levels properly in the backend datastore Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50721) Ensure that the Evergreen backend is using a configured secret for JWT
Title: Message Title R. Tyler Croy updated JENKINS-50721 Jenkins / JENKINS-50721 Ensure that the Evergreen backend is using a configured secret for JWT Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-51053 Fail to publish Dependency-Track result Change By: Steve Springett Assignee: Steve Springett Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51053) Fail to publish Dependency-Track result
Title: Message Title Steve Springett commented on JENKINS-51053 Re: Fail to publish Dependency-Track result I've confirmed this to be a defect in the Jenkins plugin. Publishing works as expected when executing from the master node but fails with an NullPointerException when running from a slave. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort updated JENKINS-50199 Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Sam Van Oort Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort started work on JENKINS-50199 Change By: Sam Van Oort Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Matt Gaspar Mike Kozell I appreciate your patience and assistance with diagnosing this. Please could you try the attached SNAPSHOTs and see if the issue is fully resolved? workflow-job.hpi workflow-cps.hpi I've done several additional rounds of testing (including unit tests based on your scenarios) and fixes to try to ensure this is as robust and the fixes are as comprehensive as possible. These changes have received initial code review, and if all looks good they will be ready for full release soon – but obviously it would be helpful to have you try them out with your situations. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Sam Van Oort Attachment: workflow-cps.hpi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: Sam Van Oort Attachment: workflow-job.hpi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51029) Option to ignore SSL certificate errors
Title: Message Title Jakub Bochenski commented on JENKINS-51029 Re: Option to ignore SSL certificate errors > Also, in order to apply this fix, would people running containerized masters have to rebuild their application image? I don't see any technical reason you couldn't do this live. It's a good practice to keep the instance in synch with the Dockerfile etc. but how you do this depends on your process. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51029) Option to ignore SSL certificate errors
Title: Message Title Jakub Bochenski commented on JENKINS-51029 Re: Option to ignore SSL certificate errors +1 from me for uploading the certificate for use by the plugin instead of just ignoring SSL errors. I'm not sure though that it's really better than just adding the cert to the truststore. I'd expect most Jenkins installations are running in a dedicated box/vm/container anyway. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51058) Upgrade Jira plugin version and httpcomponents-client
Title: Message Title Olivier Lamy started work on JENKINS-51058 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51058) Upgrade Jira plugin version and httpcomponents-client
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-51058 Upgrade Jira plugin version and httpcomponents-client Change By: Olivier Lamy Sprint: Blue Ocean 1.6 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51058) Upgrade Jira plugin version and httpcomponents-client
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-51058 Upgrade Jira plugin version and httpcomponents-client Issue Type: Task Assignee: Olivier Lamy Components: blueocean-plugin Created: 2018-05-01 23:13 Priority: Major Reporter: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-44699) Limit the number of lines that are shown for the log in the results page
Title: Message Title Jenn Briden updated an issue Jenkins / JENKINS-44699 Limit the number of lines that are shown for the log in the results page Change By: Jenn Briden Summary: Limit the number of lines that are shown for each the log in the build results page Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44699) Limit the number of lines that are shown for each log in the build results page
Title: Message Title Jenn Briden updated an issue Jenkins / JENKINS-44699 Limit the number of lines that are shown for each log in the build results page Change By: Jenn Briden Summary: Reduce step Limit the number of lines that are shown for each log length in the build results page Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50953) Tool to offer incremental updates
Title: Message Title R. Tyler Croy commented on JENKINS-50953 Re: Tool to offer incremental updates Just to make sure some requirements are clear. The output of such a tool, for Jenkins Essentials, will be something that includes a full URL for each artifact so that we can properly offer downloads. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title Steph Gosling commented on JENKINS-42860 Re: RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches Greg Smith Andres Montalban any insight into exactly what your scriptApproval.xml files looked like would be greatly appreciated. As of current LTS builds and plugins today I cannot cajole Jenkins into behaving (simply to get tags from a GitHub repo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46635) CppCheck - System throws error: javax.xml.bind.UnmarshalException, Premature end of file
Title: Message Title Michael Doubez commented on JENKINS-46635 Re: CppCheck - System throws error: javax.xml.bind.UnmarshalException, Premature end of file Hello, Your ticket is unclear: is your issue the fact that err.xml is empty ? In this case, please see how to use cppcheck (http://cppcheck.sourceforge.net/manual.pdf) is your issue the failure of the build ? It is normal for an empty file unless you ticked "Ignore blank file" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title mike cirioli commented on JENKINS-49502 Re: trigger properties in scripted pipeline require 2 builds to get registered FWIW - I just had to do a test for a blog post i am writing and when using pipeline-event-triggers, you only need to run a build once (declarative or scripted) using 2.107 core. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-21670 Option to anonymize customer labels Change By: Matt Sicker Attachment: Screen Shot 2018-05-01 at 3.47.54 PM.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Matt Sicker commented on JENKINS-21670 Re: Option to anonymize customer labels Here's a proposed admin console for this feature so far: Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51029) Option to ignore SSL certificate errors
Title: Message Title Markus Winter commented on JENKINS-51029 Re: Option to ignore SSL certificate errors I would assume that any Jenkins admin that wants to push to Elastic Search is either administrating the ES himself or has a direct contact to the owner. So he can verify upfront if the certificate is valid when it is self signed. And then it makes a difference. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-51057 EventDispatcher and ConcurrentLinkedQueue ate my JVM Issue Type: Bug Assignee: Tom FENNELLY Components: sse-gateway-plugin Created: 2018-05-01 19:36 Environment: Jenkins 2.107.2 ace-editor-1.1 analysis-core-1.95 ansicolor-0.5.2 ant-1.8 antisamy-markup-formatter-1.5 apache-httpcomponents-client-4-api-4.5.3-2.1 artifactory-2.15.1 authentication-tokens-1.3 badge-1.4 blueocean-1.5.0 blueocean-autofavorite-1.2.2 blueocean-bitbucket-pipeline-1.5.0 blueocean-commons-1.5.0 blueocean-config-1.5.0 blueocean-core-js-1.5.0 blueocean-dashboard-1.5.0 blueocean-display-url-2.2.0 blueocean-events-1.5.0 blueocean-git-pipeline-1.5.0 blueocean-github-pipeline-1.5.0 blueocean-i18n-1.5.0 blueocean-jira-1.5.0 blueocean-jwt-1.5.0 blueocean-personalization-1.5.0 blueocean-pipeline-api-impl-1.5.0 blueocean-pipeline-editor-1.5.0 blueocean-pipeline-scm-api-1.5.0 blueocean-rest-1.5.0 blueocean-rest-impl-1.5.0 blueocean-web-1.5.0 bouncycastle-api-2.16.2 branch-api-2.0.19 build-timeout-1.19 build-user-vars-plugin-1.5 buildtriggerbadge-2.9 checkstyle-3.50 cli-commander-0.3 cloudbees-bitbucket-branch-source-2.2.10 cloudbees-folder-6.4 clover-4.9.0 cobertura-1.12 command-launcher-1.2 conditional-buildstep-1.3.6 config-file-provider-2.18 copyartifact-1.39.1 credentials-2.1.16 credentials-binding-1.16 cucumber-reports-3.16.0 cvs-2.14 dashboard-view-2.9.11 display-url-api-2.2.0 docker-commons-1.11 docker-workflow-1.15.1 durable-task-1.22 email-ext-2.62 embeddable-build-status-1.9 envinject-2.1.5 envinject-api-1.5 extended-read-permission-2.0 external-monitor-job-1.7 favorite-2.3.1 findbugs-4.72 git-3.8.0 git-client-2.7.1 git-server-1.7 github-1.29.0 github-api-1.90 github-branch-source-2.3.3 github-oauth-0.29 gradle-1.28 groovy-2.0 groovy-postbuild-2.4 handlebars-1.1.1 handy-uri-templates-2-api-2.1.6-1.0 htmlpublisher-1.16 http_request-1.8.22 ibm-application-security-1.1.2 icon-shim-2.0.3 ivy-1.28 jackson2-api-2.8.11.1 jacoco-3.0.1 javadoc-1.4 jenkins-design-language-1.5.0 jira-2.5.1 job-dsl-1.69 jquery-detached-1.2.1 jsch-0.1.54.2 junit-1.24 ldap-1.20 lockable-resources-2.2 mailer-1.21 mapdb-api-1.0.9.0 matrix-auth-2.2 matrix-project-1.13 maven-plugin-3.1.2 mercurial-2.3 metrics-3.1.2.11 metrics-graphite-3.0.0 modernstatus-1.2 momentjs-1.1.1 monitoring-1.72.0 pam-auth-1.3 parameterized-trigger-2.35.2 pegdown-formatter-1.3 performance-3.8 pipeline-build-step-2.7 pipeline-github-2.0 pipeline-github-lib-1.0 pipeline-graph-analysis-1.6 pipeline-input-step-
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/google/jenkins/plugins/credentials/oauth/RemotableGoogleCredentials.java src/main/java/com/google/jenkins/plugins/util/JodaDateTimeConverter.java src/test/java/com/google/jenkins/plugins/credentials/oauth/RemotableGoogleCredentialsIntegrationTest.java http://jenkins-ci.org/commit/google-oauth-plugin/bb9c2cc5ca5940b2043ee35bf6afb3ac3c7c68af Log: JENKINS-50216 - Cleanup codestyle and re-enable Checkstyle Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/google/jenkins/plugins/util/JodaDateTimeConverter.java src/main/resources/META-INF/hudson.remoting.ClassFilter http://jenkins-ci.org/commit/google-oauth-plugin/498b54bb486d4a5dfd91ca47cfb04fbbf946502f Log: JENKINS-50216 - Whitelist org.joda.time.DateTime so that there is no need to tweak converter priorities Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Code changed in jenkins User: astroilov Path: .gitignore Jenkinsfile checkstyleJavaHeader pom.xml src/main/java/com/google/jenkins/plugins/credentials/oauth/RemotableGoogleCredentials.java src/main/resources/com/google/jenkins/plugins/credentials/oauth/GoogleRobotMetadataCredentials/config.jelly src/main/resources/com/google/jenkins/plugins/credentials/oauth/GoogleRobotPrivateKeyCredentials/config.jelly src/main/resources/com/google/jenkins/plugins/credentials/oauth/JsonServiceAccountConfig/config.jelly src/main/resources/com/google/jenkins/plugins/credentials/oauth/P12ServiceAccountConfig/config.jelly http://jenkins-ci.org/commit/google-oauth-plugin/e68bbcc00395124e4b27e90b84e1edeaff33fc74 Log: Merge pull request #17 from jglick/RemotableGoogleCredentials.expiration-JENKINS-50216 JENKINS-50216 - RemotableGoogleCredentials.expiration fix Compare: https://github.com/jenkinsci/google-oauth-plugin/compare/62126a657c2d...e68bbcc00395 *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/google/jenkins/plugins/util/JodaDateTimeConverter.java src/test/java/com/google/jenkins/plugins/credentials/oauth/RemotableGoogleCredentialsIntegrationTest.java src/test/resources/com/google/jenkins/plugins/credentials/oauth/jodaDateTimeNull.xml http://jenkins-ci.org/commit/google-oauth-plugin/dbdef9b760d3c1d21be7d8199022b1bae60864e0 Log: JENKINS-50216 - Joda DateTime converter now has higher priority than JEP-200 blacklist Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/google-oauth-plugin/51fb71acab97b80be2b1cc27aae19d9203a09a09 Log: JENKINS-50216 - Add BouncyCastle API dependency to enable tests against 2.107.2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/google/jenkins/plugins/credentials/oauth/RemotableGoogleCredentials.java src/main/java/com/google/jenkins/plugins/util/JodaDateTimeConverter.java src/test/java/com/google/jenkins/plugins/credentials/oauth/RemotableGoogleCredentialsIntegrationTest.java src/test/resources/com/google/jenkins/plugins/credentials/oauth/jodaDateTimeBroken.xml src/test/resources/com/google/jenkins/plugins/credentials/oauth/jodaDateTimeXML.xml http://jenkins-ci.org/commit/google-oauth-plugin/c47f47226c036b6f25d252877a34e68a0b1af99e Log: JENKINS-50216 - Introduce a custom serializer for org.joda.time.DateTime Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ Code changed in jenkins User: Oleg Nenashev Path: Jenkinsfile pom.xml http://jenkins-ci.org/commit/google-oauth-plugin/5e0448e8d183f26aaf056a79aa11129e73bb3329 Log: JENKINS-50216 - Add Jenkinsfile to verify JEP-200 regressions Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-51049
Re: Folders Plugin GitHub Scanning Time not being copied into the Jobs
Ok, it looks like your parent job is an organization folder and the sub jobs are multibranch projects. I am not familiar with the plugins and APIs that provide those features, but I see what appears to be related discussion in JENKINS-47077. In particular [~stephenconnolly] notes in a [comment|https://issues.jenkins-ci.org/browse/JENKINS-47077?focusedCommentId=331178&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-331178] something that makes me think this never worked.{quote}(ignore that you cannot configure the multibranch's period at present) {quote}Maybe the configuration of the folder properties has never worked, but you are only noticing it now that you are experiencing JENKINS-47077?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title Devin Nusbaum commented on JENKINS-51049 Re: Folders Plugin GitHub Scanning Time not being copied into the Jobs Ok, it looks like your parent job is an organization folder and the sub jobs are multibranch projects. I am not familiar with the plugins and APIs that provide those features, but I see what appears to be related discussion in JENKINS-47077. In particular Stephen Connolly notes in a comment something that makes me think this never worked. (ignore that you cannot configure the multibranch's period at present) Maybe the configuration has never worked, but you are only noticing it now that you are experiencing JENKINS-47077? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50077) Integration Test for RegexpFilter
Title: Message Title Ulli Hafner commented on JENKINS-50077 Re: Integration Test for RegexpFilter Packages sind wahrscheinlich kein guter Versuch mit ChecksStyle. Denn CheckStyle vergibt keine Packages, diese werden nachträglich aus den Sourcen extrahiert und zugewiesen. Dieser Schritt funktioniert aber nicht im Test, da hier ja gar keine Sourcen vorhanden sind. Versuchen Sie das mal mit PMD, dort sind die Packages im XML hinterlegt. Außerdem wird der Regexp ".parser." nur auf ein Paket mit 8 Buchstaben matchen, da ist wohl besser .\.parser\... (Aber das lässt sich am besten am Unit Tests überprüfen). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39781) Can't remove old branch builds in multibranch pipeline
Title: Message Title
James Hogarth commented on JENKINS-39781
Re: Can't remove old branch builds in multibranch pipeline
To be clear that only affects orphan status (ie when an upstream repo/branch vanishes) and not build history ... To handle build history you have to set the property in the Jenkinsfile ... or if like me you cannot control all the developers files ... run this on a regular basis
#!/usr/bin/env groovy
import org.jenkinsci.plugins.workflow.job.WorkflowJob
import hudson.tasks.LogRotator
def allItems = Jenkins.instance.getAllItems(WorkflowJob)
allItems.each { job ->
// defaults to use
newArtifactDaysToKeep = 7
newArtifactNumToKeep = 10
newDaysToKeep = 30
newNumToKeep = 100
newDiscarder = false
buildDiscarder = job.getBuildDiscarder()
// if the buildDiscarder is already configured, then check if it is partially configured
// and honour whatever settings are in the jenkinsfile
if (buildDiscarder) {
if (buildDiscarder instanceof LogRotator) {
artifactDaysToKeep = buildDiscarder.getArtifactDaysToKeep()
artifactNumToKeep = buildDiscarder.getArtifactNumToKeep()
daysToKeep = buildDiscarder.getDaysToKeep()
numToKeep = buildDiscarder.getNumToKeep()
println "Existing config is: artifactDaysToKeep (${artifactDaysToKeep}) artifactNumToKeep (${artifactNumToKeep}) daysToKeep (${daysToKeep}) numToKeep (${numToKeep})"
if ((artifactDaysToKeep < 1) || (artifactNumToKeep < 1) || (daysToKeep < 1) || (numToKeep < 1)) {
newDiscarder = true
}
if (artifactDaysToKeep > 0) {
newArtifactDaysToKeep = artifactDaysToKeep
}
if (artifactNumToKeep > 0) {
newArtifactNumToKeep = artifactNumToKeep
}
if (daysToKeep > 0) {
newDaysToKeep = daysToKeep
}
if (numToKeep > 0) {
newNumToKeep = numToKeep
}
} else {
// enforce LogRotator discarder just in case another appears
newDiscarder = true
}
} else {
// if no discarder is configured yet then we'll add our agreed defaults
newDiscarder = true
}
if (newDiscarder == true) {
// we'll persist this as that allows the settings to survive restart
// note that a jenkinsfile will only touch this is properties() is set in it
println "New config is: artifactDaysToKeep (${newArtifactDaysToKeep}) artifactNumToKeep (${newArtifactNumToKeep}) daysToKeep (${newDaysToKeep}) numToKeep (${newNumToKeep})"
newBuildDiscarder = new LogRotator(newDaysToKeep, newNumToKeep, newArtifactDaysToKeep, newArtifactNumToKeep)
job.setBuildDiscarder(newBuildDiscarder)
job.save()
}
// At this point either we've set a configure or verified the Jenkinsfile for the workflow has already got values assigned
println "Running cleanup of " + job.getFullName()
job.logRotate()
}
return "completed"
[JIRA] (JENKINS-35642) Multibranch plugin is missing "Discard Old Builds"
Title: Message Title
James Hogarth commented on JENKINS-35642
Re: Multibranch plugin is missing "Discard Old Builds"
For the benefit of google and the next person that needs to set discard properties on all their pipeline jobs due to lack of control of Jenkinsfiles from developers ... Just knocked up this bit of groovy which respects any existing setting, but mandates some limits if not set and ensures the rotate log is run when there are jobs that may only run infrequently:
#!/usr/bin/env groovy
import org.jenkinsci.plugins.workflow.job.WorkflowJob
import hudson.tasks.LogRotator
def allItems = Jenkins.instance.getAllItems(WorkflowJob)
allItems.each { job ->
// defaults to use
newArtifactDaysToKeep = 7
newArtifactNumToKeep = 10
newDaysToKeep = 30
newNumToKeep = 100
newDiscarder = false
buildDiscarder = job.getBuildDiscarder()
// if the buildDiscarder is already configured, then check if it is partially configured
// and honour whatever settings are in the jenkinsfile
if (buildDiscarder) {
if (buildDiscarder instanceof LogRotator) {
artifactDaysToKeep = buildDiscarder.getArtifactDaysToKeep()
artifactNumToKeep = buildDiscarder.getArtifactNumToKeep()
daysToKeep = buildDiscarder.getDaysToKeep()
numToKeep = buildDiscarder.getNumToKeep()
println "Existing config is: artifactDaysToKeep (${artifactDaysToKeep}) artifactNumToKeep (${artifactNumToKeep}) daysToKeep (${daysToKeep}) numToKeep (${numToKeep})"
if ((artifactDaysToKeep < 1) || (artifactNumToKeep < 1) || (daysToKeep < 1) || (numToKeep < 1)) {
newDiscarder = true
}
if (artifactDaysToKeep > 0) {
newArtifactDaysToKeep = artifactDaysToKeep
}
if (artifactNumToKeep > 0) {
newArtifactNumToKeep = artifactNumToKeep
}
if (daysToKeep > 0) {
newDaysToKeep = daysToKeep
}
if (numToKeep > 0) {
newNumToKeep = numToKeep
}
} else {
// enforce LogRotator discarder just in case another appears
newDiscarder = true
}
} else {
// if no discarder is configured yet then we'll add our agreed defaults
newDiscarder = true
}
if (newDiscarder == true) {
// we'll persist this as that allows the settings to survive restart
// note that a jenkinsfile will only touch this is properties() is set in it
println "New config is: artifactDaysToKeep (${newArtifactDaysToKeep}) artifactNumToKeep (${newArtifactNumToKeep}) daysToKeep (${newDaysToKeep}) numToKeep (${newNumToKeep})"
newBuildDiscarder = new LogRotator(newDaysToKeep, newNumToKeep, newArtifactDaysToKeep, newArtifactNumToKeep)
job.setBuildDiscarder(newBuildDiscarder)
job.save()
}
// At this point either we've set a configure or verified the Jenkinsfile for the workflow has already got values assigned
println "Running cleanup of " + job.getFullName()
job.logRotate()
}
return "completed"
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title aflat commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found And I was also able to use the same workaround Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51056) Jenkins XUnit Plugin version 1.103 fails without threshold specified
Title: Message Title
Ryan Gates created an issue
Jenkins / JENKINS-51056
Jenkins XUnit Plugin version 1.103 fails without threshold specified
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
xunit-plugin
Created:
2018-05-01 17:31
Priority:
Minor
Reporter:
Ryan Gates
After upgrading the xunit plugin from version 1.102 to 1.103, my build started failing at the following line in the jenkinsfile/pipeline.
step([$class: 'XUnitBuilder', tools: [[$class: 'XUnitDotNetTestType', pattern: '*results.xml']]])
It throws the following exception.
java.lang.NullPointerException
at org.jenkinsci.plugins.xunit.XUnitBuilder.(XUnitBuilder.java:65)
at org.jenkinsci.plugins.xunit.XUnitBuilder.(XUnitBuilder.java:71)
Caused: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:282)
Caused: java.lang.IllegalArgumentException: Could not instantiate {tools=[{$class=XUnitDotNetTestType}]} for XUnitBuilder(tools: TestType{AUnitJunitHudsonTestType(pattern: String, skipNoTestFiles: boolean, failIfNotNew: boolean, deleteOutputFiles: boolean, stopProcessingIfError: boolean) | BoostTestJunitHudsonTestTyp
[JIRA] (JENKINS-47501) 2 pods are started instead of 1 after update to version 1.1
Title: Message Title Aiman Alsari commented on JENKINS-47501 Re: 2 pods are started instead of 1 after update to version 1.1 I can confirm this is still happening on 1.5.2 - The most reliable way of reproducing this issue is to run the test case provided by the OP, have a single job running, queue up 2 or 3 behind it using the same pod template, then abort the first one. What happens is that 2 or more pods are provisioned simultaneously, disregarding the limit. This isn't that big of a deal (for me at least) but then it gets into a crazy crash loop. Something is calling "KubernetesSlave._terminate()" on one of the newly provisioned pods, it can then fail in one of two ways: The pod is terminated and the provisioning halts resulting in "java.lang.IllegalStateException: Pod no longer exists:" The master has removed the node from it's list of nodes and so JNLP fails. On the master it has "Refusing headers from remote: Unknown client name: foo-bar". On the actual JNLP pod it has "The server rejected the connection: None of the protocols were accepted". There seems to be a race condition somewhere, something is calling the _terminate method for this pod right when it starts up. My first guess was that when the first aborted job is terminating, provisioning of the two new pods happens simultaneously and the termination code of the first job then kills the new ones as well as the first one. This doesn't seem to be the case though as I can not replicate the issue reliably with just one active + one queued job, it has to be 2 or 3. Once in this state the only way to fix it is to delete all the queued jobs and clean all Error'ed pods. jenkins_log Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title aflat commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found I'm also hitting this error, trying to curl a new config.xml up to my jenkins server. Version 2.117. I curl down a config.xml, tweak the name, then curl it back up. Been using the same script for about 3 years. Now the post curl is failing. WARNING: Error while serving http://pliny.actifio.com/createItem java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:860) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:237) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:214) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:44) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:106) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:64) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)
[JIRA] (JENKINS-47501) 2 pods are started instead of 1 after update to version 1.1
Title: Message Title Aiman Alsari updated an issue Jenkins / JENKINS-47501 2 pods are started instead of 1 after update to version 1.1 Change By: Aiman Alsari Attachment: jenkins_log Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect
Title: Message Title Paul Milliken commented on JENKINS-31661 Re: Jenkins.rootUrl too often unset or incorrect Since this has been merged in 2.119, my Jenkins installation is constantly showing the "Jenkins root URL seems to be invalid. It is required for the proper operation of many Jenkins features like email notifications, PR status update, and environment variables such as BUILD_URL." notification. I have tried modified the URL setting to a completely different value, and then back to the correct value to ensure that it is definitely set, yet this message continues to display (even after a Jenkins restart). The configured URL is definitely correct. I'm guessing there's some extra check being performed which makes Jenkins believe it to be incorrect - most likely something related to the docker / nginx setup I've got going on. However, I feel like there should be a simple way of confirming to Jenkins that yes, the URL as configured is the correct one for it to be using and to stop prompting about it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43925) Personal credential management
Title: Message Title Aaron Duke commented on JENKINS-43925 Re: Personal credential management +1 for a workaround. I'm a Jenkins neophyte, but would love a solution (e.g., using a groovy script and credentials plugin) as this is the one issue preventing me from automating my jenkins deployment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21559) Default GIT to run 'git clone' instead of 'git fetch'
Title: Message Title John Lawlor commented on JENKINS-21559 Re: Default GIT to run 'git clone' instead of 'git fetch' There are other use cases for 'git clone' other than what has been outlined. We clone onto VMs provisioned by Openstack, so they are always brand new. In this scenario there is no need for 'git fetch'. I find that the default options used by the git client are much slower than a standard clone for example: time /opt/openet/git/bin/git fetch --no-tags --progress ssh://g...@bitbucket.openet.com:7999/project/repo.git +refs/heads/*:refs/remotes/origin/* --depth=5 real 4m25.940s user 2m52.796s sys 1m23.799s If I do the same thing with a standard clone: time git clone ssh://g...@bitbucket.openet.com:7999/project/repo.git --depth 5 real 0m43.012s user 0m26.575s sys 0m12.050s This particular repo has 5000 branches, if you could even turn off the '--progress' option it would help matters. The way that the jenkins plugin has decided to do the fetch favours verbosity over performance. It's 10 times slower than a standard clone. I would prefer if it favoured performance. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51055) Rebranding - HPE still appears in a few places in Job Configuration
Title: Message Title Daniel Danan updated an issue Jenkins / JENKINS-51055 Rebranding - HPE still appears in a few places in Job Configuration Change By: Daniel Danan Attachment: Jenkins_Rebranding.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51055) Rebranding - HPE still appears in a few places in Job Configuration
Title: Message Title Daniel Danan assigned an issue to Daniel Danan Jenkins / JENKINS-51055 Rebranding - HPE still appears in a few places in Job Configuration Change By: Daniel Danan Assignee: Ofir Shaked Daniel Danan Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51055) Rebranding - HPE still appears in a few places in Job Configuration
Title: Message Title Daniel Danan created an issue Jenkins / JENKINS-51055 Rebranding - HPE still appears in a few places in Job Configuration Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 2018-05-01 16:27 Labels: PerformanceCenter Priority: Minor Reporter: Daniel Danan Publish result task is still using HPE. It should be replaced by Micro Focus (just removing it will keep the task ambiguous). Add Comment
[JIRA] (JENKINS-50077) Integration Test for RegexpFilter
Title: Message Title Manuel Hampp commented on JENKINS-50077 Re: Integration Test for RegexpFilter Hallo, ich verwende für die Tests eine modifizierte checkstyle.xml Datei. In dieser versuche ich gerade ein anderes Package (für die inlcude/exclude Package Ausdrücke) hineinzubekommen. Leider funktioniert dies gar nicht wie gedacht. Sollte es nicht reichen, den Pfad zur Source-Datei zu verändern? Folgendes Beispiel: Bei der IncludePackage Regex ".parser." sollten meines Erachtens nun nur die Issues aus dem CsharpNamespaceDetector.java File übrig bleiben. Das Result ist allerdings leer. Der gleiche Ausdruck als ExcludePackage gibt mir sämtliche Issues zurück. Viele Grüße Manuel Hampp Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50729) exception when cleaning workspace
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-50729
exception when cleaning workspace
Change By:
Mark Waite
Jenkins is not able to clean workspace before updating strace git checkout. It crashes with { { noformat } } {{ Started by upstream project "[strace]" build number [98] }} {{ originally caused by: }} {{ Started by an SCM change }} {{ Building remotely on }}{{[p8-ppc64le] }} {{ (Fedora F27 ppc64le) in workspace /home/jenkins/workspace/strace/label/ppc64le }} {{ Cloning the remote Git repository }} {{ Cloning repository }}{{[https://github.com/strace/strace.git] }} {{ ERROR: Failed to clean the workspace }} {{ java.io.IOException: Unable to delete '/home/jenkins/workspace/strace/label/ppc64le'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. }} {{ at hudson.Util.deleteContentsRecursive(Util.java:238) }} {{ at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:555) }} {{ at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) }} {{ at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) }} {{ at hudson.remoting.UserRequest.perform(UserRequest.java:210) }} {{ at hudson.remoting.UserRequest.perform(UserRequest.java:53) }} {{ at hudson.remoting.Request$2.run(Request.java:364) }} {{ at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) }} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266) }} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) }} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) }} {{ at java.lang.Thread.run(Thread.java:748) }} {{ Caused by: java.io.IOException: Unable to delete /home/jenkins/workspace/strace/label/ppc64le/tests/fsync-y.dir - files in dir: [/home/jenkins/workspace/strace/label/ppc64le/tests/fsync-y.dir/078 9 }} {{ 1 }} {{ 78 \'"<<0::0>>1~ ��] }} {{ at hudson.Util.tryOnceDeleteFile(Util.java:303) }} {{ at hudson.Util.tryOnceDeleteRecursive(Util.java:369) }} {{ at hudson.Util.tryOnceDeleteContentsRecursive(Util.java:388) }} {{ at hudson.Util.tryOnceDeleteRecursive(Util.java:368) }} {{ at hudson.Util.tryOnceDeleteContentsRecursive(Util.java:388) }} {{ at hudson.Util.deleteContentsRecursive(Util.java:233) }} {{ ... 11 more }} {{ Caused by: java.nio.file.DirectoryNotEmptyException: /home/jenkins/workspace/strace/label/ppc64le/tests/fsync-y.dir }} {{ at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) }} {{ at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) }} {{ at java.nio.file.Files.deleteIfExists(Files.java:1165) }} {{ at hudson.Util.tryOnceDeleteFile(Util.java:297) }} {{ ... 16 more }} {{ ERROR: Error cloning remote repo 'origin' }} {{ hudson.plugins.git.GitException: Failed to delete workspace }} {{ at org.jenkinsci.plugins.
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Andrew Bayer commented on JENKINS-45455 Re: Restarting stages Sean Williams Will Saxon - this will not be Blue Ocean-exclusive - there'll be a classic UI for it, you can interact with it via the REST API, etc. We're just holding up merging/releasing it because we want to make sure we've got the Blue Ocean user experience for stage restarting nailed down and on its way to completion beforehand, so that we know the Blue Ocean side is coming soon and we know that the Declarative side doesn't need to be changed post-release to work with the right approach in the Blue Ocean UX. Coordination is fun. =) (also we've got to get JENKINS-46809 merged before we can merge this, and that little bugger requires, at a minimum, updates to the Blue Ocean Pipeline editor to handle changes to the intermediate representation of a Declarative Pipeline or it just blows up horribly) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46089) ProcessTreeKiller broken in pipeline jobs
Title: Message Title Georg Friedrich commented on JENKINS-46089 Re: ProcessTreeKiller broken in pipeline jobs Ah, I just found that there already IS the ability to stop Jenkins from killing processes by using the "veto kill process"-feature. You should have mentioned this Oleg Nenashev As far as I can see this is/was bugged for slave nodes but just got fixed 2 days ago. Unfortunately it missed the 2.119 release but I guess it will be available with 2.120 then. That's really great news, so I will wait patiently for the 2.120 and will create an extension for not killing the Gradle daemons. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47566) Unexpected end of ZLIB input stream on permission errors
Title: Message Title Mattias Amnefelt commented on JENKINS-47566 Re: Unexpected end of ZLIB input stream on permission errors Yes, fixing the permissions was the workaround I mentioned in the the initial ticket description. This ticket was about the error message which imho should be something better than Unexpected end of ZLIB input stream If the error message had mentioned permission denied anywhere, I would not have wasted several hours trying to find out what was wrong with the build slave. I do not think this is Not A Defect as the error message is highly misleading. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title John Mellor commented on JENKINS-51049 Re: Folders Plugin GitHub Scanning Time not being copied into the Jobs I upgraded to Jenkins 2.118 overnight, and picked up a dozen small updates to the plugins at the same time. The problem behaviour is unaltered. Attaching a slightly-redacted folder config and typical subjob config that has the problem per request. Looking back, I cannot locate a job where this is working, so I am unsure when it broke. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title John Mellor updated an issue Jenkins / JENKINS-51049 Folders Plugin GitHub Scanning Time not being copied into the Jobs Change By: John Mellor Attachment: subjob_config.xml Attachment: folder_config.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46089) ProcessTreeKiller broken in pipeline jobs
Title: Message Title Georg Friedrich commented on JENKINS-46089 Re: ProcessTreeKiller broken in pipeline jobs I think so too, Oleg Nenashev. Overriding the BUILD_ID environment variable looks very hacky. Unfortunately there is no possibility for Gradle to run the daemons initially. And of course the daemon feature of Gradle will only make sense for "always-on" build nodes, so using it in combination with docker agents is useless. That said: Would it be possible (from an architectural point of view) to disable the ProcessTreeKiller for specific builds instead of using this BUILD_ID hack? I think there are enough reasons here to give users the possibility to do so. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50883) Blue ocean:GitHub Webhook is not created after new pipeline creation
Title: Message Title Isaac Cohen commented on JENKINS-50883 Re: Blue ocean:GitHub Webhook is not created after new pipeline creation Vivek Pandey I do believe that 2.3.2 fixed the issue in Classic UI, but I still don't think it works with Blue Ocean. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29471) SSH Slaves plugin doesn't work with SSL key files
Title: Message Title Ivan Fernandez Calvo closed an issue as Incomplete https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-29471 SSH Slaves plugin doesn't work with SSL key files Change By: Ivan Fernandez Calvo Status: Open Closed Assignee: Kohsuke Kawaguchi Ivan Fernandez Calvo Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42441) add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-42441 add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42441) add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave
Title: Message Title Ivan Fernandez Calvo resolved as Duplicate Jenkins / JENKINS-42441 add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave Change By: Ivan Fernandez Calvo Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42441) add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-42441 Re: add windows 7 via ssh: Could not copy slave.jar into '/volumes1/jenkins_build' on slave see this comment https://issues.jenkins-ci.org/browse/JENKINS-42856?focusedCommentId=301254&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-301254 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43306) Copied job executes on non master node
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-43306 Copied job executes on non master node Change By: Ivan Fernandez Calvo Assignee: Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43306) Copied job executes on non master node
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-43306 Copied job executes on non master node Change By: Ivan Fernandez Calvo Component/s: core Component/s: ssh-slaves-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43306) Copied job executes on non master node
Title: Message Title Ivan Fernandez Calvo closed an issue as Incomplete https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-43306 Copied job executes on non master node Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit htt
[JIRA] (JENKINS-43306) Copied job executes on non master node
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-43306 Copied job executes on non master node Change By: Ivan Fernandez Calvo Component/s: ssh-slaves-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43986) Ubuntu slave cannot be started because ssh connection fails
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect You must import the public key of the Agent, in the know host on the Jenkins instance (in your case C:\Windows\system32\config\systemprofile\.ssh\known_hosts) if you do not do that you cannot verify the host key. Jenkins / JENKINS-43986 Ubuntu slave cannot be started because ssh connection fails Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenki
[JIRA] (JENKINS-45001) KnownHostsFileKeyVerificationStrategy is not configurable
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-45001 KnownHostsFileKeyVerificationStrategy is not configurable Change By: Ivan Fernandez Calvo Assignee: Kohsuke Kawaguchi Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49504) ssh-slaves-plugin does not honor global /etc/ssh/ssh_known_hosts
Title: Message Title Ivan Fernandez Calvo closed an issue as Duplicate Jenkins / JENKINS-49504 ssh-slaves-plugin does not honor global /etc/ssh/ssh_known_hosts Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46093) sshd zombie processes when using ssh slaves
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-46093 sshd zombie processes when using ssh slaves Change By: Ivan Fernandez Calvo Assignee: Kohsuke Kawaguchi Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47401) slave.jar gets deleted and slave gets disconnected
Title: Message Title Ivan Fernandez Calvo closed an issue as Duplicate Jenkins / JENKINS-47401 slave.jar gets deleted and slave gets disconnected Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47566) Unexpected end of ZLIB input stream on permission errors
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-47566 Re: Unexpected end of ZLIB input stream on permission errors This is your script echo foo > bar.txt sudo chown root bar.txt sudo chmod 600 bar.txt If the user that runs the agent is nor root does not have access to the bar.txt file, only root can read this file, so if you use a no root user to try to archive the artifacts you see this error. ERROR: Failed to archive artifacts: bar.txt java.io.EOFException: Unexpected end of ZLIB input stream at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186) at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) at org.apache.commons.compress.utils.IOUtils.readFully(IOUtils.java:160) at org.apache.commons.compress.utils.IOUtils.readFully(IOUtils.java:134) at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.readRecord(TarArchiveInputStream.java:419) at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getRecord(TarArchiveInputStream.java:388) at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.getNextTarEntry(TarArchiveInputStream.java:269) at hudson.FilePath.readFromTar(FilePath.java:2351) Also: Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to local at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel$2.adapt(Channel.java:986) at hudson.remoting.Channel$2.adapt(Channel.java:983) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:2280) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:245) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1752) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) java.io.IOException: This archives contains unclosed entries. at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.finish(TarArchiveOutputStream.java:225) at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.close(TarArchiveOutputStream.java:241) at hudson.util.io.TarArchiver.close(TarArchiver.java:127) at hudson.FilePath.writeToTar(FilePath.java:2337) at hudson.FilePath.access$2300(FilePath.java:208) at hudson.FilePath$45.invoke(FilePath.java:2272) at hudson.FilePath$45.invoke(FilePath.java:2268) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2816) at hudson.remoting.UserRequest.perfor
[JIRA] (JENKINS-47566) Unexpected end of ZLIB input stream on permission errors
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-47566 Unexpected end of ZLIB input stream on permission errors Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Sean Williams commented on JENKINS-45455 Re: Restarting stages Thanks for the update Jenn. Will asks a good question. I hope this is a pipeline feature - we are using declarative, but not blue ocean. While Blue Ocean is very pretty and looks very promising, we can't switch until it's all encompassing. But we do need the restart functionality. Or perhaps I'm just confused and the pipeline rendering itself is part of Blue Ocean without even having BO enabled... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47566) Unexpected end of ZLIB input stream on permission errors
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-47566 Unexpected end of ZLIB input stream on permission errors Change By: Ivan Fernandez Calvo Component/s: ssh-slaves-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47586) ssh-slaves plugin tries to install latest JDK from Oracle's website and must be updated for every new JDK release
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-47586 ssh-slaves plugin tries to install latest JDK from Oracle's website and must be updated for every new JDK release Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50092) Integration Test for HealthReport
Title: Message Title
Ulli Hafner commented on JENKINS-50092
Re: Integration Test for HealthReport
Andere Parser lassen sich durch Anpassen des Aufrufs
publisher.setTools(Collections.singletonList(new ToolConfiguration("**/*issues.txt", new Eclipse(;
auswählen. Statt new Eclipse() einfach new CheckStyle() verwenden. Am besten das Tool als Parameter in die Methode enableWarnings reinnehmen. Oder alternativ mit Eclipse und dem Verfahren vom letzten Kommentar weiterarbeiten.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48574) Agent installer GUI should not be installed on headless agents
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-48574 Agent installer GUI should not be installed on headless agents Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48829) Linux slaves disconnect intermittently
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-48829 Linux slaves disconnect intermittently Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49118) SSH Slaves 1.25 Breaks
Title: Message Title Ivan Fernandez Calvo assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-49118 SSH Slaves 1.25 Breaks Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
