[JIRA] (JENKINS-41186) java.security.spec.InvalidKeySpecException: key spec not recognised
Title: Message Title Fritz Elfert commented on JENKINS-41186 Re: java.security.spec.InvalidKeySpecException: key spec not recognised Ok guys, I have made the dependency changes suggested by Ashley Taylor except the pull request for the configfile-provider upgrade was not applied, because it has some serious functionality problems (once a config-file is saved, it cannot be modified anymore). Therefore: KEEP your configfile-provider plugin at v2.13 for now! The jclouds plugin for testing can be found here: https://jenkins.ci.cloudbees.com/job/plugins/job/jclouds-plugin/310/org.jenkins-ci.plugins$jclouds-jenkins/artifact/org.jenkins-ci.plugins/jclouds-jenkins/2.13-SNAPSHOT/jclouds-jenkins-2.13-SNAPSHOT.hpi Since I could not reproduce this bug locally, please report back soon. If this indeed fixes the issue, I will then release a new version 2.13. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41186) java.security.spec.InvalidKeySpecException: key spec not recognised
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41186 Re: java.security.spec.InvalidKeySpecException: key spec not recognised Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/pom.xml jclouds-shaded/pom.xml http://jenkins-ci.org/commit/jclouds-plugin/272de3ed7f41bc7ba3bbc8d1a5d4559632c2875f Log: Fixed JENKINS-41186 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20782) "Specific Users Strategy" verifies authentication multiple times
Title: Message Title ikedam closed an issue as Not A Defect Jenkins / JENKINS-20782 "Specific Users Strategy" verifies authentication multiple times Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20781) "Specific Users Strategy" does not validate authentication of the selected user
Title: Message Title ikedam closed an issue as Not A Defect Jenkins / JENKINS-20781 "Specific Users Strategy" does not validate authentication of the selected user Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41078) Cannot provision via jcloud (google-compute-engine)
Title: Message Title Fritz Elfert commented on JENKINS-41078 Re: Cannot provision via jcloud (google-compute-engine) Hi, just a short report on the progress of the PR from Dominik Bartholdi: The PR merges ok, but unfortunately it breaks functionality: I cannot modify config files (no errors or exceptions, just when I hit the Submit button in the config file editor, the config is not updated) - Did just a short test due to lack of time - so this needs to be investigated further... Just to let you know why this takes so long -Fritz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20783) Improper invocation of doCheckPassword() in Authoriza project
Title: Message Title ikedam closed an issue as Not A Defect Jenkins / JENKINS-20783 Improper invocation of doCheckPassword() in Authoriza project Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20812) Configuration view in Configure Global Security
Title: Message Title ikedam closed an issue as Fixed Already released in 1.0.2. Jenkins / JENKINS-20812 Configuration view in Configure Global Security Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34279) Fails with Active Directory
Title: Message Title ikedam closed an issue as Fixed Jenkins / JENKINS-34279 Fails with Active Directory Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38547) Jobs are still running as the Windows Service user
Title: Message Title ikedam closed an issue as Not A Defect Jenkins / JENKINS-38547 Jobs are still running as the Windows Service user Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40739) Introduce "Don't restrict users to configuring the job"
Title: Message Title ikedam closed an issue as Fixed Released as authorize-project-1.3.0. Jenkins / JENKINS-40739 Introduce "Don't restrict users to configuring the job" Change By: ikedam Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41274) "Run as Specific User" does not work with Pipeline Jobs
Title: Message Title ikedam resolved as Cannot Reproduce Please reopen when you report how to reproduce the issue. Jenkins / JENKINS-41274 "Run as Specific User" does not work with Pipeline Jobs Change By: ikedam Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://grou
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title ikedam closed an issue as Fixed Stephen Connolly Really sorry for having you wait for long time. I released this change as authorize-project-1.3.0. It will be available in the update center in a day. Jenkins / JENKINS-35081 Separate authorization configuration page Change By: ikedam Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenk
[JIRA] (JENKINS-41186) java.security.spec.InvalidKeySpecException: key spec not recognised
Title: Message Title Fritz Elfert started work on JENKINS-41186 Change By: Fritz Elfert Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam commented on JENKINS-41729 Re: Using utf-8 letters in property files The apparent problem is assuming that encoding is always UTF-8. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam commented on JENKINS-41729 Re: Using utf-8 letters in property files https://github.com/kohsuke/localizer/pull/13 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41729) Using utf-8 letters in property files
Title: Message Title ikedam edited a comment on JENKINS-41729 Re: Using utf-8 letters in property files https://github.com/ kohsuke stapler / localizer stapler /pull/ 13 105 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35081) Separate authorization configuration page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35081 Re: Separate authorization configuration page Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java http://jenkins-ci.org/commit/authorize-project-plugin/ac37f3fcff7a354e17996422dd33e7fc0cdcd3aa Log: JENKINS-35081 Fixed the reverted logic of doCheckPasswordRequested. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41906) Abort Job if no change in defined branch (e.g. master)
Title: Message Title
Mark Waite edited a comment on JENKINS-41906
Re: Abort Job if no change in defined branch (e.g. master)
I'm unable to duplicate the problem you're reporting, either with a freestyle job, nor with a pipeline job. The environment I'm using to duplicate the problem can be reconstructed with the following steps:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41906 $ cd JENKINS-41906 $ git checkout -b lts-with-plugins 43617aecbb2ad5250460bdbf2c5d3b6fbdc37e94 $ docker build -t jenkins:JENKINS-41906 . $ # Copy jdk8 from Oracle to ~/public_html/jdk/jdk-8u121-linux-x64.tar.gz $ # Copy ant-1.9.8 from Apache to ~/public_html/ant/apache-ant-1.9.8-bin.zip $ docker run -i --rm --publish 8080:8080 --volume ~/public_html/:/var/jenkins_home/userContent/ jenkins:JENKINS-41906{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Bugs - Individual Checks" folder# Open the "JENKINS-41906-master-branch-builds-without-change" job# Click "Poll now" (simulate the web hook), confirm that the job builds (because it has not been built before)# Click "Poll now" (simulate the web hook again), confirm that the job *does not* build (already built)I also checked it with a pipeline job in that same Docker instance. You can see the behavior in the pipeline job with the following steps:# Open the "Bugs - Pipeline Checks" folder# Open the "jenkins-bugs" pipeline job# Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches for that repository# Confirm that a job is created and built for the "master" branch and all other branches# Wait 10-15 minutes, then Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches again for that repository. That will likely detect changes on one of the branches, since I usually have tests running somewhere that will commit to that repository# Confirm that the job named "master" did not rebuild, even though other jobs rebuilt due to changes in themCan you provide more details of the steps to duplicate the problem you're seeing? Are you using a freestyle job, a multi-configuration job, a pipeline job, a multi-branch pipeline job, or some other type of job?Are there other details of your environment which I missed in my attempt to duplicate the problem?
Add Comment
[JIRA] (JENKINS-40739) Introduce "Don't restrict users to configuring the job"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40739 Re: Introduce "Don't restrict users to configuring the job" Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages_ja.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config_ja.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-dontRestrictJobConfiguration.html src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-dontRestrictJobConfiguration_ja.html src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/8e6dceb8847e45db9cd8e73bddf0a62ce384eccb Log: Merge pull request #28 from ikedam/feature/JENKINS-40739_dontRestrictUsers JENKINS-40739 Introduce "Don't restrict job configuration" to SpecificUsersAuthorizationStrategy Compare: https://github.com/jenkinsci/authorize-project-plugin/compare/627d9cbd8583...8e6dceb8847e Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-40739) Introduce "Don't restrict users to configuring the job"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40739 Re: Introduce "Don't restrict users to configuring the job" Code changed in jenkins User: ikedam Path: src/test/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategyTest.java http://jenkins-ci.org/commit/authorize-project-plugin/428f1df220e28000cf0fded076f3d49de26393a4 Log: JENKINS-40739 Add tests for "Don't restrict job configuration" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40739) Introduce "Don't restrict users to configuring the job"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40739 Re: Introduce "Don't restrict users to configuring the job" Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java http://jenkins-ci.org/commit/authorize-project-plugin/74697ca038b8c7334cd71ffb08005cbc80610fae Log: JENKINS-40739 Add since in javadoc Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40739) Introduce "Don't restrict users to configuring the job"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40739 Re: Introduce "Don't restrict users to configuring the job" Code changed in jenkins User: ikedam Path: src/main/java/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy.java src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/Messages_ja.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config.jelly src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/config_ja.properties src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-dontRestrictJobConfiguration.html src/main/resources/org/jenkinsci/plugins/authorizeproject/strategy/SpecificUsersAuthorizationStrategy/help-dontRestrictJobConfiguration_ja.html http://jenkins-ci.org/commit/authorize-project-plugin/4a55cb3c1e21f0d4451db0246762112ebd197cc8 Log: [FIXED JENKINS-40739] Introduce "Don't restrict job configuration" to SpecificUsersAuthorizationStrategy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40739) Introduce "Don't restrict users to configuring the job"
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-40739 Introduce "Don't restrict users to configuring the job" Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41955) MaskPaswordsBuildWrapper no longer hiding Passwords
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-41955 MaskPaswordsBuildWrapper no longer hiding Passwords Change By: Mark Bidewell Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41659) Stabilise ATH
Title: Message Title Michael Neale edited a comment on JENKINS-41659 Re: Stabilise ATH Nice one - it has been much more stable. I am still not sold on the utillity of using SSE events to know a job has finished (in theory if we have assertions ti does tell us problem is at front end or backend though), but it makes for harder to diagnose failures vs a simple css wait failure. But it is also good SSE is hardened to this is great! The latest failure is due to a bad commit that caused a regression to a hidden feature that has a new test . , will be resolved shortly! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41955) MaskPaswordsBuildWrapper no longer hiding Passwords
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-41955 MaskPaswordsBuildWrapper no longer hiding Passwords Issue Type: Bug Assignee: Oleg Nenashev Components: mask-passwords-plugin Created: 2017/Feb/12 1:11 AM Environment: Jenkins 2.19.4 and 2.32.4 and Mask Passwords 2.9 Priority: Minor Reporter: Mark Bidewell The MaskPasswordsBuildWrapper for Pipeline is no longer hiding passwords in Mask Passwords 2.9. Freestyle jobs appear to work. Version 2.8 works correctly. Add Comment
[JIRA] (JENKINS-41954) REGRESSION: git repo can no longer be created due to duplicate name error
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41954 REGRESSION: git repo can no longer be created due to duplicate name error Change By: Michael Neale Sprint: iapetus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41954) REGRESSION: git repo can no longer be created due to duplicate name error
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-41954 REGRESSION: git repo can no longer be created due to duplicate name error Issue Type: Bug Assignee: Cliff Meyers Components: blueocean-plugin Created: 2017/Feb/12 1:09 AM Priority: Critical Reporter: Michael Neale master fails the ATH for the localRepo test suite due to it saying that a duplicate name exists. This regression was introduced as part of this: https://github.com/jenkinsci/blueocean-plugin/pull/768 PR recently (previous version is fine). Giving to Cliff for now as his day starts before Vivek's. I may have to disable the test suite if it blocks others (unrelated features). Add Comment
[JIRA] (JENKINS-41659) Stabilise ATH
Title: Message Title Michael Neale commented on JENKINS-41659 Re: Stabilise ATH Nice one - it has been much more stable. I am still not sold on the utillity of using SSE events to know a job has finished (in theory if we have assertions ti does tell us problem is at front end or backend though), but it makes for harder to diagnose failures vs a simple css wait failure. But it is also good SSE is hardened to this is great! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41659) Stabilise ATH
Title: Message Title Michael Neale edited a comment on JENKINS-41659 Re: Stabilise ATH Nice one - it has been much more stable. I am still not sold on the utillity of using SSE events to know a job has finished (in theory if we have assertions ti does tell us problem is at front end or backend though), but it makes for harder to diagnose failures vs a simple css wait failure. But it is also good SSE is hardened to this is great! The latest failure is due to a bad commit that caused a regression to a hidden feature that has a new test. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41936) configuration not migrated
Title: Message Title David van Laatum resolved as Fixed Version 2.55 release Jenkins / JENKINS-41936 configuration not migrated Change By: David van Laatum Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5371) Cannot push tags back
Title: Message Title jrp updated an issue Jenkins / JENKINS-5371 Cannot push tags back Change By: jrp Comment: I am another person who is the 'bacon' in our little dog's breakfast of this problem: I'm assuming this bug hasn't been silently closed in some other place with a non-obvious but perfectly acceptable fix that I couldn't find. * The documented feature doesn't show up in the product, so there is no way this is not a legitimate bug.* git publisher functionality a priori isn't coherent or commensurate, * * Even if you want to push tihs to publisher, it's also the right thing here, and it not being where it belongs is a bit of incomprehensible crazy-sauce. The workaround (which I guess would be explicitly calling git push yourself in script) is blinkered for plenty of cases, including mine.Why is this not a real bug being owned by someone actually working on it, pushing towards fix instantaneously and then making the slightly embarrassed 'oops, yeah this was dumb, sorry for the delay but my cats all died from cancer during the testing of my next major project: a 240V 3phase catnip igniter, and I've been in a bit of a funk' sort of apology for the inconvenience? I mean, has this thing really been not working for 6 years?Is there another person who should be working on it, maybe, or an escalation path it can undergo? I don't know how tihngs work around here, I'm just fascinated by what is going on.Or, I suppose, you could just remove the functionality from the documentation like a wimp. Perhaps maybe my expectations are incorrectly set: is Atlassian not a real company? Or do they not have real people who own and are responsible for this? Or, is this an loosely supported open source project with few actual people working on it: I mean, should I be like grinding through your code and fixing the degeneracy? Is that what's expected? Add Comment
[JIRA] (JENKINS-41953) printlns in shared library vars classes are ignored
Title: Message Title
David Karr created an issue
Jenkins / JENKINS-41953
printlns in shared library vars classes are ignored
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2017/Feb/11 11:35 PM
Environment:
Jenkins 2.19.2, "Pipeline: Shared Groovy Libraries" 2.4.
Priority:
Minor
Reporter:
David Karr
I'm iterating through building a Jenkins pipeline shared library, so my Jenkinsfile is a little cleaner. I'm using the following page for guidance: https://jenkins.io/doc/book/pipeline/shared-libraries/ . I first defined several methods in individual files, like "vars/methodName.groovy", with a "call()" method in the code. This works ok, and I particularly note that "println" calls in these methods are seen in the Jenkins console output. I then decided I wanted to save some state between method calls, so I added a new file in "vars" named "uslutils.groovy" that begins like this (minus some required imports): class uslutils implements Serializable { I defined some "with" methods that set a property and return this. I then wrote a "public String toString()" method in "uslutils" that looks something like this: public String toString() { println "Inside uslutils.toString()." return "[currentBuild[$ {currentBuild} ] mechIdCredentials[$ {mechIdCredentials} ] " + "baseStashURL[$ {baseStashURL} ] jobName[$ {jobName} ] codeBranch[$ {codeBranch} ] " + "buildURL[$ {buildURL} ] pullRequestURL[$ {pullRequestURL} ] qBotUserID[$ {qBotUserID} ] " + "qBotPassword[$ {qBotPassword} ]]" } Then, inside my Jenkinsfile, after setting the uslutils properties, I have the following lines: println "uslutils.qBotPassword[$ {uslutils.qBotPassword} ]" println "uslutils[$ {uslutils}]" println "uslutils.toString()[${uslutils.toString()}]" Here are corresponding
[JIRA] (JENKINS-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) The master is running on Windows Server 2012 R2. None of the remote slaves have any custom node properties, including the mac. Our newest Windows slave doesn't have Node installed on the system at all, since I was using the NodeJS Plugin as a way to reduce that install requirement. That's the slave that is working fine with the custom built workaround plugin with the Node installer 'Latest' selected. With that working, I know for sure that the problem is limited to the OSX slave. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Adam Dille updated an issue Jenkins / JENKINS-41857 Correct path for installation is not provided to system/shells (build.steps) Change By: Adam Dille Attachment: Screen Shot 2017-02-11 at 4.06.29 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41952) Exception during certificate validation "IOException: DerInputStream.getLength(): lengthTag=127, too big."
Title: Message Title Cyrille Le Clerc commented on JENKINS-41952 Re: Exception during certificate validation "IOException: DerInputStream.getLength(): lengthTag=127, too big." cc Stephen Connolly James Nord ref CJP-6364 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41952) Exception during certificate validation "IOException: DerInputStream.getLength(): lengthTag=127, too big."
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-41952 Exception during certificate validation "IOException: DerInputStream.getLength(): lengthTag=127, too big." Issue Type: Bug Assignee: Stephen Connolly Attachments: image-2017-02-11-23-28-16-074.png Components: credentials-plugin Created: 2017/Feb/11 10:29 PM Environment: On https://github.com/jenkinsci/credentials-plugin/pull/82, I run "mvn -Djenkins.version=2.7.4 hpi:run" Priority: Minor Reporter: Cyrille Le Clerc Once I fix JENKINS-41946 with https://github.com/jenkinsci/credentials-plugin/pull/82 . The certificate is properly saved (the cert details are displayed) but, when I go back to the update screen, I get an "IOException: DerInputStream.getLength(): lengthTag=127, too big" Could not load keystore java.io.IOException: DerInputStream.getLength(): lengthTag=127, too big. at sun.security.util.DerInputStream.getLength(DerInputStream.java:561) at sun.security.util.DerValue.init(DerValue.java:365) at sun.security.util.DerValue.(DerValue.java:320) at sun.security.pkcs12.PKCS12KeyStore.engineLoad(PKCS12KeyStore.java:1914) at java.security.KeyStore.load(KeyStore.java:1445) at com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl$KeyStoreSourceDescriptor.validateCertificateKeystore(CertificateCredentialsImpl.java:311) at com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl$Upl
[JIRA] (JENKINS-41906) Abort Job if no change in defined branch (e.g. master)
Title: Message Title
Mark Waite edited a comment on JENKINS-41906
Re: Abort Job if no change in defined branch (e.g. master)
I'm unable to duplicate the problem you're reporting, either with a freestyle job, nor with a pipeline job. The environment I'm using to duplicate the problem can be reconstructed with the following steps:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41906 $ cd JENKINS-41906 $ git checkout -b lts-with-plugins 43617aecbb2ad5250460bdbf2c5d3b6fbdc37e94 $ docker build -t jenkins:JENKINS-41906 . $ docker run -i --rm --publish 8080:8080 --volume ~/public_html/:/var/jenkins_home/userContent/ jenkins:JENKINS-41906{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Bugs - Individual Checks" folder# Open the "JENKINS-41906-master-branch-builds-without-change" job# Click "Poll now" (simulate the web hook), confirm that the job builds (because it has not been built before)# Click "Poll now" (simulate the web hook again), confirm that the job *does not* build (already built)I also checked it with a pipeline job in that same Docker instance. You can see the behavior in the pipeline job with the following steps:# Open the "Bugs - Pipeline Checks" folder# Open the "jenkins-bugs" pipeline job# Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches for that repository# Confirm that a job is created and built for the "master" branch and all other branches# Wait 10-15 minutes, then Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches again for that repository. That will likely detect changes on one of the branches, since I usually have tests running somewhere that will commit to that repository# Confirm that the job named "master" did not rebuild, even though other jobs rebuilt due to changes in themCan you provide more details of the steps to duplicate the problem you're seeing? Are you using a freestyle job, a multi-configuration job, a pipeline job, a multi-branch pipeline job, or some other type of job?Are there other details of your environment which I missed in my attempt to duplicate the problem?
Add Comment
[JIRA] (JENKINS-41906) Abort Job if no change in defined branch (e.g. master)
Title: Message Title
Mark Waite edited a comment on JENKINS-41906
Re: Abort Job if no change in defined branch (e.g. master)
I'm unable to duplicate the problem you're reporting, either with a freestyle job, nor with a pipeline job. The environment I'm using to duplicate the problem can be reconstructed with the following steps:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41906 $ cd JENKINS-41906 $ git checkout -b lts-with-plugins 43617aecbb2ad5250460bdbf2c5d3b6fbdc37e94 $ docker build -t jenkins:JENKINS-41906 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41906{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Bugs - Individual Checks" folder# Open the "JENKINS-41906-master-branch-builds-without-change" job# Click "Poll now" (simulate the web hook), confirm that the job builds (because it has not been built before)# Click "Poll now" (simulate the web hook again), confirm that the job *does not* build (already built)I also checked it with a pipeline job in that same Docker instance. You can see the behavior in the pipeline job with the following steps:# Open the "Bugs - Pipeline Checks" folder# Open the "jenkins-bugs" pipeline job# Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches for that repository# Confirm that a job is created and built for the "master" branch and all other branches# Wait 10-15 minutes, then Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches again for that repository. That will likely detect changes on one of the branches, since I usually have tests running somewhere that will commit to that repository# Confirm that the job named "master" did not rebuild, even though other jobs rebuilt due to changes in themCan you provide more details of the steps to duplicate the problem you're seeing? Are you using a freestyle job, a multi-configuration job, a pipeline job, a multi-branch pipeline job, or some other type of job?Are there other details of your environment which I missed in my attempt to duplicate the problem?
Add Comment
This message was sent by Atlassian JI
[JIRA] (JENKINS-41906) Abort Job if no change in defined branch (e.g. master)
Title: Message Title
Mark Waite edited a comment on JENKINS-41906
Re: Abort Job if no change in defined branch (e.g. master)
I'm unable to duplicate the problem you're reporting, either with a freestyle job, nor with a pipeline job. The environment I'm using to duplicate the problem can be reconstructed with the following steps:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41906 $ cd JENKINS-41906 $ git checkout -b lts-with-plugins 43617aecbb2ad5250460bdbf2c5d3b6fbdc37e94 $ docker build -t jenkins:JENKINS-41906 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41906{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Bugs - Individual Checks" folder# Open the "JENKINS-41906-master-branch-builds-without-change" job# Click "Poll now" (simulate the web hook), confirm that the job builds (because it has not been built before)# Click "Poll now" (simulate the web hook again), confirm that the job *does not* build (already built)I also checked it with a pipeline job in that same Docker instance. You can see the behavior in the pipeline job with the following steps:# Open the "Bugs - Pipeline Checks" folder# Open the "jenkins-bugs" pipeline job# Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches for that repository# Confirm that a job is created and built for the "master" branch and all other branches# Wait 10-15 minutes, then Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches again for that repository. That will likely detect changes on one of the branches, since I usually have tests running somewhere that will commit to that repository# Confirm that the job named "master" did not rebuild, even though other jobs rebuilt due to changes in them Can you provide more details of the steps to duplicate the problem you're seeing? Are you using a freestyle job, a multi-configuration job, a pipeline job, a multi-branch pipeline job, or some other type of job?Are there other details of your environment which I missed in my attempt to duplicate the problem?
Add Comment
This message was sent by Atlassian J
[JIRA] (JENKINS-41906) Abort Job if no change in defined branch (e.g. master)
Title: Message Title Mark Waite commented on JENKINS-41906 Re: Abort Job if no change in defined branch (e.g. master) I'm unable to duplicate the problem you're reporting, either with a freestyle job, nor with a pipeline job. The environment I'm using to duplicate the problem can be reconstructed with the following steps: Clone, build, and run the docker instance $ git clone https://github.com/MarkEWaite/docker JENKINS-41906 $ cd JENKINS-41906 $ git checkout -b lts-with-plugins 43617aecbb2ad5250460bdbf2c5d3b6fbdc37e94 $ docker build -t jenkins:JENKINS-41906 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41906 Connect a web browser to that docker instance (http://localhost:8080) Open the "Bugs - Individual Checks" folder Open the "JENKINS-41906-master-branch-builds-without-change" job Click "Poll now" (simulate the web hook), confirm that the job builds (because it has not been built before) Click "Poll now" (simulate the web hook again), confirm that the job does not build (already built) I also checked it with a pipeline job in that same Docker instance. You can see the behavior in the pipeline job with the following steps: Open the "Bugs - Pipeline Checks" folder Open the "jenkins-bugs" pipeline job Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches for that repository Confirm that a job is created and built for the "master" branch and all other branches Wait 10-15 minutes, then Click the "Scan Multibranch Pipeline" link and "Run Now" to index branches again for that repository. That will likely detect changes on one of the branches, since I usually have tests running somewhere that will commit to that repository Confirm that the job named "master" did not rebuild, even though other jobs rebuilt due to changes in them
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41867
Scanning MultiBranchProject fails with IllegalStateException
Change By:
Mark Waite
Addendum - it appears I'm wrong about the root cause. I reverted scm-api 2.0.3, switching back to scm-api 2.0.2 and see the same behavior. Sorry for the false alarm on scm-api 2.0.3. My initial attempts to bisect the problem have failed. Please ignore this bug report until I investigate further. Second addendum - this bug is not visible with the updates applied as of 10 Feb 2017, it is now obscured by the more severe bug JENKINS-41948 Initial scan of branches in a multi-branch-project fails with an IllegalStateException.Steps to duplicate the problem:# Clone, build, and run the docker instance{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41867 $ cd JENKINS-41867 $ git checkout -b lts-with-plugins dac2eebcf7afc90caf9180a9f6a6de6d98ae26b6 # -t origin/lts-with-plugins $ docker build -t jenkins:JENKINS-41867 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-41867{code}# Connect a web browser to that docker instance (http://localhost:8080)# Open the "Git Client Plugin Folder"# Open the "Git Client Branches - Maven" multi-branch job# Click the "Scan Project" link and then the "Run Now" link to start branch indexing# Click the "Log" link to view the log - stack trace will appear in that logThe problem seems to be new with scm-api 2.0.3. Prior versions of scm-api did not show the same behavior.Stack trace is:{noformat}Started by user Mark Waite[Wed Feb 08 16:59:22 MST 2017] Starting branch indexing...Creating git repository in /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c > git init /var/jenkins_home/caches/git-65641b79111589c081c788caa640559c # timeout=11Setting origin to https://github.com/MarkEWaite/git-plugin.git > git config remote.origin.url https://github.com/MarkEWaite/git-plugin.git # timeout=11Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=11using GIT_ASKPASS to set credentials intentionally invalid user and password for credentials NPE in multi-branch jobs > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneGetting remote branches...Seen branch in repository origin/2.6.xSeen branch in repository origin/3.0.0-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/masterSeen branch in repository origin/master-PR439-add-ATH-subset-to-JenkinsfileSeen branch in repository origin/master-PR463-add-git-lfsSeen branch in repository origin/master-PRxxx-move-findbugs-suppressions-into-codeSeen branch in repository origin/master-findbugs-combinedSeen branch in repository origin/master-findbugs-fixesSeen branch in repository origin/ongoing/latest-jenkins-ltsSeen branch in repository origin/ongoing/ltsSeen 10 remote branchesChecking branch master-PR463-add-git-lfsScheduled build for branch: master-PR463-add-git-lfsChecking branch ongoing/ltsChecking branch masterChecking branch master-PR439-add-ATH-subset-to-Jenki
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title Pavel Batanov commented on JENKINS-41867 Re: Scanning MultiBranchProject fails with IllegalStateException My jobs just gone after update Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41951) Ordering of exexutors across all EC2 worker (slave) nodes
Title: Message Title Scipio Africanus created an issue Jenkins / JENKINS-41951 Ordering of exexutors across all EC2 worker (slave) nodes Issue Type: Improvement Assignee: Francis Upton Components: ec2-plugin Created: 2017/Feb/11 7:37 PM Environment: Jenkins with the Amazon EC2 plugin Priority: Critical Reporter: Scipio Africanus I am using Jenkins to process small data import/export jobs. At some points of the day there are a lot (usually in the morning) at other points of the day there is nothing to do (usually at night). The Amazon EC2 plugin works perfect. Whenever Jenkins needs more processing, it fires up a new worker (slave) and starts using it. Every worker (slave) has 5 executors. However when the amount of jobs is going down, all the workers stay active. This is because the jobs are send to all (free) executors at random. This results in the fact that a group of 5 workers that have nothing to do, get 1 job like every 20 minutes, and the worker stays up unless it has been idle for 30 minutes. So if every worker gets a job at random. All workers pretty much stay online. I shut them down manually now. Instead of selecting a free executor at random, it would be an awesome feature to have the EC2 plugin order all the nodes and executors. So for example 4 nodes with 5 executors each would number from 1 to 20. Node 1 has 1 till 5, node 2 has 6 till 10, etc. etc. until the last executor on node 4 has number 20. Now when a new job comes up, this executor with the lowest number is selected. This would make sure that all the extra nodes will be terminated during quiet times, because there are no jobs for them. If a node is filled with jobs, the next is chosen automaticlly. I think this system is much more effecient with excessive calculation power.
[JIRA] (JENKINS-41066) Git clone fails if username & password embedded in VSOnline, GitHub, or Bitbucket URL
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41066 Git clone fails if username & password embedded in VSOnline, GitHub, or Bitbucket URL Change By: Mark Waite If I embed my username and personal access token into a Visual Studio Online URL, GitHub URL, or BitBucket URL, I can clone that URL from command line git on my Ubuntu Linux computer, whether logged in as myself or as an entirely different user.If I use the same URL in a Jenkins job, without specifying any other credentials, the clone fails in the Jenkins job with authorization denied. It also fails with JGit, though the error message is that authentication was not provided. Work around: If I create a credential with that same user name and personal access token, and use that credential in a job which does not include the username or password in the URL, the clone succeeds. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "J
[JIRA] (JENKINS-41066) Git clone fails if username & password embedded in VSOnline, GitHub, or Bitbucket URL
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41066 Git clone fails if username & password embedded in VSOnline, GitHub, or Bitbucket URL Change By: Mark Waite Summary: Git clone fails if username / & password embedded in VSOnline git , GitHub, or Bitbucket URL Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title Mark Waite commented on JENKINS-41867 Re: Scanning MultiBranchProject fails with IllegalStateException I no longer see this issue with the latest plugin updates. I now see JENKINS-41948 which seems to interrupt branch scanning before this condition is reached. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41867 Scanning MultiBranchProject fails with IllegalStateException Change By: Mark Waite Component/s: core Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40019) slave containers are not cleaned up.
Title: Message Title Nikola Svitlica commented on JENKINS-40019 Re: slave containers are not cleaned up. This is extremely stupid issue, until it is fixed, quick fix is to add a crontab which would do a cleanup of unwanted containers: 0 * * * * root docker rm $(docker ps -q -f status=exited -f ancestor=jenkinsci/slave) This will remove all exited containers that are jenkin slaves - every hour (you can setup yours as you like) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41867) Scanning MultiBranchProject fails with IllegalStateException
Title: Message Title Pavel Batanov commented on JENKINS-41867 Re: Scanning MultiBranchProject fails with IllegalStateException Faced the same issue java.lang.IllegalStateException: Did not call mayCreate, or used the wrong Item.name for hudson.model.FreeStyleProject@7448a801[bestapps_mapi_stage_deploy/hotfix-api-doc.pprn0n] with name hotfix-api-doc.pprn0n among [production, hotfix%2Fapi-doc, master] Tries to append .XX (pprn0n) part to the branch name Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41950) Errors in agent instantiation and checkout not surfaced if post has node-requiring steps
Title: Message Title Andrew Bayer commented on JENKINS-41950 Re: Errors in agent instantiation and checkout not surfaced if post has node-requiring steps PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/113 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41950) Errors in agent instantiation and checkout not surfaced if post has node-requiring steps
Title: Message Title Andrew Bayer updated JENKINS-41950 Jenkins / JENKINS-41950 Errors in agent instantiation and checkout not surfaced if post has node-requiring steps Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41950) Errors in agent instantiation and checkout not surfaced if post has node-requiring steps
Title: Message Title Andrew Bayer started work on JENKINS-41950 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41950) Errors in agent instantiation and checkout not surfaced if post has node-requiring steps
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-41950 Errors in agent instantiation and checkout not surfaced if post has node-requiring steps Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Feb/11 6:05 PM Priority: Critical Reporter: Andrew Bayer If there's an error in the top-level agent instantiation (say, due to a checkout failing or non-existent Docker image, etc), and the post for the build includes steps that require running on a node (such as deleteDir() or emailext), those post steps will fail and end up being the only reported errors, preventing any visibility into what actually went wrong in the agent. We need to handle those error cases better. Add Comment
[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules
Title: Message Title
Alexander Komarov edited a comment on JENKINS-41876
Re: Not respecting configuration in regards of global modules
[~nfalco] I tried your branch (feature/JENKINS-41876) and I get a different failure:FATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest"Build step 'Execute NodeJS script' marked build as failureI changed the job so it wipes out the installation preemptively, then shows the contents. Here is the output.{noformat}[test-npm] $ /bin/sh -xe /tmp/hudson9048595079863518522.sh+ rm -rf /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallationUnpacking https://nodejs.org/dist/v4.7.3/node-v4.7.3-linux-x64.tar.gz to /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest on BigMemory-Swarm-34234051b8ddFATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest"Build step 'Execute NodeJS script' marked build as failurePerforming Post build task...Match found for : : TrueLogical operation result is TRUERunning script : ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest[test-npm] $ /bin/sh -xe /tmp/hudson5550127812103304562.sh+ ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest:total 996-rwxrwxr-x 1 root root 938291 Jan 31 21:05 CHANGELOG.md-rwxrwxr-x 1 root root 54656 Jan 31 21:05 LICENSE-rwxrwxr-x 1 root root 17439 Jan 31 21:05 README.mddrwxr-xr-x 2 root root 27 Feb 11 17:42 bindrwxr-xr-x 3 root root 17 Feb 11 17:42 includedrwxr-xr-x 3 root root 25 Feb 11 17:42 libdrwxr-xr-x 5 root root 42 Feb 11 17:42 share/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin:total 24252-rwxrwxr-x 1 root root 24830187 Jan 31 21:05 nodelrwxrwxrwx 1 root root 38 Feb 11 17:42 npm -> ../lib/node_modules/npm/bin/npm-cli.js{noformat} Just for fun I also tried it outside of Docker, with a normal linux slave: same behavior.
Add Comment
[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules
Title: Message Title Alexander Komarov commented on JENKINS-41876 Re: Not respecting configuration in regards of global modules Nikolas Falco I tried your branch (feature/JENKINS-41876) and I get a different failure: FATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest" Build step 'Execute NodeJS script' marked build as failure I changed the job so it wipes out the installation preemptively, then shows the contents. Here is the output. [test-npm] $ /bin/sh -xe /tmp/hudson9048595079863518522.sh + rm -rf /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation Unpacking https://nodejs.org/dist/v4.7.3/node-v4.7.3-linux-x64.tar.gz to /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest on BigMemory-Swarm-34234051b8dd FATAL: Cannot find executable from the chosen NodeJS installation "/home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest" Build step 'Execute NodeJS script' marked build as failure Performing Post build task... Match found for : : True Logical operation result is TRUE Running script : ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest [test-npm] $ /bin/sh -xe /tmp/hudson5550127812103304562.sh + ls -Rl /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest: total 996 -rwxrwxr-x 1 root root 938291 Jan 31 21:05 CHANGELOG.md -rwxrwxr-x 1 root root 54656 Jan 31 21:05 LICENSE -rwxrwxr-x 1 root root 17439 Jan 31 21:05 README.md drwxr-xr-x 2 root root 27 Feb 11 17:42 bin drwxr-xr-x 3 root root 17 Feb 11 17:42 include drwxr-xr-x 3 root root 25 Feb 11 17:42 lib drwxr-xr-x 5 root root 42 Feb 11 17:42 share /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/bin: total 24252 -rwxrwxr-x 1 root root 24830187 Jan 31 21:05 node lrwxrwxrwx 1 root root 38 Feb 11 17:42 npm -> ../lib/node_modules/npm/bin/npm-cli.js Add Comment
[JIRA] (JENKINS-41923) Different pipeline steps are executed in different directories
Title: Message Title Andrew Bayer commented on JENKINS-41923 Re: Different pipeline steps are executed in different directories D'oh! Try adding reuseNode true to your docker - it'll then run on the same agent and workspace as the top level. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules
Title: Message Title Alexander Komarov commented on JENKINS-41876 Re: Not respecting configuration in regards of global modules Answers regarding my configuration: OS: Centos 6.8 on master. Centos 7.0 on docker slaves (both Docker kernel and docker image). I still don't see a jenkins.plugins.nodejs.tools.NodeJSInstallation.xml on either slaves or master. Attaching my job config.xml: config.xml Here are all the XML files I can find: [root@4b45a776e3ee /]# find / -xdev -name '*.xml' | grep -i node | grep tool /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/lib/node_modules/npm/node_modules/node-gyp/gyp/buildbot/aosp_manifest.xml /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-03.xml /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-4-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-04.xml /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-7-latest/lib/node_modules/npm/node_modules/node-gyp/gyp/buildbot/aosp_manifest.xml /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-7-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-03.xml /home/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs-7-latest/lib/node_modules/npm/node_modules/request/node_modules/http-signature/node_modules/jsprim/node_modules/json-schema/draft-zyp-json-schema-04.xml Add Comment
[JIRA] (JENKINS-41876) Not respecting configuration in regards of global modules
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-41876 Not respecting configuration in regards of global modules Change By: Alexander Komarov Attachment: config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41946) Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
Title: Message Title
Cyrille Le Clerc commented on JENKINS-41946
Re: Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
Strange, "com.cloudbees.plugins.credentials.SecretBytes" is supposed to register a Stapler converter: https://github.com/jenkinsci/credentials-plugin/blob/d48b986efbce992da133c4be90b35e096b693c7c/src/main/java/com/cloudbees/plugins/credentials/SecretBytes.java#L363-L363
/*
* Register a converter for Stapler form binding.
*/
static {
Stapler.CONVERT_UTILS.register(new org.apache.commons.beanutils.Converter() {
/**
* {@inheritDoc}
*/
public SecretBytes convert(Class type, Object value) {
return SecretBytes.fromString(value.toString());
}
}, SecretBytes.class);
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41947) PATH value is being overwritten in declarative pipeline syntax
Title: Message Title Nikolas Falco commented on JENKINS-41947 Re: PATH value is being overwritten in declarative pipeline syntax Some more informations? Which NodeJS Plugin version you have installed? Which version of Jenkins do you use? This job runs in master Jenkins or on a slave node? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41339) Environment variables referencing other variables broken
Title: Message Title John Mellor commented on JENKINS-41339 Re: Environment variables referencing other variables broken Confirmed, restart needed after downgrading. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41566) Reconnect ping request goes crazy
Title: Message Title Tom FENNELLY started work on JENKINS-41566 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41566) Reconnect ping request goes crazy
Title: Message Title Tom FENNELLY updated JENKINS-41566 Jenkins / JENKINS-41566 Reconnect ping request goes crazy Change By: Tom FENNELLY Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41566) Reconnect ping request goes crazy
Title: Message Title Tom FENNELLY commented on JENKINS-41566 Re: Reconnect ping request goes crazy https://github.com/jenkinsci/blueocean-plugin/pull/814 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41946) Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
Title: Message Title
Cyrille Le Clerc commented on JENKINS-41946
Re: Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
According to https://github.com/stapler/stapler/blob/stapler-parent-1.243/core/src/main/java/org/kohsuke/stapler/Stapler.java#L1093 , we need a "StaplerConverterImpl" for "com.cloudbees.plugins.credentials.SecretBytes"
public static Converter lookupConverter(Class type) {
Converter c = CONVERT_UTILS.lookup(type);
if (c!=null) return c;
// fall back to compatibility behavior
c = ConvertUtils.lookup(type);
if (c!=null)return c;
// look for the associated converter
try {
if(type.getClassLoader()==null)
return null;
Class cl = type.getClassLoader().loadClass(type.getName() + "$StaplerConverterImpl");
c = (Converter)cl.newInstance();
CONVERT_UTILS.register(c,type);
return c;
} catch (ClassNotFoundException e) {
// fall through
} catch (IllegalAccessException e) {
IllegalAccessError x = new IllegalAccessError();
x.initCause(e);
throw x;
} catch (InstantiationException e) {
InstantiationError x = new InstantiationError();
x.initCause(e);
throw x;
}
// bean utils doesn't check the super type, so converters that apply to multiple types
// need to be handled outside its semantics
if (Enum.class.isAssignableFrom(type)) { // enum
return ENUM_CONVERTER;
}
return null;
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41946) Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-41946
Re: Exception saving a certificate uploading a PKCS#12 "IllegalArgumentException: Unable to convert to class com.cloudbees.plugins.credentials.SecretBytes"
After applying [PR#81 Bump parent pom from jenkins:2.10 to jenkins:2.21|https://github.com/jenkinsci/credentials-plugin/pull/81], running "{{mvn -Djenkins.version=2.7.4 hpi:run}}", I am almost sure that there is a different get the same exception bumping following the same test path:{noformat}javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate interface com.cloudbees.plugins.credentials.Credentials from {"scope":"GLOBAL","keyStoreSource":{"value":"1","uploadedKeystore":"MIIGegIBAzCCBkAGCSqGSIb3DQEHAaCCBjEEggYtMIIGKTCCAw8GCSqGSIb3DQEHBqCCAwAwggL8AgEAMIIC9QYJKoZIhvcNAQcBMBwGCiqGSIb3DQEMAQYwDgQIlyBLvtXN5nACAggAgIICyEwxMBP/+B4slNrMNsiCwGVRCsAlbtz83hBEClpinxnYDe4BBMaDfRRRnZlWDToEOsmTkoRTJikkfFGkmhFTZO9yAz4/xgy8BoPv/uw2G1IbHu+PXSvJpOob0Xf9Y7F1EmnZ6h7IZ2Yws/qoMDiCnPds5rB4dnrrpoFzYx1dWl3yOV+G/lguOdZCmaaOLNEux0JcX/hQvK067AS7Gw0V4KMxaHQNPX4kKQrPO7+1C6hUyF1BEppjuO9zjy4LymkkNPJHvrHarkgfxrFcnIaYRQrwGNKqp2zxcbGbY29f02CIpeap14ULo6anbX/HHxc5L2TS8F1ybz/TvF/HhKT+Y3BRe61Q/81xQeAqEVwWSMJkUIXtNsRVLwkHEhr1dnnoilmZxLe7zBEf8vLoCKlH9BYKIziSmhRBBupUyTnxVZwtJ7Sx8VbzkjVbgtzmWECBrLUk5iU1oTmM7O842FoDW2uyvAR4p8nBxTHihrCG+5rDl6Vhu/d9zG98F+DK52c1locZak+tF9fN5CDHLqtUoL8tzNhHeETS8zoVJbHkoeT/gMesfUusDaj9NgTzmxN8KOZLUavJWE1GlSmVnbGrYQkrJkNNfqiwdfydrR/u16sx0VGgKsueOFVy1MMoALeMycgjX4akq1zPY5WAtCd7fg8TAaUVFiy+sQrBqR7qleCjPdCrC820FdxguzbBwxn8UEmLY3lsuAhsQi2pVQ7AT9fNFAEVwb4B/DtvZP3gYRm6MCT6ngYjU+JRa9SeZzmCgIjphWxDQm66VvZ7nxaKU+3NTATqyb9aeL7Z5hTN86tmqs6+KSKThRMFGHC3Slso1UJZbYR4EDIO/l2L+KL7CyzGyVPJhQbGrTE+7ZXjY5l0o3eFxmBkuCj5gaCc9Yrmwm/mElfjOEDerdfLusSiXSPEWkEojfGftvTBhV4lxm7c6N2ncfwh4w4wggMSBgkqhkiG9w0BBwGgggMDBIIC/zCCAvswggL3BgsqhkiG9w0BDAoBAqCCAqYwggKiMBwGCiqGSIb3DQEMAQMwDgQIgGLjHcZQ9H4CAggABIICgM+k7FcDiv5dtjmKD31ktyY4tbVDIR+c1mlfO3cz+TBWreyxiPDM+RZ6ZtGE5ltEnkKUPEBygdrBNenhylWkDwOBS0nhQxk2Ly8CjR7ilxt92NznjX6xiwbUCGfcM3VWaz4DYj0dpJ696vyMI0jB4JNZHK3y3mer+LEmXDfz/R+RTDsVo/ynE/LF00OliSijdafRt5q1u7zhYpzOfPRddj0Ycj2q8c2wuuCW5PGYyOg7/RvlY+CuBoS+Id8cj+JQm3XHpmixm4M3KGBcV2rkIIIn5kb3EVxXTdWstY37rGOXnEwooxltjy34UF9TKv7US27048Bj1YGvc8zIJzOdGQOV8WyYta30JMTQ/u7/kTc9NSBWS5PI8VQu2rKcmr2V+MQzC+VvsWUNcLqgUIogYo3vfvVJmH/eskVHT/xLbmqrjPqTtHUokYDPvhvsAOwm8zJ3hUyXnNQ9xt9kokZ5Y+cpYOueDnKK4+6bRUEailFuW0YiSx7kcr1Njb12v/VPm/P2gwzvtQfUj4CyGto90InOKIxHSkZzOlNzA58BioWOXm1dGTdEqhJExoACmKD3Hi/vWZNdLO5qLqvR2cdxcpKSmCh9wzfA8BwcmVlKGOrLRAqqlIWcRAb3QHQfKj8pIt8voZvV76+wxfUDUpk3pP9PDdz5Ae3QP2v2Z0aTaHKjLNxulbHRCwW+MSE+wOJWhIbA9bICNO7VwbrYKVNTrHjkNh2whUBwgsE2Msa0Htgs6HgbWeMbDdNUnic+9kGCPCY/nQCnqWxh6fE21notHEQZvjnn1v0zEK7DCTFp/ejWuq/3FcHIViRoRJJvlbBjKb+zKfTlTN2jgL7Hqq6V/n0xPjAXBgkqhkiG9w0BCRQxCh4IAG4AbwBuAGUwIwYJKoZIhvcNAQkVMRYEFFwJgioig3q9dDV6xo6vEGdZryR5MDEwITAJBgUrDgMCGgUABBS5aqOqUR6kIld8peywddkZ7aqH2gQIzGwG2EFFsJ4CAggA","stapler-class":"com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl$UploadedKeyStoreSource","$class":"com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl$UploadedKeyStoreSource"},"password":"changeit","id":"my-certificate","description":"my-certificate","stapler-class":"com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl","$class":"com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl"} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapl
[JIRA] (JENKINS-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Karl Shultz commented on JENKINS-41945 Re: Eventual NPE while running many concurrent declarative pipelines The standard pipelines ran overnight, and are still running this morning. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41945) Eventual NPE while running many concurrent declarative pipelines
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-41945 Eventual NPE while running many concurrent declarative pipelines Change By: Karl Shultz Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41495) Jenkins Update for plugins URL not working in 2.32.1 version
Title: Message Title ikedam commented on JENKINS-41495 Re: Jenkins Update for plugins URL not working in 2.32.1 version Cristian Uroz The problem is what made the url empty. If it occurs with some specific opearations on Jenkins GUI, it should be fixed as a bug. Let me know if you secceeded to find the steps to reproduce it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41659) Stabilise ATH
Title: Message Title Tom FENNELLY resolved as Fixed Made some fixes to the SSE client code, better handling async SSE config errors and connection errors. Also did a fair bit of SSE load testing. Created a plugin with node scripts etc for this (so we can do it again later), allowing load testing in both the browser and with the headless SSE client (used by the ATH, which uses an EventSource polyfill). See https://github.com/jenkinsci/sse-gateway-plugin/tree/master/load-test. This did uncover the bugs mentioned above, but also seems to show that the SSE mechanism is solid in terms of not dropping/leaking messages under load over a long period (spanning reconnects with store and forward on the server etc). Jenkins / JENKINS-41659 Stabilise ATH Change By: Tom FENNELLY Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41935) Publish to dropbox fails
Title: Message Title René de Groot commented on JENKINS-41935 Re: Publish to dropbox fails Can you check your Jenkins log file if there are any more exceptions related to publish-to-dropbox? Another though, does recreating the credentials have any affect? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title
Nikolas Falco edited a comment on JENKINS-41857
Re: Correct path for installation is not provided to system/shells (build.steps)
If Windows and Mac are slaves, on which OS run Jenkins master (just to reproduce your scenario)?And if works on windows slave do you have customise some node properties for mac node? To do this go to "Manage Jenkins" -> "Manage Nodes" -> select mac node -> configure and see if under Node Properties section Environment variables is checked and the variable PATH is setup there That I can see on windows slave you had install a nodejs in the system, so nodejs executable could be always available. To compare behavior windows vs mac node you should select a NodeJS version different than installed in (C:\Program Files\nodejs) and add to shell{noformat}npm --version{noformat}command to ensure that you are using the NodeJS of the selected tools and not that one installed in the system.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41495) Jenkins Update for plugins URL not working in 2.32.1 version
Title: Message Title Cristian Uroz commented on JENKINS-41495 Re: Jenkins Update for plugins URL not working in 2.32.1 version ikedam The error is not related with this plugin. It is having hudson.model.UpdateCenter.xml url for default site blank (or with a malformed url). If you want to reproduce this error just keep deafult site in that file but with an empty url. As I pointed before here: https://github.com/jenkinsci/jenkins/blob/jenkins-2.32.2/core/src/main/java/hudson/model/UpdateCenter.java#L846 Load function will scan for default site inside hudson.model.UpdateCenter.xml and if it cannot find it, will create one. If default site already exist, load function will not check further if url is valid or at least not empty. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41857) Correct path for installation is not provided to system/shells (build.steps)
Title: Message Title Nikolas Falco commented on JENKINS-41857 Re: Correct path for installation is not provided to system/shells (build.steps) If Windows and Mac are slaves, on which OS run Jenkins master (just to reproduce your scenario)? And if works on windows slave do you have customise some node properties for mac node? To do this go to "Manage Jenkins" -> "Manage Nodes" -> select mac node -> configure and see if under Node Properties section Environment variables is checked and the variable PATH is setup there Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41495) Jenkins Update for plugins URL not working in 2.32.1 version
Title: Message Title ikedam commented on JENKINS-41495 Re: Jenkins Update for plugins URL not working in 2.32.1 version Cristian Uroz Broken hudson.model.UpdateCenter.xml can cause any issue. I couldn't reproduce the issue with Jenkins 2.32.2 with updatesites-manager plugin, and I'm not sure it's actually related to updatesites-manager plugin. Please create a new ticket when you find the cause. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41495) Jenkins Update for plugins URL not working in 2.32.1 version
Title: Message Title ikedam updated an issue Jenkins / JENKINS-41495 Jenkins Update for plugins URL not working in 2.32.1 version sharat sathyanarayan "id=simpleupdatesite" means this is an issue of SimpleUpdateSite plugin. I could reproduce the issue. Uninstalling SimpleUpdateSite plugin and restarting Jenkins resolved the issue. I changed the component/s to simpleupdatesite-plugin. Change By: ikedam Component/s: simpleupdatesite-plugin Component/s: update-sites-manager-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are sub
[JIRA] (JENKINS-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-40990 Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail Change By: Daniel Beck Labels: jdk regression remoting3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title Daniel Beck commented on JENKINS-40990 Re: Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail Oleg Nenashev FYI see previous comment. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41949) ZFS features are not used in non-"SunOS" deployments
Title: Message Title Jim Klimov created an issue Jenkins / JENKINS-41949 ZFS features are not used in non-"SunOS" deployments Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Feb/11 8:56 AM Priority: Minor Reporter: Jim Klimov As discovered during research for JENKINS-41932 the libzfs.jar used in Jenkins apparently only works for systems detected as "SunOS" - Solaris and illumos spin-offs. This leaves the rest of broader OpenZFS community (*BSDs, Linux via ZoL project, etc.) without benefits of integrated Jenkins support for ZFS. Add Comment
[JIRA] (JENKINS-41932) libzfs native API changed for OpenZFS - causes crashes on newer illumos distributions
Title: Message Title Jim Klimov updated an issue Jenkins / JENKINS-41932 libzfs native API changed for OpenZFS - causes crashes on newer illumos distributions Change By: Jim Klimov Context: Jenkins.WAR ships with a libzfs-0.5.jar which gets enabled and loaded on operating systems detected as Solaris or similar, which currently is a broad family including the proprietary Oracle Solaris and various open-source distributions that appeared from the legacy of OpenSolaris and are currently based on the illumos core and its intimate relationship to the OpenZFS spin-off project, sharing code with *BSD, ZoL and perhaps (inofficial) MacOS support of ZFS.Problem: The libzfs.jar provides JNA wrapping to internal (not public, not committed) API /ABI of the native libzfs.so which is the best (only) binding there is, de-facto. Unfortunately, such non-committed APIs changed (after the split of Oracle and FOSS codebases) , ; the change happened in OpenZFS codebase about 5 years ago and when was picked back up by illumos-gate about 9 months ago - so the issue began manifesting in rolling-releases of OSes that deploy a new illumos core as commits land, so since about June 2016. When the existing JAR tries to call a native function with a wrong signature, the JVM segfaults. Currently libzfs.jar assumes that ZFS is only present on Solaris-like OSes, so the issue did not manifest in other platforms that support it in fact - but those also do not take advantage of ZFS either (this is a separate issue though).As discussed with [~ci_jenkinsci_org] at FOSDEM, there are in fact several codebases for libzfs.jar itself too - one on his github account https://github.com/kohsuke/libzfs4j (which in fact has the fix for newer ZFS API in https://github.com/kohsuke/libzfs4j/commit/05067e754e56e7249e320d86cea769c3b878aeeb ), and another at java.net ( https://java.net/projects/zfs - with older API, and so it seems to be the one shipped in Jenkins).It seems feasible and safe to detect presence of new API by querying the libzfs.so for presence of routines that support ZFS feature flags (something that Oracle ZFS will likely never have) and so assume make assumptions OpenZFS vs OracleZFS, and further assuming a recent OpenZFS - set a Java boolea flag and use the new function signature following a Java if-clause.As a fallback for cases where automagic guesses wrongly, and/or as the initial implementation, the same toggle can be done by an envvar set in the application server initscript/service. At least, this fix will hold for the lifetime of the server, across updates of Jenkins.war (currently the custom build of libzfs.jar has to be substituted as part of upgrade procedure). Another option to explore is to perhaps integrate instead with libzfs_core https://github.com/openzfs/openzfs/tree/master/usr/src/lib/libzfs_core https://www.illumos.org/issues/2882 which is AFAIK the attempt at a stable and public API/ABI to tools using and managing ZFS in OpenZFS and illumos, and maybe at libzfs_jni https://github.
[JIRA] (JENKINS-41923) Different pipeline steps are executed in different directories
Title: Message Title Roberto Fasciolo commented on JENKINS-41923 Re: Different pipeline steps are executed in different directories It's already there Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40019) slave containers are not cleaned up.
Title: Message Title Nikola Svitlica commented on JENKINS-40019 Re: slave containers are not cleaned up. Oh, this is killing us! None of the slaves does not gets cleaned up after build... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40019) slave containers are not cleaned up.
Title: Message Title Nikola Svitlica updated an issue Jenkins / JENKINS-40019 slave containers are not cleaned up. Change By: Nikola Svitlica Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title
Andreas Mandel edited a comment on JENKINS-40990
Re: Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Ok, cause is that with the new {{remoting} the causing {{UnsupportedClassVersionError}} is not part of the getCause chain of the caught {{IOException}} any more. Need to find out how the cause is reported now through the channel. The switch works fine with Jenkins core 2.26 but fails with 2.27. 2.27 introduced the new {{remoting}} 3.0.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40990) Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail
Title: Message Title Andreas Mandel updated an issue Jenkins / JENKINS-40990 Jenkins 2.27 with remoting 3.0 causes Java 5/6 Maven builds to fail Change By: Andreas Mandel Summary: Jenkins 2. 32 27 with remoting 3 . 1 0 causes Java 5/6 Maven builds to fail Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5371) Cannot push tags back
Title: Message Title Jason Pascucci commented on JENKINS-5371 Re: Cannot push tags back I am another person who is the 'bacon' in our little dog's breakfast of this problem: I'm assuming this bug hasn't been silently closed in some other place with a non-obvious but perfectly acceptable fix that I couldn't find. The documented feature doesn't show up in the product, so there is no way this is not a legitimate bug. git publisher functionality a priori isn't coherent or commensurate, * Even if you want to push tihs to publisher, it's also the right thing here, and it not being where it belongs is a bit of incomprehensible crazy-sauce. The workaround (which I guess would be explicitly calling git push yourself in script) is blinkered for plenty of cases, including mine. Why is this not a real bug being owned by someone actually working on it, pushing towards fix instantaneously and then making the slightly embarrassed 'oops, yeah this was dumb, sorry for the delay but my cats all died from cancer during the testing of my next major project: a 240V 3phase catnip igniter, and I've been in a bit of a funk' sort of apology for the inconvenience? I mean, has this thing really been not working for 6 years? Is there another person who should be working on it, maybe, or an escalation path it can undergo? I don't know how tihngs work around here, I'm just fascinated by what is going on. Or, I suppose, you could just remove the functionality from the documentation like a wimp. Perhaps maybe my expectations are incorrectly set: is Atlassian not a real company? Or do they not have real people who own and are responsible for this? Or, is this an loosely supported open source project with few actual people working on it: I mean, should I be like grinding through your code and fixing the degeneracy? Is that what's expected? Add Comment
