[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title trinadh teegala assigned an issue to Alex Earl Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: trinadh teegala Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202172.1569500879000.6415.1569563580180%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson created an issue Jenkins / JENKINS-59557 Support Gitea required status checks Issue Type: Improvement Assignee: Unassigned Components: gitea-plugin Created: 2019-09-27 05:23 Labels: plugin Priority: Major Reporter: David Svantesson Gitea now supports [required status checks before merge|https://github.com/go-gitea/gitea/pull/7481] and will be available in next release (Gitea 1.10.0). However because the Gitea plugin reports status checks with the context "Pipeline/PR-#" it is not possible to choose a required status check because it will alter for each PR. The number in the end should be removed from the reported context, or at least give the option to doing so. Add Comment
[JIRA] (JENKINS-59543) Unable to provision slaves due to network interface and subnet ID both being set
Title: Message Title Derek Ellis commented on JENKINS-59543 Re: Unable to provision slaves due to network interface and subnet ID both being set Encountered same issue, confirming plugin downgrade from 1.46 to 1.45 was able to unblock EC2 plugin usage. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202173.1569501392000.6396.1569551400197%40Atlassian.JIRA.
[JIRA] (JENKINS-59257) [Git publisher error] Tag to push name could not aware jenkins variable
Title: Message Title nicolas choi commented on JENKINS-59257 Re: [Git publisher error] Tag to push name could not aware jenkins variable please anybody help this Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201724.1567745391000.6393.1569550920220%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Daniel Beck started work on JENKINS-59552 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202183.1569511656000.6389.1569543360339%40Atlassian.JIRA.
[JIRA] (JENKINS-58770) Reconsider GAV scheme
Title: Message Title Jesse Glick updated JENKINS-58770 Jenkins / JENKINS-58770 Reconsider GAV scheme Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201075.156467412.6386.1569542820238%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title Adam Smith commented on JENKINS-59556 Re: Global Pipeline shared library version "now" fails when using Helix Library I may have mistitled this ticket. Digging in further: any version number I use produces the same error. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202188.156953784.6377.1569540480048%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP Experimentally the proposal from the previous comment seems to work well enough. Right now I'm doing a "fake" request rooted in the nearest Ancestor that's an AccessControlled + its restOfPath (which will point to a file served by the DBS). I'm still passing the real request and response, so need to prevent the response from being written to by setting a ThreadLocal flag to not write output by DBS. Seems super fragile, and I probably want a dummy HttpServletResponse so the real one cannot be messed up this way. Alternatively, I may be able to use this mechanism to write the actual response. That way, I wouldn't even have to store magic DBS instances, just the URL of the DBS, its nearest AccessControlled / restOfPath, and similar metadata. In that case I'll need to make sure to always request the correct file. Right now, it's whatever file was requested for the "main" request that redirected from the regular URL to the resource URL, since I only use it for the permission check. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.178741.1486645144000.6372.1569538080197%40Atlassian.JIRA.
[JIRA] (JENKINS-59556) Global Pipeline shared library version "now" fails when using Helix Library
Title: Message Title
Adam Smith created an issue
Jenkins / JENKINS-59556
Global Pipeline shared library version "now" fails when using Helix Library
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-09-26 22:44
Environment:
Jenkins 2.176.3 P4 Plugin 1.10.3
Priority:
Minor
Reporter:
Adam Smith
I've tried several configurations of the Helix Library Modern SCM to configure my shared library, all to no avail. Name: SampleLibrary Path: //libraries/sample (or //libraries/sample/... as documented, however the logs seem to show this being appended automagically) Default Version: now (also tried head, master) Load Implicitly: false Allow version override: false (or true) Include in changesets: false Running this sample pipeline:
pipeline {
agent any
libraries { lib('SampleLibrary') }
stages {
stage('stage') {
steps {
echo 'Library loaded successfully!'
}
}
}
}
results in the following error:
(p4):stop:10
(p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-lib-d94a3a59-55d8-4afb-a69d-9d8da59be94e/...@1___
p4 changes -m1 -ssubmitted //jenkins-lib-d94a3a59-55d8-4afb-a69d-9d8da59be94e/...@1,-1
Invalid changelist/client/label/date '@-1'.
(p4):stop:11
ERROR: P4: Unable to initialise CheckoutTask:
[JIRA] (JENKINS-58770) Reconsider GAV scheme
Title: Message Title Jesse Glick commented on JENKINS-58770 Re: Reconsider GAV scheme Now blocked by repository-permissions-updater #1286. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201075.156467412.6369.1569537420124%40Atlassian.JIRA.
[JIRA] (JENKINS-54163) Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds
Title: Message Title Alex Earl commented on JENKINS-54163 Re: Email-Ext 2.63: brokenBuildSuspects recipient provider is not working for pipeline builds Sorry, I need to get a machine that I can do releases from. I'll do that ASAP. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.194792.1539944186000.6363.1569533700189%40Atlassian.JIRA.
[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Darin Pope started work on JENKINS-59527 Change By: Darin Pope Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202156.1569432268000.6361.1569531960344%40Atlassian.JIRA.
[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Darin Pope updated an issue Jenkins / JENKINS-59527 Trim white space from pipeline library name and version field Change By: Darin Pope Labels: hacktoberfest newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202156.1569432268000.6359.1569531900149%40Atlassian.JIRA.
[JIRA] (JENKINS-59555) Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub
Title: Message Title Darin Pope updated an issue Jenkins / JENKINS-59555 Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub Change By: Darin Pope We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|https://plugins.jenkins.io/]. See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub.Steps: * Select a plugin you want to improve, clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile]Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on [ https://plugins.jenkins.io/ ] . Add Comment
[JIRA] (JENKINS-59555) Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub
Title: Message Title Darin Pope created an issue Jenkins / JENKINS-59555 Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub Issue Type: Improvement Assignee: Unassigned Components: other Created: 2019-09-26 21:02 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Darin Pope We have recently introduced support of GitHub documentation on the Jenkins Plugin Site. See https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with Release Drafter. We recommend all plugins to migrate documentation to GitHub. Steps: Select a plugin you want to improve, clone this issue and assign the correct component ID Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update Modify the documentation URL in the project file: https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile Once the steps are completed and your pull request is merged by the maintainer, the GitHub
[JIRA] (JENKINS-59555) Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub
Title: Message Title Darin Pope assigned an issue to Darin Pope Jenkins / JENKINS-59555 Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub Change By: Darin Pope Assignee: Darin Pope Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202187.1569531759000.6356.1569531780219%40Atlassian.JIRA.
[JIRA] (JENKINS-51440) Configure alternative context for each Tomcat container
Title: Message Title Robin Jansohn reopened an issue Jenkins / JENKINS-51440 Configure alternative context for each Tomcat container Change By: Robin Jansohn Resolution: Duplicate Status: Closed Reopened Assignee: Adrien Lecharpentier Julien Béti Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.190796.1526817852000.6347.1569530820391%40Atlassian.JIRA.
[JIRA] (JENKINS-59554) Avoid capturing an automatic bundle immediately after startup
Title: Message Title Owen Wood updated JENKINS-59554 Will release as part of 2.62 Jenkins / JENKINS-59554 Avoid capturing an automatic bundle immediately after startup Change By: Owen Wood Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-59554) Avoid capturing an automatic bundle immediately after startup
Title: Message Title Owen Wood assigned an issue to Jesse Glick Jenkins / JENKINS-59554 Avoid capturing an automatic bundle immediately after startup Change By: Owen Wood Assignee: Emilio Escobar Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202186.1569530151000.6332.1569530220626%40Atlassian.JIRA.
[JIRA] (JENKINS-59554) Avoid capturing an automatic bundle immediately after startup
Title: Message Title Owen Wood commented on JENKINS-59554 Re: Avoid capturing an automatic bundle immediately after startup https://github.com/jenkinsci/support-core-plugin/pull/191 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202186.1569530151000.6341.1569530220765%40Atlassian.JIRA.
[JIRA] (JENKINS-59554) Avoid capturing an automatic bundle immediately after startup
Title: Message Title Owen Wood updated JENKINS-59554 Jenkins / JENKINS-59554 Avoid capturing an automatic bundle immediately after startup Change By: Owen Wood Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202186.1569530151000.6338.1569530220722%40Atlassian.JIRA.
[JIRA] (JENKINS-59554) Avoid capturing an automatic bundle immediately after startup
Title: Message Title Owen Wood started work on JENKINS-59554 Change By: Owen Wood Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202186.1569530151000.6335.1569530220676%40Atlassian.JIRA.
[JIRA] (JENKINS-59554) Avoid capturing an automatic bundle immediately after startup
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-59554 Avoid capturing an automatic bundle immediately after startup Issue Type: Task Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-09-26 20:35 Priority: Minor Reporter: Owen Wood I have noticed that managed masters in CloudBees Core can be unexpectedly slow to start, and thread dumps often implicate automatic support bundle capture. It seems this happens within ~7s of Jenkins starting up, during which time lots of stuff is still being initialized, so attempting to browse the web UI can be quite slow as Jelly compilation competes with background support file writing often of hundreds of Kib of content. Better to defer this for a few minutes until Jenkins is comfortably up and running. Workaround: -Dcom.cloudbees.jenkins.support.SupportPlugin.AUTO_BUNDLE_PERIOD_HOURS=0 Add Comment
[JIRA] (JENKINS-59453) Cleanup plugin dependencies / Move to BOM
Title: Message Title Owen Wood updated JENKINS-59453 Jenkins / JENKINS-59453 Cleanup plugin dependencies / Move to BOM Change By: Owen Wood Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202044.1568928952000.6325.1569529920314%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-59552 Detached plugins installed are those with security warnings Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202183.1569511656000.6321.1569529020208%40Atlassian.JIRA.
[JIRA] (JENKINS-59453) Cleanup plugin dependencies / Move to BOM
Title: Message Title Owen Wood started work on JENKINS-59453 Change By: Owen Wood Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202044.1568928952000.6310.1569528661515%40Atlassian.JIRA.
[JIRA] (JENKINS-59454) Increase Advisor bundle generation delay to 30mins
Title: Message Title Owen Wood updated JENKINS-59454 Will release as part of 2.11 Jenkins / JENKINS-59454 Increase Advisor bundle generation delay to 30mins Change By: Owen Wood Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP try to virtually navigate back to that path The only way I can imagine this working (manual Stapler#invoke ) will just end up generating a lot of additional DBS instances, since the request needs to go to the doWhatever that returns the DBS. The catch is that Stapler does not currently offer an API to evaluate a token sequence from app root on demand I would imagine I could attempt to find the ancestor corresponding to dbs.owner, grab all further ancestors' tokens as of the constructor invocation of DBS, and then call Stapler#invoke(…, …, dbs.owner, furtherTokens) whenever a resource domain URL is accessed? Would save at least the navigation through to dbs.owner. Even if that works, there's way too much that can go wrong with this and it is unclear to me how I would handle that… Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-59545) PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed
Title: Message Title René Scheibe edited a comment on JENKINS-59545 Re: PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed Is this maybe similar to JENKINS-18736 and JENKINS-3660 ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202175.156950339.6300.1569526500219%40Atlassian.JIRA.
[JIRA] (JENKINS-59545) PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed
Title: Message Title René Scheibe commented on JENKINS-59545 Re: PAM login issue - pam_krb5: chown of [Kerberos] ticket cache [file] failed Is this maybe similar to JENKINS-18736? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202175.156950339.6297.1569526320234%40Atlassian.JIRA.
[JIRA] (JENKINS-59013) Cannot uninstall PAM Authentication
Title: Message Title René Scheibe commented on JENKINS-59013 Re: Cannot uninstall PAM Authentication I hit the same issue. After "uninstallation" of the plugin its version was just downgraded. Therefore it's then listed under the plugins with available updates. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201366.1566319847000.6294.1569525900235%40Atlassian.JIRA.
[JIRA] (JENKINS-59553) Automatic hook registration use different scoped REST path for Update
Title: Message Title Nikolas Falco started work on JENKINS-59553 Change By: Nikolas Falco Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202185.156952561.6291.1569525840172%40Atlassian.JIRA.
[JIRA] (JENKINS-59553) Automatic hook registration use different scoped REST path for Update
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-59553 Automatic hook registration use different scoped REST path for Update Issue Type: Bug Assignee: Joseph Petersen Components: bitbucket-branch-source-plugin Created: 2019-09-26 19:20 Environment: bitbucket-branch-source-plugin 2.4.7 bitbucket cloud Priority: Major Reporter: Nikolas Falco In our production jenkins server I can see a lot of exceptions about web hook automatic registration. The issue happens only when try to update an existing the web hook. The issue does not happens when register a new one. In update I got a 403. The reason is why it get the list of web hooks for each repository and register using the path specific for each one repository but try to update using the path of team. This cause the issue because the build user is not an administrator of the team. Only an administrator of the team could add or update webhook inherited by all repositories. For security reason the build user can only manager repository. In short actually the cloud api client to retrieve the list of web hooks and register new ones uses REST path specific for repository instead to update use the team REST API path.
[JIRA] (JENKINS-58770) Reconsider GAV scheme
Title: Message Title Jesse Glick updated JENKINS-58770 Jenkins / JENKINS-58770 Reconsider GAV scheme Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201075.156467412.6287.1569525120220%40Atlassian.JIRA.
[JIRA] (JENKINS-55000) Missing scope for bitbucket hooks registration
Title: Message Title Nikolas Falco commented on JENKINS-55000 Re: Missing scope for bitbucket hooks registration I got the same issue on update instead in your case seems to be during creation of not existing webhook. Since the response say 403 check that you tecnical user has admin permission on catalog-etl repository. If not tecnically you can not create hook on bitbucket cloud Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.196036.1543916864000.6285.1569524760174%40Atlassian.JIRA.
[JIRA] (JENKINS-48566) Jenkins Stage History Fails When Job is Renamed
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-48566 Jenkins Stage History Fails When Job is Renamed Change By: Josh Soref Summary: Jenkis Jenkins Stage History Fails When Job is Renamed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187187.1513269614000.6279.1569523860519%40Atlassian.JIRA.
[JIRA] (JENKINS-23898) Jenkins and Swarm Plugin Installation problem
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-23898 Jenkins and Swarm Plugin Installation problem Change By: Josh Soref Summary: Jinkins Jenkins and Swarm Plugin Instalation Installation problem Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.156363.1405930145000.6276.1569523860436%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Jesse Glick commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP I wonder whether you can save the request URI in effect when the DirectoryBrowserSupport is created, along with the user ID, and then try to virtually navigate back to that path whenever serving a request to see if it is still permitted? The catch is that Stapler does not currently offer an API to evaluate a token sequence from app root on demand. (I have wanted such an API a couple of times in the past.) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.178741.1486645144000.6270.1569522720203%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite edited a comment on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL [~piyush_devops] if you are passing the GitHub personal access token as a parameter to a job, you're making a mistake. Don't do that.Job parameters are visible from the "Parameters" link on the left-hand side of the individual job history. In my case, job #7 shows the parameters which were used to run that job. If a personal access token had been entered into a parameter field to run that job, the value of the personal access token would be visible from that page. !parameter-values-visible-in-build-detail.png|thumbnail! Please use Jenkins credentials. They are designed to store credentials. They work well with Jenkins plugins. Investigate why your credentials are not working. Don't pass sensitive text as a parameter to a Jenkins job. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6257.1569521100560%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title piyush sachdeva commented on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL Mark Waite, yes that is why I was using Jenkins credential store along with the masked variable but it's not able to resolve the variable. I don't want it to print in Jenkins console output that is why I have posted in this thread(my first comment). I will keep digging into it. Thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6251.1569521100491%40Atlassian.JIRA.
[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 Attachment: parameter-values-visible-in-build-detail.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6255.1569521100537%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP Richard Bywater FYI, you may be interested in this feature for HTML Publisher, so your input would be appreciated. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.178741.1486645144000.6247.1569520860418%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite commented on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL piyush sachdeva if you are passing the GitHub personal access token as a parameter to a job, you're making a mistake. Don't do that. Job parameters are visible from the "Parameters" link on the left-hand side of the individual job history. In my case, job #7 shows the parameters which were used to run that job. If a personal access token had been entered into a parameter field to run that job, the value of the personal access token would be visible from that page. Please use Jenkins credentials. They are designed to store credentials. They work well with Jenkins plugins. Investigate why your credentials are not working. Don't pass sensitive text as a parameter to a Jenkins job. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6241.1569520860280%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title piyush sachdeva commented on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL Mark Waite, the reason I am commenting on this thread is because the status of this bug is still unresolved and I am facing the exact same issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6236.1569520020158%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP So… how bad would it be to allow admins to choose? Here's my proposed help text: This option [Name TBD] improves the compatibility with plugins not specifically supporting this feature, at the cost of relaxed security checks. When unchecked (the default) plugins need to explicitly register every directory browser instance they intend to make available via a resource URL below the resources root URL. Otherwise it will not redirect requests to files to their corresponding resources URL, but serve files directly and add Content-Security-Policy headers. Registering includes defining security checks to perform on the user identity for which a resource URL is created before access is granted. As a result, when a user loses the permission to access a workspace, job, or other directory browser, the corresponding resource URLs will stop working as well, as the user's permissions are checked every time the resource URL is accessed. When checked, all directory browsers are implicitly registered on first access, and only require that the user retains read access to the model object (typically a job) that the directory browser is associated with. If a user loses a more specific, otherwise required permission, such as Item/Workspace or Build/Artifacts, they will still be able to access the files through resource URLs until those URLs expire. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Andrew Widdersheim commented on JENKINS-59552 Re: Detached plugins installed are those with security warnings Go for it. I'm busy too. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202183.1569511656000.6228.1569517920155%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite commented on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL piyush sachdeva please don't use a bug report as a place to request help with configuration issues. This bug report describes a failure to expand a parameter in a git URL that is provided to a Freestyle job. Your issue is different and should be handled through the user mailing list or the chat system. Many, many users are successfully cloning repositories with GitHub personal access tokens. The most likely problem is a configuration error somewhere in your environment. That's not a bug, it is a configuration error. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6197.1569516300198%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title piyush sachdeva commented on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL Hi Mark, Thanks for your reply however, I have tried the approach already but I am still getting the below error fatal: could not read Username for 'https://github.xx.com': terminal prompts disabled. PS: My Jenkins is running as a Docker container/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6188.1569515880158%40Atlassian.JIRA.
[JIRA] (JENKINS-59548) Automatically enable "Deploy Key" for Gitlab project
Title: Message Title
Christian Ciach updated an issue
Jenkins / JENKINS-59548
Automatically enable "Deploy Key" for Gitlab project
Change By:
Christian Ciach
To enable Jenkins to checkout our Git projects from Gitlab, the "Deploy Key" of Jenkins currently must be enabled for each project in Gitlab individually.This is a tedious task that can be automated using the Gitlab API.A practical example: # In Gitlab, go to "Admin Area" -> "Deploy Keys" and add a new key that we will call "jenkins-gitlab". # To enable Jenkins to checkout the source code of the project named "MyProject", we must enable the deploy key for this project in Gitlab. For this, I currently have to go to the Settings of the Gitlab-Project gitlab project "MyProject" manually ("Settings" -> "Repository" -> "Deploy Keys") to enable the Deploy Key called "jenkins-gitlab").Using the gitlab-branch-source-plugin, this is the only thing I currently still have to do manually for each new gitlab project.Fortunately, this could be automated using the Gitlab API. Please have a look at the section "Enable a deploy key": [https://docs.gitlab.com/ce/api/deploy_keys.html#enable-a-deploy-key|https://docs.gitlab.com/ee/api/deploy_keys.html#enable-a-deploy-key]If would be really great if I could configure the "Deploy Key" to use at organization-folder level in Gitlab (or maybe even as a system setting) that "gitlab-branch-source-plugin" uses to automatically call the Gitlab API to enable the deploy config for the gitlab projects. I think this should be offered as a trait that shows a combobox of available Deploy Keys. To fill the combox of available Deploy Keys, you can use this API: [ https://docs.gitlab.com/ce/api/deploy_keys.html#list-all-deploy-keys ]
Add Comment
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite edited a comment on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL [~piyush_devops] there is already a solution for that case. Create a Jenkins username/password credential which contains the username and the personal access token. Use that credential in your operations. The value of the credential is not displayed when a credential is used in a Jenkins job. Refer to "[Using Credentials|https://jenkins.io/doc/book/using/using-credentials/]" in the Jenkins Handbook for more information. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6183.1569514560442%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title Mark Waite commented on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL piyush sachdeva there is already a solution for that case. Create a Jenkins username/password credential which contains the username and the personal access token. Use that credential in your operations. The value of the credential is not displayed when a credential is used in a Jenkins job. Refer to "Using Credentials" in the Jenkins Handbook for more information. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6179.1569514560326%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Daniel Beck commented on JENKINS-59552 Re: Detached plugins installed are those with security warnings Andrew Widdersheim Sorry about the lack of responses, I was busy. Happy to take this, unless you want to? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202183.1569511656000.6174.1569512700135%40Atlassian.JIRA.
[JIRA] (JENKINS-57936) Parameters not expanded in username or password portion of https git URL
Title: Message Title piyush sachdeva commented on JENKINS-57936 Re: Parameters not expanded in username or password portion of https git URL Hi, I am facing the same issue, I generated a personal access token and using that as a credential parameter(secret text) in Git plugin like https://$to...@github.com but its not able to resolve the variable and if I dont use the variable then it will appear in console output. Do we have a possible solution yet? Thanks, Piyush Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.6172.1569512580224%40Atlassian.JIRA.
[JIRA] (JENKINS-59513) Defunct hyperlink in PULL_REQUEST_TEMPLATE.md
Title: Message Title Mike Ajala updated JENKINS-59513 Jenkins / JENKINS-59513 Defunct hyperlink in PULL_REQUEST_TEMPLATE.md Change By: Mike Ajala Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202136.1569338752000.6168.1569512160388%40Atlassian.JIRA.
[JIRA] (JENKINS-59505) Minor typo fix to the pluginSetupWizard.properties file
Title: Message Title Mike Ajala closed an issue as Fixed Jenkins / JENKINS-59505 Minor typo fix to the pluginSetupWizard.properties file Change By: Mike Ajala Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202127.1569317932000.6166.1569512160328%40Atlassian.JIRA.
[JIRA] (JENKINS-59505) Minor typo fix to the pluginSetupWizard.properties file
Title: Message Title Mike Ajala updated JENKINS-59505 Jenkins / JENKINS-59505 Minor typo fix to the pluginSetupWizard.properties file Change By: Mike Ajala Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202127.1569317932000.6164.1569512100223%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-59552 Detached plugins installed are those with security warnings Change By: Jesse Glick Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202183.1569511656000.6162.1569511980455%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59552 Detached plugins installed are those with security warnings Change By: Jesse Glick Labels: security Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202183.1569511656000.6159.1569511980418%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59552 Detached plugins installed are those with security warnings Change By: Jesse Glick Component/s: core Component/s: docker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202183.1569511656000.6156.1569511980383%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Created https://issues.jenkins-ci.org/browse/JENKINS-59552. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.199434.155810265.6148.1569511740229%40Atlassian.JIRA.
[JIRA] (JENKINS-59552) Detached plugins installed are those with security warnings
Title: Message Title Andrew Widdersheim created an issue Jenkins / JENKINS-59552 Detached plugins installed are those with security warnings Issue Type: Bug Assignee: Carlos Sanchez Components: docker Created: 2019-09-26 15:27 Priority: Critical Reporter: Andrew Widdersheim When running Jenkins with the official Docker container, some plugins will pull in detached plugins that have security vulnerabilities and also have newer versions available that could be used instead. To replicate, you can install https://plugins.jenkins.io/purge-build-queue-plugin# for example. This will pull in a vulnerable version of https://plugins.jenkins.io/pam-auth: jenkins_1 | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/pam-auth.jpi jenkins_1 | WARNING: Created /var/jenkins_home/plugins/pam-auth/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness jenkins_1 | INFO: Took 0ms for Loading plugin PAM Authentication plugin v1.1 (pam-auth) by pool-6-thread-4 jenkins_1 | INFO: Took 0ms for Initializing plugin pam-auth by pool-6-thread-1 According to Jesse Glick, this is a bug and not intended behavior. This might be scoped to just running with Docker but it's the only place I'm able to test and replicate.
[JIRA] (JENKINS-59551) jCasC: enable colums for sectionedView
Title: Message Title
Maria Mueller updated an issue
Jenkins / JENKINS-59551
jCasC: enable colums for sectionedView
Change By:
Maria Mueller
Hi everybody,I would like to configure a sectioned View on our Jenkins with the help of Jenkins Configuration as Code (jCasC). The following code: {code:java} - sectioned: name: "test" sections: - listViewSection: alignment: CENTER includeRegex: ".*(master_).*" name: "test1" width: FULL - listViewSection: alignment: CENTER includeRegex: ".*(nightly_).*" name: "test2" width: FULL {code} creates a view with the two sections containing the jobs, but the columns are not present, see image:!image-2019-09-26-17-13-37-799.png! When configuring manually, all default columns are selected and visible.The columns could be configured maybe like this: {code:java} - sectioned: name: "test" sections: - listViewSection: columns: - "status" - "jobName" - "lastSuccess" - "lastFailure" - "lastDuration" alignment: CENTER includeRegex: ".*(master_).*" name: "test1" width: FULL {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59551) jCasC: enable colums for sectionedView
Title: Message Title Maria Mueller created an issue Jenkins / JENKINS-59551 jCasC: enable colums for sectionedView Issue Type: New Feature Assignee: Timothy Bingaman Attachments: image-2019-09-26-17-13-37-799.png Components: sectioned-view-plugin Created: 2019-09-26 15:15 Labels: configuration Priority: Major Reporter: Maria Mueller Hi everybody, I would like to configure a sectioned View on our Jenkins with the help of Jenkins Configuration as Code (jCasC). The following code: sectioned: name: "test" sections: listViewSection: alignment: CENTER includeRegex: ".(master_)." name: "test1" width: FULL listViewSection: alignment: CENTER includeRegex: ".(nightly_)." name: "test2" width: FULL creates a view with the two sections containing the jobs, but the columns are not present, see image: When configuring manually, all default columns are selected and visible. The columns could be configured maybe like this: sectioned: name: "test" sections: listViewSection: columns: "status"
[JIRA] (JENKINS-59538) Introduce TcpSlaveAgentListener.getAdvertisedHost()
Title: Message Title Alexander Link updated an issue Jenkins / JENKINS-59538 Introduce TcpSlaveAgentListener.getAdvertisedHost() Change By: Alexander Link _TcpSlaveAgentListener_ provides a method _getAdvertisedPort()_ to get the advertised port, but does not have a method _getAdvertisedHost()_ to get the host. Instead it has a field _CLI_HOST_NAME _which _CLI_HOST_NAME_ which is restricted to _NoExternalUse_ and therefore cannot be used from other plugins.For the [Kubernetes plugin|https://github.com/jenkinsci/kubernetes-plugin/pull/602] we need to get this information and TcpSlaveAgentListener.getAdvertisedHost() would be the cleanest way. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-32658) Multibranch pipeline 'checkout scm' does not handle Git submodules
Title: Message Title james smith commented on JENKINS-32658 Re: Multibranch pipeline 'checkout scm' does not handle Git submodules I ran into this problem today, submodules not being checked out, and the problem in my case was that I added the submodules to use ssh, but the multibranch pipeline uses https to do the git checkout. Once I updated my .gitmodules to use https urls it worked fine. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.167810.1453920592000.6138.1569509700520%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Jesse Glick commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP I think it would be acceptable to do the (for example) WORKSPACE check against the current authenticated user once, when the DirectoryBrowserSupport is being created, and then serve a URL prefix which is good for an hour. An administrator might happen to revoke that user’s permission (or delete the user from the security realm) ten minutes later, but so what? If they were going to steal sensitive content, they could have done so already, and if this comes as a surprise and they are being escorted from the building by security they have probably lost the magic link by the time they get out on the sidewalk. Anyway, if you feel strongly that we need to define a new abstract API type which saves arbitrary data (in this example I guess a User.id + AbstractProject.fullName) and rechecks permissions on each request, there are only 43 OSS plugins I see creating DirectoryBrowserSupport, so it could be adopted incrementally—most eagerly by plugins which actually record content that is problematic for CSP, or that are widely used (perhaps workflow-support, htmlpublisher, javadoc, maven-plugin, junit-attachments). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-49834) Variable at branch name do not eval
Title: Message Title Martin Weber commented on JENKINS-49834 Re: Variable at branch name do not eval Issue is not fixed. See https://issues.jenkins-ci.org/browse/JENKINS-49758?focusedCommentId=376459=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-376459 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188818.1519977736000.6120.1569508680107%40Atlassian.JIRA.
[JIRA] (JENKINS-49758) when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
Title: Message Title Martin Weber commented on JENKINS-49758 Re: when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value Updated to Major. Ran into the exact issue described in https://issues.jenkins-ci.org/browse/JENKINS-49834!image-2019-09-26-16-32-02-026.png!!image-2019-09-26-16-34-33-817.png! The whole feature is essentially not working. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188704.1519700423000.6112.1569508620326%40Atlassian.JIRA.
[JIRA] (JENKINS-49758) when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
Title: Message Title Martin Weber edited a comment on JENKINS-49758 Re: when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value Updated to Major. Ran into the exact issue described in https://issues.jenkins-ci.org/browse/JENKINS-49834 !image-2019-09-26-16-32-02-026.png! !image-2019-09-26-16-34-33-817.png!The whole feature is essentially not working. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188704.1519700423000.6114.1569508620381%40Atlassian.JIRA.
[JIRA] (JENKINS-49758) when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-49758 when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value Change By: Martin Weber Attachment: image-2019-09-26-16-34-33-817.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188704.1519700423000.6102.1569508500705%40Atlassian.JIRA.
[JIRA] (JENKINS-59550) Show build queue for each particular node
Title: Message Title Mohamed Ali TMAR updated an issue Jenkins / JENKINS-59550 Show build queue for each particular node Change By: Mohamed Ali TMAR Summary: Show build queue for each particular node Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202181.1569508123000.6097.1569508380533%40Atlassian.JIRA.
[JIRA] (JENKINS-49758) when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-49758 when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value Change By: Martin Weber Attachment: image-2019-09-26-16-32-02-026.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188704.1519700423000.6093.1569508380468%40Atlassian.JIRA.
[JIRA] (JENKINS-59550) Show build queue for particular node
Title: Message Title Mohamed Ali TMAR updated an issue Jenkins / JENKINS-59550 Show build queue for particular node Change By: Mohamed Ali TMAR Summary: Show build queue for particular node Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202181.1569508123000.6095.1569508380504%40Atlassian.JIRA.
[JIRA] (JENKINS-59550) Show queue for particular node
Title: Message Title Mohamed Ali TMAR assigned an issue to Shenyu Zheng Jenkins / JENKINS-59550 Show queue for particular node Change By: Mohamed Ali TMAR Assignee: Shenyu Zheng Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202181.1569508123000.6087.1569508200212%40Atlassian.JIRA.
[JIRA] (JENKINS-59550) Show queue for particular node
Title: Message Title Mohamed Ali TMAR created an issue Jenkins / JENKINS-59550 Show queue for particular node Issue Type: New Feature Assignee: Unassigned Components: _unsorted Created: 2019-09-26 14:28 Priority: Blocker Reporter: Mohamed Ali TMAR It's better to show the queue for each node. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-49758) when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-49758 when passing in ref_spec with build parameters, the exact string "$REF_SPEC" is used rather then the value Change By: Martin Weber Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188704.1519700423000.6082.1569508140619%40Atlassian.JIRA.
[JIRA] (JENKINS-27127) wait/notify steps
Title: Message Title Jesse Glick commented on JENKINS-27127 Re: wait/notify steps See workflow-basic-steps #98 for an example of the semaphore use case. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.160920.1424877995000.6063.1569507780301%40Atlassian.JIRA.
[JIRA] (JENKINS-5598) Along with Build Executor status on a particular node, useful to show jobs queued up for that particular node
Title: Message Title Mohamed Ali TMAR commented on JENKINS-5598 Re: Along with Build Executor status on a particular node, useful to show jobs queued up for that particular node Hello, Any news about this ticket. I need this feature. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.135687.1265801936000.6062.1569507780285%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title
Daniel Beck edited a comment on JENKINS-41891
Re: Serve static files from second domain as an alternative to setting CSP
Unfortunately I don't think it's possible to implement this without API additions, i.e. plugins will not just magically pick this up when it's added in core.The problem is that we need to support permission checks as the URL on the second/resource domain is accessed, and cannot just assume that Read access to {{owner}} will be enough. An example in core for that is [https://github.com/jenkinsci/jenkins/blob/b8e32de403ad40a7641d0b15ff2f1e36cf522ff4/core/src/main/java/hudson/model/AbstractProject.java#L1832] which has an additional permission check.Alternatively we're good with that for the lifetime of a session (+ some undetermined delay), but I'd rather now not .
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google 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.178741.1486645144000.6056.1569507720197%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP Unfortunately I don't think it's possible to implement this without API additions, i.e. plugins will not just magically pick this up when it's added in core. The problem is that we need to support permission checks as the URL on the second/resource domain is accessed, and cannot just assume that Read access to owner will be enough. An example in core for that is https://github.com/jenkinsci/jenkins/blob/b8e32de403ad40a7641d0b15ff2f1e36cf522ff4/core/src/main/java/hudson/model/AbstractProject.java#L1832 which has an additional permission check. Alternatively we're good with that for the lifetime of a session (+ some undetermined delay), but I'd rather now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.178741.1486645144000.6050.1569507540252%40Atlassian.JIRA.
[JIRA] (JENKINS-59548) Automatically enable "Deploy Key" for Gitlab project
Title: Message Title
Christian Ciach updated an issue
Jenkins / JENKINS-59548
Automatically enable "Deploy Key" for Gitlab project
Change By:
Christian Ciach
To enable Jenkins to checkout our Git projects from Gitlab, the "Deploy Key" of Jenkins currently must be enabled for each project in Gitlab individually.This is a tedious task that can be automated using the Gitlab API.A practical example: # In Gitlab, go to "Admin Area" -> "Deploy Keys" and add a new key that we will call "jenkins-gitlab". # To enable Jenkins to checkout the source code of the project named "MyProject", we must enable the deploy key for this project in Gitlab. For this, I currently have to go to the Settings of the Gitlab-Project manually ("Settings" -> "Repository" -> "Deploy Keys") to enable the Deploy Key called "jenkins-gitlab").Using the gitlab-branch-source-plugin, this is the only thing I currently still have to do manually for each new gitlab project.Fortunately, this could be automated using the Gitlab API. Please have a look at the section "Enable a deploy key": [https://docs.gitlab.com/ ce/api/deploy_keys.html#enable-a-deploy-key|https://docs.gitlab.com/ ee/api/deploy_keys.html#enable-a-deploy-key]If would be really great if I could configure a the "Deploy Token title Key " to use at organization-folder level in Gitlab (or maybe even as a system setting) that "gitlab-branch-source-plugin" uses to automatically call the Gitlab API to enable the deploy config for the gitlab projects. I think this should be offered as a trait that shows a combobox of available Deploy Keys. To fill the combox of available Deploy Keys, you can use this API: https://docs.gitlab.com/ce/api/deploy_keys.html#list-all-deploy-keys
Add Comment
[JIRA] (JENKINS-59549) Jenkins is not responsive when s3 plugin upload many big files
Title: Message Title Piotr Wielgołaski created an issue Jenkins / JENKINS-59549 Jenkins is not responsive when s3 plugin upload many big files Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2019-09-26 14:16 Priority: Critical Reporter: Piotr Wielgołaski In our cases Jenkins has 2G memory and we publish 1.5G from 900 files it crash as S3 occupy 1.5G of heap. Each file could occupy in memory 16M https://github.com/jenkinsci/s3-plugin/blob/70e1d8f622556b1725ee9faa6f2a9b8eba082131/src/main/java/hudson/plugins/s3/Uploads.java#L29 I would like to have a wait to upload my artifacts, but dont crash Jenkins at the same time. Add Comment
[JIRA] (JENKINS-59548) Automatically enable "Deploy Key" for Gitlab project
Title: Message Title
Christian Ciach updated an issue
Jenkins / JENKINS-59548
Automatically enable "Deploy Key" for Gitlab project
Change By:
Christian Ciach
To enable Jenkins to checkout our Git projects from Gitlab, the "Deploy Key" of Jenkins currently must be enabled for each project in Gitlab individually.This is a tedious task that can be automated using the Gitlab API.A practical example: # In Gitlab, go to "Admin Area" -> "Deploy Keys" and add a new key that we will call "jenkins-gitlab". # If To enable Jenkins should be able to checkout the source code of the project named "MyProject", we must enable the deploy key for this project. For this, I currently have to go to the Settings of the Gitlab-Project manually ("Settings" -> "Repository" -> "Deploy Keys") to enable the Deploy Key called "jenkins-gitlab").Using the gitlab-branch-source-plugin, this is the only thing I currently still have to do manually for each new gitlab project.Fortunately, this could be automated using the Gitlab API. Please have a look at the section "Enable a deploy key": [https://docs.gitlab.com/ee/api/deploy_keys.html#enable-a-deploy-key]If would be really great if I could configure a "Deploy Token title" at organization-folder level in Gitlab (or maybe even as a system setting) that "gitlab-branch-source-plugin" uses to automatically call the Gitlab API to enable the deploy config for the gitlab projects.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title James Nord updated an issue Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: James Nord Labels: UX newbie-friendly ui Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202130.1569325102000.6044.1569507360345%40Atlassian.JIRA.
[JIRA] (JENKINS-59548) Automatically enable "Deploy Key" for Gitlab project
Title: Message Title
Christian Ciach updated an issue
Jenkins / JENKINS-59548
Automatically enable "Deploy Key" for Gitlab project
Change By:
Christian Ciach
To enable Jenkins to checkout our Git projects from Gitlab, the "Deploy Key" of Jenkins currently must be enabled for each project in Gitlab individually.This is a tedious task that can be automated using the Gitlab API.A practical example: # In Gitlab, go to "Admin Area" -> "Deploy Keys" and add a new key that we will call "jenkins-gitlab". # To enable Jenkins to checkout the source code of the project named "MyProject", we must enable the deploy key for this project in Gitlab . For this, I currently have to go to the Settings of the Gitlab-Project manually ("Settings" -> "Repository" -> "Deploy Keys") to enable the Deploy Key called "jenkins-gitlab").Using the gitlab-branch-source-plugin, this is the only thing I currently still have to do manually for each new gitlab project.Fortunately, this could be automated using the Gitlab API. Please have a look at the section "Enable a deploy key": [https://docs.gitlab.com/ee/api/deploy_keys.html#enable-a-deploy-key]If would be really great if I could configure a "Deploy Token title" at organization-folder level in Gitlab (or maybe even as a system setting) that "gitlab-branch-source-plugin" uses to automatically call the Gitlab API to enable the deploy config for the gitlab projects.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59548) Automatically enable "Deploy Key" for Gitlab project
Title: Message Title
Christian Ciach created an issue
Jenkins / JENKINS-59548
Automatically enable "Deploy Key" for Gitlab project
Issue Type:
New Feature
Assignee:
Christian Ciach
Components:
gitlab-branch-source-plugin
Created:
2019-09-26 14:14
Priority:
Minor
Reporter:
Christian Ciach
To enable Jenkins to checkout our Git projects from Gitlab, the "Deploy Key" of Jenkins currently must be enabled for each project in Gitlab individually.This is a tedious task that can be automated using the Gitlab API. A practical example:
In Gitlab, go to "Admin Area" -> "Deploy Keys" and add a new key that we will call "jenkins-gitlab".
If Jenkins should be able to checkout the source code of the project named "MyProject", we must enable the deploy key for this project. For this, I currently have to go to the Settings of the Gitlab-Project manually ("Settings" -> "Repository" -> "Deploy Keys") to enable the Deploy Key called "jenkins-gitlab").
Using the gitlab-branch-source-plugin, this is the only thing I currently still have to do manually for each new gitlab project. Fortunately, this could be automated using the Gitlab API. Please have a look at the section "Enable a deploy key": https://docs.gitlab.com/ee/api/deploy_keys.html#enable-a-deploy-key If would be really great if I could configure a "Deploy Token title" at organization-folder level in Gitlab (or maybe even as a system setting) that "gitlab-branch-source-plugin" uses to automatically call the Gitlab API to enable the deploy config for the gitlab projects.
[JIRA] (JENKINS-59542) There is problem while I'm trying to give CIFS share builds in Jenkins
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-59542 There is problem while I'm trying to give CIFS share builds in Jenkins Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202172.1569500879000.6040.1569507180186%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Baptiste Mathus commented on JENKINS-59508 Re: sidebar link names are not truncated causing funky rendering Just added newbie-friendly, because I think that might be an easy one for UI developer, but no guaranty . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202130.1569325102000.6038.1569506880083%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-59508 sidebar link names are not truncated causing funky rendering Change By: Baptiste Mathus Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202130.1569325102000.6036.1569506820208%40Atlassian.JIRA.
[JIRA] (JENKINS-39881) waitUntil block never gets called back
Title: Message Title Jesse Glick resolved as Cannot Reproduce No further information, and pretty old. Jenkins / JENKINS-39881 waitUntil block never gets called back Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-59547) "build with parameters" missing after creating a "new item" and choosing a folder in "copy from"
Title: Message Title Amit Ron created an issue Jenkins / JENKINS-59547 "build with parameters" missing after creating a "new item" and choosing a folder in "copy from" Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-26 13:42 Environment: Jenkins ver. 2.150.3 System Properties Name ↓ Value awt.toolkit sun.awt.X11.XToolkit executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.security.HudsonPrivateSecurityRealm.ID_REGEX ^[a-zA-Z0-9_.-]+$ java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/java/jre1.8.0_201-amd64/lib/endorsed java.ext.dirs /usr/java/jre1.8.0_201-amd64/lib/ext:/usr/java/packages/lib/ext java.home /usr/java/jre1.8.0_201-amd64 java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.8.0_201-b09 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_201 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.201-b09 JENKINS_HOME /var/lib/jenkins jetty.git.hash 27208684755d94a92186989f695db2d7b21ebc51 jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/dyninst:/usr/lib64/mysql jnidispatch.path /tmp/jna--1712433994/jna8724238926852422975.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.0-862.el7.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/java/jre1.8.0_201-amd64/lib/resources.jar:/usr/java/jre1.8.0_201-amd64/lib/rt.jar:/usr/java/jre1.8.0_201-amd64/lib/sunrsasign.jar:/usr/java/jre1.8.0_201-amd64/lib/jsse.jar:/usr/java/jre1.8.0_201-amd64/lib/jce.jar:/usr/java/jre1.8.0_201-amd64/lib/charsets.jar:/usr/java/jre1.8.0_201-amd64/lib/jfr.jar:/usr/java/jre1.8.0_201-amd64/classes sun.boot.library.path /usr/java/jre1.8.0_201-amd64/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Jesse Glick updated JENKINS-56809 Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198459.1553858983000.6023.1569505020239%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title W Basu Perforce commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly Hi Eric Boehm, we will interested to know why automatic labels are not an option for your workflow, so if you could explain that would be great. Happy to reach out via our customer support and have call with you if needed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200194.1561145922000.6019.1569504900228%40Atlassian.JIRA.
[JIRA] (JENKINS-56446) IOException in FileLogStorage maybeFlush
Title: Message Title
John Lengeling commented on JENKINS-56446
Re: IOException in FileLogStorage maybeFlush
Ran into this issue under Jenkins 2.176.3 with workflow-api 2.37, mailer 1.27 , email-ext 2.66. It occurred thou in the job post section trying to send an email notification. Over a couple of days, the stacktraces filled up the partition since it outputs about every 30s-60s. Tried to abort the job but it would not die. Tried to kill the thread from Melody but it would not die. Had to restart Jenkins and the job started running again after the restart. Then I quickly killed it. ``` {{Sep 25, 2019 8:22:34 AM org.jenkinsci.plugins.workflow.log.FileLogStorage maybeFlush WARNING: failed to flush /opt/apache/.jenkins/jobs/Reprogramming/jobs/verify/branches/master/builds/604/log java.io.IOException: Stream Closed at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:326) at org.jenkinsci.plugins.workflow.log.DelayBufferedOutputStream$FlushControlledOutputStream.write(DelayBufferedOutputStream.java:129) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at java.io.FilterOutputStream.flush(FilterOutputStream.java:140) at org.jenkinsci.plugins.workflow.log.FileLogStorage.maybeFlush(FileLogStorage.java:190) at org.jenkinsci.plugins.workflow.log.FileLogStorage.overallLog(FileLogStorage.java:198) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogText(WorkflowRun.java:1019) at hudson.plugins.emailext.AttachmentUtils$LogFileDataSource.getInputStream(AttachmentUtils.java:100) at javax.mail.internet.MimeUtility.getEncoding(MimeUtility.java:197) at javax.mail.internet.MimeUtility.getEncoding(MimeUtility.java:256) at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1366) at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1021) at javax.mail.internet.MimeMultipart.updateHeaders(MimeMultipart.java:419) at javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1345) at javax.mail.internet.MimeMessage.updateHeaders(MimeMessage.java:2106) at javax.mail.internet.MimeMessage.saveChanges(MimeMessage.java:2074) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1769) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:484) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:224) at hudson.plugins.emailext.EmailExtStep$EmailExtStepExecution.run(EmailExtStep.java:163) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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)}} ```
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198459.1553858983000.6009.1569504780281%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Jesse Glick started work on JENKINS-56809 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198459.1553858983000.6011.1569504780435%40Atlassian.JIRA.
[JIRA] (JENKINS-25106) Minimum number of slaves for cloud
Title: Message Title Nick Jones commented on JENKINS-25106 Re: Minimum number of slaves for cloud This looks like it was released in 1.4.6? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.158607.1412964836000.5999.1569504180358%40Atlassian.JIRA.
[JIRA] (JENKINS-59546) Git submodule checkout not working
Title: Message Title tobs h created an issue Jenkins / JENKINS-59546 Git submodule checkout not working Issue Type: Bug Assignee: Liam Newman Components: github-branch-source-plugin Created: 2019-09-26 13:21 Environment: Jenkins ver. 2.176.3 System Properties: awt.toolkit sun.awt.X11.XToolkit executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/local/openjdk-8/jre/lib/endorsed java.ext.dirs /usr/local/openjdk-8/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/local/openjdk-8/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_222-b10 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_222 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.222-b10 jenkins.model.Jenkins.slaveAgentPort 5 jetty.git.hash eb70b240169fcf1abbd86af36482d1c49826fa0b jna.loaded true jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib:/usr/local/openjdk-8/lib/amd64/jli:/usr/local/openjdk-8/lib/amd64 jnidispatch.path /tmp/jna-3506402/jna1882685250874189469.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 4.4.0-57-generic path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/local/openjdk-8/jre/lib/resources.jar:/usr/local/openjdk-8/jre/lib/rt.jar:/usr/local/openjdk-8/jre/lib/sunrsasign.jar:/usr/local/openjdk-8/jre/lib/jsse.jar:/usr/local/openjdk-8/jre/lib/jce.jar:/usr/local/openjdk-8/jre/lib/charsets.jar:/usr/local/openjdk-8/jre/lib/jfr.jar:/usr/local/openjdk-8/jre/classes sun.boot.library.path /usr/local/openjdk-8/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/share/jenkins/jenkins.war --httpPort=8082 sun.java.launcher SUN_STANDARD
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Jesse Glick commented on JENKINS-56809 Re: No lastCompletedBuild symlink I need to access files directly on filesystem This is not supported. If somehow works this way for you, fine, but it may not, or may stop working in the future. While a lastCompletedBuild is defined in the code as of JENKINS-26270, it is not actually used by Job.getLastCompletedBuild(), which is odd. But LAST_COMPLETED_BUILD is in the BUILTIN list which is normally updated by PeepholePermalink.RunListenerImpl.onCompleted; I think the actual issue here is that LAST_COMPLETED_BUILD is a general Permalink and not a PeepholePermalink. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198459.1553858983000.5994.1569504060100%40Atlassian.JIRA.
[JIRA] (JENKINS-58149) p4-plugin 1.10.0 does not sync to label correctly
Title: Message Title Eric Boehm commented on JENKINS-58149 Re: p4-plugin 1.10.0 does not sync to label correctly We can work around it by doing the p4 sync @label in a build step but that means re-configuring a bunch of jobs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200194.1561145922000.5989.1569504000299%40Atlassian.JIRA.
