[JIRA] (JENKINS-58112) Triggering mulibranch pipeline from jira-trigger-plugin
Title: Message Title Krishan Hettihewa updated an issue Jenkins / JENKINS-58112 Triggering mulibranch pipeline from jira-trigger-plugin Change By: Krishan Hettihewa Issue Type: Story Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200156.1561013839000.4167.1561013880840%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering mulibranch pipeline from jira-trigger-plugin
Title: Message Title Krishan Hettihewa created an issue Jenkins / JENKINS-58112 Triggering mulibranch pipeline from jira-trigger-plugin Issue Type: Story Assignee: Wisen Tanasa Components: jira-trigger-plugin Created: 2019-06-20 06:57 Environment: Jenkins ver. 2.138.2 Priority: Major Reporter: Krishan Hettihewa I have Jenkins Mutibranch pipeline. I want to integrate my Jira with one of multibranch project. I have installed the JIRA Trigger Plugin and configured Webhook in Jira. however, when I checked in my Jenkins job it does not show me the Build when an issue is updated in JIRA but it shows when I go to View Configuration in the particular branch. it allows me to select the Build when an issue is updated in JIRA but there is no option to save the changes. I know this might be a reason the option is view only. but how can I configure this? Is anyone configured JIRA Trigger Plugin with Jenkins mutibranch project where using Jenkinsfile? and what is the correct way of integrating this? Should I do some coding in the Jenkins file to get this done?
[JIRA] (JENKINS-49351) Jacoco plugin should also run on unstable or failed builds
Title: Message Title centic resolved as Fixed Merged PR https://github.com/jenkinsci/jacoco-plugin/pull/104 this will be included in the next release of the JaCoCo plugin. Jenkins / JENKINS-49351 Jacoco plugin should also run on unstable or failed builds Change By: centic Status: Open Resolved Resolution: Fixed Released As: 3.0.5 or 3.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188217.1517649535000.
[JIRA] (JENKINS-58111) Github webhooks triggers a multibranch scan of all refs
Title: Message Title connor poole created an issue Jenkins / JENKINS-58111 Github webhooks triggers a multibranch scan of all refs Issue Type: Bug Assignee: Unassigned Components: github-api-plugin, github-branch-source-plugin, scm-api-plugin Created: 2019-06-20 04:50 Environment: jenkins 2.176.1 latest versions of all plugins in LTS Priority: Minor Reporter: connor poole Jenkins handles a monorepo well enough when using git scm with ssh clone. If we have the following repo structure: // code placeholder api-one/ Jenkinsfile api-two/ Jenkinsfile ... api-n/ Jenkinsfile We create one multibranch pipeline per Jenkinsfile in order to have many independent pipelines (CI + CD) for our projects. These projects all share common code through jenkins shared libraries and everything works ok. However, if we want to use the github branch source and want to enable webhooks from github we immediately run into rate limit issues. We have a large repository - thousands of pushes a day. Every time a webhook is fired from github and hits jenkins all N multibranch pipelines begin scanning ALL remote refs for the repository. In our repository there are 10s of thousands of tags. A single scan on a single multibranch pipeline eliminates our entire github rate limit budget. I am not entirely sure why jenkins must rescan the entire repo. It seems at the very least the webhook from github contains all information about the ref to be built and the individual jobs could simply take the w
[JIRA] (JENKINS-57119) maven-plugin random socket leak, leading to threads leak on slave and master
Title: Message Title Olivier Lamy closed an issue as Fixed Jenkins / JENKINS-57119 maven-plugin random socket leak, leading to threads leak on slave and master Change By: Olivier Lamy Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198869.1555676489000.4156.1561005240357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57119) maven-plugin random socket leak, leading to threads leak on slave and master
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-57119 maven-plugin random socket leak, leading to threads leak on slave and master Change By: Olivier Lamy Labels: maven-plugin-3.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198869.1555676489000.4152.1561005240309%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57119) maven-plugin random socket leak, leading to threads leak on slave and master
Title: Message Title Olivier Lamy updated JENKINS-57119 Jenkins / JENKINS-57119 maven-plugin random socket leak, leading to threads leak on slave and master Change By: Olivier Lamy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198869.1555676489000.4154.1561005240333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57384) Artifactory Plugin Bug - Resolve Artifacts Not Consistant
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-57384 Artifactory Plugin Bug - Resolve Artifacts Not Consistant Change By: Olivier Lamy Labels: artifactory-plugin jenkins maven-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199166.1557397706000.4150.1561005180196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58110) Move "writeFailedPluginsToFile" out of PluginManager
Title: Message Title Kristin Whetstone created an issue Jenkins / JENKINS-58110 Move "writeFailedPluginsToFile" out of PluginManager Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-20 04:10 Priority: Minor Reporter: Kristin Whetstone As something for phase 2, it would make writing failed plugins to a file something that's configurable. Certain library consumers might prefer having that as a return option instead. Add Comment This mes
[JIRA] (JENKINS-58109) Perforce ditto mappings from clientspec do not work
Title: Message Title sc1234 c updated an issue Jenkins / JENKINS-58109 Perforce ditto mappings from clientspec do not work Change By: sc1234 c Hi I use p4 plugin in my free style jenkins jobs to sync down source from our perforce server with a clientspec spec file located in depot . We use perforce [ditto mappings|[https://www.perforce.com/manuals/p4guide/Content/P4Guide/configuration.workspace_view.one-to-many.html]] in our clientspec to map few files from one to many locations. While this works on our own machines with the p4 client, it fails on our jenkins job with warning like below. Warning: Client Spec line invalid, ignoring. (&//depot/mysource/a.xml //sc1234-ws/mysource/v1/a.xml) My clientspec view file has lines like +/depot/mysource/a.xml //sc1234-ws/mysource/v1/a.xml &/depot/mysource/a.xml //sc1234-ws/mysource/v2/a.xml+/depot/mysource/b.xml //sc1234-ws/mysource/v1/b.xml &/depot/mysource/b.xml //sc1234-ws/mysource/v2/b.xml Are ditto mapping supported by this p4-plugin? And if yes, is this a bug? Please help. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58004) Localhost: Not able to connect Webhook from Bitbucket with Jenkins for automatic build for each commit.
Title: Message Title Pramin Senapati updated an issue Jenkins / JENKINS-58004 Localhost: Not able to connect Webhook from Bitbucket with Jenkins for automatic build for each commit. Change By: Pramin Senapati Summary: Localhost: Not able to connect Webhook from Bitbucket and with Jenkins for automatic build for each commit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200021.156042606.4144.1561001460211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58004) Localhost: Not able to connect Bitbucket and Jenkins for automatic build for each commit.
Title: Message Title Pramin Senapati updated an issue Jenkins / JENKINS-58004 Localhost: Not able to connect Bitbucket and Jenkins for automatic build for each commit. Change By: Pramin Senapati Summary: Localhost: Not able to connect Bitbucket and Jenkins for automatic build for each commit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200021.156042606.4138.1561001160189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58004) Localhost: Not able to connect Bitbucket for automatic build for each commit.
Title: Message Title Pramin Senapati updated an issue Jenkins / JENKINS-58004 Localhost: Not able to connect Bitbucket for automatic build for each commit. Change By: Pramin Senapati Summary: Localhost: Not able to connect Bitbucket for automatic build for each commit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200021.156042606.4136.1561001100282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58109) Perforce ditto mappings from clientspec do not work
Title: Message Title sc1234 c updated an issue Jenkins / JENKINS-58109 Perforce ditto mappings from clientspec do not work Change By: sc1234 c Hi I use p4 plugin in my free style jenkins jobs to sync down source from our perforce server with a clientspec. We use perforce [ditto mappings |[https://www.perforce.com/manuals/p4guide/Content/P4Guide/configuration.workspace_view.one-to-many.html]] in our clientspec to map few files from one to many locations. While this works on our own machines with the p4 client, it fails on our jenkins job with warning like below. Warning: Client Spec line invalid, ignoring. (&//depot/mysource/a.xml //sc1234-ws/mysource/v1/a.xml) My clientspec view file has lines like +/depot/mysource/a.xml //sc1234-ws/mysource/v1/a.xml&/depot/mysource/a.xml //sc1234-ws/mysource/v2/a.xml+/depot/mysource/b.xml //sc1234-ws/mysource/v1/b.xml&/depot/mysource/b.xml //sc1234-ws/mysource/v2/b.xml Are ditto mapping supported by this p4-plugin? And if yes, is this a bug? Please help. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com
[JIRA] (JENKINS-58109) Perforce ditto mappings from clientspec do not work
Title: Message Title sc1234 c created an issue Jenkins / JENKINS-58109 Perforce ditto mappings from clientspec do not work Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-06-20 03:18 Environment: Jenkins version 2.158 P4-Plugin version 1.9.5 Jenkins master server running on a centOS 7.3 VM. Jenkins slave launched through jenkins console. Slaves are also centos 7.3 VMs. Priority: Minor Reporter: sc1234 c Hi I use p4 plugin in my free style jenkins jobs to sync down source from our perforce server with a clientspec. We use perforce [ditto mappings |https://www.perforce.com/manuals/p4guide/Content/P4Guide/configuration.workspace_view.one-to-many.html] in our clientspec to map few files from one to many locations. While this works on our own machines with the p4 client, it fails on our jenkins job with warning like below. Warning: Client Spec line invalid, ignoring. (&//depot/mysource/a.xml //sc1234-ws/mysource/v1/a.xml) My clientspec view file has lines like +/depot/mysource/a.xml //sc1234-ws/mysource/v1/a.xml &/depot/mysource/a.xml //sc1234-ws/mysource/v2/a.xml +/depot/mysource/b.xml //sc1234-ws/mysource/v1/b.xml &/depot/mysource/b.xml //sc1234-ws/mysource/v2/b.xml Are ditto mapping supported by this p4-plugin? And if yes, is this a bug? Please help. Thanks
[JIRA] (JENKINS-58108) Jenkins is not able to connect to remote server to copy slave.jar while trying to SCP
Title: Message Title aniket khedekar created an issue Jenkins / JENKINS-58108 Jenkins is not able to connect to remote server to copy slave.jar while trying to SCP Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: jenkins logs.txt Components: remote-terminal-access-plugin, scp-plugin Created: 2019-06-20 02:53 Environment: my Jenkins ver. 2.131, is working on redhat hat linux 6. the browser is google chrome Labels: jenkins configuration Priority: Minor Reporter: aniket khedekar i have created a new node to connect to a remote server but when i launch the agent it failed with the attached error saying it cannot copy slave.jar to the home directory of the remote server. i manually tried to scp to the remote server from where the jenkins server is installed and it works using the same password and username but the jenkins agent does not gets connected to it.
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title vinoth SS commented on JENKINS-57772 Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days it makes sense, I think we need to create annotated tags would actually trigger the job build automatically. if people created the lightweight tags, you should note that the tag created date would be last commit date Note: date of tag creation for annotated tags and the date of the last commit for lightweight tags: https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/jenkins/plugins/git/GitTagSCMHead.java#L37-L38 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199719.1559261241000.4128.1560993480176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I have a strange scenario with this error. So I have jobs which are huge in size the 1st job is about 1200 lines long and it works completely fine and the 2nd job is about 850 lines and it got this error. And by removing some lines from the code worked fine. I added the same code again adding stage by stage and it worked fine again. It's the same code, same number of lines nothing changed but different behaviors. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.4071.1560991021191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58016) Move Parsing to Plugin Management CLI from Library
Title: Message Title Natasha Stopa commented on JENKINS-58016 Re: Move Parsing to Plugin Management CLI from Library Should this also include making the parsing more robust? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200036.1560455413000.4069.1560988920105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58107) Fix mvn findbugs issues
Title: Message Title Natasha Stopa started work on JENKINS-58107 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200150.1560987744000.4059.1560987780187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58107) Fix mvn findbugs issues
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58107 Fix mvn findbugs issues Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-19 23:42 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa mvn clean install throws errors unless -Dfindbugs.skip=true is added as a parameter. The findbugs issues need to be investigated and resolved. Add Comment
[JIRA] (JENKINS-58078) Clean Up Outstanding Issues from First PR of Converting Bash Script to Java
Title: Message Title Natasha Stopa updated JENKINS-58078 Pull request was merged. Jenkins / JENKINS-58078 Clean Up Outstanding Issues from First PR of Converting Bash Script to Java Change By: Natasha Stopa Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200103.1560876896000.4057.1560987600086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58078) Clean Up Outstanding Issues from First PR of Converting Bash Script to Java
Title: Message Title Natasha Stopa updated JENKINS-58078 Jenkins / JENKINS-58078 Clean Up Outstanding Issues from First PR of Converting Bash Script to Java Change By: Natasha Stopa Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200103.1560876896000.4056.1560987540077%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50095) Remoting should check the "Remoting-Minimum-Version" header when connecting to the master
Title: Message Title Jeff Thompson updated JENKINS-50095 Released in Remoting 3.32. Not yet integrated into Jenkins. Jenkins / JENKINS-50095 Remoting should check the "Remoting-Minimum-Version" header when connecting to the master Change By: Jeff Thompson Status: In Review Fixed but Unreleased Resolution: Fixed Released As: Remoting 3.32 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189103.1520712598000.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-57959 Upgrade past args4j 2.32 Change By: Jeff Thompson Comment: Remoting side is released in 3.32. Not yet included into master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4019.1560984420110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson resolved as Fixed Jenkins / JENKINS-57959 Upgrade past args4j 2.32 Change By: Jeff Thompson Status: In Progress Resolved Resolution: Fixed Released As: Remoting 3.32 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4013.1560984360388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson commented on JENKINS-57959 Re: Upgrade past args4j 2.32 Remoting side is released in 3.32. Not yet included into master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4017.1560984360470%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57959) Upgrade past args4j 2.32
Title: Message Title Jeff Thompson reopened an issue Jenkins / JENKINS-57959 Upgrade past args4j 2.32 Change By: Jeff Thompson Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199940.1560260408000.4015.1560984360421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58018) High CPU load at slave with SSH-agent running freestyle project
Title: Message Title Jeff Thompson commented on JENKINS-58018 Re: High CPU load at slave with SSH-agent running freestyle project I don't have your configuration, but I've tried a couple of different configurations to see if I can reproduce anything similar. No luck. Do you think the gmake and Makefile approach you use has any significance? I tried that on one of my configurations but I wouldn't think that would be meaningful. I'm not certain what your profiler session is showing (they can be difficult to read and this one appears to be cutoff or in a different layout than I've used before). It looks like it shows that the agent is spending quite a while blocked waiting to read, which is expected behavior. Especially if the job isn't doing anything, these threads will spend most of their time blocked waiting for input. That wouldn't cause high CPU load. You might see if you can catch the number of times the thread performs this operation, which could possibly affect CPU load. I've tried it with 2 cores and not seen any problems with CPU load. The only setup I currently have with 2 cores uses a different platform, but the code is the same. I'm sure lots of people run agents on machines with two cores. And the SSH-agent launcher is very popular. If it's a general problem we would expect to see more problem reports or others adding on here. We have seen, though, that VMs can be susceptible to weird problems, including odd load and I/O problems. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200038.1560499496000.4010.1560983940131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58106) org.apache.http.client.HttpResponseException: Not Found on jenkins.getJobs();
Title: Message Title
Vivek Selvaraj created an issue
Jenkins / JENKINS-58106
org.apache.http.client.HttpResponseException: Not Found on jenkins.getJobs();
Issue Type:
Bug
Assignee:
Karl-Heinz Marbaise
Components:
java-client-api
Created:
2019-06-19 22:20
Priority:
Minor
Reporter:
Vivek Selvaraj
jenkins-client - 0.3.8 Jenkins Server - 2.164.2 Code Snippet: jenkinsHttpClient=new JenkinsHttpClient(new URI("http://localhost:8080/jenkins"), "storedb", jenkinsHttpClient=new JenkinsHttpClient(new URI("http://10.207.140.201:8080/jenkins"), "username", "password"); System.out.println(jenkinsHttpClient.getJenkinsVersion()); jenkins = new JenkinsServer(jenkinsHttpClient); ; Map jobs = jenkins.getJobs(); error faced : org.apache.http.client.HttpResponseException: Not Foundorg.apache.http.client.HttpResponseException: Not Found at com.offbytwo.jenkins.client.validator.HttpResponseValidator.validateResponse(HttpResponseValidator.java:11) at com.offbytwo.jenkins.client.JenkinsHttpClient.get(JenkinsHttpClient.java:152) at com.offbytwo.jenkins.JenkinsServer.getJobs(JenkinsServer.java:169) at com.offbytwo.jenkins.JenkinsServer.getJobs(JenkinsServer.java:127) at com.kohls.main.JenkinsJobXMLFileStatus.main(JenkinsJobXMLFileStatus.java:25)
[JIRA] (JENKINS-58106) org.apache.http.client.HttpResponseException: Not Found on jenkins.getJobs();
Title: Message Title
Vivek Selvaraj updated an issue
Jenkins / JENKINS-58106
org.apache.http.client.HttpResponseException: Not Found on jenkins.getJobs();
Change By:
Vivek Selvaraj
jenkins-client - 0.3.8Jenkins Server - 2.164.2 Code Snippet: jenkinsHttpClient=new JenkinsHttpClient(new URI("http://localhost:8080/jenkins"), "storedb", jenkinsHttpClient=new JenkinsHttpClient(new URI("http://10.207.140.201:8080/jenkins"), "username", "password"); System.out.println(jenkinsHttpClient.getJenkinsVersion()); jenkins = new JenkinsServer(jenkinsHttpClient); ; Map jobs = jenkins.getJobs(); error faced : org.apache.http.client.HttpResponseException: Not Foundorg.apache.http.client.HttpResponseException: Not Found at com.offbytwo.jenkins.client.validator.HttpResponseValidator.validateResponse(HttpResponseValidator.java:11) at com.offbytwo.jenkins.client.JenkinsHttpClient.get(JenkinsHttpClient.java:152) at com.offbytwo.jenkins.JenkinsServer.getJobs(JenkinsServer.java:169) at com.offbytwo.jenkins.JenkinsServer.getJobs(JenkinsServer.java:127) at com.kohls.main.JenkinsJobXMLFileStatus.main(JenkinsJobXMLFileStatus.java:25)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email t
[JIRA] (JENKINS-58008) Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0
Title: Message Title Alexander Komarov edited a comment on JENKINS-58008 Re: Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0 I discovered the following through trial and error: # Freestyle Jobs are also affected and there is no workaround as for Pipeline Jobs. # The issue is caused by a client-server version mismatch. The plugin is not backwards compatible. I have plugin 8.9.0 and server 8.8.0. After downgrading the plugin (Found an old version [here|[https://www.checkmarx.com/plugins/ # ]]), the error disappeared.Lack of backwards compatibility is not intuitive in my opinion. In my company, one department maintains the server and leaves it up to each team to set up their CI. Server and client will thus have different upgrade paths, and backwards compatibility is a reasonable expectation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200025.1560433096000.4004.1560982260036%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58008) Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0
Title: Message Title Alexander Komarov edited a comment on JENKINS-58008 Re: Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0 I discovered the following through trial and error: # Freestyle Jobs are also affected and there is no workaround as for Pipeline Jobs. # The issue is caused by a client-server version mismatch. The plugin is not backwards compatible. I have plugin 8.9.0 and server 8.8.0. After downgrading the plugin (Found an old version [here|[https://www.checkmarx.com/plugins/ # ]]), the error disappeared.Lack of backwards compatibility is not intuitive in my opinion. In my company, one department maintains the server and leaves it up to each team to set up their CI. Server and client will thus have different upgrade paths, and backwards compatibility is a reasonable expectation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200025.1560433096000.4000.1560982210181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58008) Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0
Title: Message Title Alexander Komarov edited a comment on JENKINS-58008 Re: Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0 I discovered the following through trial and error: # Freestyle Jobs are also affected and there is no workaround as for Pipeline Jobs. # The issue is caused by a client-server version mismatch. The plugin is not backwards compatible. I have plugin 8.9.0 and server 8.8.0. After downgrading the plugin (Found an old version [here| [ https://www.checkmarx.com/plugins/] ] ), the error disappeared.Lack of backwards compatibility is not intuitive in my opinion. In my company, one department maintains the server and leaves it up to each team to set up their CI. Server and client will thus have different upgrade paths, and backwards compatibility is a reasonable expectation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200025.1560433096000.4002.1560982221417%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58105) Add feature for pipeline/jenkinsfile "Permission to Copy Artifact"
Title: Message Title
Jon Kelley updated an issue
Jenkins / JENKINS-58105
Add feature for pipeline/jenkinsfile "Permission to Copy Artifact"
Change By:
Jon Kelley
There is no documentation around "{color:#44}Permission to Copy Artifact{color}" in groovy.This is the construct concept/feature I would like to define in groovy JENKINS-20398 . Please add the feature, or if the API exists resolve this and maybe we can update the docs? Here's the code supporting artifact permissions. [https://github.com/jenkinsci/copyartifact-plugin/blob/581773632060e85369a030860a7698d50ad1cb9b/src/main/java/hudson/plugins/copyartifact/CopyArtifactPermissionProperty.java#L61]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200148.1560978871000.3987.1560978960548%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58105) Add feature for pipeline/jenkinsfile "Permission to Copy Artifact"
Title: Message Title
Jon Kelley updated an issue
Jenkins / JENKINS-58105
Add feature for pipeline/jenkinsfile "Permission to Copy Artifact"
Change By:
Jon Kelley
There is no documentation around "{color:#44}Permission to Copy Artifact{color}" in groovy.This is the concept/feature I would like to define in groovy JENKINS-20398. Please add the feature, or if the API exists resolve this and maybe we can update the docs? Here's the code class supporting artifact permissions.[https://github.com/jenkinsci/copyartifact-plugin/blob/581773632060e85369a030860a7698d50ad1cb9b/src/main/java/hudson/plugins/copyartifact/CopyArtifactPermissionProperty.java#L61]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200148.1560978871000.3988.1560978960604%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55270) JavaDoc for UpdateCenter.getPlugin() references hudson.util.VersionNumber but returns 404
Title: Message Title Rudolf-Walter Kiss-Szakacs updated an issue Jenkins / JENKINS-55270 JavaDoc for UpdateCenter.getPlugin() references hudson.util.VersionNumber but returns 404 Change By: Rudolf-Walter Kiss-Szakacs Component/s: core Component/s: jenkow-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196356.1545259961000.3991.1560978960696%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58105) Add feature for pipeline/jenkinsfile "Permission to Copy Artifact"
Title: Message Title Jon Kelley created an issue Jenkins / JENKINS-58105 Add feature for pipeline/jenkinsfile "Permission to Copy Artifact" Issue Type: New Feature Assignee: Unassigned Components: copyartifact-plugin Created: 2019-06-19 21:14 Priority: Minor Reporter: Jon Kelley There is no documentation around "Permission to Copy Artifact" in groovy. This is the construct I would like to define in groovy. Please add the feature, or if the API exists resolve this and maybe we can update the docs? https://github.com/jenkinsci/copyartifact-plugin/blob/581773632060e85369a030860a7698d50ad1cb9b/src/main/java/hudson/plugins/copyartifact/CopyArtifactPermissionProperty.java#L61 Add Comment
[JIRA] (JENKINS-53018) Windows slave service does not connect via JNLP4
Title: Message Title Jeff Thompson closed an issue as Not A Defect Peter Jiang, please do not re-open unrelated issues with general questions. One resource for general questions is the Jenkins user email list. Jenkins / JENKINS-53018 Windows slave service does not connect via JNLP4 Change By: Jeff Thompson Status: Reopened Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193006.1534173535000.3981.1560978300396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Mark Waite commented on JENKINS-57341 Re: Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Thanks for the reminder Jesse Glick! I'll submit the pull request for the tutorial after the index rebuild makes the changes visible to me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3979.1560976680425%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Mark Waite updated JENKINS-57341 Jenkins / JENKINS-57341 Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Change By: Mark Waite Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3972.1560976620623%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-57341 Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3975.1560976621000%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Mark Waite updated JENKINS-57341 Jenkins / JENKINS-57341 Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Change By: Mark Waite Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3971.1560976620610%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Jesse Glick commented on JENKINS-57341 Re: Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Mark Waite acc. to the issue description, you also needed to update the tutorial or something? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3969.1560976020132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I have a strange scenario with this error. So I have jobs which are huge in size the 1st job is about 1200 lines long and it works completely fine and the 2nd job is about 850 lines and it got this error. And by removing some lines from the code worked fine. I added the same code again adding stage by stage and it worked fine again. It's the same code, same number of lines nothing changed but different behaviors. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3967.1560975781789%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani updated an issue Jenkins / JENKINS-37984 org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Change By: sivanarayana baisani Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3859.1560975422878%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I have a strange scenario with this error. So I have jobs which are huge in size the 1st job is about 1200 lines long and it works completely fine and the 2nd job is about 850 lines and it got this error. And by removing some lines from the code worked fine. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3804.1560975360944%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title sivanarayana baisani commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I have a strange scenario with this error. So I have jobs which are huge in size the 1st job is about 1200 lines long and it works completely fine and the 2nd job is about 850 lines and it got this error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3802.1560975302337%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57864) Test Converted Docker Plugin Bash Script
Title: Message Title Natasha Stopa commented on JENKINS-57864 Re: Test Converted Docker Plugin Bash Script TODO: After looking at the Jenkins docker plugin-installation.sh documentation, I don't think I've tested installation plugins from the incremental repository thoroughly enough. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199826.1559753122000.3747.1560973980043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58008) Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-58008
Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0
Change By:
Alexander Komarov
The snippet generator does not display a checkbox for the generate XML option *generateXmlReport* , so the resulting snippet doesn't have it either.During job execution, the following error is raised:{noformat} [Cx-Warning]: Failed to generate HTML report: The following has evaluated to null or missing: ==> config.generateXmlReport [in template "report.ftl" at line 1583, column 32] Tip: It's the step after the last dot that caused this error, not those before it. Tip: If the failing _expression_ is known to legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the _expression_; to cover the whole _expression_, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? FTL stack trace ("~" means nesting-related): - Failed at: #if config.sastEnabled && config.gene... [in template "report.ftl" at line 1583, column 5] {noformat}Manually adding {code:java}generateXmlReport: true,{code}To the snippet resolves this issue and the report is successfully published in Jenkins. Here is the original generated snippet (all defaults):{code:java}step([$class: 'CxScanBuilder', comment: '', credentialsId: '', excludeFolders: 'test,tests,fonts,docker,datagen,testing', excludeOpenSourceFolders: '', exclusionsSetting: 'global', failBuildOnNewResults: false, filterPattern: '''!**/_cvs/**/*, !**/.svn/**/*, !**/.hg/**/*, !**/.git/**/*, !**/.bzr/**/*, !**/bin/**/*,!**/obj/**/*, !**/backup/**/*, !**/.idea/**/*, !**/*.DS_Store, !**/*.ipr, !**/*.iws,!**/*.bak, !**/*.tmp, !**/*.aac, !**/*.aif, !**/*.iff, !**/*.m3u, !**/*.mid, !**/*.mp3,!**/*.mpa, !**/*.ra,!**/*.wav, !**/*.wma, !**/*.3g2, !**/*.3gp, !**/*.asf, !**/*.asx,!**/*.avi, !**/*.flv, !**/*.mov, !**/*.mp4, !**/*.mpg, !**/*.rm, !**/*.swf, !**/*.vob,!**/*.wmv, !**/*.bmp, !**/*.gif, !**/*.jpg, !**/*.png, !**/*.psd, !**/*.tif, !**/*.swf,!**/*.jar, !**/*.zip, !**/*.rar, !**/*.exe, !**/*.dll, !**/*.pdb, !**/*.7z, !**/*.gz,!**/*.tar.gz, !**/*.tar, !**/*.gz, !**/*.ahtm, !**/*.ahtml, !**/*.fhtml, !**/*.hdm,!**/*.hdml,!**/*.hsql, !**/*.ht, !**/*.hta, !**/*.htc, !**/*.htd, !**/*.war, !**/*.ear,!**/*.htmls, !**/*.ihtml, !**/*.mht, !**/*.mhtm, !**/*.mhtml, !**/*.ssi, !**/*.stm,!**/*.stml,!**/*.ttml, !**/*.txn, !**/*.xhtm, !**/*.xhtml, !**/*.class, !**/*.iml, !Checkmarx/Reports/*.*,!**/*.xml, !**/*.xsd, !**/*.gradle, !**/*.properties,!**/*.csv, !**/*.txt,!**/*.md, !**/.gitignore, !**/*.yml, !**/*.yaml,!**/*.sh,!**/*.adoc,!**/*.css,
[JIRA] (JENKINS-58008) Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-58008 Checkmarx Jenkins plugin 8.9.0 is not backwards compatible with server 8.8.0 Change By: Alexander Komarov Summary: Checkmarx configuration Jenkins plugin 8.9.0 is missing 'generateXmlReport' in pipeline snippet generator not backwards compatible with server 8.8.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200025.1560433096000.3744.1560973380227%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58008) Checkmarx configuration is missing 'generateXmlReport' in pipeline snippet generator
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-58008 Checkmarx configuration is missing 'generateXmlReport' in pipeline snippet generator Change By: Alexander Komarov Environment: Jenkins 2.174Checkmarx plugin 8.90.1Checkmarx server 8.8. 3 0HF8 Pipeline plugin 2.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200025.1560433096000.3742.1560973320162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57929) BlueOcean steps do not appear green when they were successful when using parallel stages while still running
Title: Message Title Jon B commented on JENKINS-57929 Re: BlueOcean steps do not appear green when they were successful when using parallel stages while still running If I can find some time Ill create a repro case... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199903.1560145735000.3740.1560973020124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58008) Checkmarx configuration is missing 'generateXmlReport' in pipeline snippet generator
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-58008 Checkmarx configuration is missing 'generateXmlReport' in pipeline snippet generator Change By: Alexander Komarov Environment: Jenkins 2.174Checkmarx plugin 8.90.1 Checkmarx server 8.8.3 Pipeline plugin 2.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200025.1560433096000.3737.1560972960118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58104) Make Update Center Values Configurable
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58104 Make Update Center Values Configurable Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-19 19:28 Labels: plugin-manager Priority: Minor Reporter: Natasha Stopa The current install-plugins scripts gets the values for update centers via the following environment variables: JENKINS_UC JENKINS_UC_EXPERIMENTAL JENKINS_INCREMENTALS_REPO_MIRROR These values are currently hardcoded the the Java version of the bash script. This should be updated to support the current functionality. Add Comment
[JIRA] (JENKINS-58008) Checkmarx configuration is missing 'generateXmlReport' in pipeline snippet generator
Title: Message Title Alexander Komarov commented on JENKINS-58008 Re: Checkmarx configuration is missing 'generateXmlReport' in pipeline snippet generator I discovered the following through trial and error: Freestyle Jobs are also affected and there is no workaround as for Pipeline Jobs. The issue is caused by a client-server version mismatch. The plugin is not backwards compatible. I have plugin 8.9.0 and server 8.8.0. After downgrading the plugin (Found an old version here), the error disappeared. Lack of backwards compatibility is not intuitive in my opinion. In my company, one department maintains the server and leaves it up to each team to set up their CI. Server and client will thus have different upgrade paths, and backwards compatibility is a reasonable expectation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200025.1560433096000.3734.1560971100132%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57936
Parameters not expanded in username or password portion of https git URL
Change By:
Mark Waite
When a parameterized job attempts to use the value of the parameter as the username or password of an https based git repository URL, the git client plugindoes not expand the parameter reference. If a string parameter {{USERNAME}} and a password parameter {{PASSWORD}} are defined in either a Freestyle or a Pipeline job, references to those variables are not expanded in the username and password portion of the repository URL. {noformat}https://${USERNAME}:${PASSWORD}@github.com/${USERNAME}/secret-repo.git{noformat}becomes:{noformat}https://${USERNAME}:${PASSWORD}@github.com/MarkEWaite/secret-repo.git{noformat}Notice that the USERNAME parameter is replaced in some parts of the URL, but not in all parts of the URL. Dear Jenkins users,I'm use Jenkins 2.164.3 and trying to clone a repository with Git Plugin I get the error " authentication failed", because for some reason git plugin add "%24" in front of my password read from password parameter. I read from ticket JENKINS-20533It was an old bug of 5 years ago of very old git plugin, but now should be solved!Could you help me? Thanks.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you
[JIRA] (JENKINS-55203) Jenkins EC2 plugin prints private key contents in Jenkins log
Title: Message Title
Tilman Blumenbach updated an issue
Jenkins / JENKINS-55203
Jenkins EC2 plugin prints private key contents in Jenkins log
Change By:
Tilman Blumenbach
The Jenkins EC2 plugin prints the contents of the private key into the main jenkins log when it spins up and connects to new slaves. Please can this information be excluded from the logging.I believe the line that needs to be changed is: https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java#L278-L279Example log output given below: ``` {noformat} Dec 14, 2018 9:42:50 AM hudson.plugins.ec2.EC2Cloud logINFO: Getting keypair...Dec 14, 2018 9:42:50 AM hudson.plugins.ec2.EC2RetentionStrategy startINFO: Start requested for Jenkins Generic Agents (i-092c20a865eed9e81)Dec 14, 2018 9:42:50 AM hudson.plugins.ec2.EC2Cloud logINFO: Launching instance: i-092c20a865eed9e81Dec 14, 2018 9:42:50 AM hudson.plugins.ec2.EC2Cloud logINFO: bootstrap()Dec 14, 2018 9:42:50 AM hudson.plugins.ec2.EC2Cloud logINFO: Getting keypair...Dec 14, 2018 9:42:50 AM hudson.plugins.ec2.EC2Cloud logINFO: Using key: my-jenkins-keyf1:xf:81:b4:d4:4f:49:1f:b2:f6:2a:hg:39:77:t4:4v-BEGIN RSA PRIVATE KEY- ``` {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57936 Parameters not expanded in username or password portion of https git URL Change By: Mark Waite Component/s: git-client-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199912.1560167892000.3726.1560970684378%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57936 Parameters not expanded in username or password portion of https git URL Change By: Mark Waite When a parameterized job attempts to use the value of the parameter as the username or password of an https based git repository URL, the git client plugin Dear Jenkins users,I'm use Jenkins 2.164.3 and trying to clone a repository with Git Plugin I get the error " authentication failed", because for some reason git plugin add "%24" in front of my password read from password parameter. I read from ticket JENKINS-20533It was an old bug of 5 years ago of very old git plugin, but now should be solved!Could you help me? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199912.1560167892000.3724.1560970684347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46809) Allow sequential stages inside parallel in Declarative syntax
Title: Message Title Nick Roosevelt commented on JENKINS-46809 Re: Allow sequential stages inside parallel in Declarative syntax For what is is worth, I can't figure out if this was done, and if it was, when it was, and what version it is in or how to use it. And also, it seems like if we had the ability to have multiple pipelines for one push, that would help with all of this workload management. I would like to have nested parallelism as well as nested sequence. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185161.1505213938000.3621.1560970682164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55203) Jenkins EC2 plugin prints private key contents in Jenkins log
Title: Message Title Tilman Blumenbach assigned an issue to Tilman Blumenbach Jenkins / JENKINS-55203 Jenkins EC2 plugin prints private key contents in Jenkins log Change By: Tilman Blumenbach Assignee: Tilman Blumenbach Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196273.1544798485000.3616.1560970500225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55203) Jenkins EC2 plugin prints private key contents in Jenkins log
Title: Message Title Tilman Blumenbach started work on JENKINS-55203 Change By: Tilman Blumenbach Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196273.1544798485000.3618.1560970500251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56839) Allow disabling T2/T3 unlimited for T3 instances
Title: Message Title Tilman Blumenbach started work on JENKINS-56839 Change By: Tilman Blumenbach Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198499.1554149339000.3613.1560970200392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56839) Allow disabling T2/T3 unlimited for T3 instances
Title: Message Title Tilman Blumenbach assigned an issue to Tilman Blumenbach Jenkins / JENKINS-56839 Allow disabling T2/T3 unlimited for T3 instances Change By: Tilman Blumenbach Assignee: FABRIZIO MANFREDI Tilman Blumenbach Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198499.1554149339000.3611.1560970200360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Mark Waite updated JENKINS-57341 Jenkins / JENKINS-57341 Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3605.1560967680330%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Mark Waite updated JENKINS-57341 Jenkins / JENKINS-57341 Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3606.1560967680342%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58013) Restart From Stage link missing
Title: Message Title Sundeep Koluguri commented on JENKINS-58013 Re: Restart From Stage link missing Looks like there is a bug. I found that the button re-appears if we do the following Click on the Build number. Click on "Replay" or "Pipeline Steps" button. Click on either the Browser back button or on the Build number. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200031.1560446918000.3603.1560966720231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57341) Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11
Title: Message Title Jesse Glick commented on JENKINS-57341 Re: Plugin archetype and tutorial do Java 7 and Java 8 but not Java 11 Archetype changes released as 1.5. Typically the index gets rebuilt once a week, on Sundays IIRC. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199116.1557144976000.3600.1560966600102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58103) Fix suppressed findbugs errors
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-58103 Fix suppressed findbugs errors Issue Type: Task Assignee: Jack Shen Components: working-hours-plugin Created: 2019-06-19 17:41 Priority: Minor Reporter: Jeff Pearce SInce the dev branch is still in-process, I suppressed a few findbugs errors. We need to remove those suppressions before merging to master. Also WorkingHoursPlugin.getDisplayName was changed to return "" instead of null, since we can't make it nullable. We need to address that somehow Add Comment
[JIRA] (JENKINS-58074) Unknown user displaying in jenkins for commits
Title: Message Title chintu chintu assigned an issue to Erina Gomi Jenkins / JENKINS-58074 Unknown user displaying in jenkins for commits Change By: chintu chintu Assignee: Erina Gomi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200098.156087171.3596.1560965220392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-57936 Parameters not expanded in username or password portion of https git URL Change By: Mark Waite Summary: Git plugin Parameters not expanded in username or password bug portion of https git URL Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199912.1560167892000.3589.1560964620238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58101) jenkins slowdown with many offline nodes
Title: Message Title
Märt Bakhoff updated an issue
Jenkins / JENKINS-58101
jenkins slowdown with many offline nodes
Change By:
Märt Bakhoff
Having a large number of offline executors causes massive slowdown in hudson.model.Queue. The maintain method is holding the queue lock over 80% of the time in some cases.{noformat}"AtmostOneTaskExecutor[Periodic Jenkins queue maintenance] java.lang.Thread.State: RUNNABLEat org.jenkinsci.plugins.durabletask.executors.ContinuedTask$Scheduler.canTake(ContinuedTask.java:66)at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:278)at hudson.model.Queue.maintain(Queue.java:1616)at hudson.model.Queue$1.call(Queue.java:325)at hudson.model.Queue$1.call(Queue.java:322){noformat}Steps to reproduce:# install jenkins + job-dsl-plugin + matrix-project-plugin + ssh-slaves-plugin + workflow-durable-task-step (Pipeline: nodes and processes)# create a ssh node with 500 executors , add some random labels "a b c d e f g h i" # mark the node offline using configure->availability->"bring online according to schedule"# create the jobs using job dsl below# wait for the jobs to start, observe the sluggish queue, fire up jvisualvm to analyze{code}configs = []for (int i = 0; i < 100; i++) { configs.add(String.valueOf(i))}for (int i = 0; i < 10; i++) { matrixJob("matrix-"+i) {axes { text('cfg', configs)}triggers { cron('* * * * *')}steps { shell('sleep 30')} }}{code}It seems each "parked executor" causes a Queue$JobOffer to be created, which is turn triggers some getCauseOfBlockage analysis. This seems to do blockedItems * buildableItems operations which can get quite slow for a large job queue. How it was found: We have ~80 nodes with 10 executors each. We took half of them offline during a hardware migration. Soon our jobs filled the queue with 2000 items. Jenkins started timing out due to queue lock contention - a single maintain() call took around 60sec.
Add Comment
[JIRA] (JENKINS-58094) mTLS client certificates broken in 2.176.1+ by changes in jetty
Title: Message Title
joe miller updated an issue
Jenkins / JENKINS-58094
mTLS client certificates broken in 2.176.1+ by changes in jetty
Change By:
joe miller
Client certificate support is broken in 2.176.1+ by changes in Jetty.When running jenkins with winstone/jetty configured to require client cert auth most (all?) client certs will fail validation with an error such as:{noformat}java.security.cert.CertificateException: No subject alternative names matching IP address x.x.x.x.x found{noformat}This error message is only visible if debug logging is enabled: JAVA_OPTS= -Djavax.net.debug=ssl:handshakeWe have tracked this down to the Winstone 5.2 upgrade in 2.176.1 ([https://github.com/jenkins-infra/jenkins.io/blob/master/content/_data/changelogs/lts.yml#L2518]) which in turn was caused by a change in jetty 9.4.15+The summary of the issue is that Jetty changed the default behavior of their SslContextFactory to improve cert verification for their HttpClient implementation. Since both the Http server and client functions in jetty use the same SslContextFactory this broke the https server use case. There are several bug/issue reports against the Jetty project for this: * [https://github.com/eclipse/jetty.project/issues/3454] * [https://github.com/eclipse/jetty.project/issues/3554]Jetty decided to address this bug by creating SslContextFactory.Server and .Client subclasses in v9.4.18+. But the broken behavior remains in the parent SslContextFactory which is what winstone is using: [https://github.com/eclipse/jetty.project/pull/3480] There are several bug/issue reports against the Jetty project for this: * [https://github.com/eclipse/jetty.project/issues/3454] * [https://github.com/eclipse/jetty.project/issues/3554] It appears that there are two possible fixes in winstone: # Switch from using SslContextFactory -> SslContextFactory.Server # or, set endpointIdentificationAlgorithm to "null" in the existing use of SslContextFactoryHere is an example from the apache/felix project of how they fixed this bug by switching to the new . Server factory subclass introduced by jetty #3480 (v9.4.18+): [https://github.com/apache/felix/pull/199/files]I have been unable to find a workaround for this such as setting the "endpointIdentificationAlgorithm" property to 'null' using JAVA_OPTS. The only fix we've found is to pin our use of jenkins to v2.164.3
[JIRA] (JENKINS-58102) GlobalAnnotator does not annotate lines that are part of a multi-line color sequence
Title: Message Title Basil Crow commented on JENKINS-58102 Re: GlobalAnnotator does not annotate lines that are part of a multi-line color sequence Jesse Glick This is possibly related to the html.startsWith logic in GlobalAnnotator. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200145.1560960833000.3585.1560961140106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58102) GlobalAnnotator does not annotate lines that are part of a multi-line color sequence
Title: Message Title
Basil Crow created an issue
Jenkins / JENKINS-58102
GlobalAnnotator does not annotate lines that are part of a multi-line color sequence
Issue Type:
Bug
Assignee:
Steven G Brown
Components:
timestamper-plugin
Created:
2019-06-19 16:13
Environment:
timestamper 1.9 ansicolor 0.6.2 pipeline-build-step 2.9 pipeline-github-lib 1.0 pipeline-githubnotify-step 1.0.4 pipeline-graph-analysis 1.10 pipeline-input-step 2.10 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.9 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.9 pipeline-model-extensions 1.3.9 pipeline-rest-api 2.11 pipeline-stage-step 2.3 pipeline-stage-tags-metadata 1.3.9 pipeline-stage-view 2.11 pipeline-utility-steps 2.3.0 workflow-aggregator 2.6 workflow-api 2.35 workflow-basic-steps 2.18 workflow-cps 2.70 workflow-cps-global-lib 2.13 workflow-durable-task-step 2.31 workflow-job 2.32 workflow-multibranch 2.21 workflow-scm-step 2.9 workflow-step-api 2.20 workflow-support 3.3
Priority:
Minor
Reporter:
Basil Crow
Steps to reproduce 1. Install timestamper 1.9 and ansicolor 0.6.2. 2. Set the global option to enable timestamps for all Pipeline builds. 3. Create a job with a console log as follows, and view the console in the classic UI.
[2019-06-18T19:59:27.250Z] ^[[32mDone resetting Postgres targets^[[39m
[2019-06-18T19:59:27.250Z] ^[[34m# vm.example.com:
[2019-06-18T19:59:27.250Z] Could not fetch logs: Error while executing command: "awk 'BEGIN { CAPTURE="Could not fetch logs: Error while executing command: "grep -c "Starting initial_setup_tests.test_developer_reset
[JIRA] (JENKINS-57936) Git plugin password bug
Title: Message Title
Mark Waite edited a comment on JENKINS-57936
Re: Git plugin password bug
Thanks for the steps. I've confirmed that the bug can be duplicated. Steps I took:# Define a parameterized job with two parameters, a String parameter {{USERNAME}} with default value {{MarkEWaite}} and a Password parameter {{PASSWORD}} with default value of a newly created GitHub personal access token# Define the git repository for that job as {{https://${USERNAME}:${PASSWORD}@github.com/${USERNAME}/jenkins-bugs-private}}# Run the jobThe job fails and provides the following output:{noformat}No credentials specified > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://%24{USERNAME}:%24{PASSWORD}@github.com/MarkEWaite/jenkins-bugs-private # timeout=10Fetching upstream changes from https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private > git --version # timeout=10 > git fetch --no-tags --force --progress https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private +refs/heads/master:refs/remotes/origin/master # timeout=10ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1119) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1150) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --force --progress https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private +refs/heads/master:refs/remotes/origin/master" returned status code 128:stdout: stderr: remote: Invalid username or password.fatal: Authentication failed for 'https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2298) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1910) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:488) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to testing-a-jagent at hudson.remoting.Cha
[JIRA] (JENKINS-48420) Provide lightweight checkout capability for Subversion
Title: Message Title Philip Steiner commented on JENKINS-48420 Re: Provide lightweight checkout capability for Subversion Robert Orrock Yes it did! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187018.151260504.3558.1560960720835%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58101) jenkins slowdown with many offline nodes
Title: Message Title
Märt Bakhoff updated an issue
Jenkins / JENKINS-58101
jenkins slowdown with many offline nodes
Change By:
Märt Bakhoff
Having a large number of offline executors causes massive slowdown in hudson.model.Queue. The maintain method is holding the queue lock over 80% of the time in some cases.{noformat}"AtmostOneTaskExecutor[Periodic Jenkins queue maintenance] java.lang.Thread.State: RUNNABLEat org.jenkinsci.plugins.durabletask.executors.ContinuedTask$Scheduler.canTake(ContinuedTask.java:66)at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:278)at hudson.model.Queue.maintain(Queue.java:1616)at hudson.model.Queue$1.call(Queue.java:325)at hudson.model.Queue$1.call(Queue.java:322){noformat}Steps to reproduce:# 1) install jenkins + job-dsl-plugin + matrix-project-plugin + ssh-slaves-plugin + workflow-durable-task-step (Pipeline: nodes and processes)# create a ssh node with 500 executors# mark the node offline using configure->availability->"bring online according to schedule"# create the jobs using job dsl below# wait for the jobs to start, observe the sluggish queue, fire up jvisualvm to analyze{code}configs = []for (int i = 0; i < 100; i++) { configs.add(String.valueOf(i))}for (int i = 0; i < 10; i++) { matrixJob("matrix-"+i) {axes { text('cfg', configs)}triggers { cron('* * * * *')}steps { shell('sleep 30')} }}{code}It seems each "parked executor" causes a Queue$JobOffer to be created, which is turn triggers some getCauseOfBlockage analysis. This seems to do blockedItems * buildableItems operations which can get quite slow for a large job queue. How it was found: We have ~80 nodes with 10 executors each. We took half of them offline during a hardware migration. Soon our jobs filled the queue with 2000 items. Jenkins started timing out due to queue lock contention - a single maintain() call took around 60sec.
Add Comment
[JIRA] (JENKINS-58101) jenkins slowdown with many offline nodes
Title: Message Title Märt Bakhoff created an issue Jenkins / JENKINS-58101 jenkins slowdown with many offline nodes Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-19 16:06 Environment: linux java8 x64, jenkins 2.176.1, workflow-durable-task-step 2.30 Priority: Minor Reporter: Märt Bakhoff Having a large number of offline executors causes massive slowdown in hudson.model.Queue. The maintain method is holding the queue lock over 80% of the time in some cases. "AtmostOneTaskExecutor[Periodic Jenkins queue maintenance] java.lang.Thread.State: RUNNABLE at org.jenkinsci.plugins.durabletask.executors.ContinuedTask$Scheduler.canTake(ContinuedTask.java:66) at hudson.model.Queue$JobOffer.getCauseOfBlockage(Queue.java:278) at hudson.model.Queue.maintain(Queue.java:1616) at hudson.model.Queue$1.call(Queue.java:325) at hudson.model.Queue$1.call(Queue.java:322) Steps to reproduce: #1) install jenkins + job-dsl-plugin + matrix-project-plugin + ssh-slaves-plugin + workflow-durable-task-step (Pipeline: nodes and processes) create a ssh node with 500 executors mark the node offline using configure->availability->"bring online according to schedule" create the jobs using job dsl be
[JIRA] (JENKINS-57936) Git plugin password bug
Title: Message Title
Mark Waite commented on JENKINS-57936
Re: Git plugin password bug
Thanks for the steps. I've confirmed that the bug can be duplicated. Steps I took:
Define a parameterized job with two parameters, a String parameter USERNAME with default value MarkEWaite and a Password parameter PASSWORD with default value of a newly created GitHub personal access token
Define the git repository for that job as https://${USERNAME}:${PASSWORD}@github.com/${USERNAME}/jenkins-bugs-private
Run the job
The job fails and provides the following output:
No credentials specified
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://%24{USERNAME}:%24{PASSWORD}@github.com/MarkEWaite/jenkins-bugs-private # timeout=10
Fetching upstream changes from https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private
> git --version # timeout=10
> git fetch --no-tags --force --progress https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private +refs/heads/master:refs/remotes/origin/master # timeout=10
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:904)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1119)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1150)
at hudson.scm.SCM.checkout(SCM.java:504)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1818)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.plugins.git.GitException: Command "git fetch --no-tags --force --progress https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private +refs/heads/master:refs/remotes/origin/master" returned status code 128:
stdout:
stderr: remote: Invalid username or password.
fatal: Authentication failed for 'https://%24{USERNAME}@github.com/MarkEWaite/jenkins-bugs-private/'
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2298)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1910)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:488)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Reques
[JIRA] (JENKINS-39824) Plugin does not work with read-only perforce replica
Title: Message Title Karl Wirth commented on JENKINS-39824 Re: Plugin does not work with read-only perforce replica Only just seen above comment. I beleive it's the revert that is blocking this. Note: Review builds are also not allowed on build-servers because the do not support unshelving: p4 unshelve -f -s568 -cdefault Replica does not support this command. P4JAVA: Replica does not support this command. P4 Task: attempt: 1 ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s): P4JAVA: Replica does not support this command. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176419.1479389338000.3504.1560958560148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Ashwin Y commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script hello, Is there any solution or workaround for this? This is open from last 3 months !! Please provide some solution to this.. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3450.1560958261140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58100) sshagent doesn't get the private key correctly from credential
Title: Message Title
ghost ghost created an issue
Jenkins / JENKINS-58100
sshagent doesn't get the private key correctly from credential
Issue Type:
Bug
Assignee:
Unassigned
Components:
ssh-agent-plugin
Created:
2019-06-19 15:28
Priority:
Blocker
Reporter:
ghost ghost
when i use physique private key stocked on my server the ssh connection is well done , but when i use sshagent to get the private key form the credential which have the same key (allready verified) the connection is failed. /!\ i'm using sshagent in the groovy pipeline because i need to use differents credentials : stage { steps { sshagent (credentials: ['f6cd2c20-74c6-48c1-b728-cce2b7c99687']) { dir("${PLAY_PATH}") { ansiblePlaybook( colorized: true, installation: 'ansible', playbook: 'deploy_dc.yaml', hostKeyChecking: false, extras: '-', extraVars: [ USER: "${USER_ID}", application: "${Application}" ] ) } } } } ERROR: ssh-agent] Using credentials jenkins [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-YIpaWLmGXvTs/agent.96914 SSH_AGENT_PID=96918 Running ssh-add (command line suppressed) Identity added: /app/list/jenkins/workspace/VFI_SILO1_ETAT_TEST@tmp/private_key_5247074270144721685.key (/app/list/jenkins/workspace/VFI_SILO1_ETAT_TEST@tmp/private_key_5247074270144721685.key) [ssh-agent] Started. [Pipeline] { [Pipeline] dir Running in /app/list/ansible/Ansible [Pipeline] { [Pipeline] ansiblePlaybook [AnsibleCAGIP] $ ansible-play
[JIRA] (JENKINS-58099) Stage View doesn't appears
Title: Message Title
ghost ghost created an issue
Jenkins / JENKINS-58099
Stage View doesn't appears
Issue Type:
Bug
Assignee:
Unassigned
Components:
status-view-plugin
Created:
2019-06-19 15:24
Environment:
linux red7
Labels:
jenkins
Priority:
Major
Reporter:
ghost ghost
My problème is, when i launch the build,the block of stage view doesn't appears to show me the state oh every stage, i need to go to the console eveyr time to see the logs i installed the plugin "Pipeline Stage View version 2.11, And i created a differents stages: pipeline { agent any options { ansiColor('xterm') } environment { PLAY_NAME = 'PLAY' PLAY_PATH = "/app/list/ansible/Ansible" } stages { stage('preserve build user') { steps { wrap([$class: 'BuildUser']) { script { USER_ID = "${BUILD_USER_ID}" } } echo "${USER_ID}" } } stage("kerberos") { steps { sh 'echo ${Kerberos} | /usr/share/centrifydc/kerberos/bin/kinit -C ${USER_ID}'
[JIRA] (JENKINS-56502) xunit thresholds may have a bug in parallel pipeline runs
Title: Message Title Nikolas Falco closed an issue as Cannot Reproduce Jenkins / JENKINS-56502 xunit thresholds may have a bug in parallel pipeline runs Change By: Nikolas Falco Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198109.1552307085000.3446.1560957780344%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58030) TFS plugin failing in Jenkins
Title: Message Title prav teja updated an issue Jenkins / JENKINS-58030 TFS plugin failing in Jenkins Change By: prav teja Hello Olivier David , Hope you are doing good. We are facing some Jenkins TFS plugin issue from TFS (2015) to trigger the Release post build. I see we are facing some authenticator issues which says invalid credential with 401 status code. I have although tried connecting to one of the Azure devops instance, using the same TFS plugin and it works fine. Need some suggestion, to work that Jenkins TFS plugin from TFS 2015. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199979.1560368858000.3442.1560955621958%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58030) TFS plugin failing in Jenkins
Title: Message Title prav teja edited a comment on JENKINS-58030 Re: TFS plugin failing in Jenkins Thanks Olivier for the reply. [~dastahel] please assist this issue for us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199979.1560368858000.3440.1560955320098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58098) Fix commented out tests in dev branch
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-58098 Fix commented out tests in dev branch Issue Type: Task Assignee: Jack Shen Components: working-hours-plugin Created: 2019-06-19 14:40 Priority: Major Reporter: Jeff Pearce In order to build the dev branch, we had to comment out some tests which fail due to refactoring. We need to fix those tests before we can merge to master Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58030) TFS plugin failing in Jenkins
Title: Message Title prav teja commented on JENKINS-58030 Re: TFS plugin failing in Jenkins Thanks Olivier for the reply. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199979.1560368858000.3436.1560955200608%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53018) Windows slave service does not connect via JNLP4
Title: Message Title Peter Jiang reopened an issue Hello, I am new to Jenkins. I can download the slave.jar, but I don't know how to deal with this slave.jar file, i.e., where i should place into, how to run to update the old slave.jar, and where is the location of old slave.jar. Can you please help me out? Much appreciate! Jenkins / JENKINS-53018 Windows slave service does not connect via JNLP4 Change By: Peter Jiang Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193006.1534173535000.3433.1560955080840%40Atlassian.JIRA. For more options, visit https://groups.go
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title
Timo Sand commented on JENKINS-53912
Re: Unable to use SSHCheckoutTrait
Liam Newman The same issue with trying to use { { originPullRequestDiscoveryTrait } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194446.1538670788000.3427.1560955021478%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title
Timo Sand edited a comment on JENKINS-53912
Re: Unable to use SSHCheckoutTrait
[~bitwiseman] The same issue with trying to use \ { { code:java} originPullRequestDiscoveryTrait {code } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194446.1538670788000.3429.1560955021751%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53018) Windows slave service does not connect via JNLP4
Title: Message Title Peter Jiang commented on JENKINS-53018 Re: Windows slave service does not connect via JNLP4 Hello, I am new to Jenkins. I can download the slave.jar, but I don't know how to deal with this slave.jar file, i.e., where i should place into, how to run to update the old slave.jar, and where is the location of old slave.jar. Can someone please help me out? Much appreciate! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193006.1534173535000.3423.1560954420389%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58097) The slave agent is not able to connect to master after disabled JNLP2 protocol
Title: Message Title Peter Jiang created an issue Jenkins / JENKINS-58097 The slave agent is not able to connect to master after disabled JNLP2 protocol Issue Type: Improvement Assignee: Unassigned Components: _unsorted Created: 2019-06-19 14:25 Labels: jenkins Priority: Major Reporter: Peter Jiang After I disabled the deprecated "Inbound TCP Agent Protocol/2" on our server but only checked in "Inbound TCP Agent Protocol/4", it seems like the Windows slave service cannot connect with JNLP4. The log says: Jun 15, 2019 4:30:37 PM hudson.remoting.jnlp.Main$CuiListener errorJun 15, 2019 4:30:37 PM hudson.remoting.jnlp.Main$CuiListener errorSEVERE: The server rejected the connection: Disabled protocol:Protocol:JNLP2-connectjava.lang.Exception: The server rejected the connection: Disabled protocol:Protocol:JNLP2-connect at hudson.remoting.Engine.onConnectionRejected(Engine.java:306) at hudson.remoting.Engine.run(Engine.java:276) Both of my master and slave agent machine runs same Java version 1.8.0_77. My jenkins version is 2.176.1. I read a post online (URL: https://issues.jenkins-ci.org/browse/JENKINS-53018?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel), someone said "I managed to figure out why our machine couldn't connect with JNLP4. By default the slave.jar file on Windows is not updated automatically. After manually downloading the file and putting it in the right place our WIndows slave happily connects using JNLP4." I can download the slave.jar, but I don't know how to deal with this slave.jar file, i.e., where i should place into, how to run to update the old slave.jar, and where is the location of old slave.jar. I am new to Jenkins, hope someone can help me out. Much appreciate! Also, it would be great if that could be fixed so that eve
[JIRA] (JENKINS-58014) Parallel Build with List not working as expected
Title: Message Title gourav sharma commented on JENKINS-58014 Re: Parallel Build with List not working as expected never mind , its working fine now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200032.1560449175000.3419.1560954300148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58014) Parallel Build with List not working as expected
Title: Message Title gourav sharma updated JENKINS-58014 Jenkins / JENKINS-58014 Parallel Build with List not working as expected Change By: gourav sharma Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200032.1560449175000.3418.1560954300119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58096) Authorize Project plugin not working for pipeline
Title: Message Title
Mike Marcucilli created an issue
Jenkins / JENKINS-58096
Authorize Project plugin not working for pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
authorize-project-plugin
Created:
2019-06-19 14:20
Environment:
Windows Server 2012 R2
Priority:
Major
Reporter:
Mike Marcucilli
When I run a pipeline build with the Authorization set to either "Run as User who Triggered Build" or "Run as Specific User", the commands still execute as the account my Jenkins service is running as (hps\svcBuildAdmin). The below script demonstrates the problem
pipeline {
agent any
stages {
stage ('Check User') {
steps {
bat "whoami"
}
}
}
}
Output:
Started by user Michael Marcucilli
Running as Michael Marcucilli
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in C:\Program Files (x86)\Jenkins\workspace\ApplicationADSyncer-Deploy
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Check User)
[Pipeline] bat
C:\Program Files (x86)\Jenkins\workspace\ApplicationADSyncer-Deploy>whoami
hps\svcbuildadmin
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
[JIRA] (JENKINS-58095) Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes
Title: Message Title Jim Klimov updated an issue Jenkins / JENKINS-58095 Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes Change By: Jim Klimov I am trying to make our internal build farm more dynamic than a set of predefined SSH agents, and swarm client is quite a successful replacement for us.We do however miss some of the generic agents' configurability that we need as different workers are used for different cases.One such item is ability to pass Environment variables (and/alternately to Prepare jobs environment, from EnvInject plugin) as part of the swarm client's configuration, perhaps from file handling similar to what is now done for labels. We need it to set up proxies, paths, etc. as applicable to this or that agent deployment. At least, for this half of of the problem we can export the fixed variables from the wrapper script (service method) which starts the swarm client for us, as a workaround. We can not change the definitions without restarting the client, however. The other problem is harder to work around: restriction of jobs executions, at least the option to filter by regex of the job name(s). We have use-cases where node labels are good, and some cases where they come short (e.g. we don't want or can't change a node label definition in an experimental project branch, but want that branch practically built on dedicated workers and not intermix with master development - filtering by full-jobname regex supported this use-case well). Add Comment
[JIRA] (JENKINS-58095) Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes
Title: Message Title Jim Klimov created an issue Jenkins / JENKINS-58095 Add support for configurable "Restrict jobs execution at node" and "Environment variables" equivalent of generic nodes Issue Type: New Feature Assignee: Unassigned Components: swarm-plugin Created: 2019-06-19 14:17 Priority: Major Reporter: Jim Klimov I am trying to make our internal build farm more dynamic than a set of predefined SSH agents, and swarm client is quite a successful replacement for us. We do however miss some of the generic agents' configurability that we need as different workers are used for different cases. One such item is ability to pass Environment variables (and/alternately to Prepare jobs environment, from EnvInject plugin) as part of the swarm client's configuration, perhaps from file handling similar to what is now done for labels. We need it to set up proxies, paths, etc. as applicable to this or that agent deployment. At least, for this half of of the problem we can export the fixed variables from the wrapper script (service method) which starts the swarm client for us, as a workaround. The other problem is harder to work around: restriction of jobs executions, at least the option to filter by regex of the job name(s). We have use-cases where node labels are good, and some cases where they come short (e.g. we don't want or can't change a node label definition in an experimental project branch, but want that branch practically built on dedicated workers and not intermix with master development - filtering by full-jobname regex supported this use-case well).
