[JIRA] (JENKINS-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title
Keith Zantow edited a comment on JENKINS-37704
Re: REGRESSION: Karaoke mode is busted on master
[~tscherler] use the format in your PR title: {{ \ [FIX JENKINS-#]}}, it will automatically link changes back to the ticket
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Gurpreet Singh commented on JENKINS-32118 Re: Opening Robot Framework log failed For chrome we can use this plugin: Disable Content-Security-Policy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title Keith Zantow commented on JENKINS-37704 Re: REGRESSION: Karaoke mode is busted on master Thorsten Scherler use the format in your PR title: FIX JENKINS-#, it will automatically link changes back to the ticket Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37727) Multibranch pipeline project jobs are not deleted when branches are deleted
Title: Message Title Mark Waite edited a comment on JENKINS-37727 Re: Multibranch pipeline project jobs are not deleted when branches are deleted Thanks for catching that bug before release!The master branch adds command line git support for multi-branch pipelines, and makes command line git the default (just as command line git is the default in other cases). Unfortunately, the calling sequence which worked for JGit (fetch() followed by prune()) behaves better in JGit than CliGit. Changing the calling sequence to fetch_().prune().execute() fixes the issue for both JGit and CliGit).I was able to duplicate the problem as reported. It is included in my [bug verification docker instance|https://github.com/MarkEWaite/docker/blob/lts-with-plugins/ref/jobs/jenkins-bugs-multibranch-pipeline/config.xml] and references the [JENKINS-37727 branch of my jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37727].If I change the job definition from using the command line git implementation to use the jgit implementation, the jobs which correspond to deleted branches are removed, so long as the local branch extension is not enabled (create a branch for each build). If the local branch extension is enabled, or if I switch from jgit to the command line implementation, the jobs which correspond to deleted branches are not removed.I suspect there may be two problems here. # If the local branch extension is enabled, I suspect that the cache repository (used to extract the Jenkinsfile) performs a checkout to a named branch matching the target branch. That checkout of a named branch in the cache repository is necessary (to extract the Jenkinsfile), but it does not need to checkout as a named branch. It can use a detached head checkout.# Command line git branch pruning doesn't seem to be working in the cacheI marked this as critical, since users will not want to modify their multi-branch job definitions to use JGit, especially since there are authentication cases which command git can handle that JGit cannot.I've found what appears to be a [clean fix for the problem|https://github.com/MarkEWaite/git-plugin/pull/2]. I've not yet completed the testing, Unit test and still need integration test are both available to write a confirm the problem is fixed. The unit test could use some further work to show assure it tests both the problem CliGit and JGit implementations , but it seems sufficient that will need to resolve the issue, replaces a call to a deprecated method, and simplifies the code wait for another time . Add Comment
[JIRA] (JENKINS-37727) Multibranch pipeline project jobs are not deleted when branches are deleted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37727 Re: Multibranch pipeline project jobs are not deleted when branches are deleted Code changed in jenkins User: Mark Waite Path: src/main/java/jenkins/plugins/git/AbstractGitSCMSource.java src/test/java/jenkins/plugins/git/AbstractGitSCMSourceTest.java http://jenkins-ci.org/commit/git-plugin/0197c85c64807fa4f6acdab5c04c02bb36e33c42 Log: Prune during AbstractGitSCMSource fetch Need for separate prune is removed by switching from deprecated fetch() method to fetch_() method. [Fix JENKINS-37727] CliGit leaves deleted branches in multi-branch jobs Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37729) See/Add the octopus deploy output log in Jenkins log
Title: Message Title Brian Adriance commented on JENKINS-37729 Re: See/Add the octopus deploy output log in Jenkins log Great idea! Do you or your team want to submit a PR for this or are you asking for the feature? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32980) Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins
Title: Message Title Jonathan Rogers commented on JENKINS-32980 Re: Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins How is one supposed to use this? I tried "cert" with "@" and a file name containing a PEM-encoded certificate and received an error: '"---END CERTIFICATE" is not a valid option'. This seems to indicate a parsing problem. I also tried pasting the entire PEM-encoded certificate on the command line inside single quotes. I saw no errors related to the -cert option, but got the usual complaint about failing to validate the server's certificate. I tried supplying both the CA cert and the server's cert. After all this failed, I added the CA cert to the Java key store and everything worked without the -cert option. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32980) Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins
Title: Message Title Jonathan Rogers edited a comment on JENKINS-32980 Re: Make it easier to use JNLP slaves with self-signed TLS certificates on Jenkins How is one supposed to use this? I tried "-cert" with "@" and a file name containing a PEM-encoded certificate and received an error: ' "-END CERTIFICATE-" is not a valid option '. This seems to indicate a parsing problem. I also tried pasting the entire PEM-encoded certificate on the command line inside single quotes. I saw no errors related to the -cert option, but got the usual complaint about failing to validate the server's certificate. I tried supplying both the CA cert and the server's cert. After all this failed, I added the CA cert to the Java key store and everything worked without the -cert option. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) ComboBoxList text is unreadable due to Jenkins 2 style change
Title: Message Title Joseph Petersen commented on JENKINS-37549 Re: ComboBoxList text is unreadable due to Jenkins 2 style change Cheers oleg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) ComboBoxList text is unreadable due to Jenkins 2 style change
Title: Message Title Oleg Nenashev commented on JENKINS-37549 Re: ComboBoxList text is unreadable due to Jenkins 2 style change Joseph Petersen reclassified the issue to bug and added lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) ComboBoxList text is unreadable due to Jenkins 2 style change
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37549 ComboBoxList text is unreadable due to Jenkins 2 style change Change By: Oleg Nenashev Summary: Colors for ComboBoxList text is unreadable due to Jenkins 2 style change Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) Colors for ComboBoxList
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37549 Colors for ComboBoxList Change By: Oleg Nenashev Labels: 2.0 lts-candidate user-experience Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) Colors for ComboBoxList
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-37549 Colors for ComboBoxList Change By: Oleg Nenashev Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37709) Multijob crashes after update to jenkins 2.19
Title: Message Title Ryan Graham commented on JENKINS-37709 Re: Multijob crashes after update to jenkins 2.19 Is this the same as JENKINS-37453? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37609) A problem occurred while processing the request error thrown after creating the multi job with Build Step
Title: Message Title Ryan Graham commented on JENKINS-37609 Re: A problem occurred while processing the request error thrown after creating the multi job with Build Step Is this the same as JENKINS-37453? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37453) Execute Shell in Multijob project
Title: Message Title Ryan Graham commented on JENKINS-37453 Re: Execute Shell in Multijob project Downgrading to 1.21 worked for me as well. Thanks, Anders Larsen. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) Colors for ComboBoxList
Title: Message Title Joseph Petersen commented on JENKINS-37549 Re: Colors for ComboBoxList Possible backport for next LTS? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33374) Setup wizard not properly offering the restart button
Title: Message Title Oleg Nenashev commented on JENKINS-33374 Re: Setup wizard not properly offering the restart button The fix has been merged towards jenkins-2.20 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29956) Wipe out repository & force clone ignore's Windows directory junctions
Title: Message Title Oleg Nenashev resolved as Fixed The fix has been merged towards jenkins-2.20 Jenkins / JENKINS-29956 Wipe out repository & force clone ignore's Windows directory junctions Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-37360) Selecting "edit description" for View All shows the System Message HTML text and tags.
Title: Message Title Oleg Nenashev commented on JENKINS-37360 Re: Selecting "edit description" for View All shows the System Message HTML text and tags. The fix has been merged towards jenkins-2.20 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36748) Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException
Title: Message Title Oleg Nenashev commented on JENKINS-36748 Re: Jobs with syntactically incorrect config missing the cron spec for a trigger produces NullPointerException Additional fix has been merged towards jenkins-2.20 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37559) cannot abort shell scripts on 64-bit Solaris
Title: Message Title Oleg Nenashev updated JENKINS-37559 The fix has been merged towards jenkins-2.20 Jenkins / JENKINS-37559 cannot abort shell scripts on 64-bit Solaris Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-37549) Colors for ComboBoxList
Title: Message Title Oleg Nenashev commented on JENKINS-37549 Re: Colors for ComboBoxList The fix has been merged towards jenkins-2.20 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37616) Cloud.PROVISION is not a first class citizen permission
Title: Message Title Oleg Nenashev commented on JENKINS-37616 Re: Cloud.PROVISION is not a first class citizen permission The fix has been merged towards jenkins-2.20 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37559) cannot abort shell scripts on 64-bit Solaris
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37559 Re: cannot abort shell scripts on 64-bit Solaris Code changed in jenkins User: csiden Path: core/src/main/java/hudson/util/ProcessTree.java core/src/main/java/hudson/util/jna/GNUCLibrary.java http://jenkins-ci.org/commit/jenkins/0f364e3a554a1bc6cddbfe7740993b835cae010e Log: JENKINS-37559 cannot abort shell scripts on 64-bit Solaris (#2507) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) Colors for ComboBoxList
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37549 Colors for ComboBoxList Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37549) Colors for ComboBoxList
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37549 Re: Colors for ComboBoxList Code changed in jenkins User: Joseph Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/c505dec68516837a4ca90d9e5a373ecce93730ed Log: [FIXED JENKINS-37549] - Fixed background color for ComboBoxList (#2511) Hard to see anything with Gray background and White Text. Style is in line with Selects and other form inputs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37616) Cloud.PROVISION is not a first class citizen permission
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37616 Re: Cloud.PROVISION is not a first class citizen permission Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/slaves/Cloud.java core/src/main/resources/hudson/slaves/Messages.properties core/src/test/java/hudson/slaves/CloudTest.java http://jenkins-ci.org/commit/jenkins/11af7d0bc1031d8f8458cf7556a0c845b939 Log: [FIXED JENKINS-37616] Make Cloud.PROVISION independent from Jenkins.ADMINISTER (#2521) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37616) Cloud.PROVISION is not a first class citizen permission
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-37616 Cloud.PROVISION is not a first class citizen permission Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37727) Multibranch pipeline project jobs are not deleted when branches are deleted
Title: Message Title Mark Waite edited a comment on JENKINS-37727 Re: Multibranch pipeline project jobs are not deleted when branches are deleted Thanks for catching that bug before release!The master branch adds command line git support for multi-branch pipelines, and makes command line git the default (just as command line git is the default in other cases). Unfortunately, the calling sequence which worked for JGit (fetch() followed by prune()) behaves better in JGit than CliGit ) . Changing the calling sequence to fetch_().prune().execute() fixes the issue for both JGit and CliGit).I was able to duplicate the problem as reported. It is included in my [bug verification docker instance|https://github.com/MarkEWaite/docker/blob/lts-with-plugins/ref/jobs/jenkins-bugs-multibranch-pipeline/config.xml] and references the [JENKINS-37727 branch of my jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37727].If I change the job definition from using the command line git implementation to use the jgit implementation, the jobs which correspond to deleted branches are removed, so long as the local branch extension is not enabled (create a branch for each build). If the local branch extension is enabled, or if I switch from jgit to the command line implementation, the jobs which correspond to deleted branches are not removed.I suspect there may be two problems here. # If the local branch extension is enabled, I suspect that the cache repository (used to extract the Jenkinsfile) performs a checkout to a named branch matching the target branch. That checkout of a named branch in the cache repository is necessary (to extract the Jenkinsfile), but it does not need to checkout as a named branch. It can use a detached head checkout.# Command line git branch pruning doesn't seem to be working in the cacheI marked this as critical, since users will not want to modify their multi-branch job definitions to use JGit, especially since there are authentication cases which command git can handle that JGit cannot.I've found what appears to be a [clean fix for the problem|https://github.com/MarkEWaite/git-plugin/pull/2]. I've not yet completed the testing, and still need to write a unit test to show the problem, but it seems sufficient to resolve the issue, replaces a call to a deprecated method, and simplifies the code. Add Comment
[JIRA] (JENKINS-37727) Multibranch pipeline project jobs are not deleted when branches are deleted
Title: Message Title Mark Waite edited a comment on JENKINS-37727 Re: Multibranch pipeline project jobs are not deleted when branches are deleted Thanks for catching that bug before release!The master branch adds command line git support for multi-branch pipelines, and makes command line git the default (just as command line git is the default in other cases). Unfortunately, it appears there may be some implicit dependency on the calling sequence which worked for JGit behavior (fetch() followed by prune()) behaves better in JGit than CliGit). Changing the AbstractGitSCMSource or GitSCMSource implementation which causes branches calling sequence to remain even though they were deleted from fetch_().prune().execute() fixes the remote repository issue for both JGit and CliGit) .I was able to duplicate the problem as reported. It is included in my [bug verification docker instance|https://github.com/MarkEWaite/docker/blob/lts-with-plugins/ref/jobs/jenkins-bugs-multibranch-pipeline/config.xml] and references the [JENKINS-37727 branch of my jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37727].If I change the job definition from using the command line git implementation to use the jgit implementation, the jobs which correspond to deleted branches are removed, so long as the local branch extension is not enabled (create a branch for each build). If the local branch extension is enabled, or if I switch from jgit to the command line implementation, the jobs which correspond to deleted branches are not removed.I suspect there may be two problems here. # If the local branch extension is enabled, I suspect that the cache repository (used to extract the Jenkinsfile) performs a checkout to a named branch matching the target branch. That checkout of a named branch in the cache repository is necessary (to extract the Jenkinsfile), but it does not need to checkout as a named branch. It can use a detached head checkout.# Command line git branch pruning doesn't seem to be working in the cacheI marked this as critical, since users will not want to modify their multi-branch job definitions to use JGit, especially since there are authentication cases which command git can handle that JGit cannot.I've found what appears to be a [clean fix for the problem|https://github.com/MarkEWaite/git-plugin/pull/2]. I've not yet completed the testing, and still need to write a unit test to show the problem, but it seems sufficient to resolve the issue, replaces a call to a deprecated method, and simplifies the code. Add Comment
[JIRA] (JENKINS-35184) Failed to load jenkins.util.SystemProperties on slaves due to ServletContext
Title: Message Title Oleg Nenashev commented on JENKINS-35184 Re: Failed to load jenkins.util.SystemProperties on slaves due to ServletContext CC Andrew Bayer. Likely the plugin does not shade this API... Or not. Maybe we need a fix in the core in order to make the implementation more robust Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37649) Build the plugin using JDK8, there are three warnings errors
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-37649 Build the plugin using JDK8, there are three warnings errors Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37649) Build the plugin using JDK8, there are three warnings errors
Title: Message Title Baptiste Mathus commented on JENKINS-37649 Re: Build the plugin using JDK8, there are three warnings errors I suppose the second "JDK8" is a typo, and you meant JDK7? Also, I would obviously welcome a PR on such subject. Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35184) Failed to load jenkins.util.SystemProperties on slaves due to ServletContext
Title: Message Title David Resnick commented on JENKINS-35184 Re: Failed to load jenkins.util.SystemProperties on slaves due to ServletContext The impact of this bug is that Jenkins 2.x doesn't work with the JClouds plugin, which provisions slaves on CloudStack. This is blocking our upgrade to Jenkins 2.x. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35258) [Gitlab plugin] ci-skip and author should use the latest commit, not the first one from the push event
Title: Message Title Vladimir Sitnikov commented on JENKINS-35258 Re: [Gitlab plugin] ci-skip and author should use the latest commit, not the first one from the push event Wonderful. Will check. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37704) REGRESSION: Karaoke mode is busted on master
Title: Message Title Thorsten Scherler commented on JENKINS-37704 Re: REGRESSION: Karaoke mode is busted on master Keith Zantow https://github.com/jenkinsci/blueocean-plugin/pull/437 we used to link the other way around. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37727) Multibranch pipeline project jobs are not deleted when branches are deleted
Title: Message Title Mark Waite edited a comment on JENKINS-37727 Re: Multibranch pipeline project jobs are not deleted when branches are deleted Thanks for catching that bug before release!The master branch adds command line git support for multi-branch pipelines, and makes command line git the default (just as command line git is the default in other cases). Unfortunately, it appears there may be some implicit dependency on JGit behavior in the AbstractGitSCMSource or GitSCMSource implementation which causes branches to remain even though they were deleted from the remote repository.I was able to duplicate the problem as reported. It is included in my [bug verification docker instance|https://github.com/MarkEWaite/docker/blob/lts-with-plugins/ref/jobs/jenkins-bugs-multibranch-pipeline/config.xml] and references the [JENKINS-37727 branch of my jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37727].If I change the job definition from using the command line git implementation to use the jgit implementation, the jobs which correspond to deleted branches are removed, so long as the local branch extension is not enabled (create a branch for each build). If the local branch extension is enabled, or if I switch from jgit to the command line implementation, the jobs which correspond to deleted branches are not removed.I suspect there may be two problems here. # If the local branch extension is enabled, I suspect that the cache repository (used to extract the Jenkinsfile) performs a checkout to a named branch matching the target branch. That checkout of a named branch in the cache repository is necessary (to extract the Jenkinsfile), but it does not need to checkout as a named branch. It can use a detached head checkout.# Command line git branch pruning doesn't seem to be working in the cacheI marked this as critical, since users will not want to modify their multi-branch job definitions to use JGit, especially since there are authentication cases which command git can handle that JGit cannot. I've found what appears to be a [clean fix for the problem|https://github.com/MarkEWaite/git-plugin/pull/2]. I've not yet completed the testing, and still need to write a unit test to show the problem, but it seems sufficient to resolve the issue, replaces a call to a deprecated method, and simplifies the code. Add Comment
[JIRA] (JENKINS-37727) Jobs of a multibranch pipeline project are not deleted when branches are deleted
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37727 Jobs of a multibranch pipeline project are not deleted when branches are deleted Change By: Mark Waite Summary: Jobs of a multibranch pipeline project are not deleted when branch is branches are deleted Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37727) Multibranch pipeline project jobs are not deleted when branches are deleted
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37727 Multibranch pipeline project jobs are not deleted when branches are deleted Change By: Mark Waite Summary: Jobs of a multibranch Multibranch pipeline project jobs are not deleted when branches are deleted Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33373) Rebuild open Merge Request
Title: Message Title Robin Müller commented on JENKINS-33373 Re: Rebuild open Merge Request Is this still an issue with the latest version of the plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34640) Jenkins job does not trigger on gitlab merge request
Title: Message Title Robin Müller closed an issue as Fixed Closing this due to no reaction of the reporter to the last question for a while. Please reopen if the issue still exists. Jenkins / JENKINS-34640 Jenkins job does not trigger on gitlab merge request Change By: Robin Müller Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Robin Müller resolved as Fixed Fixed in version 1.3.1. Jenkins / JENKINS-36863 [Gitlab plugin] Credentials drop-down doesn't show API token credential! Change By: Robin Müller Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35258) [Gitlab plugin] ci-skip and author should use the latest commit, not the first one from the push event
Title: Message Title Robin Müller resolved as Fixed Fixed in version 1.3.1. Jenkins / JENKINS-35258 [Gitlab plugin] ci-skip and author should use the latest commit, not the first one from the push event Change By: Robin Müller Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36882) Gitlab integration - Double job execution
Title: Message Title Robin Müller commented on JENKINS-36882 Re: Gitlab integration - Double job execution Could you please configure a logger for the gitlab-plugin as descibed here and post its output for a double job execution here. With the log we should be able to say if the gitlab-plugin causes the double job execution or if something else in your Jenkins setup is responsible for this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37727) Jobs of a multibranch pipeline project are not deleted when branch is deleted
Title: Message Title Mark Waite edited a comment on JENKINS-37727 Re: Jobs of a multibranch pipeline project are not deleted when branch is deleted Thanks for catching that bug before release!The master branch adds command line git support for multi-branch pipelines, and makes command line git the default (just as command line git is the default in other cases). Unfortunately, it appears there may be some implicit dependency on JGit behavior in the AbstractGitSCMSource or GitSCMSource implementation which causes branches to remain even though they were deleted from the remote repository.I was able to duplicate the problem as reported. It is included in my [bug verification docker instance|https://github.com/MarkEWaite/docker/blob/lts-with-plugins/ref/jobs/jenkins-bugs-multibranch-pipeline/config.xml] and references the [JENKINS-37727 branch of my jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37727].If I change the job definition from using the command line git implementation to use the jgit implementation, the jobs which correspond to deleted branches are removed , so long as the local branch extension is not enabled (create a branch for each build) . If the local branch extension is enabled, or if I switch from jgit to the command line implementation, the jobs which correspond to deleted branches are not removed.I suspect there may be two problems here. # If the local branch extension is enabled, I suspect that the cache repository (used to extract the Jenkinsfile) performs a checkout to a named branch matching the target branch. That checkout of a named branch in the cache repository is necessary (to extract the Jenkinsfile), but it does not need to checkout as a named branch. It can use a detached head checkout.# Command line git branch pruning doesn't seem to be working in the cacheI marked this as critical, since users will not want to modify their multi-branch job definitions to use JGit, especially since there are authentication cases which command git can handle that JGit cannot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37737) Intermittent login failures with Active Directory / Matrix-based security
Title: Message Title Derek Sakauye created an issue Jenkins / JENKINS-37737 Intermittent login failures with Active Directory / Matrix-based security Issue Type: Bug Assignee: Derek Sakauye Components: active-directory-plugin Created: 2016/Aug/27 3:06 PM Environment: Jenkins ver. 1.653. Active Directory Plugin 1.47 (Windows AD, Matrix-based security) Windows Server 2012 R2 Chrome Labels: login authentication Priority: Major Reporter: Derek Sakauye Helllo! We are experiencing intermittent login issues since early August, 2016 for all users from any browser or workstation (location does not seem to be an issue). We have a cross domain - VPN tunnel, which has not experienced recent outages to cause failed logons or AD lookups. Other systems relying on the VPN tunnel are not experiencing authentication issues. Successful manual telnet tests between the Domain Controllers were successful during Jenkins failed logins. We are not ruling out a network issue but we can't see any problems. We have not recently upgraded Jenkins or the Active Directory Plugin. Looking forward to any help to resolve our issue. Output from log: Aug 27, 2016 7:11:51 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser WARNING: Credential exception trying to authenticate against ### domain org.acegisecurity.BadCredentialsException: Failed to retrieve user information for ##; nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: DomainDnsZones. [Root exception is
[JIRA] (JENKINS-37727) Jobs of a multibranch pipeline project are not deleted when branch is deleted
Title: Message Title Mark Waite edited a comment on JENKINS-37727 Re: Jobs of a multibranch pipeline project are not deleted when branch is deleted Thanks for catching that bug before release!The master branch adds command line git support for multi-branch pipelines, and makes command line git the default (just as command line git is the default in other cases). Unfortunately, it appears there may be some implicit dependency on JGit behavior in the AbstractGitSCMSource or GitSCMSource implementation which causes branches to remain even though they were deleted from the remote repository. I was able to duplicate the problem as reported. It is included in my [bug verification docker instance|https://github.com/MarkEWaite/docker/blob/lts-with-plugins/ref/jobs/jenkins-bugs-multibranch-pipeline/config.xml] and references the [JENKINS-37727 branch of my jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37727].If I change the job definition from using the command line git implementation to use the jgit implementation, the jobs which correspond to deleted branches are removed. If I switch from jgit to the command line implementation, the jobs which correspond to deleted branches are not removed.I marked this as critical, since users will not want to modify their multi-branch job definitions to use JGit, especially since there are authentication cases which command git can handle that JGit cannot. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-37727) Jobs of a multibranch pipeline project are not deleted when branch is deleted
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37727 Jobs of a multibranch pipeline project are not deleted when branch is deleted Change By: Mark Waite Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37727) Jobs of a multibranch pipeline project are not deleted when branch is deleted
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37727 Jobs of a multibranch pipeline project are not deleted when branch is deleted Change By: Mark Waite Summary: Jobs of a multibranch pipeline project are not anymore deleted in upstream if "/" in when branch name is deleted Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30298) Gitlab plugin doesn't start build automatically on request from gitlab server
Title: Message Title Robin Müller closed an issue as Cannot Reproduce Closing this as there was no answer from the reporter to the last question for a while. Please reopen if the Problem still exists. Jenkins / JENKINS-30298 Gitlab plugin doesn't start build automatically on request from gitlab server Change By: Robin Müller Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-34284) Web hook http://JENKINS_URL/project/PROJECT_NAME fails
Title: Message Title Robin Müller commented on JENKINS-34284 Re: Web hook http://JENKINS_URL/project/PROJECT_NAME fails From the stacktrace I'd say you had configured the option to update the GitLab commit status but you hadn't configured a GitLab connection in the global Jenkins settings. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34396) Gitlab plugin does not work with jenkins pipeline plugin
Title: Message Title Robin Müller resolved as Fixed Since version 1.3.0 support for mutlibranch pipelines is implemented. Jenkins / JENKINS-34396 Gitlab plugin does not work with jenkins pipeline plugin Change By: Robin Müller Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-34442) Wrong URL in diff
Title: Message Title Robin Müller closed an issue as Not A Defect The gitlab-plugin doesn't provide any diff URL this is done by the git-plugin. You have to select the correct Repository Browser in your git configuration to get the correct URL. Jenkins / JENKINS-34442 Wrong URL in diff Change By: Robin Müller Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-29285) Getting error CreateProcess error=206, The filename or extension is too long when tried to build maven project
Title: Message Title Ronald Carl commented on JENKINS-29285 Re: Getting error CreateProcess error=206, The filename or extension is too long when tried to build maven project You can use Long Path Tool for such issue of process error-206 and also it reduce the problem of long filename or extension.It really works well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37727) Jobs of a multibranch pipeline project are not anymore deleted in upstream if "/" in branch name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37727 Jobs of a multibranch pipeline project are not anymore deleted in upstream if "/" in branch name Change By: Mark Waite Summary: Jobs of a multibranch pipeline project are not anymore deleted in upstream if "/" in branch name Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37736) $class-less syntax doesn't work as expected for build steps with no-args ctor
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-37736 $class-less syntax doesn't work as expected for build steps with no-args ctor Issue Type: Improvement Assignee: Jesse Glick Components: pipeline Created: 2016/Aug/27 10:43 AM Priority: Minor Reporter: Christopher Orr Possibly working-as-intended / could be (somehow?) fixed by me in my plugin implementation, but thought I'd mention it… I upgraded Android Lint to use the @Symbol annotation (which is an excellent feature!), and it has been working great. However, the class that this applies to, LintPublisher, has a no-args @DataBoundConstructor — if no other parameters are specified, a default file pattern is used. So I saw that while "androidLint pattern: '**/foo.xml'" works fine, the no-args variant "androidLint" does not work at all, as Pipeline looks for a global binding with that name: groovy.lang.MissingPropertyException: No such property: androidLint for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:24) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:3) at ___cps.transform___(Native Method) I discovered that in order to get the default behaviour, I have
[JIRA] (JENKINS-37735) Aligning the check box in login page
Title: Message Title Lakshitha Madushan created an issue Jenkins / JENKINS-37735 Aligning the check box in login page Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Aug/27 8:46 AM Environment: ubuntu 16.04 x64 Google Chrome Priority: Trivial Reporter: Lakshitha Madushan the "Remember me on this computer" check box is on the login page is not aligned. It will looks good if it will aligned. It just looks strange. Add Comment
[JIRA] (JENKINS-32148) highlight test result lines on hover
Title: Message Title Lakshitha Madushan assigned an issue to Unassigned Jenkins / JENKINS-32148 highlight test result lines on hover Change By: Lakshitha Madushan Assignee: Lakshitha Madushan Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37634) Generate Sauce Support Zip fails in Pipeline
Title: Message Title Gavin Mogan commented on JENKINS-37634 Re: Generate Sauce Support Zip fails in Pipeline I can't reproduce it. Do you know what ACL you are using? Can you run println(Jenkins.getInstance().getAuthorizationStrategy()) println(User.current()) In the groovy console? Ideally I'd like to know what permissions you have, especially per project Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
