[JIRA] (JENKINS-44425) global variables overwrite node variables
Title: Message Title daniel zhang commented on JENKINS-44425 Re: global variables overwrite node variables We encountered the same issue and it happens after the Pipeline: Job plugin version 2.25. And I tend to agree with Pascal van Kempen. If we are going to create a new pipeline job, then we can follow the method provided by Jesse Glick, but if we already have a lot of jobs at Jenkins, then we have to ask all users to check and modify their jobs, this will be a huge disaster to users. 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.182252.1495477579000.2335.1574063340924%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Stephan Wezel commented on JENKINS-59694 Re: When build step fails or get aborted upload is still tried Thanks, I will test it when the next release with this fix is published 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.202393.1570520886000.2331.1574063100225%40Atlassian.JIRA.
[JIRA] (JENKINS-60103) Cannot send junit results to Octane, because there is no permission on slave to create log folder
Title: Message Title pretbc pretbc commented on JENKINS-60103 Re: Cannot send junit results to Octane, because there is no permission on slave to create log folder any news regarding dev version ? 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.202949.1573206476000.2329.1574062380221%40Atlassian.JIRA.
[JIRA] (JENKINS-60158) ConversionException: Refusing to unmarshal log for security reasons EnvironmentVarSetter
Title: Message Title Dragana Stojanovikj commented on JENKINS-60158 Re: ConversionException: Refusing to unmarshal log for security reasons EnvironmentVarSetter Okay then, thank you 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.203024.1573655768000.2327.1574061840139%40Atlassian.JIRA.
[JIRA] (JENKINS-60192) Unable to start Jenkins service. After INFO: jetty-winstone-2.9.
Title: Message Title P Mdada updated an issue Jenkins / JENKINS-60192 Unable to start Jenkins service. After INFO: jetty-winstone-2.9. Change By: P Mdada Priority: Minor Blocker 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.203161.1574059881000.2325.1574060100104%40Atlassian.JIRA.
[JIRA] (JENKINS-60192) Unable to start Jenkins service. After INFO: jetty-winstone-2.9.
Title: Message Title P Mdada created an issue Jenkins / JENKINS-60192 Unable to start Jenkins service. After INFO: jetty-winstone-2.9. Issue Type: Task Assignee: Unassigned Components: core Created: 2019-11-18 06:51 Priority: Minor Reporter: P Mdada Hi Team, I get below error when ever i try to start jenkins services. Running from: /usr/share/jenkins/jenkins.war Nov 18, 2019 6:02:00 AM winstone.Logger logInternal INFO: Beginning extraction from war file Nov 18, 2019 6:02:01 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: jetty-winstone-2.9 Running from: /usr/share/jenkins/jenkins.war Nov 18, 2019 6:08:51 AM winstone.Logger logInternal INFO: Beginning extraction from war file Nov 18, 2019 6:08:52 AM org.eclipse.jetty.util.log.JavaUtilLog info INFO: jetty-winstone-2.9 after this it's not moving further. Add Comment
[JIRA] (JENKINS-60192) Unable to start Jenkins service. After INFO: jetty-winstone-2.9.
Title: Message Title P Mdada updated an issue Jenkins / JENKINS-60192 Unable to start Jenkins service. After INFO: jetty-winstone-2.9. Change By: P Mdada Priority: Blocker Minor 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.203161.1574059881000.2324.1574059920348%40Atlassian.JIRA.
[JIRA] (JENKINS-60192) Unable to start Jenkins service. After INFO: jetty-winstone-2.9.
Title: Message Title P Mdada updated an issue Jenkins / JENKINS-60192 Unable to start Jenkins service. After INFO: jetty-winstone-2.9. Change By: P Mdada Priority: Minor Blocker 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.203161.1574059881000.2323.1574059920332%40Atlassian.JIRA.
[JIRA] (JENKINS-59498) ItemsContent should be optimized and selected by default
Title: Message Title Allan BURDAJEWICZ updated JENKINS-59498 Jenkins / JENKINS-59498 ItemsContent should be optimized and selected by default Change By: Allan BURDAJEWICZ 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.202117.1569295137000.2311.1574038860208%40Atlassian.JIRA.
[JIRA] (JENKINS-60158) ConversionException: Refusing to unmarshal log for security reasons EnvironmentVarSetter
Title: Message Title Damian Szczepanik commented on JENKINS-60158 Re: ConversionException: Refusing to unmarshal log for security reasons EnvironmentVarSetter Problem has been already fixed by dependency upgrade but logs might be visible because you have first upgraded the Jenkins, then library 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.203024.1573655768000.2305.1574028300161%40Atlassian.JIRA.
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title Mark Waite commented on JENKINS-56569 Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set I think that JENKINS-47531 (dedicated LFS credentials) is less and less relevant to Jenkins users. I'm in favor of making the "Git LFS Pull" option truly mean that LFS is enabled. WIthout it, LFS would be disabled. That makes a very clear distinction between LFS pull enabled and disabled for a job. However, René Scheibe, wouldn't that mean being incompatible with users that explicitly enabled LFS with the configuration file settings that you mentioned? 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.198184.1552593939000.2302.1574025060215%40Atlassian.JIRA.
[JIRA] (JENKINS-60116) Overall/Administer permission required to configure jobs
Title: Message Title Daniel Kjellin updated an issue Jenkins / JENKINS-60116 Overall/Administer permission required to configure jobs Change By: Daniel Kjellin Released As: 1.0.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.202963.1573262524000.2297.1574024820521%40Atlassian.JIRA.
[JIRA] (JENKINS-60116) Overall/Administer permission required to configure jobs
Title: Message Title Daniel Kjellin updated JENKINS-60116 Jenkins / JENKINS-60116 Overall/Administer permission required to configure jobs Change By: Daniel Kjellin Status: Fixed but Unreleased 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.202963.1573262524000.2300.1574024820597%40Atlassian.JIRA.
[JIRA] (JENKINS-60191) Migrate Audit Trail documentation to Github
Title: Message Title Pierre Beitz updated JENKINS-60191 Jenkins / JENKINS-60191 Migrate Audit Trail documentation to Github Change By: Pierre Beitz 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.203158.1574023152000.2293.1574023380183%40Atlassian.JIRA.
[JIRA] (JENKINS-60191) Migrate Audit Trail documentation to Github
Title: Message Title Pierre Beitz updated JENKINS-60191 Jenkins / JENKINS-60191 Migrate Audit Trail documentation to Github Change By: Pierre Beitz 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.203158.1574023152000.2294.1574023380228%40Atlassian.JIRA.
[JIRA] (JENKINS-60191) Migrate Audit Trail documentation to Github
Title: Message Title Pierre Beitz created an issue Jenkins / JENKINS-60191 Migrate Audit Trail documentation to Github Issue Type: Task Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2019-11-17 20:39 Priority: Minor Reporter: Pierre Beitz 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
[JIRA] (JENKINS-59943) Issue while uploading android apk to app center
Title: Message Title Mez Pahlan commented on JENKINS-59943 Re: Issue while uploading android apk to app center Will close this due to inactivity. I can confirm that with the correct API key the correct permissions are available to upload APKs. 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.202747.1572095551000.2283.1574015820281%40Atlassian.JIRA.
[JIRA] (JENKINS-59943) Issue while uploading android apk to app center
Title: Message Title Mez Pahlan closed an issue as Not A Defect Jenkins / JENKINS-59943 Issue while uploading android apk to app center Change By: Mez Pahlan Status: Open Closed Resolution: Not A Defect 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.202747.1572095551000.2285.1574015820314%40Atlassian.JIRA.
[JIRA] (JENKINS-59943) Issue while uploading android apk to app center
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-59943 Issue while uploading android apk to app center Change By: Mez Pahlan Priority: Blocker Trivial 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.202747.1572095551000.2281.1574015760307%40Atlassian.JIRA.
[JIRA] (JENKINS-59792) Update README for AppCenter
Title: Message Title Mez Pahlan commented on JENKINS-59792 Re: Update README for AppCenter Hi Abel Berhane thanks for starting this. I agree that the README should be updated but I think some of these changes are better done elsewhere. > 1) Removed the release notes from upcoming functionality since its been released I think this is fine, we can take this one forward. > 2) Added a breakdown of what the Plugin can currently do I don't want to constantly remember to update the README when updating functionality. The changes are already in the change log and a "basic" upload is catered for in the README. That's as far as I want to go with it (specifically) in the README. > 3) Added a breakdown of what the Plugin is expecting you to fill out and some helpful hints. I think this is good but, again, better suited elsewhere. We already have JENKINS-59377 that looks to cater for this in the appropriate places. I'll make the same comment on the PR. 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.202522.1571157542000.2279.1574013960234%40Atlassian.JIRA.
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title
René Scheibe edited a comment on JENKINS-56569
Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set
Regarding this point: René Scheibe [~renescheibe] {quote}If the remote server requires authentication and none is configured on the system (e.g. ssh key), the checkout fails.{quote} Florian Klink [~flokli] {quote}Shouldn't then the clone itself fail, too? Normal ssh clone setups nowadays execute `git-lfs-authenticate` to obtain http urls and authentication, even when purely cloning over ssh. Once you're able to clone, resolving LFS pointers should work too.{quote}In the git-client-plugin it's implemented that the following steps are performed # {{git fetch}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L563]) # {{git checkout}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2681]) # in case of a specified "Git LFS pull after checkout" behaviour also {{git lfs pull}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2693])If credentials are specified by the user they are only provided for {{git fetch}} and {{git lfs pull}}.Therefore if {{git-lfs filter-process}} is triggered automatically via {{git checkout}} the checkout fails because the credentials are not provided here.If one really wants to go the other direction to never use {{GIT_LFS_SKIP_SMUDGE}} as described in JENKINS-59139 than the checkout should at least always be performed with providing the credentials. But JENKINS-47531 (to provide dedicated LFS credentials) is then still not covered. What's your opinion on this [~markewaite]?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title
René Scheibe updated an issue
Jenkins / JENKINS-56569
Prevent automatic pulling of lfs files if no GitLFSPull option is set
Change By:
René Scheibe
Depending on the used method to install git on a system, git lfs is enabled per default on a system via these settings in the system-wide config file:{code:java}[filter "lfs"]clean = git-lfs clean -- %fsmudge = git-lfs smudge -- %fprocess = git-lfs filter-processrequired = true{code}This means that even if no "git lfs pull" is performed explicitly, on checkout lfs files are pulled automatically due to the smudge filter.Problems # If the remote server requires authentication and none is configured - on the system - on a Jenkins agent (e.g. ssh key in \{{~/.ssh/}} ), the checkout fails. # If lfs files shall not be pulled at all, there is no way to configure this in the plugin.I therefore suggest to always set the environment variable {{GIT_LFS_SKIP_SMUDGE=1}} even if no "GitLFSPull" option was specified. This makes sure that no "git lfs" commands that are not controlled by the git-client-plugin are launched and thus resolves the issue that the checkout fails in case the remote server requires authentication. This also prevents pulling lfs files regardless of a system's configuration and requires to explicitly pull lfs files via the "GitLFSPull" option.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title
René Scheibe edited a comment on JENKINS-56569
Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set
Regarding this point:René Scheibe{quote}If the remote server requires authentication and none is configured on the system (e.g. ssh key), the checkout fails.{quote}Florian Klink{quote}Shouldn't then the clone itself fail, too? Normal ssh clone setups nowadays execute `git-lfs-authenticate` to obtain http urls and authentication, even when purely cloning over ssh. Once you're able to clone, resolving LFS pointers should work too.{quote}In the git-client-plugin it's implemented that the following steps are performed # {{git fetch}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L563]) # {{git checkout}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2681]) # in case of a specified "Git LFS pull after checkout" behaviour also {{git lfs pull}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2693])If credentials are specified by the user they are only provided for {{git fetch}} and {{git lfs pull}}.Therefore if {{git-lfs filter-process}} is triggered automatically via {{git checkout}} the checkout fails because the credentials are not provided here.If one really wants to go the other direction to never use {{GIT_LFS_SKIP_SMUDGE}} as described in JENKINS-59139 than the checkout should at least always be performed with providing the credentials. But JENKINS-47531 (to provide dedicated LFS credentials) is then still not covered. What's your opinion on this [~markewaite]?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title
René Scheibe edited a comment on JENKINS-56569
Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set
Regarding this point:René Scheibe{quote}If the remote server requires authentication and none is configured on the system (e.g. ssh key), the checkout fails.{quote}Florian Klink{quote}Shouldn't then the clone itself fail, too? Normal ssh clone setups nowadays execute `git-lfs-authenticate` to obtain http urls and authentication, even when purely cloning over ssh. Once you're able to clone, resolving LFS pointers should work too.{quote}In the git-client-plugin it's implemented that the following steps are performed # {{git fetch}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L563]) # {{git checkout}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2681]) # in case of a specified "Git LFS pull after checkout" behaviour also {{git lfs pull}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2693])If credentials are specified by the user they are only provided for {{git fetch}} and {{git lfs pull}}.Therefore if {{git-lfs filter-process}} is triggered automatically via {{git checkout}} the checkout fails because the credentials are not provided here.If one really want's wants to go the other direction to never use {{GIT_LFS_SKIP_SMUDGE}} as described in JENKINS-59139 than the checkout should at least always be performed with providing the credentials. What's your opinion on this [~markewaite]?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title
René Scheibe edited a comment on JENKINS-56569
Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set
Regarding this point:René Scheibe{quote}If the remote server requires authentication and none is configured on the system (e.g. ssh key), the checkout fails.{quote}Florian Klink{quote}Shouldn't then the clone itself fail, too? Normal ssh clone setups nowadays execute `git-lfs-authenticate` to obtain http urls and authentication, even when purely cloning over ssh. Once you're able to clone, resolving LFS pointers should work too.{quote}In the git-client-plugin it's implemented that the following steps are performed # {{git fetch}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L563]) # {{git checkout}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2681]) # in case of a specified "Git LFS pull after checkout" behaviour also {{git lfs pull}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2693])If credentials are specified by the user they are only provided for {{git fetch}} and {{git lfs pull}}. Therefore if {{git-lfs filter-process}} is triggered automatically via {{git checkout}} the checkout fails because the credentials are not provided here. If one really want's to go the other direction to never use {{GIT_LFS_SKIP_SMUDGE}} as described in JENKINS-59139 than the checkout should at least always be performed with providing the credentials. What's your opinion on this [~markewaite]?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title
René Scheibe edited a comment on JENKINS-56569
Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set
Regarding this point:René Scheibe{quote}If the remote server requires authentication and none is configured on the system (e.g. ssh key), the checkout fails.{quote}Florian Klink{quote}Shouldn't then the clone itself fail, too? Normal ssh clone setups nowadays execute `git-lfs-authenticate` to obtain http urls and authentication, even when purely cloning over ssh. Once you're able to clone, resolving LFS pointers should work too.{quote}In the git-client-plugin it's implemented that first a the following steps are performed # {{git fetch}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L563]) and then a # {{git checkout}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2681]) is performed and # in case of a specified "Git LFS pull after checkout" behaviour also {{git lfs pull}} (see [here|https://github.com/jenkinsci/git-client-plugin/blob/git-client-3.0.0/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L2693]) .If credentials are specified by the user they are only provided for {{git fetch}} and {{git lfs pull}}. Therefore if {{git-lfs filter-process}} is triggered automatically via {{git checkout}} the checkout fails because the credentials are not provided here.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because
[JIRA] (JENKINS-56569) Prevent automatic pulling of lfs files if no GitLFSPull option is set
Title: Message Title René Scheibe commented on JENKINS-56569 Re: Prevent automatic pulling of lfs files if no GitLFSPull option is set Regarding this point: René Scheibe If the remote server requires authentication and none is configured on the system (e.g. ssh key), the checkout fails. Florian Klink Shouldn't then the clone itself fail, too? Normal ssh clone setups nowadays execute `git-lfs-authenticate` to obtain http urls and authentication, even when purely cloning over ssh. Once you're able to clone, resolving LFS pointers should work too. In the git-client-plugin it's implemented that first a git fetch (see here) and then a git checkout (see here) is performed and in case of a specified "Git LFS pull after checkout" behaviour also git lfs pull (see here). If credentials are specified by the user they are only provided for git fetch and git lfs pull. Therefore if git-lfs filter-process is triggered automatically via git checkout the checkout fails because the credentials are not provided here. 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
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Mez Pahlan updated JENKINS-59694 Jenkins / JENKINS-59694 When build step fails or get aborted upload is still tried Change By: Mez Pahlan Status: In Review 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.202393.1570520886000.2262.1574011260288%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Mez Pahlan updated JENKINS-59694 Jenkins / JENKINS-59694 When build step fails or get aborted upload is still tried Change By: Mez Pahlan 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.202393.1570520886000.2259.1574010600358%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Mez Pahlan commented on JENKINS-59694 Re: When build step fails or get aborted upload is still tried Finally got some time to look at this. Thanks for the prompts . We now exit early if we detect that the build result is worse or equal to FAILURE. This means the following will abort the execution of this plugin: FAILURE, NOT_BUILT, ABORTED. Hope this helps! 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.202393.1570520886000.2256.1574010300183%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Mez Pahlan started work on JENKINS-59694 Change By: Mez Pahlan 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.202393.1570520886000.2253.1574008320233%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-59694 When build step fails or get aborted upload is still tried Change By: Mez Pahlan 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.202393.1570520886000.2250.1574007660694%40Atlassian.JIRA.
[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!
Title: Message Title centic commented on JENKINS-55996 Re: jacoco: Error while reading the sourcefile! The error-message in the attached logs is different: "AccessDeniedException: /jenkins/jobs/revenueCycleApiService-trunk/builds/11/jacoco/sources/java/com/.svn/entries", maybe this is unrelated? Did some other user write to the directory before? 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.197412.1549469008000.2246.1574007600223%40Atlassian.JIRA.
[JIRA] (JENKINS-59879) yet-another-docker-0.1.4 docker cloud does not work with >= ssh-slaves-plugin-1.30.0
Title: Message Title Ivan Fernandez Calvo closed an issue as Cannot Reproduce Jenkins / JENKINS-59879 yet-another-docker-0.1.4 docker cloud does not work with >= ssh-slaves-plugin-1.30.0 Change By: Ivan Fernandez Calvo Status: In Progress Closed 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 https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202624.1571736369000.2235.1574000220309%40Atlassian.JIRA.
[JIRA] (JENKINS-60186) Unable to download configuration-as-code-plugin.hpi
Title: Message Title Ian Williams commented on JENKINS-60186 Re: Unable to download configuration-as-code-plugin.hpi This is what is actually there : https://updates.jenkins.io/2.190/latest/configuration-as-code.hpi. bad reference? 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.203149.1573830043000.2227.1573989600169%40Atlassian.JIRA.
[JIRA] (JENKINS-57263) Java java.lang.ClassNotFoundException on Jenkins Startup
Title: Message Title
René Scheibe edited a comment on JENKINS-57263
Re: Java java.lang.ClassNotFoundException on Jenkins Startup
Just for reference, the following line is related to JENKINS-36696 and not an error.{code:java}Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skippin skipping {code}
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.199028.1556648065000.2223.1573988280495%40Atlassian.JIRA.
[JIRA] (JENKINS-57263) Java java.lang.ClassNotFoundException on Jenkins Startup
Title: Message Title René Scheibe commented on JENKINS-57263 Re: Java java.lang.ClassNotFoundException on Jenkins Startup Just for reference, the following line is related to JENKINS-36696 and not an error. Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skippin 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.199028.1556648065000.2219.1573988280428%40Atlassian.JIRA.
